We’re excited to announce the new release of Gravity Forms v.2.4.11! Inside this release, you’ll find:

• Added security enhancements
• Added various bug fixes

Gravity Forms v2.4.11 is now available for auto-update from the WordPress plugins page and also on the downloads page in the account area.

Gravity Forms v2.4.11 Changelog

• Added security enhancements. Credit: SimranJeet Singh (@TurbanatorSJS).
• Added accessibility enhancements.
• Updated the minimum version of WordPress required for support to 5.1.
• Updated the system report to include timezone details.
• Updated new Drop Down type Quantity fields to default to numeric choices. Credit: The GravityView team.
• Updated the Website type field input markup, removing the unused maxLength attribute. Credit: The GravityView team.
• Updated the Single Line Text field to validate the value length during submission when the maxLength property is configured. Credit: The GravityView team.
• Fixed an issue where special characters (e.g. accented characters) in List and Multi-Select fields are ignored when searching for entries.
• Fixed form scripts not enqueueing when Form block is nested.
• Fixed an issue where the use of GLOB_BRACE during the daily cron task can cause PHP errors in non-GNU operating systems.
• Fixed an issue with conditional notification routing when checking if a field value ends with a 0 due to it being treated as an empty string rather than an integer.
• Fixed the legacy table access PHP notices being displayed when deleting a site on multi-site installations.
• Fixed an issue with the Address field in the form editor where the source field setting doesn’t display the previously selected option when copying values of another field.
• Fixed an issue with the Rich Text Editor for the Paragraph and Post Body fields with WordPress 5.2 when submit button conditional logic is configured.
• Fixed an issue with PHP 7.0+ where the submission could die when an invalid calculation formula is evaluated. Credit: The GravityView team.
• Fixed a PHP notice during validation of the Password strength if JavaScript is disabled in the browser. Credit: The GravityView team.
• Fixed an issue with submitting when multiple AJAX enabled forms are embedded into one page and invisible reCAPTCHAs are present.
• Fixed an issue when tabbing through a form where an invisible reCAPTCHA is present.
• Fixed an issue where a field’s character count text could duplicate when submitting an AJAX enabled form.
• Fixed the required Address field city input missing the aria-required attribute when the zip input is located before the city.
• Fixed an issue with the background tasks response in the system report containing extraneous characters.

Gravity Forms v2.4.11 API Changelog

• API: Added GFAPI::log_debug() and GFAPI::log_error() which write to the “Gravity Forms API” log.
• API: Added support for the id query param on the export entries page (/wp-admin/admin.php?page=gf_export&view=export_entry&id=[FORM ID]) to preselect the form. Credit: The GravityView team.
• API: Added logging helpers and logging statements to various methods in REST API v2.
• API: Updated REST API v1 to write to the “Gravity Forms API” log.
• API: Fixed GFAPI::update_entry() and GFAPI::update_entry_field() for repeater fields.
• API: Fixed an issue with GFAPI::update_entry_field() not saving zero when passed as an integer if the input doesn’t have an existing entry value.
• API: Fixed an issue with GFAPI::submit_form() and the POST forms/[form ID]/submissions endpoint where validation fails for product fields.

Gravity Forms v2.4.11 Add-On Framework Changelog

• AF: Added header title support for dynamic field map settings fields.
• AF: Updated + and – icons so that they are consistent accross all settings fields.