what do you prefer?
NULL for tstatus by default?
Thread Starter
thpani
(@thpani)
Whatever works?
Unless I’m missing something, this plugin is handling mPAY confirmations and trying to update the order status accordingly. But as tstatus will always default to ERROR I don’t see how this could be working for anybody — it will always take the ‘error’ branch here: https://plugins.trac.wordpress.org/browser/woocommerce-mpay24-gateway/tags/1.4.1/gateway-mpay24.php#L675
No, the tstatus is updated in https://plugins.trac.wordpress.org/browser/woocommerce-mpay24-gateway/tags/1.4.1/class-wc-mpay24-shop.php#L502
This is triggered from mPAY24 over the sent success_url/error_url which leads to https://plugins.trac.wordpress.org/browser/woocommerce-mpay24-gateway/tags/1.4.1/gateway-mpay24.php#L603
Yes, default the tstatus is error if the transaction is created in the database via the plugin. But it will be updated by a callback from mpay24.
If your orders stuck to error maybe there is another problem with your orders? Have you enabled the plugin’s logfiles?
Thread Starter
thpani
(@thpani)
Thanks for the quick reply! Then I have to take a closer look at what’s going on, my logs look like this: https://gist.github.com/thpani/4a1aaecdc15ddaf77140
I suppose in the last line it should say billed instead of error
Do you have a htaccess page protection on your wordpress site? If so you have to provide the credentials in the gateway settings that mpay24 can send the feedback.
otherwise I would suggest you to contact also the mpay24 support to check if the problem is on their side or give you further advice.
Please can you check if the token from here (https://gist.github.com/thpani/4a1aaecdc15ddaf77140#file-gistfile1-txt-L100) is the same as send in the PayREQUEST Confirmation URL.
This should be above in your log file.
Thread Starter
thpani
(@thpani)
I’ve updated the gist to include all SOAP messages, the token matches the one passed in the confirmation URL. There’s no authentication.
I’ll try to track down where the transaction update fails tomorrow.
Thread Starter
thpani
(@thpani)
Found the culprit, the confirmation callback contains a PROFILE_ID field, which causes $wpdb->update to fail with:
Unknown column 'profile_id' in 'field list'
Should this column be added to the DB? Or filter the $update array to only include columns present in the DB?
I’ve talked to mpay24 concerning the profile_id field. It’s only on a few accounts with special settings.
I will provide a bugfix soon.
Hi,
there is a new version that should fix your problem.
Thread Starter
thpani
(@thpani)
Many thanks for the wonderful support, now it works perfectly!
