2.9.10

Gravity Forms v2.9.10 Changelog

• Fixed an issue where the background processing queue can become indefinitely paused if the theme or another plugin is using a WP option filter or action hook incorrectly.
• Fixed an issue with the background processor AJAX request arguments, improving form submission performance for add-ons where feed processing takes a while.
• Fixed an issue where the form title and description can be removed when the form fails validation using the new AJAX submission method.
• Fixed an issue with new AJAX where form submissions can break if the form action attribute changes to the admin-ajax.php URL when form markup is updated.
• AF: Improved support for WordPress plugin checks in GFAddOn::minimum_requirements(). Credit: The Gravity Wiz Team.
• AF: Fixed a fatal error that occurs when validating a select type setting when the option to select multiple choices is enabled.

2.9.9

Gravity Forms v2.9.9 Changelog

• Fixed a JavaScript error that occurs when a submit button located outside the form is clicked. Includes a browser console error statement that recommends checking the settings of fields in the form editor for invalid HTML.
• Fixed an inconsistency in the Rich Text Editor content when using the new AJAX submission method.
• Fixed several RTL issues for feed pages and form settings icons.
• Fixed an issue where the multi-column vertical list ready classes are not working for the Orbital theme.
• Fixed an issue that prevents validation messages from displaying correctly in repeater fields.
• Updated error handling by moving it from GF_Feed_Processor to GF_Background_Process, and improved it, so it will also catch and log errors that occur when the notifications processor is used.
• Updated Gravity Forms admin page header to reflect updated branding.
• Updated new AJAX submission so that the form is submitted correctly even when third-party code outputs text in the AJAX response.
• Updated the Autocomplete Attribute setting tooltip to provide clearer instructions about valid values and added a link to a list of supported attributes.
• Updated the error messages that are displayed any time you try to change or delete a field when there is conditional logic based on that field so that the messages are more informative.
• API: Fixed an incorrect parameter being passed to gform_field_map_choices filter. Credit: The GravityKit Team
• API: added the ability to query notes from multiple entries at once. Credit: The GravityKit Team.

2.9.8

Gravity Forms v2.9.8 Changelog

