Re: Dealing with da back button

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 24728
interpreted = N
texte = One of the things I find most annoying, is when you forget to fill in a fiedls of a form and you are asked to go back to fill it in and then you have to start filling in the whole form again.To avoid this, on the back button [referrer], I pass all of the values from the form back to the form page and if they are not empty, I put them into the form field. That way, only the forgotten info will have to be re-entered.About cookies, one cannot use [getcookie] and [setcookie] on the same page if they are for the same cookie, ie. one cannot set a cookie at the top of the page and try to get it at the bottom of the page, but one can set one cookie while getting a different cookie on the same page.ie. get user_id cookie and set session_id cookie.D.> Just curious, how are you setting the cookie to expire? My site > allows visitors to return to check on the status of their order, so I > want that cookie expired before then. But, I'd like to have it not > expire, if say, they want to surf somewhere else during that browser > session and come back and finish their order... > > Will>After someone finishes their order I usually set the cookie equal to the >value clear or null whatever, some value that is not a cart. Then >whenever I get to the point where I set a cookie I only set the cookie if >either the cookie sent by their browser is equal to clear or equal to >nothing (the case when they've never visited the site). In other words use >[getcookie] to check for a valid cart, if it is not valid use [setcookie] >to >set a cookie. I try to wrap all this logic into an include file which I can >just include at the top of all pages. The only trick to remember is that >you >can not use [getcookie] and [setcookie] on the same page. >-JoshRe: Dealing with da back button -- David Bastedo New Media AuthorMacLaren McCann Interactive david.bastedo@maclaren.com http://www.maclareninteractive.com 416.594.6779http://www.maclaren.com/interactive http://www.bastedo.com ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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: Dealing with da back button (David Bastedo 1999)
  2. Re: Dealing with da back button (Josh Tiger 1999)
  3. Re: Dealing with da back button (Will Starck 1999)
  4. Re: Dealing with da back button (Josh Tiger 1999)
One of the things I find most annoying, is when you forget to fill in a fiedls of a form and you are asked to go back to fill it in and then you have to start filling in the whole form again.To avoid this, on the back button [referrer], I pass all of the values from the form back to the form page and if they are not empty, I put them into the form field. That way, only the forgotten info will have to be re-entered.About cookies, one cannot use [getcookie] and [setcookie] on the same page if they are for the same cookie, ie. one cannot set a cookie at the top of the page and try to get it at the bottom of the page, but one can set one cookie while getting a different cookie on the same page.ie. get user_id cookie and set session_id cookie.D.> Just curious, how are you setting the cookie to expire? My site > allows visitors to return to check on the status of their order, so I > want that cookie expired before then. But, I'd like to have it not > expire, if say, they want to surf somewhere else during that browser > session and come back and finish their order... > > Will>After someone finishes their order I usually set the cookie equal to the >value clear or null whatever, some value that is not a cart. Then >whenever I get to the point where I set a cookie I only set the cookie if >either the cookie sent by their browser is equal to clear or equal to >nothing (the case when they've never visited the site). In other words use >[getcookie] to check for a valid cart, if it is not valid use [setcookie] >to >set a cookie. I try to wrap all this logic into an include file which I can >just include at the top of all pages. The only trick to remember is that >you >can not use [getcookie] and [setcookie] on the same page. >-JoshRe: Dealing with da back button -- David Bastedo New Media AuthorMacLaren McCann Interactive david.bastedo@maclaren.com http://www.maclareninteractive.com 416.594.6779http://www.maclaren.com/interactive http://www.bastedo.com ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 David Bastedo

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:

Associative lookup style? (1997) Some Questions (1997) No luck with taxes (1997) Part Html part WebDNA (1997) Hiding HTML and page breaks (1997) WebCat2 several catalogs? (1997) RE: error count with $purchase (1997) Accepting credit cards (1997) Help! WebCat2 bug (1997) Problem displaying search result (1997) WebCat2.0 [format thousands .0f] no go (1997) Caching [include] files ... (1997) Closing db's & caching templates (was: Shippingcalculations) (1997) Tax and Shipping Examples (1997) WC2b15 File Corruption (1997) NetSplat and WebCat2 (1997) WC1.6 to WC2 date formatting -FIXED! (1997) WebCatalog for guestbook ? (1997) I forgot (1998) Searchable list archive (1997)