Get 50% off all new Gravity Forms licenses today!

Buy Now
News & Updates -

Gravity Forms v2.3 Add-On Compatibility Updates

Carl Hancock By Carl Hancock Published January 29, 2018

The release of Gravity Forms v2.3 is fast approaching and we have released updates to several Gravity Forms Add-Ons in preparation for this release.

The following add-ons have been updated for compatibility with the database schema changes that will be coming in the next major Gravity Forms release: Authorize.Net, Partial Entries, PayPal Payments Standard, PayPal Payments Pro, Signature, and User Registration.

Gravity Forms Authorize.net Add-On v2.4 Changelog

  • Added support for Gravity Forms v2.3.
  • Added “Automatic Retry is turned on in my Authorize.Net account” checkbox to Settings Page. This feature is required for ARB.
  • Added additional error messages.
  • Updated “Override Default Settings” so it can be translated.
  • Fixed an issue with logging a message when the error_message array in the response object was empty.
  • Fixed strings for translations.
  • Fixed a test description appearing on the add-on settings page with Gravity Forms 2.2+.

Gravity Forms Partial Entries Add-On v1.1 Changelog

  • Added support for Gravity Forms v2.3.
  • Added Author URI to plugin header.
  • Updated Plugin URI in plugin header to be https.
  • Updated the feed conditional logic progress choices to support the “is” operator.
  • Updated the “Complete” choice of the “Progress” entry meta item to support the “is not” operator.
  • Updated text “Enable Condition” to “Enable” in making Add-Ons consistent.
  • Updated partial-entries.js to include heartbeat.js as a dependency.
  • Fixed the handling of the “No Duplicates” field setting where validation fails on submission if a partial entry contains a duplicate value. The “No Duplicates” setting is now ignored when saving partial entries. Partial entries are now ignored when checking for duplicates on final submission – only complete entries are checked.
  • Fixed a PHP notice while viewing the entry list with WordPress 4.8.3.
  • Fixed a PHP notice during partial entry creation if the form includes a fileupload type field.

Gravity Forms PayPal Payments Standard Add-On v2.9 Changelog

  • Added compatibility with Gravity Forms v2.3.
  • Fixed an issue where PayPal can display an error instead of the cart if the option labels exceed 64 characters.

Gravity Forms PayPal Payments Pro Add-On v2.3 Changelog

  • Added support for Gravity Forms v2.3.
  • Fixed a PHP notice which would occur when sending a request to PayPal.

Gravity Forms Signature Add-On v3.4 Changelog

  • Added compatibility with Gravity Forms v2.3.
  • Updated IeModalFix init option to only be set for IE browsers; fixes issue with FireFox with 3+ paths on a signature.
  • Fixed a JavaScript error which could occur in the form editor with Gravity Forms 2.3-beta.
  • Fixed an issue where the field could be populated with the value from another form on the same page if both fields have the same ID.
  • Fixed an issue where the signature file could remain after the entry was permanently deleted.

Gravity Forms User Registration Add-On v3.9 Changelog

  • Added support for Gravity Forms v2.3.
  • Added GPL to the plugin header.
  • Added the “Preserve current email” choice to the email address mapping drop down on the update type feed.
  • Updated URIs in plugin header to use https.
  • Updated username validation message to match WordPress’ equivalent validation message.
  • Updated strings in pending activations so they could be translated.
  • Fixed an issue which can prevent pending activations from being listed due to collation mismatch after installing the add-on after upgrading MySQL from 5.5 to 5.6.
  • Fixed a PHP warning related to the login form/widget logged in/out links.

Note for Developers

This is an important reminder that Gravity Forms v2.3 will introduce a database schema change to improve performance and scalability. If you have code that accesses the Gravity Forms tables directly you will need to update your code so that it uses the correct table and column names. Existing code that uses the Gravity Forms API functions (GFAPI) will not be affected.