Hey Chris,

Updated ubercart core the other day and noticed a new issue.

Running D6, ubercart 6-2.7
problem occurs on pxpay and a similar problem with pxaccess.

So just to clarify the steps to reproduce:
order takes you to dps payment page, dps says transaction accepted and redirects back to drupal
Drupal has error: dps payment has been declined. Please contact us for assistance.
The order isn't notifying customers and it isn't appearing as a declined payment order in store > orders > view orders
So no such order record exists but payment is coming through! Which on a side note is good, but not that good....

I tried this with Robbie McKays, uc_dps_pxpay < been using this for a couple of years with no hassles, plus the paymentexpress built in pxaccess modules.

pxaccess doesn't report an error, but the order isn't added to uc and no notifications to customer or admin, but the transaction isn't going through either.. so bit of a problem there.

We haven't added any new modules for a long time, but if you can suggest a better debugging method please say so and I'll give that a try.

Thanks man!

Comments

xurizaemon’s picture

Component: Code » Code - PXPay
Status: Active » Postponed (maintainer needs more info)

That doesn't look like an error message from the current version of this module. I've tested with uc_dps_pxpay from 6.x-1.x-dev and it works as expected.

If you're still using the tarball from #653850: PxPay module, that's not supported. Please upgrade to a recent 6.x-1.x-dev instead.

snlnz’s picture

Hey thanks for your reply. So I uninstalled the old module completely and installed the 6.x-1.x-dev as you mentioned.

Nothings changed. Still get to DPS screen, payment is accepted then when the redirect back to site, I'm still getting:
Your DPS payment was declined. Please feel free to continue shopping or contact us for assistance.

Is it possible that it's an issue at DPS rather than the module? All seems a bit odd that the dps payment manager is capturing the payment but the site decline's it.

xurizaemon’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I've verified that ubercart-6.x-2.7 + uc_paymentexpress-6.x-1.x is working as expected for PxPay.

You'll need some investigation to work out what's misbehaving on your site. Feel free to contact me directly for commercial support if you need.

snlnz’s picture

Thanks man I'll see how I go, but I've managed to free up some time this week which is helpful!
I'll pull a dev copy of the site apart and see where the oil leak is so to speak. :)

codeworkshop’s picture

Has anyone managed to find a helpful fix for this issue?

All of a sudden I'm experiencing the same on a website of mine. I have updated the DPS module to the latest version, and have tested on DEV with the latest version of Ubercart (as my PROD site continues with Ubercart 2.4 until a custom module is upgraded).

The issue is present with both the site's PROD DPS account and my DEV DPS account, therefore I can't see that there is an issue at DPS' end.

I can only assume that there is a conflict with a module I have installed recently or a setting on the new web server as the site has been moved recently.

Any help is very much appreciated.

xurizaemon’s picture

Version: 6.x-1.0 » 6.x-1.x-dev
Category: bug » support
Status: Closed (cannot reproduce) » Fixed

Looks like (for @codeworkshop at least) this was Suhosin config. For him, the fix was to edit /etc/php5/conf.d/suhosin.ini and replace the commented out default value
;suhosin.get.max_value_length = 512
with this override, which allows for a larger $_GET value
suhosin.get.max_value_length = 8192

(8K might be overkill, but the DPS value is 3K and I'm inclined to leave plenty of room)

#1262340: $_GET value "result" empty on return from DPS due to suhosin configuration

Karu, can you try the same on your system?

snlnz’s picture

Hey Chris, I did fix it in the end by removing every module and uninstalling each one from the db then re-installed each module one by one testing each modules functionality painstakingly bit by bit.

I couldn't' even tell you which module was the culprit but so many were stripped out or updated in the end.
Admittedly I failed to document my rebuild which ultimately prevented learning from what was fixed, I was too set on getting it fixed to be honest. :O

Sorry I can't be more helpful it was a nightmare of a job too!

If I can dig up an old backup I'll give it a try.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

snlnz’s picture

Version: 6.x-1.x-dev » 6.x-1.1

Hey Chris, I can confirm this fixes the problem after debugging a recurrence last night.
Thanks saved a heap of time.

xurizaemon’s picture

Status: Closed (fixed) » Closed (duplicate)