Re: Shopping Cart Best Practices
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 67188
interpreted = N
texte = One tradeoff is that you lose the security that a saved cart/order provides. One benefit is that you can quickly review orders and subtotals from dbs and you can name your own fields. You also lose the date issue that can arise in an order context. I couldn't think of much else. Bill -----Original Message----- From: Clint Davis
Sent: Fri, 12 May 2006 07:09:18 -0500 To: "WebDNA Talk" Subject: Shopping Cart Best Practices In building a new store from the ground up, I'm coming across some limitations with the default WebDNA shopping cart functionality. I'm thinking of ignoring the whole WebDNA orderfile system and storing everything in databases from start to finish - lineitems, billing/shipping addresses, etc. Anyone have pros/cons to share for this approach? ------------------------------------------------------------- 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://webdna.smithmicro.com/ ------------------------------------------------------------- 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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
One tradeoff is that you lose the security that a saved cart/order provides. One benefit is that you can quickly review orders and subtotals from dbs and you can name your own fields. You also lose the date issue that can arise in an order context. I couldn't think of much else. Bill -----Original Message----- From: Clint Davis Sent: Fri, 12 May 2006 07:09:18 -0500 To: "WebDNA Talk" Subject: Shopping Cart Best Practices In building a new store from the ground up, I'm coming across some limitations with the default WebDNA shopping cart functionality. I'm thinking of ignoring the whole WebDNA orderfile system and storing everything in databases from start to finish - lineitems, billing/shipping addresses, etc. Anyone have pros/cons to share for this approach? ------------------------------------------------------------- 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://webdna.smithmicro.com/ ------------------------------------------------------------- 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://webdna.smithmicro.com/
devaulw@onebox.com
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:
This Code Kills My WebCatalog Dead (2003)
Netscape v. IE (1997)
Email (1998)
Document Contains no data, or showcart error. (1997)
Email template names (1997)
ShowIf & HideIf Question? (1998)
WebCatalog can't find database (1997)
no shopping cart (2000)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
Sorting problem (2002)
Reindexing a db with duplicate numbers... (1999)
RAM variables (1997)
WebTen Memory Error with Plug-In (1998)
Doctype (2004)
webcatalog [date] bug (1999)
dbQuickView 2.0 (2005)
[WebDNA] OT: what is the "right" platform ? (2009)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
Deleting associated records from 2 different databases (2001)
[format 40s]text[/format] doesn't work (1997)