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

This WebDNA talk-list message is from

2010

It keeps the original formatting. numero = 105506
interpreted = N
texte = This is a multi-part message in MIME format.--------------070706000701020803080901Content-Type: text/plain; charset=windows-1252; format=flowedContent-Transfer-Encoding: 7bitpretty good answers.thanksjymKenneth Grome wrote:>> What does "The [purchase] tag is not deprecated >> though, but should not be operational" even mean?>> >> If you want to continue using the old commerce system that's been available since the PCS days (early 1990's) you should absolutely stick with version 6.2 or earlier -- that's the bottom line. >> Let me repeat this in another way:>> Do NOT use v7.x with your existing webdna sites if they use any of these legacy commerce tags or files:>> [addlineitem] > [clearlineitems]> [lineitems]> [orderfile]> [purchase]> [removelineitem]> [setheader]> [setlineitem] > formulas.db> cart/order files>> Just keep using v6.2 for backward compatibility with all your old commerce sites.>> Makes sense, right?>> Look ... if you want to use a modern new commerce system that's based on v7.0 or later you will simply have to wait a while for WSC (or someone else) to create this new commerce system -- because it does not yet exist.>> The fact is, creating a new commerce system that runs on databases and external template code will be a lot of work. I know because I did it more than a decade ago -- and I made it run on Typhoon which could open only one database -- and that was long before we had [function] capabilities! >> Yet after I accomplished this task I had a far more flexible commerce system than webdna could ever offer with its hard-coded built-in capabilities. And since I actually did this so many years ago (with such limited software) I know for a fact that it can be done again today, and far more easily given a multi-database and function capable webdna. But it's still a lot of work even today.>> Regardless of all that, let's just face the facts here:>> - The old commerce system is an inflexible relic of the 1990's that should have been replaced or upgraded a very long time ago, but it never was. >> - WSC is actually trying to upgrade and improve the webdna software, and unfortunately this is going to mean losing some backward compatibility. But fortunately WSC is thoughtful enough to continue to distribute v6.2 for those who insist upon using the original webdna commerce system.>> - WSC plans to remove the inflexible internally coded commerce functions, and just because that code still exists in v7.0 is no reason to assume that you should be moving your existing commerce sites to v7.0 -- because you should NOT!>> - WSC's decision to move commerce code to external templates and db files is going to make the FUTURE of webdna commerce unbelievably flexible and customizable ... and everyone wants to be able to customize their own systems, right?>> RIGHT???>> :)>> So here's the bottom line as I understand it:>> 1- You should continue using v6.2 or earlier if you require backward compatibility with the webdna commerce system that's been programmed into webdna since the 1990's.>> 2- A modern commerce system for v7.x is not yet available, and when it becomes available it is going to be based on external templates and databases to make it customizable by webdna users like us ... but we simply have to wait for WSC to build this new system unless we are willing to build it ourselves.>> Patience is a virtue ... :)>> So please don't waste time trying to figure out if your old commerce sites will run under v7.x because unless you do a lot of adjusting they won't. And yes the legacy commerce tags are still hard-coded in v7.0 ... but that doesn't mean you're supposed to try to use them! >> And it doesn't mean they will still be there in any future versions either ... so sooner or later you're going to have to get rid of your feeling that you have to upgrade to every new version that happens to come along.>> Maybe now is the time to realize that you do NOT have to upgrade your old sites to v7.0 ... ???>>> >> By now, anyone paying attention will likely be thinking of writing all>> future webdna shopping sites with their own db-based system.. instead>> of using the old shopping cart file system and the related e-commerce>> [contexts].. >> >> Good observation Govinda. But someone could take it upon him/herself to write such a system then sell it as an add-on to other webdna users, too.>> :)>>> >> but meanwhile we just want to know if all our old>> untouched shopping sites which did rely on those e-commerce>> *[contexts]* are going to break under webdna 7?>> >> Yes they will break *UNLESS* you do all these things and more:>> 1- create your own ShoppingCarts folder> 2- create your own Orders folders> 3- create your own formulas.db> 4- create other files/folders currently missing from the v7.0 folder hierarchy> 5- move your prefs over to the new webdna.ini file> 6- write a new [thisurl] function to override the v7.0 [thisurl] tag>> Why bother with all these changes (and probably more than I haven't even thought of) when Chris has already said that he is still going to distribute v6.2? After all, v6.2 is 100% compatible with the legacy commerce system, which means you do not have to make all kinds of changes to get it working!>> Here is the important question I have to ask:>> 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?>> 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. >> 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?>> 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?>> 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.>> Sincerely,> Kenneth Grome>>>> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us>> -- Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet - PrintPhone: (877) 443-1323 Email: jym@purposemedia.com Web: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725, Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025, Capistrano Beach, CA 92624--------------070706000701020803080901Content-Type: text/html; charset=windows-1252Content-Transfer-Encoding: quoted-printable pretty good answers.
thanks

