Re: back button loses cart

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 31034
interpreted = N
texte = > And that fact (and the example headers posted by others in the >archives) is the reason I put the meta no-cache tag in. But.. the problem >with the backup button preceded that and is the reason I did the searches >in the first place. > >Regardless I'll pull it out first thing (ie...when I'm back in the office >at an admin station). But I don't think that's the cause of this issue.The meta tag causes me to not be able to go back to a completed form via Netscape, which *properly* does NOT cache the page when meta no-cache tags are used. Getting rid of the no cache tags will fix this in Netscape. >Other suggestions, thoughts? What puzzles me is why are the tags >properly interpreted in the first place, but then lost when using th back >button.Someone just said that it's probably not *ALL* your webdna tags that are not being interpreted, instead it's probably only a few or all of the ecommerce tags that are not getting interpreted.So what's the real story here? Are ALL webdna tags uninterpreted, or not?Try putting a [thisurl] tag in the template at the very bottom of the page. If it gets interpreted every time, then this issue has nothing to do with improper server configuration, and everything to do with problems in the webdna code in your templates. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Associated Messages, from the most recent to the oldest:

    
  1. Re: back button loses cart (update for ken) (John Reginald Harris Jr 2000)
  2. Re[2]: back button loses cart (jpeacock@univpress.com 2000)
  3. Re: back button loses cart (John Butler 2000)
  4. Re: back button loses cart (John Reginald Harris Jr 2000)
  5. Re: back button loses cart (Kenneth Grome 2000)
  6. Re: back button loses cart (John Reginald Harris Jr 2000)
  7. Re: back button loses cart (Kenneth Grome 2000)
  8. Re: back button loses cart (John Butler 2000)
  9. Re: back button loses cart - ON SECURE PAGES ONLY (John Butler 2000)
  10. Re: back button loses cart (Kenneth Grome 2000)
  11. Re: back button loses cart (John Butler 2000)
  12. Re: back button loses cart (John Butler 2000)
  13. Re: back button loses cart (John Reginald Harris Jr 2000)
  14. Re: back button loses cart - (error in text) (Kenneth Grome 2000)
  15. Re: back button loses cart (Kenneth Grome 2000)
  16. Re: back button loses cart (John Reginald Harris Jr 2000)
  17. Re: back button loses cart (Glenn Busbin 2000)
  18. Re: back button loses cart (tech 2000)
  19. Re: back button loses cart (Kenneth Grome 2000)
  20. Re: back button loses cart (Kenneth Grome 2000)
  21. back button loses cart (John Butler 2000)
> And that fact (and the example headers posted by others in the >archives) is the reason I put the meta no-cache tag in. But.. the problem >with the backup button preceded that and is the reason I did the searches >in the first place. > >Regardless I'll pull it out first thing (ie...when I'm back in the office >at an admin station). But I don't think that's the cause of this issue.The meta tag causes me to not be able to go back to a completed form via Netscape, which *properly* does NOT cache the page when meta no-cache tags are used. Getting rid of the no cache tags will fix this in Netscape. >Other suggestions, thoughts? What puzzles me is why are the tags >properly interpreted in the first place, but then lost when using th back >button.Someone just said that it's probably not *ALL* your webdna tags that are not being interpreted, instead it's probably only a few or all of the ecommerce tags that are not getting interpreted.So what's the real story here? Are ALL webdna tags uninterpreted, or not?Try putting a [thisurl] tag in the template at the very bottom of the page. If it gets interpreted every time, then this issue has nothing to do with improper server configuration, and everything to do with problems in the webdna code in your templates. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Kenneth Grome

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:

2 Questions (2001) Progress !! WAS: Trouble with formula.db (1997) upgrade problem with users.db (1998) Bug or syntax error on my part? (1997) Re[3]: 2nd WebCatalog2 Feature Request (1996) [showif] results returned... (2003) Unix Timestamp using WebDNA [code req] (2003) Summing fields (1997) multiple db's (2003) [WebDNA] WebDNA glitch, no response required ... (2009) Search all Fields in a db (1997) Processing stops (2006) RE: Can a database get stomped by simultaneous access? (1997) A Global Variable (1997) [addlineitems] display (1997) sort problems....bug or brain fart? (1997) PSC recommends what date format yr 2000??? (1997) Running _every_ page through WebCat ? (1997) Format 1.15 to 1:15:00 or 01:15:00 (2002) Request for help on a new *automated* WebCatalog function ... (1998)