Posted - December 19 2005 : 09:25:23
| Does anyone know why the shopping cart would erratically create an additional customerid for a customer during checkout? (Further, this customerid has a blank password while the original customer ID has the password field filled with the correct data.)
Is the answer to the question impacted at all by the fact that I use an authorze.net gateway?
If this is a common issue, is there a way to prevent these new customers from being added, but rather to have the order connected to the original customerID?
This question is much more simple restatement of my topic:
Solution: The situation was caused by our session variables being dropped when we moved from some custom data entry forms we were using into shopaddtocart.asp. The following code, added to shopaddtocart.asp resolved our issue:
[main logic at top of shopcustomer.asp]. . .
if sError = "" Then
UpdateOrderInformation ' put in customer and order data
'[CUSTOMIZATION] In case we come from a custom form, the application 'seems to lose it's customerid session variable during the following 'sub UpdateCustomerSessionData. If session var exists, store in 'temporary variable and put back afterwards.
If Len(GetSess("CustomerId")) > 0 then
tempSessionCustromerID = GetSess("CustomerId")
If Len(tempSessionCustromerID) > 0 then
SetSess "CustomerId", tempSessionCustromerID
'[End of customization]
' End of main logic
Edited by - rapidlaw on January 27 2006 08:50:11