Gravity Forms DPS PxPay version 2.0.2 has just been released. This release brings Gravity Forms 2.3 compatibility; a fix for the UAT environment in test mode; and there’s a new custom merge tag for the Entry Date.

Gravity Forms 2.3

Gravity Forms 2.3 is due out soon, and it brings changes to the database structure used to store form entries. This release removes any direct access to Gravity Forms tables, using API calls instead, so that it will maintain compatibility with all versions from 2.0 up.

The UAT environment

When you set up the add-on, you need to specify which PxPay environment to use for your sandbox. Older accounts were always set up on the SEC (secure) environment, but DPS created a UAT (user acceptance test) environment which all newer accounts can access. At some point, I broke the use of UAT — but I fixed it, so all is good again! Sorry!

Entry Date merge tag

If you are sending Gravity Forms notifications as receipts, you probably use the standard Date merge tag. For eWAY transactions, you can now use the Entry Date instead — and you should, because if you resend a notification you want it to have the date of submission, not today’s date.

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