News & Updates -

Gravity Forms v2.3.2 Released

By Carl Hancock Published May 21, 2018

Gravity Forms v2.3.2 is now available via automatic update and the downloads page.

For complete details on what is new in Gravity Forms v2.3.2 see the changelog below. If you have not already upgraded to v2.3, be sure to read the Gravity Forms v2.3 release announcement before upgrading.

Gravity Forms v2.3.2 Changelog

• Added the gform_field_filters filter enabling the filter settings for the form fields, entry properties, and entry meta to be overridden.
• Added gform_use_post_value_for_conditional_logic_save_entry to support fetching values from the $_POST when evaluating a field’s conditional logic while re-saving an existing entry.
• Updated the routing rule value select on the edit notification page to include the field placeholder, if configured.
• Updated the {save_email_input} merge tag to support using the placeholder attribute to override the inputs placeholder e.g. {save_email_input:placeholder=”Enter your email address”}.
• Updated form stylesheets to be registered and enqueued instead of directly enqueued.
• Updated list of available languages for reCAPTCHA.
• Updated GFFeedAddon::get_single_submission_feed() method to only return cached feed if the same form object is provided.
• Fixed an issue on the field editor that caused the field UI to be duplicated in certain conditions.
• Fixed an issue with checkbox field where preview wasn’t taking into account selected value.
• Fixed an issue with list field merge tag processing when a comma separated list of modifiers was used. Credit: The team at GravityView.
• Fixed a PHP notice which could occur when sending a notification which uses routing if a routing rule property is not defined.
• Fixed issue allowing site admins to uninstall network activated add-ons.
• Fixed the save email input placeholder not being translatable.
• Fixed a performance issue which forces the autoload options to reload on every request.
• Fixed a performance issue when checking the database version.
• Fixed an issue where elements could not escape content container in tabbed content sections.
• Fixed an issue with the entry search when searching for values in nullable columns in the entry table. For example, this fixes an issue when filtering entries for payment status is not ‘Processing’ where null values are ignored.
• Fixed JS errors which can occur when using the reCAPTCHA field if there is a slow network connection or jQuery is included in the page footer.
• Fixed an issue with the upgrade process where the table check for the incomplete submissions table may fail.
• Fixed a JavaScript error when sites use jQuery v3 on the front-end.
• Fixed bad text strings in messages regarding Add-Ons incompatible with the version of Gravity Forms.
• Fixed GFCommon::get_product_fields() interacting with option and shipping fields as arrays instead of using object notation.
• Fixed an issue with how the result from the gform_product_info_name_include_field_label filter was being used.
• Fixed the admin label not being used for the option and shipping fields when using the {all_fields:admin} merge tag.
• Fixed an issue where products with no options, no name, and no price could be included in the products info used to populate the summary table.
• Fixed some options remaining in the database on uninstall resulting in submissions being blocked or a failed database upgrade occurring on reinstall.
• Fixed issue where fields disabled by default were re-enabled via conditional logic.
• Fixed text format notifications being formatted to include HTML br tags.
• Fixed an issue with the Date field layout.
• Fixed an issue with the entry search where incorrect results are returned when searching for a meta value that is not empty.

Gravity Forms v2.3.2 API Changelog

• Fixed an issue with the entry search where searching for an empty string meta value will return zero results.
• Fixed issue with GFAPI::count_entries( 0 ) where the result is always zero.

Gravity Forms v2.3.2 Add-On Framework Changelog

• Fixed an issue with the Ajax request for the “show more” link on the Results page which prevented additional results being displayed.

You can update to the latest version of Gravity Forms using Automatic Update. Just visit the Updates page under the Forms navigation in your WordPress Dashboard. Update deployment is staged so if you do not see the update available, try again in a few hours. You can also download the latest version of the plugin from the Downloads page.

Don’t own a Gravity Forms Yet? What are you waiting for? Purchase a copy today!