VirtueMart Forum

VirtueMart 2 + 3 + 4 => Virtuemart Development and bug reports => Topic started by: ermes on August 21, 2018, 21:16:34 PM

Title: Bug in registration process with OPC active
Post by: ermes on August 21, 2018, 21:16:34 PM
Hi forum, i work on last version of joomla and virtuemart (3.8.11 and 3.2.14). If i set as new users activation method "email" , when i add a product into the cart, on checkout page i insert my data and click on "register on checkout" i complete the checkout correctly but when i click on the link sent to me via email joomla said that the "Verification code not found.". I have googled and some users has same problem (but with other extensions that login the users before that they confirm the registration). Anyone with this problem?
Title: Re: Bug in registration process with OPC active
Post by: jenkinhill on August 21, 2018, 22:35:29 PM
Why require confirmation of registration? Almost guaranteed to put shopper off.  I rarely require registration on my sites.

However I just tested confirm by email registration for shopper and the link to register worked perfectly, no errors. I'm using J3.8.11 and VM3.2.15 and native OPC AJAX is enabled. Running under SSL.

I should point out that the shopper can still checkout without waiting to receive the email and to confirm, and the order goes through just fine as they are registered in VM - although not yet registered in Joomla.
Title: Re: Bug in registration process with OPC active
Post by: ermes on August 22, 2018, 09:43:23 AM
If i disable the email confirmation, it works correctly. Another thest to do (actually as my config) set homepage as redirect page after login. The store is multilang (ita and eng).
Title: Re: Bug in registration process with OPC active
Post by: GJC Web Design on August 22, 2018, 11:19:58 AM
see also http://forum.virtuemart.net/index.php?topic=140701.msg494971#msg494971

this might be what u mean
Title: Re: Bug in registration process with OPC active
Post by: ermes on August 27, 2018, 16:58:50 PM
Sorry GJC Web Design, but this is a huge bug. It will be fixed in future?