Hello, i am not sure is ir a bug or "by design" but i came into really awkward situations:
- If i set some pass rules in Joomla configuration it becomes a mess
- First of all VM allows users to register with passwords like 123 without any notice
- So in simplest case if shortest pass = 4 VM would allow registration with 123 but then user can not "SelfActivate" account because he bumps into 403 error
- In case password falls in the policy then SelfActivation works fine
- So had to minimize restriction not to fool customers
In the end really embarrassing, any solution for this? Misconfiguration on my Joomla/VM/Template side or a bug?
Thanks
VM does not use the joomla password rules..
I would never use any form of activation on an ecommerce site .. if they have got as far as adding to cart and checkout->reg get their money without requiring more pointless hurdles to jump...
Thanks GJC, would you still advice to use Registration to Checkout?
I tnik i have one small problem here, when i use Standard payment method, and user is first time buyer somehow he requested to Confirm payment, and confirm order once again, though i am in a Single page checkout.
I give them the opportunity to register but it depends on your business model -- if you have a lot of repeat sales then users IMHO like to register
The 2nd bit i don't understand...
I believe second one is a bit off topic, but maybe you can give me a hand here.
I have payment method Bank Transfer as "VM payment - standard" and somehow, sometimes, and i am not sure yet under witch circumstances if i fill all cart details and choose this Bank Transfer, then in the Cart instead of "Confirm Order" happens some "Confirm Payment" action, and then user need to confirm it again. Basically press same button twice.
Something isn't immediately validated .. there is a 2 stage VM checkout validation process .. has been for many years and was much discussed at the time..
Plenty of posts on here about the methodology etc
Quote from: NoOneLt on March 26, 2020, 10:12:25 AM
I believe second one is a bit off topic, but maybe you can give me a hand here.
I have payment method Bank Transfer as "VM payment - standard" and somehow, sometimes, and i am not sure yet under witch circumstances if i fill all cart details and choose this Bank Transfer, then in the Cart instead of "Confirm Order" happens some "Confirm Payment" action, and then user need to confirm it again. Basically press same button twice.
Have you not a problme with ajax update?
In some old template you have to modify the javascript, because last changes in Vm 3.6
in vm3.6 are changes which disturb a cart layout?
Quote from: Milbo on April 22, 2020, 21:08:09 PM
in vm3.6 are changes which disturb a cart layout?
If you display 2 'confirmed' buttons, only first button is working because the javascript use the button ID.
I had another little problem, but don't remember me.
The shipment plugins from valerie need adjustment depending the Vm release.
I wrote a payment plugin for a client that needed some adjustment too(because javascript)
I had another problem because i needed a specific button render and task was always "updatecart".
All this problem was after update to VM3.6+ . sometime from VM 3.0, 3.2 or 3.4
Of course, all this is because all the templates use overrides.
Not that addCheckRequiredJs in the view.html is bad for override, in my case i cannot use this line :
jQuery("#checkoutFormSubmit");
With 2 confirmation buttons
Note : that all this depend the Vm 3.6 release. Some is fixed, some not.
jQuery("#checkoutFormSubmit");
Lets use a class for it?