Re: [WebDNA] fastcgi 7+ & [cart]?

This WebDNA talk-list message is from

2010

It keeps the original formatting. numero = 105491
interpreted = N
texte = On Jul 6, 2010, at 9:55, Kenneth Grome wrote:> Is there some new feature or new capability or bug fix introduced in =v7.0 that encourages you to want to use it on your old v6.2 commerce =sites? If so, what is this new feature or bug fix that you simply =cannot live without?>=20> I ask this question because we already learned that in v7.0 the =[thisurl] tag no longer works like it has always worked before, and this =was discovered by accident not by WSC reporting the change to us in =advance. =20>=20> So what will we do if we find that other changes in v7.0 end up =breaking our existing v6.2 sites? Are we just going to bitch and =complain about it?the new behaviour of the [thisurl] tag has not been planned: it must be =a collateral. We can change it back to its original behaviour. Here the =situation:The [thisurl] tag in v6.x produces this:/x/y/z/index.dnaBut the [thisurl] tag in v7.0 produces this:/x/y/z/index.dna?a=3Db&c=3DdIn my opinion, the new behaviour could be a "plus" when we have to =recover variables and it is pretty easy to strip the extra data out with =a small function, this is why i would be inclined towards keeping the =new behaviour. For instance, and if needed, it will make possible to use =the "back" button from the browser, or not -your choice- while the older =behaviour does not.> Or are we going to face the fact that none of our existing sites =should be moved to v7.0 UNLESS we are willing to figure out how to make =them work ourselves -- WITHOUT bugging WSC for answers on how to get =them working on this new version?>=20> Seems to me that with WSC's limited resources we should not be wasting =them by pestering Chris asking him how we can get our old sites running =on v7.0, especially when he has essentially told us not to bother -- =because v7.0 is a "new animal" and it is not supposed to be used to run =v6.x websites.Ken is right: the new policy of the company is to enlarge as much as =possible our WebDNA users base: thus the freeware which will be the main =version, the multiple webservers compatibility, multiple OS =compatibility, simplicity, small footprint, without being bogged down =with heavy applications like the SiteBuilder, or the Enterprise Edition =applications, or the very specific module version (only apache 2.2 =compatible) we had.We want WebDNA to be a light product with powerful capabilities, and =recover the purity and beauty of this language for a new start.- chris Associated Messages, from the most recent to the oldest:

On Jul 6, 2010, at 9:55, Kenneth Grome wrote:> Is there some new feature or new capability or bug fix introduced in =v7.0 that encourages you to want to use it on your old v6.2 commerce =sites? If so, what is this new feature or bug fix that you simply =cannot live without?>=20> I ask this question because we already learned that in v7.0 the =[thisurl] tag no longer works like it has always worked before, and this =was discovered by accident not by WSC reporting the change to us in =advance. =20>=20> So what will we do if we find that other changes in v7.0 end up =breaking our existing v6.2 sites? Are we just going to bitch and =complain about it?the new behaviour of the [thisurl] tag has not been planned: it must be =a collateral. We can change it back to its original behaviour. Here the =situation:The [thisurl] tag in v6.x produces this:/x/y/z/index.dnaBut the [thisurl] tag in v7.0 produces this:/x/y/z/index.dna?a=3Db&c=3DdIn my opinion, the new behaviour could be a "plus" when we have to =recover variables and it is pretty easy to strip the extra data out with =a small function, this is why i would be inclined towards keeping the =new behaviour. For instance, and if needed, it will make possible to use =the "back" button from the browser, or not -your choice- while the older =behaviour does not.> Or are we going to face the fact that none of our existing sites =should be moved to v7.0 UNLESS we are willing to figure out how to make =them work ourselves -- WITHOUT bugging WSC for answers on how to get =them working on this new version?>=20> Seems to me that with WSC's limited resources we should not be wasting =them by pestering Chris asking him how we can get our old sites running =on v7.0, especially when he has essentially told us not to bother -- =because v7.0 is a "new animal" and it is not supposed to be used to run =v6.x websites.Ken is right: the new policy of the company is to enlarge as much as =possible our WebDNA users base: thus the freeware which will be the main =version, the multiple webservers compatibility, multiple OS =compatibility, simplicity, small footprint, without being bogged down =with heavy applications like the SiteBuilder, or the Enterprise Edition =applications, or the very specific module version (only apache 2.2 =compatible) we had.We want WebDNA to be a light product with powerful capabilities, and =recover the purity and beauty of this language for a new start.- chris christophe.billiottet@webdna.us

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

WebDNA 4.5 not starting on boot? (2002) How to Display text in empty fields (1997) tab deliminated txt file (2001) Searching multiple fields from one form field (1997) Alternating colors (1997) Bill To - Ship To Information display (1997) (2000) Upgrade to web DNA6.0 (2004) WebCat2: multiple currency support (1997) (OT) Support system (2000) slightly OT: advertising schemes (2004) Applescript, WebDNA, and PDF (1997) searching multiple databases in single search (1997) Is there a way......... (2000) Next (1997) wow (1998) [WebDNA] Math Precision Preshmilson (2019) Misc Stuff That Might Help (1997) a new bug? (1999) advanced sorting (2001)