Personally, I have them become a user before check out and then have the
items in a shopping cart table based on their user id.
That way it saves their cart for later purchase if needed. Else they can
remove the items.
-Original Message-
From: Les Mizzell [mailto:[EMAIL PROTECTED]
I'm for storing them in a table. I suppose that if you wanted to allow
guest shopping, you could assign a temporary user id (some UUID) and store
it on their machine as a cookie, and then use that as a key in the cart
table. That's just a thought off the top of my head, so there could be some
I have done both. It really depends on what the client wants and the hosting
environment. I did one where the items were held in a temporary database
table with a UUID simply because the client wanted to make sure that the
customer could come back to their items if they either changed their minds
I use CF Webstore which stores shopping cart data in a database table. I
think this is more customer-friendly since average mortals don't want to be
troubled by session expiration.
-Original Message-
From: Les Mizzell [mailto:[EMAIL PROTECTED]
Sent: Monday, September 17, 2007 9:41 AM
What would the rest of you consider the optimal way to store items
before checking out?
One request that the client made was that you could have an account -
but that it be possible to shot/checkout *without* and account as well.
So, there's a sign in to retrieve your data before you
5 matches
Mail list logo
