Re: Variables not being passed *back*
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 33841
interpreted = N
texte = Some browsers do not cache when they should... the best workaround is to make your forms submit to themselves and write custom code (or tweak someone elses - see archives) which does error checking on that same page and displays any problems if there are any... if there are no problems, then the page can silently redirect on to the next page (the page you really wanted the form submit to go to in the first place). Sorry to say this is going to be some work, but at this point it appears there is no better alternative. On the up side - once you manage this new type of technique, you can keep using it and no longer worry so much how well (or not) the latest browsers are handling caching.ask if something hear was not clear-JohnChristopher Mackay wrote:> Hi, > > My forms are now in pretty good shape, but not perfect. All data gets > carried through properly to the end as long as the customer makes no > mistakes. If they do, say they enter their Visa number incorrectly, > then hitting the back button in the browser resets all lineitems' > quantities to 1 (no matter what they were), and turns shiptostate > values, such as NB or NS, into [__shiptostate]. > > I've tried passing these values through the URL, thinking that might > make them less susceptible to being broken by the back button, but it > doesn't help. In fact, it makes it worse, so that it no longer works > even in the absence of user-error/back button use. > > There's something fundamental that I'm missing here... > -- > > Regards, > > Christopher Mackay, Multimedia Developer > Tantramar Interactive, http://www.tantramar.com/ > 506/364-1097 cell: 364-7659 fax: 536-2409 > ------------------------------------------------------------- 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 Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Some browsers do not cache when they should... the best workaround is to make your forms submit to themselves and write custom code (or tweak someone elses - see archives) which does error checking on that same page and displays any problems if there are any... if there are no problems, then the page can silently redirect on to the next page (the page you really wanted the form submit to go to in the first place). Sorry to say this is going to be some work, but at this point it appears there is no better alternative. On the up side - once you manage this new type of technique, you can keep using it and no longer worry so much how well (or not) the latest browsers are handling caching.ask if something hear was not clear-JohnChristopher Mackay wrote:> Hi, > > My forms are now in pretty good shape, but not perfect. All data gets > carried through properly to the end as long as the customer makes no > mistakes. If they do, say they enter their Visa number incorrectly, > then hitting the back button in the browser resets all lineitems' > quantities to 1 (no matter what they were), and turns shiptostate > values, such as NB or NS, into [__shiptostate]. > > I've tried passing these values through the URL, thinking that might > make them less susceptible to being broken by the back button, but it > doesn't help. In fact, it makes it worse, so that it no longer works > even in the absence of user-error/back button use. > > There's something fundamental that I'm missing here... > -- > > Regards, > > Christopher Mackay, Multimedia Developer > Tantramar Interactive, http://www.tantramar.com/ > 506/364-1097 cell: 364-7659 fax: 536-2409 > ------------------------------------------------------------- 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 Web Archive of this list is at: http://search.smithmicro.com/
John Butler
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:
Part 2 - [showif] if variable exists (1998)
OT - Friday afternoon Fun with Toys (2002)
Emailer Set Up (1997)
Running 2 two WebCatalog.acgi's (1996)
math on date? (1997)
Errata: WCS Newbie question (1997)
Superfilous Characters (1998)
Automatic [URL]ing by the webdna engine (2003)
Emailer Problem (1998)
form data submission gets truncated (1997)
WebCat Hosting (1998)
Problems with Price field (1997)
[sendmail] questions... (1997)
command line in webDNA 5?! (2003)
WebCat2b15MacPlugin - showing [math] (1997)
Mixing and/or in searches (1998)
OT: javascript help (2003)
Help w/Multi User Admins (1997)
multi-paragraph fields (1997)
Removing [showif] makes a big difference in speed (1997)