eWAY Payment Gateway v3.6.0

eWAY Payment Gateway v3.6.0 has just been released. Basic logging has been added to assist with support problems, and some changes have been made for better compatibility with WordPress 4.6 and WooCommerce 2.6.

To make it easier to provide support when there’s a problem, I’ve added some basic logging to each of the integrations. Logging is disabled by default, and can be enabled for just errors or for all messages. The log files are stored in undiscoverable folders and never contain credit card details — just in case! You can enable logging from the settings page for each integration, e.g. here’s the WooCommerce one:

Logging settings for WooCommerce integration

Logging settings for WooCommerce integration

WordPress 4.6 will be making some changes to the remote requests functions. Specifically, the data returned will be an object instead of an array. In preparation, I now use the wp_remote_retrieve_body() function as recommended.

WooCommerce 2.6 has just been released, with some changes to payment gateway integration. I’ve updated the integration for WooCommerce to work with those changes, which will prevent some deprecated function errors in log files.

All forms have had a bit of a refresher to improve accessibility a little. This includes admin settings forms for some integrations, and all custom credit card forms. There should be no noticeable difference unless you are assisted by accessibility-friendly HTML!

More changes are coming… including Rapid API support. Stay tuned!

You can update to the latest version from your WordPress plugin admin page. Here’s the full changelog for eWAY Payment Gateway.

Posted on