News & Updates -

Gravity Forms v1.9 Beta 4 Released

Carl Hancock By Carl Hancock Published November 24, 2014

Gravity Forms v1.9 Beta 4 is now available via automatic update and the customer downloads page. Automatic updates will only occur if you are already running a beta version of Gravity Forms v1.9.

Gravity Forms v1.9 is a major feature release and we would like as many people as possible helping us test these beta releases. We’ll even give you swag and an extension of your license for doing so! Check out this blog post for more information.

For support issues or bug reports for Gravity Forms v1.9 Beta 3 please submit your request via the Beta Support request form.

For a complete rundown of everything that is new in Gravity Forms v1.9 please see the Beta 1 Release Announcement.

What’s New in Gravity Forms v1.9 Beta 4

  • Deprecated GFCommon::get_us_states() and GFCommon::get_canadian_provinces().
  • Added shortcode preview in the post/page editor visual editor. The preview is disabled by default. Use the gform_shortcode_preview_disabled filter to enable.
  • Added support for ‘gform_file_upload_markup’ JS and PHP hooks; useful for modifying the multi-file upload “preview”.
  • Added the gform_incomplete_submissions_expiration_days filter to allow the lifetime of saved incomplete submissions to be customized.
  • Added change event when updating value of total input.
  • Added “Processing” as an option for payment status when adding conditional logic rules.
  • Added support for rendering forms in admin pages with the gravity_form() function and the gravityform shortcode. Use in conjunction with gravity_form_enqueue_scripts().
  • Added support for retrieving form markup via ajax.
  • Updated GFCommon::replace_variables_prepopulate to support replacing custom merge tags via the ‘gform_replace_merge_tags’ hook.
  • Updated set_logging_supported function to be public instead of protected.
  • Updated Spanish translation (94% done).
  • Updated register strings with URLs in them to be able to be translated properly.
  • Updated trim_conditional_logic_values_from_element function to handle when the element’s class is GF_Field.
  • Updated merge tag list to exclude credit card field options, except the credit card number (last 4 digits) and credit card type for Confirmations and Notifications.
  • Updated notification’s From Name and Subject to use the Text version of merge tags.
  • Updated notification’s From Name so that it is sanitized before being used.
  • Fixed notices generated by logging statements for add-ons that don’t have a feedName field.
  • Fixed a backwards compatibility issue with GF_Field.
  • Fixed backwards compatibility issue with GFFormsModel::get_field().
  • Fixed issue when exporting custom post fields of type “checkbox”.
  • Fixed php warning (js error for AJAX forms) for confirmation query strings containing new lines.
  • Fixed an issue with the entry list filter, results page filters and export conditional logic where number field values would be treated as strings by the entry search query.
  • Fixed issue with conditional logic and the gf_inline class.
  • Fixed XSS vulnerability.
  • Fixed an issue with the date field where required validation can fail incorrectly for date field and date drop-down input types.
  • Fixed an issue with the time field where required validation can fail incorrectly.
  • Fixed an issue with the time field where the default am/pm value is ignored if upper case.
  • Fixed an issue with the entry detail page resend notifications box to display only notifications assigned to the form submission event. This removes the save and continue notifications.
  • Fixed issue where entry exports were saved with a .txt extension in Safari.
  • Fixed backwards compatibility issue with GFCommon::replace_variables().
  • Fixed security vulnerability with the file upload field for some server configurations.
  • Fixed the remove button for the multiselect field with enhanced UI.
  • Fixed an issue when updating entry with conditional logic fields via the gform_entry_id_pre_save_lead.
  • Fixed an issue with the id attribute for the address field city label.
  • Fixed an issue with the email field where the confirmation input doesn’t maintain its value when when recovering a saved submission and when changing pages in a multi-page form.
  • Fixed notices on form import generated by use of get_class().
  • Fixed issue with delete_password() function modifying entry that was changed via hooks during submission.
  • Fixed issue with {ip} merge tag return incorrect IP when re-sending notifications.
  • Fixed an issue with the product field in the form editor where the size setting is not displayed when the user-defined price field type is selected.
  • Fixed an issue with the {pricing_fields} merge tag and text format notifications.
  • Fixed a backwards compatibility issue with GFCommon::get_lead_field_display().
  • Fixed tabindex issue with selects hidden by conditional logic.
  • Fixed issue with “Form” not showing up under the “New” menu in the admin bar on the frontend.
  • Fixed an issue with total field change event which could trigger infinite loops.
  • Fixed an issue with the address field incorrectly failing validation when the field is required, the copy values setting is enabled and activated and the source address field is not required but does contain a complete address.

Add-On Framework Updates in Gravity Forms v1.9 Beta 4

  • Fixed issue where feed saved successfully message still displayed when fields failed validation.
  • Fixed an issue with the URL for the add-on settings tab.
  • Updated feed field mapping to exclude credit card field options, except the credit card number (last 4 digits) and credit card type as choices.
  • Added support in the results page for score averages by row in multi-row Likert fields.
  • Fixed issue causing feeds not to get created when updating add-ons to the framework version.

API Updates in Gravity Forms v1.9 Beta 4

  • Fixed an issue with GFAPI::update_entry() where empty values are ignored when specifying a different entry ID to the ID in the entry array.
  • Added update_entry_field() to allow updates of individual entry fields.

You can update to the latest version of the Gravity Forms v1.9 Beta using Automatic Update IF you are already running a v1.9 Beta release. 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.

If you have not yet installed the Gravity Forms v1.9 Beta you can download the latest beta release from the Downloads page.

Please Note: Automatic Update will only work if you have correctly entered your License Key in the Settings page of Gravity Forms in your WordPress Dashboard.
Don’t own Gravity Forms yet? What are you waiting for?! Purchase a copy today!