Scottymo Posted December 5, 2013 Share Posted December 5, 2013 I get The following errors were detected: That email address is already being used. People should be able to check out as a guest even if they have been a customer or ghost customer. Right now, if a customer purchases something a month ago, for example, an account is automatically created for him. Then he comes back again a month later, but can't simply make a purchase as a guest and gets the warning about how his email address is already in use. He probably won't know his login (since it was automatically created on the first purchase) and would have to do the "forgot password" thing. I would like to have the guest checkout not require someone to log in, even if they were a previous customer or a ghost. I was hoping this would be changed in in the latest update V5.2.5, but it isn't. I was upgrading from CC V3, but I can't use V5 until this is fixed as it will deter many customers from purchasing. A guest checkout should not require a login, even if they are a previous customer. Is there a fix for this? is it in the works? Quote Link to comment Share on other sites More sharing options...
bsmither Posted December 5, 2013 Share Posted December 5, 2013 "Is there a fix for this? is it in the works?" Not yet. Very soon. Quote Link to comment Share on other sites More sharing options...
Scottymo Posted December 5, 2013 Author Share Posted December 5, 2013 Thanks bsmither, I hope so! Quote Link to comment Share on other sites More sharing options...
northwalesinks Posted December 10, 2013 Share Posted December 10, 2013 Good i am getting this message too Quote Link to comment Share on other sites More sharing options...
rosarymau Posted January 11, 2014 Share Posted January 11, 2014 Looking forward to a fix for this. Quote Link to comment Share on other sites More sharing options...
i.ahmed Posted April 26, 2015 Share Posted April 26, 2015 Do we know if this has been fixed? Quote Link to comment Share on other sites More sharing options...
bsmither Posted April 26, 2015 Share Posted April 26, 2015 I think it has. I think the problem carried forward to CC6 and has been fixed in that series, but I do not know if the fix has been applied to the CC5 series. Quote Link to comment Share on other sites More sharing options...
sailing123 Posted April 28, 2015 Share Posted April 28, 2015 This was an issue with our existing V4 as well and just upgrading to 6.0.4 for testing and I can confirm that the problem has been resolved.Fantastic !!!!Thank you :-) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.