Gravity Forms eWAY v1.0.3 has just been released, with a few minor fixes for mapped fields and a work-around for a plugin conflict.

I’ve been testing some new features for a forthcoming version, and it helped me discover a couple of bugs in the current version that I hadn’t tripped over before. See, more testing is better testing! Rather than sit on the fixes until I finish the new features, I’m getting the fixes out now before someone else trips over them.

The first bug was with the customer’s title. If you enabled the “prefix” part of a Name field and mapped it to the customer title, it wouldn’t send it. I hadn’t noticed this before, but I’ve been fiddling with token payments and they require a customer title; skipping this field mapping resulted in the customer getting assigned the title “Mr”. I imagine someone would have told me about unhappy customers sooner or later…

The next bug was failing to use the form total for recurring payments amounts. It seems all my tests were with a specific form field; now rectified, both in my test cases and in the add-on. This is required when forms use multiple products or calculated fields to arrive at a total, something I bumped into on a website just the other day. Thankfully, it’s now fixed.

A user of the free Gravity Forms eWAY add-on tripped over a problem caused by a plugin called T2T Toolkit, which was a core part of the theme for his website. That plugin breaks the form total field posted back to the website by Gravity Forms, when there was a product with an options field. Weird, and no errors anywhere (not even the browser console). I’ve added a work-around so that such problems don’t stop the form total from being calculated.

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