Gravity Forms DPS PxPay version 1.6.1 has just been released. This release fixes PHP 7 compatibility, fixes another conflict with T2T Toolkit, and ensures WordPress 4.6 compatibility.
WordPress 4.6 was going to deliver some major changes to accessing remote resources like eWAY, so this release changes how messages are sent to Payment Express in line with this WordPress trac comment. It sounds like that was going to cause too much trouble so it’s no longer going ahead in the same way, but we’re covered “just in case”. The new approach is more future proof, so the change is for the better.
I finally upgraded my development environment to PHP 7, and found a few incompatibility bugs. For the technically minded, they were all due to the changes to indirect variable evaluation — you can read about that on PHP 7 backwards incompatible changes. The plugin is now compatible with PHP 7, and also still compatible with PHP 5.6+ (If you’re still running an older version of PHP, the plugin will probably still work — but you should upgrade your PHP version anyway to continue receiving security patches!)
Returning from the Payment Express page to the website was getting a 404 Page Not Found on some themes, due to a conflict on the WordPress
parse_request action. The plugin now uses the
do_parse_request filter instead, which happens sooner and avoids such conflicts.
The T2T Toolkit plugin keeps on giving, this time it’s a conflict with the Coupons add-on to Gravity Forms. I’ve now switched to using Gravity Forms’
get_order_total() to get the order total, since I can now depend on it being there. This should fix T2T Toolkit conflicts once and for all!
You can update to the latest version from your WordPress plugin admin page. Here’s the full changelog for Gravity Forms DPS PxPay.Posted on