Re: Shopping carts and reloading pages

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 11783
interpreted = N
texte = >>If I have been following this thread correctly, a user who *does* return to >>the front door would mess up the shopping cart value. Is this correct? > >Yes they would get a new cart number. In general, any URL that does not >contain an explicit cart=xxx in it will cause a new cart# to be generated >in that page's [cart] tags. > >But sometimes you want that: when you are done shopping and have purchased >something, you need to go back to the front door and get a new cart if you >want to shop some more. The old one is waiting to be processed and is not >allowed to be used again.Makes sense, but there are going to be lots of times when you really *don't* want a new cart.Like all the times when I'm just being a navigation bozo.Even if you make it difficult to navigate back to that front door page within your own store pages - the browser go back options leave it easily accessable...> >An alternative would be to have your customers register with a >username/password which is then used as a lookup into a database for some >kind of permanent cart id. Then you'd protect every page in your site >with a forced username dialog so no matter how many times they reload or >jump into the middle, they'd get the same id.Great info - so there are ways to actually prevent the problem.ThanksStephanie Wright WebSTAR Tech Support StarNine/Quarterdeck Associated Messages, from the most recent to the oldest:

    
  1. Re: Shopping carts and reloading pages (Stephanie Wright 1997)
  2. Re: Shopping carts and reloading pages (Grant Hulbert 1997)
  3. Shopping carts and reloading pages (Stephanie Wright 1997)
>>If I have been following this thread correctly, a user who *does* return to >>the front door would mess up the shopping cart value. Is this correct? > >Yes they would get a new cart number. In general, any URL that does not >contain an explicit cart=xxx in it will cause a new cart# to be generated >in that page's [cart] tags. > >But sometimes you want that: when you are done shopping and have purchased >something, you need to go back to the front door and get a new cart if you >want to shop some more. The old one is waiting to be processed and is not >allowed to be used again.Makes sense, but there are going to be lots of times when you really *don't* want a new cart.Like all the times when I'm just being a navigation bozo.Even if you make it difficult to navigate back to that front door page within your own store pages - the browser go back options leave it easily accessable...> >An alternative would be to have your customers register with a >username/password which is then used as a lookup into a database for some >kind of permanent cart id. Then you'd protect every page in your site >with a forced username dialog so no matter how many times they reload or >jump into the middle, they'd get the same id.Great info - so there are ways to actually prevent the problem.ThanksStephanie Wright WebSTAR Tech Support StarNine/Quarterdeck Stephanie Wright

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:

showif errors (1998) Exclamation point (1997) Pull Down Search (2000) formula.db problem (1999) If Empty ? (1997) Personal Web Server (1998) Multiple Users.db Possible? (1997) problems with WebCat-Plugin (1997) NOT Search (1998) [input] [/input] (1997) New commands in Final candidate (1997) Is this possible, WebCat2.0 and checkboxes (1997) Error Log.db --however (1997) WebCat2final1 crashes (1997) [WebDNA] feature request - .hdr files (2011) AIM & SIM Issue (2001) State Coalition Approves Internet Sales Tax Plan (2002) Not really WebCat (1997) Digital Postcards (1999) timing out? (1997)