jym

Kenneth Grome wrote:

What does "The [purchase] tag is not deprecated=20though, but should not be operational" even mean?

If you want to continue using the old commerce system that's been availab=le since the PCS days (early 1990's) you should absolutely stick with ver=sion 6.2 or earlier -- that's the bottom line. =20Let me repeat this in another way:Do NOT use v7.x with your existing webdna sites if they use any of these =legacy commerce tags or files:[addlineitem]=20[clearlineitems][lineitems][orderfile][purchase][removelineitem][setheader][setlineitem]=20formulas.dbcart/order filesJust keep using v6.2 for backward compatibility with all your old commerc=e sites.Makes sense, right?Look ... if you want to use a modern new commerce system that's based on =v7.0 or later you will simply have to wait a while for WSC (or someone el=se) to create this new commerce system -- because it does not yet exist.The fact is, creating a new commerce system that runs on databases and ex=ternal template code will be a lot of work.  I know because I did it more= than a decade ago -- and I made it run on Typhoon which could open only =one database -- and that was long before we had [function] capabilities! ==20Yet after I accomplished this task I had a far more flexible commerce sys=tem than webdna could ever offer with its hard-coded built-in capabilitie=s.  And since I actually did this so many years ago (with such limited so=ftware) I know for a fact that it can be done again today, and far more e=asily given a multi-database and function capable webdna.  But it's still= a lot of work even today.Regardless of all that, let's just face the facts here:- The old commerce system is an inflexible relic of the 1990's that shoul=d have been replaced or upgraded a very long time ago, but it never was. ==20- WSC is actually trying to upgrade and improve the webdna software, and =unfortunately this is going to mean losing some backward compatibility.  =But fortunately WSC is thoughtful enough to continue to distribute v6.2 f=or those who insist upon using the original webdna commerce system.- WSC plans to remove the inflexible internally coded commerce functions,= and just because that code still exists in v7.0 is no reason to assume t=hat you should be moving your existing commerce sites to v7.0 -- because =you should NOT!- WSC's decision to move commerce code to external templates and db files= is going to make the FUTURE of webdna commerce unbelievably flexible and= customizable ... and everyone wants to be able to customize their own sy=stems, right?RIGHT???:)So here's the bottom line as I understand it:1- You should continue using v6.2 or earlier if you require backward comp=atibility with the webdna commerce system that's been programmed into web=dna since the 1990's.2- A modern commerce system for v7.x is not yet available, and when it be=comes available it is going to be based on external templates and databas=es to make it customizable by webdna users like us ... but we simply have= to wait for WSC to build this new system unless we are willing to build =it ourselves.Patience is a virtue ... :)So please don't waste time trying to figure out if your old commerce site=s will run under v7.x because unless you do a lot of adjusting they won't=.  And yes the legacy commerce tags are still hard-coded in v7.0 ... but =that doesn't mean you're supposed to try to use them! =20And it doesn't mean they will still be there in any future versions eithe=r ... so sooner or later you're going to have to get rid of your feeling =that you have to upgrade to every new version that happens to come along.Maybe now is the time to realize that you do NOT have to upgrade your old= sites to v7.0 ... ???

By now, anyone paying attention will likely be thinkin=g of writing allfuture webdna shopping sites with their own db-based system.. insteadof using the old shopping cart file system and the related e-commerce[contexts]..=20

Good observation Govinda.  But someone could take it upon him/herself to =write such a system then sell it as an add-on to other webdna users, too.:)

but meanwhile we just want to know if all our olduntouched shopping sites which did rely on those e-commerce*[contexts]* are going to break under webdna 7?

