possible bug with customers being given the same umbraco member Id?
Hi there, I may have come accross a bug when ucommerce is creating customers and relating them to umbraco members.
This is producing some unexpected results, especially when recalling last address and order after login using the xslt call CommerceLibrary:GetMemberOrderHistory('Paid') as its bringing the history for multiple members.
does uCommerce check to see whether an Umbraco member with that Id exists already?
uCommerce will match customers based on e-mail address. It will look for a member with the specified e-mail first, if a member is not found, it will look for a member with the e-mail address for login name, and finally if that's doesn't exist it will create a new member with the specifed e-mail for both login name and member e-mail.
Could you e-mail me specifics at ssl AT ucommerce DOT dk? Thanks.
possible bug with customers being given the same umbraco member Id?
Hi there, I may have come accross a bug when ucommerce is creating customers and relating them to umbraco members.
This is producing some unexpected results, especially when recalling last address and order after login using
the xslt call CommerceLibrary:GetMemberOrderHistory('Paid') as its bringing the history for multiple members.
does uCommerce check to see whether an Umbraco member with that Id exists already?
has anyone else come accross this?
uCommerce will match customers based on e-mail address. It will look for a member with the specified e-mail first, if a member is not found, it will look for a member with the e-mail address for login name, and finally if that's doesn't exist it will create a new member with the specifed e-mail for both login name and member e-mail.
Could you e-mail me specifics at ssl AT ucommerce DOT dk? Thanks.
I had an issue with this today. Seems orders have been falling over at the final stage. Checking in the umbraco log I found:
"Duplicate User name! A member with the user name [email protected] already exists..."
When I checked it, there was an 'empty' user created somehow (blank username and email). Once this was deleted the error was fixed.
Time for me to go back and check the form validator...
is working on a reply...