It does. It also has admin connectivity to your MySagePay which is why this is a commercial release ... and because it's commercial, that's about as much as I can say about it on the forums.
It does. It also has admin connectivity to your MySagePay which is why this is a commercial release ... and because it's commercial, that's about as much as I can say about it on the forums.
Development Manager @ JSWeb Ltd
Over 15 years with Zencart
I have bought the commercial version and get exactly the same problem with my store and with a clean Zen Cart 1.5.1 installation. The checkout button and everything below it is missing from the final page of checkout.
Why are you installing 1.51? What happens with 1.54? I will be testing next week with a clean install - do you get any error logs? I believe the php version also causes an issue
Also what response did jsweb give?
@micromouse
Turns out the reason it's failing for mbrogan is indeed a server configuration issue - it's missing PHP's MCRYPT module. Probably the same issue for the free version too.
Development Manager @ JSWeb Ltd
Over 15 years with Zencart
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
I've got it running on one of the live servers - Mcrypt was missing from out test server, I just need to wait for the protocol warning to filter down to sagepay.
Did anyone fix up this broken module? (broken since recent 3DS Version 2 change)
Is it broken? If so, it's not due to 3d secure v2, as this is a form integration module, which by default means it's using a third party server (i.e. SagePay/Opayo) and it's their responsibility to implement v2 processing and you need to do nothing. We've been using 2.1.x for some years now and all is fine. As the Opayo docs say:
Form integration – There will be no mandatory changes to your current integration. Simply activate 3D Secure within MySagePay. To do this click on the Settings tab, followed by 3D secure. You will then be able to activate the 3D secure scheme. If you are using Custom Templates you will need to update your templates to take advantage of 3DSv2...
Bookmarks