Yes they will break *UNLESS* you do all these things and more:1- create your own ShoppingCarts folder2- create your own Orders folders3- create your own formulas.db4- create other files/folders currently missing from the v7.0 folder hier=archy5- move your prefs over to the new webdna.ini file6- write a new [thisurl] function to override the v7.0 [thisurl] tagWhy bother with all these changes (and probably more than I haven't even =thought of) when Chris has already said that he is still going to distrib=ute v6.2?  After all, v6.2 is 100% compatible with the legacy commerce sy=stem, which means you do not have to make all kinds of changes to get it =working!Here is the important question I have to ask: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 wi=thout?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 disco=vered by accident not by WSC reporting the change to us in advance. =20So 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 i=t?Or are we going to face the fact that none of our existing sites should b=e 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?Seems to me that with WSC's limited resources we should not be wasting th=em 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 web=sites.Sincerely,Kenneth Grome---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us

Jym Duane - CTO - Purpose Media

Creating Your Success Story

Marketing : Television - Internet - Print

Phone: (877) 443-1323=A0=A0

Email: jym@purposemedia.com=A0 =A0

Web: www.purposemedia.com

Oregon - www.GuideToOregon.com

PO Box 1725,=A0 Jacksonville,OR 97530

California - www.OrangeCounty.net

PO Box 2025,=A0 CapistranoBeach, CA 92624

--------------070706000701020803080901-- Associated Messages, from the most recent to the oldest:

This is a multi-part message in MIME format.--------------070706000701020803080901Content-Type: text/plain; charset=windows-1252; format=flowedContent-Transfer-Encoding: 7bitpretty good answers.thanksjymKenneth Grome wrote:>> What does "The [purchase] tag is not deprecated >> though, but should not be operational" even mean?>> >> If you want to continue using the old commerce system that's been available since the PCS days (early 1990's) you should absolutely stick with version 6.2 or earlier -- that's the bottom line. >> Let me repeat this in another way:>> Do NOT use v7.x with your existing webdna sites if they use any of these legacy commerce tags or files:>> [addlineitem] > [clearlineitems]> [lineitems]> [orderfile]> [purchase]> [removelineitem]> [setheader]> [setlineitem] > formulas.db> cart/order files>> Just keep using v6.2 for backward compatibility with all your old commerce sites.>> Makes sense, right?>> Look ... if you want to use a modern new commerce system that's based on v7.0 or later you will simply have to wait a while for WSC (or someone else) to create this new commerce system -- because it does not yet exist.>> The fact is, creating a new commerce system that runs on databases and external template code will be a lot of work. I know because I did it more than a decade ago -- and I made it run on Typhoon which could open only one database -- and that was long before we had [function] capabilities! >> Yet after I accomplished this task I had a far more flexible commerce system than webdna could ever offer with its hard-coded built-in capabilities. And since I actually did this so many years ago (with such limited software) I know for a fact that it can be done again today, and far more easily given a multi-database and function capable webdna. But it's still a lot of work even today.>> Regardless of all that, let's just face the facts here:>> - The old commerce system is an inflexible relic of the 1990's that should have been replaced or upgraded a very long time ago, but it never was. >> - WSC is actually trying to upgrade and improve the webdna software, and unfortunately this is going to mean losing some backward compatibility. But fortunately WSC is thoughtful enough to continue to distribute v6.2 for those who insist upon using the original webdna commerce system.>> - WSC plans to remove the inflexible internally coded commerce functions, and just because that code still exists in v7.0 is no reason to assume that you should be moving your existing commerce sites to v7.0 -- because you should NOT!>> - WSC's decision to move commerce code to external templates and db files is going to make the FUTURE of webdna commerce unbelievably flexible and customizable ... and everyone wants to be able to customize their own systems, right?>> RIGHT???>> :)>> So here's the bottom line as I understand it:>> 1- You should continue using v6.2 or earlier if you require backward compatibility with the webdna commerce system that's been programmed into webdna since the 1990's.>> 2- A modern commerce system for v7.x is not yet available, and when it becomes available it is going to be based on external templates and databases to make it customizable by webdna users like us ... but we simply have to wait for WSC to build this new system unless we are willing to build it ourselves.>> Patience is a virtue ... :)>> So please don't waste time trying to figure out if your old commerce sites will run under v7.x because unless you do a lot of adjusting they won't. And yes the legacy commerce tags are still hard-coded in v7.0 ... but that doesn't mean you're supposed to try to use them! >> And it doesn't mean they will still be there in any future versions either ... so sooner or later you're going to have to get rid of your feeling that you have to upgrade to every new version that happens to come along.>> Maybe now is the time to realize that you do NOT have to upgrade your old sites to v7.0 ... ???>>> >> By now, anyone paying attention will likely be thinking of writing all>> future webdna shopping sites with their own db-based system.. instead>> of using the old shopping cart file system and the related e-commerce>> [contexts].. >> >> Good observation Govinda. But someone could take it upon him/herself to write such a system then sell it as an add-on to other webdna users, too.>> :)>>> >> but meanwhile we just want to know if all our old>> untouched shopping sites which did rely on those e-commerce>> *[contexts]* are going to break under webdna 7?>> >> Yes they will break *UNLESS* you do all these things and more:>> 1- create your own ShoppingCarts folder> 2- create your own Orders folders> 3- create your own formulas.db> 4- create other files/folders currently missing from the v7.0 folder hierarchy> 5- move your prefs over to the new webdna.ini file> 6- write a new [thisurl] function to override the v7.0 [thisurl] tag>> Why bother with all these changes (and probably more than I haven't even thought of) when Chris has already said that he is still going to distribute v6.2? After all, v6.2 is 100% compatible with the legacy commerce system, which means you do not have to make all kinds of changes to get it working!>> Here is the important question I have to ask:>> 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?>> 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. >> 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?>> 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?>> 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.>> Sincerely,> Kenneth Grome>>>> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us>> -- Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet - PrintPhone: (877) 443-1323 Email: jym@purposemedia.com Web: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725, Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025, Capistrano Beach, CA 92624--------------070706000701020803080901Content-Type: text/html; charset=windows-1252Content-Transfer-Encoding: quoted-printable pretty good answers.
thanks

