WorldPay Module version 1.03 now available.
New version at
http://########################.co.uk/WorldPay_ZC1.3.x_v1.03.zip
only one change, unfortunately some legacy code was informing shoppers that though they had paid successfully, they were still in Test Mode, the correct emails were still going out, so they would t least of had some form of confirmation. Thanks to snowy2007 for spotting this.
Philip.
Re: WorldPay Module version 1.03 now available.
Sorry, I have been absent from the board for a while and not left any feedback.
One of my problems, identified by Philip was my slow hosting which didn't help things when trying to debug the module..
Any how, new host in place, I have installed the newest version from Philip as above v1.03. For whatever reason, it didn't work first time but by all accounts that was something to do with the way my hosting was set up and nothing to do with the module. Philip no doubt will fill in the blanks, on this.
To cut a long story short, with all the hard work and determination from Philip, initial tests of this module works!!! with MD5 and secure response......
I can't thank you enough Philip
Kind Regards
AfterHouR
http://www.allgoodideas.co.uk
Collectable walking sticks and canes for the discerning customer
Re: WorldPay Module for ZenCartv1.3x
I have installed the new mod ok and i can make a payment through the site.
However no order shows in my admin and the payment screen does not return back to my site after completion.
*EDIT* My fault, one missing passowrd and it appears to work fine now!
Re: WorldPay Module for ZenCartv1.3x
Glad you sorted it out OK.
I have made sure that my passwords in Worldpay test, match the passwords in production, as was mentioned in a previous post. I didn't want any ambiguities causing problems, I have had enough of those with hosting providers :)
Regards
AfterHouR
http://www.allgoodideas.co.uk
Wedding canes and stickmaking supplies
Re: WorldPay Module for ZenCartv1.3x
Quote:
Originally Posted by
DVDTitan
*EDIT* My fault, one missing passowrd and it appears to work fine now!
Pillock ! (I'm the author), use the debug feature next time and check if worlpay is sending the field callbackPW.
Re: WorldPay Module for ZenCartv1.3x
Hey Again guys.
Good job on the updated module. Discovered a few things I've missed.
Anyway, I installed the module on a 1.3.8 (as opposed to a 1.3.7) and removed all old files.
I set everything up according to your helpful documentation and tried a test transaction.... it goes back to how it was before. i.e. a thankyou page, but no callback to the old site.
When I get the debug email (awesome idea by the way) I get 'password failure' at the top. It's odd, since I've ensured that both md5 and payment response passwords are exactly the same.
Not tried the live one yet.
EDIT. looking at the above post, no callbackpw has been sent. What could cause this?
Re: WorldPay Module for ZenCartv1.3x
Hi thomasharding
Make sure the passwords in both envirnments of worldpay are the same, for instance you md5 and payment response in test environment are set to 123456, you must also have the same in your production environment ie 123456
I hope that helps
Regards
AfterHouR
http://www.allgoodideas.co.uk
[email protected]
Re: WorldPay Module for ZenCartv1.3x
Hi again.
Yeah, the test worked fine this time. The callback worked fine!
However, I'm back to square one again when doing the live transaction. I still get the "Money has not changed hands" message.
The debug email states that it was a success and it's passed everything through fine. I really do. not. know. whats going on!!!
Thanks again!
Re: WorldPay Module for ZenCartv1.3x
I know this isn't a fix but a workaround, if everything is going through fine look for that text in developer toolkit and edit out the text between the quotes, so it is not displayed on screen.
Re: WorldPay Module for ZenCartv1.3x
Hahaha, I never thought about that. Looking at things from that perspective, the order has gone through and shown up in the admin area, along with the payment to worldpay (which was authorised).
I've been having the same error message for like a month now, so by all means it could have been sorted long ago!