After upgrading to 1.6 the payments are no longer saved as transactions on the individual orders - but the order still goes through.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | quickpay-md5-check-2005422-3.patch | 345 bytes | xen |
After upgrading to 1.6 the payments are no longer saved as transactions on the individual orders - but the order still goes through.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | quickpay-md5-check-2005422-3.patch | 345 bytes | xen |
Comments
Comment #1
lsolesen commentedComment #2
lsolesen commentedAnd a "Adgang nægtet" on with this message:
Comment #3
xen commentedMD5 check failed. Please try the attached patch.
Comment #4
lsolesen commentedThen everything works again, so a new release should probably be rolled :) However, the transactions in quickpay was successful, but they failed to be created in the commerce interface, so the errorhandling might need a little tweaking?
Comment #5
xen commentedWhat went wrong in commerce?
Comment #6
lsolesen commentedWell, there was no payment transaction connected to the order. So actually the transaction was created in the quickpay interface, but it failed to created in the commerce backend. The patch, though, now both creates the payment at quickpay and in commerce.
Comment #7
xen commentedWell, in that case there's not much the error handling can do. If the MD5 check fails, we can't be sure the request was not forged, so we should thoroughly ignore it.
Anyway, the fix has been committed, and a new release will follow shortly.
Comment #8.0
(not verified) commentedAdded more info.