jym

Kenneth Grome wrote:

What does "The [purchase] tag is not deprecated=20though, but should not be operational" even mean?

If you want to continue using the old commerce system that's been availab=le since the PCS days (early 1990's) you should absolutely stick with ver=sion 6.2 or earlier -- that's the bottom line. =20Let me repeat this in another way:Do NOT use v7.x with your existing webdna sites if they use any of these =legacy commerce tags or files:[addlineitem]=20[clearlineitems][lineitems][orderfile][purchase][removelineitem][setheader][setlineitem]=20formulas.dbcart/order filesJust keep using v6.2 for backward compatibility with all your old commerc=e sites.Makes sense, right?Look ... if you want to use a modern new commerce system that's based on =v7.0 or later you will simply have to wait a while for WSC (or someone el=se) to create this new commerce system -- because it does not yet exist.The fact is, creating a new commerce system that runs on databases and ex=ternal template code will be a lot of work.  I know because I did it more= than a decade ago -- and I made it run on Typhoon which could open only =one database -- and that was long before we had [function] capabilities! ==20Yet after I accomplished this task I had a far more flexible commerce sys=tem than webdna could ever offer with its hard-coded built-in capabilitie=s.  And since I actually did this so many years ago (with such limited so=ftware) I know for a fact that it can be done again today, and far more e=asily given a multi-database and function capable webdna.  But it's still= a lot of work even today.Regardless of all that, let's just face the facts here:- The old commerce system is an inflexible relic of the 1990's that shoul=d have been replaced or upgraded a very long time ago, but it never was. ==20- WSC is actually trying to upgrade and improve the webdna software, and =unfortunately this is going to mean losing some backward compatibility.  =But fortunately WSC is thoughtful enough to continue to distribute v6.2 f=or those who insist upon using the original webdna commerce system.- WSC plans to remove the inflexible internally coded commerce functions,= and just because that code still exists in v7.0 is no reason to assume t=hat you should be moving your existing commerce sites to v7.0 -- because =you should NOT!- WSC's decision to move commerce code to external templates and db files= is going to make the FUTURE of webdna commerce unbelievably flexible and= customizable ... and everyone wants to be able to customize their own sy=stems, right?RIGHT???:)So here's the bottom line as I understand it:1- You should continue using v6.2 or earlier if you require backward comp=atibility with the webdna commerce system that's been programmed into web=dna since the 1990's.2- A modern commerce system for v7.x is not yet available, and when it be=comes available it is going to be based on external templates and databas=es to make it customizable by webdna users like us ... but we simply have= to wait for WSC to build this new system unless we are willing to build =it ourselves.Patience is a virtue ... :)So please don't waste time trying to figure out if your old commerce site=s will run under v7.x because unless you do a lot of adjusting they won't=.  And yes the legacy commerce tags are still hard-coded in v7.0 ... but =that doesn't mean you're supposed to try to use them! =20And it doesn't mean they will still be there in any future versions eithe=r ... so sooner or later you're going to have to get rid of your feeling =that you have to upgrade to every new version that happens to come along.Maybe now is the time to realize that you do NOT have to upgrade your old= sites to v7.0 ... ???

By now, anyone paying attention will likely be thinkin=g of writing allfuture webdna shopping sites with their own db-based system.. insteadof using the old shopping cart file system and the related e-commerce[contexts]..=20

Good observation Govinda.  But someone could take it upon him/herself to =write such a system then sell it as an add-on to other webdna users, too.:)

but meanwhile we just want to know if all our olduntouched shopping sites which did rely on those e-commerce*[contexts]* are going to break under webdna 7?

Yes they will break *UNLESS* you do all these things and more:1- create your own ShoppingCarts folder2- create your own Orders folders3- create your own formulas.db4- create other files/folders currently missing from the v7.0 folder hier=archy5- move your prefs over to the new webdna.ini file6- write a new [thisurl] function to override the v7.0 [thisurl] tagWhy bother with all these changes (and probably more than I haven't even =thought of) when Chris has already said that he is still going to distrib=ute v6.2?  After all, v6.2 is 100% compatible with the legacy commerce sy=stem, which means you do not have to make all kinds of changes to get it =working!Here is the important question I have to ask: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 wi=thout?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 disco=vered by accident not by WSC reporting the change to us in advance. =20So 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 i=t?Or are we going to face the fact that none of our existing sites should b=e 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?Seems to me that with WSC's limited resources we should not be wasting th=em 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 web=sites.Sincerely,Kenneth Grome---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list <talk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us>archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us