WorldPay Module version 3.0 - Support thread

[niccol]

Well, I have a fairly heavily re-written version of this module that will work with 'Force cookie use' set to true (which I think should resolve the 'callback issues' that this module suffers) and makes some other changes that I think are desirable and just gets rid of some of the bloat. I will release that at some point, probably as Version 4 of this module, but if anyone wants to help out with some testing then that would be great. Just drop me a PM.

Thanks

[Nick1973]

Well, I have a fairly heavily re-written version of this module that will work with 'Force cookie use' set to true (which I think should resolve the 'callback issues' that this module suffers) and makes some other changes that I think are desirable and just gets rid of some of the bloat. I will release that at some point, probably as Version 4 of this module, but if anyone wants to help out with some testing then that would be great. Just drop me a PM.

Thanks

Hi Nick, I could possibly test it for you since I have a site going live in the next few days. My only concern is would your version be useable in a live environment if the callback issues are resolved?

I seem to recall that the callback issues were a mixture between the module and a setting in the worldpay admin panel last time I had an issue. I think there was a tickbox or something in worldpay that wasn't very clear, but I can't remember what it was now. I am praying that the settings I have been giving will just work to be honest.

I'm just wondering if it's possible to run the current Worldpay mod and your Worldpay mod side by side for testing?


Thanks
Nick

[niccol]

Up to you really, Nick.

Basically, the old module will not work with 'Force Cookie Use' set to true in Zen Cart admin. This is basically because when the callback happens the appropriate session cannot be recreated. There may be other problems with the callbacks but I haven't found them and that reason would explain why some people were getting errors and others not.

I'd guess you probably want to run the production site with Force-cookie-use set to true. So, you are going to have problems with the old module.

To be honest, I could make it so that you can run both but I just can't be bothered :-) I'd use my version. Much of the code is pretty much the same except that it has less bloated nonsense, is a bit more secure, and works with force-cookie-use to true. What's not to like?

[SpaceMonkey]

Well, I have a fairly heavily re-written version of this module that will work with 'Force cookie use' set to true (which I think should resolve the 'callback issues' that this module suffers)... but if anyone wants to help out with some testing then that would be great. Just drop me a PM.

Thanks

PM Sent. Thank you for sharing.

[niccol]

I have just submitted an updated version of this module.

I'll set up a new thread once it has been accepted.

Thanks

Nick

[gunni]

I have just submitted an updated version of this module.

I'll set up a new thread once it has been accepted.

Thanks

Nick

I dont know about the module you have updated
but I do like your website :)

[Nick1973]

Do you have a copy of your version please niccol?

[niccol]

After a bit of thought (and slightly fortunately having made a typo in the first submission of this module) I have decided that I am not going to submit a version of this module. The reason for this is because I think that Worldpay is not the best payment gateway. In fact, I would recommend not using it. The way it handles transferring information back to the cart is just bizarre and does not work all that well. Under those circumstances I really do not want to be supporting a module or become the person to go to with Worldpay problems :-)

There is a slight fix however for some of those people experiencing problems with callbacks. As I have discovered this may not solve all the problems but it will solve some of them. The source of some of the problems is that the session is not recreated during the callback request. That is becausee the session is recreated from a zenid in the URL. So, one solution is to put the attached override init_sessions.php file in includes/init_includes/overrides. (You may have to merge the changes if you already have a file in that position)

The only real change in this file is at line 67:

if (SESSION_FORCE_COOKIE_USE == 'True' && $_GET['main_page'] != 'wp_callback') {

Which just means that for the wp_callback page Zen will always allow the session to be created from the zenid.

Best of luck.

Nick

[Nick1973]

Nick, right after lots of stress over the weekend and several hours today we have Worldpay working. I am not sure if I can submit anything updated yet as I didn't work on the troubleshooting. However, in short, the zenID was generating an & in the ID which would of course break it. Some code has been added to check this before passing it and ensure the chars do not encode into an &. So when the session was coming back the ID was different so got forwarded to the page you were seeing as a 302 as the session didn’t exist under that id. - That was received from the guy who helped me.