• Added a setting to disable the dashboard widget.
• Fixed a PHP fatal error that occurs during background processing if another plugin includes an older version of WP_Async_Request that doesn't include maybe_wp_die().
• Fixed a PHP fatal error that occurs in wp_date() for some PHP versions and timestamps during background processing if a batch has previously been attempted.
• Fixed a nonce validation error that occurs when a background processor dispatch method is called during an admin-ajax.php request, such as the one used to process new Ajax enabled form submissions.
• Fixed an accessibility issue where the consent field description does not get keyboard focus.
• Fixed an issue that causes the URL field properties to be overwritten by defaults in the form editor.
• Fixed an issue where the honeypot doesn't work with new Ajax.
• Fixed a deprecation notice for the utf8_encoded() PHP function.
• Updated tables on the System Report page to improve accessibility.
• Updated the default honeypot action from "Do not create an entry" to "Create an entry and mark it as spam".
• Updated the flyout in the form editor to be more consistent.
• Removed the unused data-js-reload attribute from field markup.
• AF: Updated the generic map field to show Entry Date and Entry ID as options when the field types are date and number, respectively.
• API: Fixed an issue with the gform/post_render event being fired too early during an AJAX submission, which causes conflicts with certain add-ons.
• API: Updated GFAPI::submit_form()`` to support an optional 6th param, ``$initiated_by, the process that initiated the submission. Supported integers are 1 (aka GFFormDisplay::SUBMISSION_INITIATED_BY_WEBFORM) or 2 (aka GFFormDisplay::SUBMISSION_INITIATED_BY_API). Defaults to GFFormDisplay::SUBMISSION_INITIATED_BY_API.
• API: Updated the result returned by `GFAPI::submit_form()`` to include the is_spam, confirmation_message, and confirmation_type properties when the form fails honeypot validation and it is configured to use the "Do not create an entry" action.

2.9.7.2

Gravity Forms v2.9.7.2 Changelog

• API: Fixed an issue with the gform/post_render event being fired too early during an AJAX submission, which causes conflicts with certain add-ons.
• Updated the default honeypot action from "Do not create an entry" to "Create an entry and mark it as spam".
• Fixed an issue where the honeypot doesn't work with new Ajax.
• API: Updated GFAPI::submit_form() to support an optional 6th param, $initiated_by, the process that initiated the submission. Supported integers are 1 (aka GFFormDisplay::SUBMISSION_INITIATED_BY_WEBFORM) or 2 (aka GFFormDisplay::SUBMISSION_INITIATED_BY_API). Defaults to GFFormDisplay::SUBMISSION_INITIATED_BY_API.
• API: Updated the result returned by GFAPI::submit_form() to include the is_spam, confirmation_message, and confirmation_type properties when the form fails honeypot validation and it is configured to use the "Do not create an entry" action.
• Fixed a PHP fatal error that occurs during background processing if another plugin includes an older version of WP_Async_Request that doesn't include maybe_wp_die().
• Fixed a PHP fatal error that occurs in wp_date() for some PHP versions and timestamps during background processing if a batch has previously been attempted.
• Fixed a 403 error that occurs when a background processor dispatch method is called during an admin-ajax.php request, such as the one used to process new Ajax enabled form submissions.

Gravity Forms v2.9.7.1 Changelog

• Fixed an accessibility issue where the consent field description does not get keyboard focus.
• Added a setting to disable the dashboard widget.
• Fixed an issue that causes the field properties to be overwritten by defaults.

Gravity Forms v2.9.7 Changelog

• Added the autocomplete attribute setting to Website field.
• Fixed spacing and margin issues in the admin and help sections in RTL languages.
• Fixed a PHP fatal error that occurs when the gform_form_switcher_forms filter returns an invalid value, or when a deleted form remains in the current users recent forms list.
• Updated the minimum WordPress version (for support) on the System Status page to 6.7.
• Removed trailing spaces from some translatable strings to improve translation.
• AF: Fixed an issue where the placeholder attribute isn't rendered for text input fields in add-on feed settings. Credit: GravityKit team
• AF: Updated the background processor to pause when a task encounters an error (e.g. external API rate limit), and resume later on the fallback cron job.
• API: Added the submission type ("submission_type" property) to the result returned by an AJAX submission.
• API: Fixed an issue where the conditional logic setting instructions property could not be overridden. Credit: GravityKit team

2.9.7.1

Gravity Forms v2.9.7.1 Changelog

• Fixed an accessibility issue where the consent field description does not get keyboard focus.
• Added a setting to disable the dashboard widget.
• Fixed an issue that causes the field properties to be overwritten by defaults.

Gravity Forms v2.9.7 Changelog

• Added the autocomplete attribute setting to Website field.
• Fixed spacing and margin issues in the admin and help sections in RTL languages.
• Fixed a PHP fatal error that occurs when the gform_form_switcher_forms filter returns an invalid value, or when a deleted form remains in the current users recent forms list.
• Updated the minimum WordPress version (for support) on the System Status page to 6.7.
• Removed trailing spaces from some translatable strings to improve translation.
• AF: Fixed an issue where the placeholder attribute isn't rendered for text input fields in add-on feed settings. Credit: GravityKit team
• AF: Updated the background processor to pause when a task encounters an error (e.g. external API rate limit), and resume later on the fallback cron job.
• API: Added the submission type ("submission_type" property) to the result returned by an AJAX submission.
• API: Fixed an issue where the conditional logic setting instructions property could not be overridden. Credit: GravityKit team

2.9.7

Gravity Forms v2.9.7 Changelog

• Added the autocomplete attribute setting to Website field.
• Fixed spacing and margin issues in the admin and help sections in RTL languages.
• Fixed a PHP fatal error that occurs when the gform_form_switcher_forms filter returns an invalid value, or when a deleted form remains in the current users recent forms list.
• Updated the minimum WordPress version (for support) on the System Status page to 6.7.
• Removed trailing spaces from some translatable strings to improve translation.
• AF: Fixed an issue where the placeholder attribute isn't rendered for text input fields in add-on feed settings. Credit: GravityKit team
• AF: Updated the background processor to pause when a task encounters an error (e.g. external API rate limit), and resume later on the fallback cron job.
• API: Added the submission type ("submission_type" property) to the result returned by an AJAX submission.
• API: Fixed an issue where the conditional logic setting instructions property could not be overridden. Credit: GravityKit team

2.9.6.1

Gravity Forms v2.9.6 Changelog

• Added a performance improvement by making the form switcher only show the most recent 10 forms.
• Updated the gform_form_switcher_forms filter to allow developers to also filter the forms that show up in the form switcher search results.
• Updated dropdowns in the admin to be more consistent.
• Fixed an issue where save_callback is not called for fields located in tabs.
• Fixed an issue where the submit button is replaced with a next button on the last page of a multi-page form when that page is hidden by conditional logic and fails validation.
• Fixed an issue where the field map setting is not working when no conflict mode is enabled.
• Fixed an issue where the form submits or the next page is displayed if the previous button does not include the gform_previous_button class when clicked. Note: When using filters like gform_submit_button, gform_next_button, or gform_previous_button to replace the input elements with button elements, make sure to keep the attributes from the original elements. Example code.
• Fixed an issue where a javascript error occurs if a calculation is attempted and the calculation field does not have an input.
• API: Added inline documentation for the Foundation layer of the Theme Framework.
• API: Added temporary blocking mechanism when version.php API calls return server errors (5xx) to prevent excessive failed requests.
• API: Updated the generic map setting field to support using textareas when mapping to a custom value.

2.9.5

Gravity Forms v2.9.5 Changelog

• Fixed an issue where a javascript error is thrown when using multiple forms on the same page with conditional logic.
• Fixed a bug that causes a PHP error when you try to duplicate a duplicate of a form. Credit: The GravityKit Team.
• Fixed a JavaScript error that occurs when the selected option is not found in the pricing fields meta retrieved post render.
• Fixed an issue where the total is not updated when the form is embedded using the shortcode, and the selected option field choices are being modified via a form filter based on a query argument.
• Fixed various issues with the new Ajax submission functionality to make sure that hooks and filters are run and validation messages are displayed correctly.
• Fixed a PHP notice that occurs on post or page display when the embedded form has been deleted.
• Updated the form import confirmation message to display the count of both failed and successful forms and to include a link to the list of imported forms.
• Removed hidden fields that provide instructions in the form templates.
• AF: Fixed a PHP notice that occurs when creating or editing a coupon.
• API: Updated the generic map setting field to support using textareas when mapping to a custom value.
• API: Added a new User Select field to the Settings API.
• API: Updated the submission process to support submission method changes via the gform/submission/pre_submission filter.
• API: Removed support for the SUBMISSION_METHOD_CUSTOM submission method.

2.9.4

Gravity Forms v2.9.4 Changelog

• Added the gform_feed_settings_before_fields filter to allow developers to change the content that is displayed before the feed settings.
• Fixed an issue where field-specific validation was no longer running when No Duplicates setting was enabled.
• Fixed an issue that prevents the form editor from working properly when the form doesn't have a submit button configured.
• Fixed a styling issue with the generic field map setting where the merge tag link overlaps the input.
• Fixed an issue where the Gravity Forms block is not rendering or working correctly in the site editor (iframed block editor).
• Updated the form switcher so that it stays on the same settings page when switching forms.
• Updated the minimum WordPress version to 6.5.
• Updated the minimum PHP version to 7.4.
• Updated the minimum WordPress version (for support) on the System Status page to 6.6.
• API: Added GFAPI::update_entry_feed_status(), GFAPI::get_entry_feed_status(), and GFAPI::get_entry_feed_status_key().
• AF: Added GFFeedAddOn::save_entry_feed_status(), GFFeedAddOn::post_process_feed(), and GFFeedAddOn::fulfill_entry().
• AF: Updated GFFeedAddOn::maybe_process_feed() to support saving the feed processing result for compatible add-ons. This is dependent on the value returned by the add-ons process_feed() method:
  • void or null when the feed status should not be saved.
  • false or a WP_Error when a failed status should be saved. The code, message, and data properties from the WP_Error will also be saved.
  • true or the $entry when a success status should be saved.

2.9.3

Gravity Forms v2.9.3 Changelog

• Added the gform_file_upload_tmp_dir filter to allow developers to change the temporary directory used for file uploads.
• Fixed an issue with conditional logic for numbers formatted as date or time.
• Fixed an issue that causes the entry list to sometimes have display problems on mobile screens.
• Fixed an issue where some icons are missing in compact view in the form editor.
• Fixed an issue where Ajax submissions can abort when the field values block setting contains multiple parameters or when using a tabindex of -1.
• Fixed an issue where Ajax submissions can abort when a third-party embed method passes a string instead of a boolean as the value of the $display_title or $display_description arguments of the gravity_form function.
• Fixed an issue where calculations based on an Image Choice field only run if you click the input, not the image.
• Fixed an issue where the form list page throws a JavaScript error if the user does not have the gravityforms_create_form capability.
• Fixed an issue that allows the File Upload Field to bypass validation checks when using a maximum file constraint.
• Fixed an issue where the :value of product fields in calculations uses price upon submission.
• Fixed an issue where changing the 'gform_sticky_admin_messages' database values can cause a fatal error.
• Fixed an issue with product fields that do not update the total when the markup is updated via custom code.
• Removed "send you a birthday cake" custom validation message from template library forms.
• Updated handling of images for the Image Choice field so that thumbnail sizes are only generated for images used in the field.
• Updated the form preview to use the Orbital theme.
• API: Updated the React components to support the use of the newly created internal component icon kit.