Re: [WebDNA] upgrading to 8.1 or 8.2?

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 112848
interpreted = N
texte = 431 Hi Ken, I don't use any WebDNA eCommerce tags. Everything I have that is ecommerce is written similar to the UPS integration you helped me with a while back. Thanks, Steve On 06/21/2016 04:05 PM, Kenneth Grome wrote: >> What WebDNA "commands" are you referring? > Commands are the original way of telling WebDNA to do something. > They are passed in URLs and forms. Here's an example: > > http://www.domain.com/page.dna?command=showcart > > Contexts replaced commands for most WebDNA users many years ago > because contexts are far more secure. But if your site still uses > commands they will not work in the FastCGI version, so you'd have > to (1) rewrite that part of your code to use contexts instead of > commands, or (2) use the Server version instead of the FastCGI > version. > > If I were you I would be far more concerned about the fact that > you're running an online store using legacy WebDNA eCommerce code > -- which will NOT work in the FastCGI version. I tried switching > another client's eCommerce site to the FastCGI version a long time > ago and it failed because the FastCGI version cannot interpret > WebDNA eCommerce tags/contexts. So instead I went with the latest > Server version and had no upgrade problems whatsoever. > > You're already using what is essentially an old Server version, so > if I were you I would just forget about the FastCGI version and > use the latest Server version. Then you're more or less > guaranteeing that the site will still work properly without > creating any more problems for yourself. > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration > --------------------------------------------------------- > 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 --------------------------------------------------------- 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 . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] upgrading to 8.1 or 8.2? (Kenneth Grome 2016)
  2. Re: [WebDNA] upgrading to 8.1 or 8.2? (WebDNA Steve Raslevich 2016)
  3. Re: [WebDNA] upgrading to 8.1 or 8.2? (WebDNA Steve Raslevich 2016)
  4. Re: [WebDNA] upgrading to 8.1 or 8.2? (Kenneth Grome 2016)
  5. Re: [WebDNA] upgrading to 8.1 or 8.2? (Matthew Perosi 2016)
  6. Re: [WebDNA] upgrading to 8.1 or 8.2? (WebDNA 2016)
  7. Re: [WebDNA] upgrading to 8.1 or 8.2? (WebDNA 2016)
  8. Re: [WebDNA] upgrading to 8.1 or 8.2? (Kenneth Grome 2016)
431 Hi Ken, I don't use any WebDNA eCommerce tags. Everything I have that is ecommerce is written similar to the UPS integration you helped me with a while back. Thanks, Steve On 06/21/2016 04:05 PM, Kenneth Grome wrote: >> What WebDNA "commands" are you referring? > Commands are the original way of telling WebDNA to do something. > They are passed in URLs and forms. Here's an example: > > http://www.domain.com/page.dna?command=showcart > > Contexts replaced commands for most WebDNA users many years ago > because contexts are far more secure. But if your site still uses > commands they will not work in the FastCGI version, so you'd have > to (1) rewrite that part of your code to use contexts instead of > commands, or (2) use the Server version instead of the FastCGI > version. > > If I were you I would be far more concerned about the fact that > you're running an online store using legacy WebDNA eCommerce code > -- which will NOT work in the FastCGI version. I tried switching > another client's eCommerce site to the FastCGI version a long time > ago and it failed because the FastCGI version cannot interpret > WebDNA eCommerce tags/contexts. So instead I went with the latest > Server version and had no upgrade problems whatsoever. > > You're already using what is essentially an old Server version, so > if I were you I would just forget about the FastCGI version and > use the latest Server version. Then you're more or less > guaranteeing that the site will still work properly without > creating any more problems for yourself. > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration > --------------------------------------------------------- > 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 --------------------------------------------------------- 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 . WebDNA Steve Raslevich

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:

WebCat2b12 - nesting [tags] (1997) Stopping bad HTML propagation ? (1997) Searching multiple records for certain info (2000) still having shipCost.db Problem (1997) Help!!!! (1997) [WebDNA] Searching Possible Bug (2009) carriage returns in data (1997) lookups (2000) WebCat2b12 - nesting [tags] (1997) Merchant and WebCat 3.0 (1998) Updating a database once per day - An example (1998) simple but wierd [shownext] behavior?? (2000) suggestion (1997) Moment of Thanks (1997) Linux -> OS X (2002) Running 2 two WebCatalog.acgi's (1996) stumped on simple sort (1999) Fun with Dates - revisited (1997) Extended [ConvertChars] (1997) how to determine the actual file format of an image file? (2002)