Re: back button loses cart
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31001
interpreted = N
texte = >Ken: > >On a related note: I'm another person who's had IE weirdness.Everyone has seen IE 'weirdness, that's the nature of IE -- but if you don't understand the real cause of the problem, you can finds yourself wasting time trying to solve the problem improperly, and never getting the results you would like to see. >I've done this already: adding [random] x 3 tags to links and >no caching headers to the page.Did you add 'real' no-cache HTTP headers? Or did you simply use
no-cache tags in the page? >But that hasn't stopped caching totally when using the back button.Nothing stops the Back button from doing what it is supposed to do, except for properly-formatted no-cache HTTP headers, which will force the previous page to be reloaded from the server instead of from the browser cache. >The >back button is the bugger: Since it's navigation without a link involved, >so I can't specify the random tags and thus uniqueness, and the browser >merely backs up to page.tpl&aa=654, with 654 being an example of the >result from the 3 random tags.That's exactly what the back button is supposed to do. >It pulls this page from cache and shows >the raw webdna tags in place without data.Well then, the page you're going Back to was never served by webcatalog in the first place!!! IT is impossible for the browser to display interpreted webdna tags, so you have other problems to deal with here ... >I presume this is because it's showing the page out of cache > and it's not being interpreted via Webcat.No, it's because the page you're going Back to was never interpreted by webcatalog in the first place. Did you look at the full URL to make sure it begins with http:// and not file:// ?Because the fact of the matter is that if you have webcatalog properly configured on the server -- to serve the pages your visitors are retrieving -- then it is impossible for the visitor to see raw webdna tags in those pages, provided webcatalog is running properly *and* provided that you have not misused the [raw] context in the webdna code in your templates.Look, this is how it works:1- WebCatalog interprets webdna tags and contexts on the server.2- WebCatalog renders the dynamic html page on the server. At this point there are NO raw (uninterpreted) webdna tags left, they are all 'consumed' as they are interpreted by webcatalog, leaving the resulting file completely bare of all webdna language tags.3- WebCatalog sends that page (with no webdna tags in it) to the web server software.4- The web server software then serves it to the browser.5- The browser stores the page in its cache, to be available via the Back button as soon as the next page is loaded.In other words, if you *EVER* see raw (uninterpreted) webdna tags in your browser, it is never the browser's fault, it is always the result of one of three possible situations:1- You are viewing the page via file:// instead of http:// (common newbee error).2- The page you are viewing was never processed by webcatalog on the server (improper server configuration).3- You used a [raw] context improperly in the webdna template the page comes from (bad webdna coding technique). ================================ 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:
>Ken: > >On a related note: I'm another person who's had IE weirdness.Everyone has seen IE 'weirdness, that's the nature of IE -- but if you don't understand the real cause of the problem, you can finds yourself wasting time trying to solve the problem improperly, and never getting the results you would like to see. >I've done this already: adding [random] x 3 tags to links and >no caching headers to the page.Did you add 'real' no-cache HTTP headers? Or did you simply use no-cache tags in the page? >But that hasn't stopped caching totally when using the back button.Nothing stops the Back button from doing what it is supposed to do, except for properly-formatted no-cache HTTP headers, which will force the previous page to be reloaded from the server instead of from the browser cache. >The >back button is the bugger: Since it's navigation without a link involved, >so I can't specify the random tags and thus uniqueness, and the browser >merely backs up to page.tpl&aa=654, with 654 being an example of the >result from the 3 random tags.That's exactly what the back button is supposed to do. >It pulls this page from cache and shows >the raw webdna tags in place without data.Well then, the page you're going Back to was never served by webcatalog in the first place!!! IT is impossible for the browser to display interpreted webdna tags, so you have other problems to deal with here ... >I presume this is because it's showing the page out of cache > and it's not being interpreted via Webcat.No, it's because the page you're going Back to was never interpreted by webcatalog in the first place. Did you look at the full URL to make sure it begins with http:// and not file:// ?Because the fact of the matter is that if you have webcatalog properly configured on the server -- to serve the pages your visitors are retrieving -- then it is impossible for the visitor to see raw webdna tags in those pages, provided webcatalog is running properly *and* provided that you have not misused the [raw] context in the webdna code in your templates.Look, this is how it works:1- WebCatalog interprets webdna tags and contexts on the server.2- WebCatalog renders the dynamic html page on the server. At this point there are NO raw (uninterpreted) webdna tags left, they are all 'consumed' as they are interpreted by webcatalog, leaving the resulting file completely bare of all webdna language tags.3- WebCatalog sends that page (with no webdna tags in it) to the web server software.4- The web server software then serves it to the browser.5- The browser stores the page in its cache, to be available via the Back button as soon as the next page is loaded.In other words, if you *EVER* see raw (uninterpreted) webdna tags in your browser, it is never the browser's fault, it is always the result of one of three possible situations:1- You are viewing the page via file:// instead of http:// (common newbee error).2- The page you are viewing was never processed by webcatalog on the server (improper server configuration).3- You used a [raw] context improperly in the webdna template the page comes from (bad webdna coding technique). ================================ 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:
Wanted: More Math Functions (or, Can You Solve This?) (1997)
WebCat2: Items xx to xx shown, etc. (1997)
Img in goodpath (2001)
Webten + Webcat running smooth (1998)
New index for docs (1997)
US Postal Service API (2007)
Math function in Formula.db (1997)
Trouble with Netscape (1998)
Cold Fusion Buster (1997)
Can't add a field (1998)
OOPS [Was: OH CRAP!!!!!- Template not found error!!! ] (1999)
Size limit for tmpl editor ? (1997)
WebCommerce: Folder organization ? (1997)
Nested tags count question (1997)
WebDNA Solutions ... sorry! (1997)
shell problems again... (2003)
Weird problems with [SHOWIF]s (1997)
Plain Language Manual? (1998)
Can anyone help me with this shipping thing? (1998)
[lookup] speed sales pitch (2003)