Re: Problems when user hit back
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 34522
interpreted = N
texte = Do you have an example of the code?-RodolfoEl 7/11/00 11:30 AM, Sam Lewis sam@samLewis.com escribió:>> The only way to safely deal with it is to design your site so that the >> user never wants to use the Back button. ;~( The issue is that when the >> user goes back, the browser resubmits the command to add the last line >> item. >> >> If you can guarantee that there will never be more than one line with >> a given SKU, you can write a small loop to check for duplicates and >> forbid the subsequent adds. This really only works well if you are >> using contexts to add to the cart, instead of commands. > > > I deal with it by adding a rn=[random] to all of my links. On the > shopping cart page I set a header to the rn value the first time > through. Then on subsequent hits to that page I check to see if rn > equals my header value if so then the user either hit reload or back > so I don't add the item to the cart again. For every hit to the cart > page that has a unique rn value I set my header to that value to > check on the next hit. ------------------------------------------------------------- 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:
Do you have an example of the code?-RodolfoEl 7/11/00 11:30 AM, Sam Lewis sam@samLewis.com escribió:>> The only way to safely deal with it is to design your site so that the >> user never wants to use the Back button. ;~( The issue is that when the >> user goes back, the browser resubmits the command to add the last line >> item. >> >> If you can guarantee that there will never be more than one line with >> a given SKU, you can write a small loop to check for duplicates and >> forbid the subsequent adds. This really only works well if you are >> using contexts to add to the cart, instead of commands. > > > I deal with it by adding a rn=[random] to all of my links. On the > shopping cart page I set a header to the rn value the first time > through. Then on subsequent hits to that page I check to see if rn > equals my header value if so then the user either hit reload or back > so I don't add the item to the cart again. For every hit to the cart > page that has a unique rn value I set my header to that value to > check on the next hit. ------------------------------------------------------------- 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/
Rodolfo de la Garza
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:
Online reference (1997)
Review comparison by PC Magazine: Open for On-line Business (1997)
WebCat2 beta 11 - new prefs ... (1997)
default image if image in code not available (2003)
UPDATE - Refusing connections issue ... (1999)
searchable list archive (1997)
Multiple prices (1997)
Is this possible, WebCat2.0 and checkboxes (1997)
TCPConnect (2002)
Introduction/Tutorial/QuickStart (1997)
updating with ProductEditor (1998)
[searchString] (1997)
Nitro plugin? (1998)
FAX orders (1996)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
WebCat B13 Mac CGI -- Frames question (1997)
Protect vs Authenicate (1997)
Pager notification of completed orders (1998)
WebCatalog2 Feature Feedback (1996)
NT or Mac (1998)