Gravity Forms v2.3 Beta 2 Released

Gravity Forms v2.3 Beta 2 is now available via the downloads page. It is only available via automatic update if you previously installed Gravity Forms v2.3 Beta 1. Version 2.3 is a feature release that includes a variety of enhancements and improvements. A complete rundown of the features, enhancements, and changes can be found below.
This is the first time Gravity Forms has ever made such a major change to the database schema so we want to ensure that every site is upgraded successfully without any loss of entry data. To avoid potential issues we advise all customers to test this version before the final release and report any issues.
Now is the time for 3rd party developers and customers who have implemented customizations that may be impacted by these changes to be testing and readying changes in preparation for the final release of Gravity Forms v2.3 via automatic update.

Gravity Forms v2.3 Highlights

  • Improved accessibility: tabindex attribute is now suppressed unless enabled via the shortcode or gform_tabindex filter.
  • Select All choice added to Checkbox Field to easily select/deselect all choices.
  • Multiple form export files can now be imported at once using the Import/Export tools.
  • Introduced support for OpenSSL encryption.
  • Deprecated support for Mcrypt encryption.
  • Added Notifications setting for defining CC email to Email Notification. Enabled using the new gform_notification_enable_cc filter.
  • Updated the included Chosen JS library for the enhanced Drop Down field UI to the latest version.

Upgrading to v2.3

The database upgrade process will be completely automatic and transparent and you won’t need to intervene. If your site or multisite network has a large number of entries (100k+) then, depending on your server resources, you may find the migration takes a long time to complete. If you have any questions, or see any errors, please open a support ticket so we can help you.

Note for Developers

The database schema has changed in v2.3 to improve performance and scalability. If you have any code that accesses the Gravity Forms tables directly you will need to update your table and column names. Any existing code that uses Gravity Forms API functions (GFAPI) will not be affected.

Gravity Forms v2.3 Beta 2 Changelog

  • Added a dismissible admin message while upgrading.
  • Updated the upgrade process to fail form validation while upgrading. The form is now displayed.
  • Updated site registration to minimize changes of API request getting blocked by Armor.
  • Fixed the upgrade process for multisite.

Gravity Forms v2.3 Beta 2 Rest API v1 Changelog

  • Deprecated GFCommon::encrypt() and GFCommon::decrypt().
  • Added multisite support to GF_Background_Process.
For a complete list of all the changes included in Gravity Forms v2.3 Beta 1, see the release announcement. Once you have installed and activated Gravity Forms v2.3 Beta 1 or Beta 2 you will have access to beta release updates via automatic update.
4 Responses to "Gravity Forms v2.3 Beta 2 Released"
  1. JenF says:

    Hi,

    Is there a reference mapping current table and column names to the new ones? I've made some customizations to my form that accesses the Gravity Forms tables directly but I'm not sure what the new names should be!

    Thanks

  2. Jeff Matson says:

    You can find the full storage structure here:
    Database Storage Structure Reference

  3. JimBurke says:

    Please help. I am trying to open a support ticket but cannot do so.
    I have just purchased a GF license but the system rejects it.
    I cannot submit a System Status report as my running version is pre-2.2 and therefore does not feature the System Status page - it wants me to upgrade.
    However I cannot upgrade because I cannot enter the new license key. Please help.

    PHP Version 5.6.32
    MySQL Version 5.6.36
    WordPress Version 4.9
    Gravity Forms Version 1.9.18.5

    Regards,
    Jim Burke

  4. Richard Wawrzyniak says:

    Jim, Please use our contact us form: https://www.gravityforms.com/contact-us/

Leave a Reply