CRE Loaded Community

When a customer orders for a second time without creating an account gets the following error:

1062 - Duplicate entry 'email@mydomain.com' for key 2

insert into customers (purchased_without_account, customers_firstname, customers_lastname, customers_email_address, customers_telephone, customers_fax, customers_newsletter, customers_password, customers_dob) values ('1', '[firstname]', '[surname]', '[email address]', '[phpne number]', '', '', 'c419b06b4c6579b50ff05adb3b8424f1:bd', '19700521')

TEP_DB_ERRORR

Any suggestions?

customers_firstname You should not set this field to unique in customers table.

just chek the schema of your customer table and chek it with a fresh creloaded.

are You sure it stated key 2 for duplicate entry.

Satish Mantri

Thanks but this was resolved by Sherry just before she departed. Apparently it's designed that way to prevent people ordering twice without creating an account? (Doesn't sound right to me either.) In any event it was over-riden and is now working.

Benz1

I have this error too:

When a customer orders for a second time without creating an account gets the following error:

1062 - Duplicate entry 'email@mydomain.com' for key 2

This thread is about the same issue, no resolution is offered yet.
http://www.creloaded.com/forums/Forums/ ... tml#116386

onlinewebcommunities,
I have tried to reproduce the issue on our demos, QA sites and on my personal 6.3.3 fresh installs placing mulitle orders without creating an account. At no point during my testing did I receive any error about a duplicate email for a customer.

I am unsure about Sherry's investigation and what it turned-up, but I can assure you that there is no code logic or database configuration in our distribution that will cause a returning customer without an account to be rejected when placing a second order.

As the issue has been reported more than once, I would suspect an added third-party module is becoming involved. Can you report on any add-on module that may deal with customer handling or order handling? I am genuinely curious and want to see this symptom documented.

Thanks for looking at this VecDaddy,

I am using an almost stock version of CRE Loaded6 v6.2 B2B White Label[13.2 (SP1)]

The only third-party module I'm running is Quick Updates.

I have seen this problem on the same version without any mods.

The easiest way to recreate this is to create an account and remember the email address used.

Then delete your cookies, come in as a new person, "Proceed Directly to Checkout" without creating an account, then on the next page (Order_Info.php) use the same exact email address and that's all I need to crash the cart with the message:


Note, the only duplicate field that has been repeated is the email, I deliberately made up all the other field inputs to make sure that they are unique.

In the example you posted above, yes there logic to require a customer with an account matching the email to login when placing the order. However, it should not be producing a sql error. Rather, a defined error message from the language files should display on the screen.



I am going to continue to look into this and hopefully have either a solution or work-around shortly.

Thank you VecDaddy!

I have seen that same "Account already exists..." message before, and with the same system that is producing the SQL errors. This have occured in a time period between the SQL errors, indicating the system was not working, then broken, but vulnerable to a certain set of conditions.

The SQL error predominates and the "Account already..." message has only popped up rarely.

If there's anything I can do to help in troubleshooting, feel free to ask.

We have disabled the account creation, and force users to proceed to checkout. Orders seem to process just fine (atleast we have not had any customer complaints yet) however, every now-and-then the store emails the store owner with this error report:



This forum post looks very similar to the problem I am experiencing, and I wonder if anyone knows the work-a-round?

Thank You,

Joe