Gravity Forms v1.9.17 is now available via automatic update and the downloads page.
This is the last major maintenance and developer focused release before the upcoming Gravity Forms v2.0 Beta 1 release. This update includes security enhancements, new hooks/filters, and important updates to the Gravity Forms Add-On Framework and API.
This version will be required for upcoming Add-Ons nearing public release.
What's New in Gravity Forms v1.9.17
- Added the GF_MIN_WP_VERSION_SUPPORT_TERMS constant and a message on the settings page when the site is not eligible for support.
- Added the GFEntryDetail::maybe_display_empty_fields() helper to determine if empty fields should be displayed when the lead detail grid is processed.
- Added {admin_url} and {logout_url} merge tags for use with User Registration Add-On.
- Added proactive security hardening enhancements.
- Updated save and continue confirmations to support shortcodes.
- Updated form view count and lead count so that they are cached to improve performance.
- Updated Bengali translation. Credit: Md Akter Hosen.
- Updated entry info filters to include additional payment statuses supported by the AF.
- Updated Dutch translation. Credit: Eenvoud Media B.V. / Daniel Koop.
- Fixed an PHP notice related to the field specific version of the gform_save_field_value hook which could occur when using GFAPI::update_entry().
- Fixed an issue with the empty form validation and fields configured as admin only which do have a value.
- Fixed an issue with the confirmation query string when using the merge tag for a currency formatted Number field.
- Fixed an issue which prevented the gform_save_field_value hook running for custom field types when the input value was an array.
- Fixed a layout issue in the form editor for custom field settings assigned the gform_setting_left_half or gform_setting_right_half classes.
- Fixed field labels escaping field container in the form editor.
- Fixed an issue which caused merge tags added by autocomplete to be lost on form save.
- Fixed uppercase characters for save and continue merge tags in Danish translation.
- Fixed an issue with the admin-ajax url for the add field, duplicate field and change input type requests when WPML is active.
- Fixed issue with name field styles on certain scenarios.
API Updates in Gravity Forms v1.9.17
- Fixed an issue with a logging statement for the Web API.
Add-On Framework Updates in Gravity Forms v1.9.17
- Added support for select_custom settings field on the plugin settings page.
- Added Customizer to supported admin_page types for enqueueing scripts.
- Updated select_custom settings field to hide default custom option if custom option is within an optgroup.
- Fixed issue where no other script enqueue rules would run if first rule was a callback.
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!
Share This
Can you go into more detail with regard to,
Added {admin_url} and {logout_url} merge tags for use with User Registration Add-On.
thanks
Be on the look out for the Gravity Forms User Registration Add-On v3.2 release. Those new merge tags will be mentioned in the blog post announcement. It's release is imminent along with the Gravity Forms v2.0 Beta 1 release and some others.
thanks, .
amazed by 5 minute reply. you guys rock!
This auto update crashed our site: Call to undefined function wp_hash()
We have disabled the plugin through FTP, but need to get a fix ASAP!
That is unusual because the wp_hash() function is a core WordPress function. So it should not be undefined because it's a WordPress function and not a Gravity Forms function. Support is not managed via comments. Try downloading the latest Gravity Forms build via the support site and install it via FTP and then activate it. If you still get the error message submit a support ticket our support team can assist you.
I came here too to see what the "Added {admin_url} and {logout_url} merge tags" were all about..
You guys are amazing!
There is more about these merge tags and what they are designed to be used for in the new blog post about the User Registration Add-On v3.2 release. They were designed to be used with the new Login widget in that Add-On.