Gravity Forms v2.0 Beta 1 is now available via the downloads page.

This is a major feature release that introduces new features and enhancements to Gravity Forms, the Gravity Forms API and the Gravity Forms Add-On Framework.

Following a similar philosophy as the WordPress core team, we utilize iterative development. Our feature releases introduce new user facing features and functionality while our maintenance releases focus on more developer focused enhancements when new hooks/filters are needed to support Add-Ons, bug fixes and of course security enhancements.

This release also sets the stage for feature add-ons currently in development that will be introduced in the near future.

Keep reading for a quick rundown of the new features and enhancements and we’d love for you to help us beta test the next feature release of Gravity Forms!

Conditional Logic Enhancements

Conditional Logic has been updated and enhanced to support fields it did not previously support. You can now utilize conditional logic on multi-input fields such as the Name Field and the Address Field.

The underlying conditional logic functionality has also been enhanced to make adding support for additional fields and upcoming Add-Ons which will utilize conditional logic easier to implement.

Responsive Admin UI Enhancements

Gravity Forms makes extensive use of core WordPress functionality to display data such as forms and entries. As WordPress has evolved it has introduced new underlying features that we can take advantage of.

We have updated admin interfaces such as the Form List and Entry List to utilize the new responsive table functionality introduced in WordPress. This makes it easier to browse the Gravity Forms admin within the WordPress Dashboard on mobile devices.

Sorting for columns has also been added to tables that did not previously support them, such as on the Forms page that lists all of your Gravity Forms. The WordPress UI Screen Options feature has been implemented in areas such as the Entries page to give you more control over the number of entries that are shown, and the Entry Detail page to configure what metaboxes are displayed.

Just like WordPress does with the UI in the Post Editor, the Entry Detail page when viewing an entry has been updated to support re-arranging metaboxes via drag-n-drop to suit your needs.

The Gravity Forms navigation toolbar has also been updated to adopt the look and feel of the horizontal navigation found within the Themes and Plugin area of the WordPress Dashboard.

Our team will continue to enhance and refine the Gravity Forms admin interface to bring it further in line with how WordPress itself does things to provide users (and their clients) with a consistent user experience within the WordPress Dashboard.

Responsive Form Enhancements

The Gravity Forms markup and styles have been updated to better support mobile devices. We will continue to do so on an iterative basis to limit the disruption this may bring to existing custom styling existing users may have applied via CSS. But some changes will be unavoidable in order to provide a mobile first responsive design philosophy. So be sure to test out the new version with your theme.

reCAPTCHA v2.0

The reCAPTCHA field has been updated to utilize reCAPTCHA v2.0. In order to implement the new reCAPTCHA you will need to update the API keys in the main Settings of Gravity Forms.

Existing sites may continue to use reCAPTCHA v1.0 or switch to v2.0 via Settings, however new Gravity Forms sites will only be able to use reCAPTCHA v2.0 going forward.

Rich Text Editor Field Support

The Paragraph Field and the Post Body Field have been updated to support integrating the rich text editor built into WordPress. You can enable this option via the field settings.

We have limited the available options that are displayed as part of the rich text editor to just the basic controls that would typically be needed. This behavior and the available controls can be customized via hooks.

Accessibility Enhancements

Accessibility is important. It is also hard. We have made enhancements to Gravity Forms to improve upon it’s existing accessibility and will continue to do so on an ongoing basis.

We have also improved the RTL localization support in Gravity Forms for those languages that utilize an RTL format.

Security Hardening

Our team has been hard at work making sure Gravity Forms is as secure as possible. We have made numerous enhancements to the core to further mitigate the potential for vulnerabilities.

These are not critical security issues, any critical vulnerabilities would be patched via public releases and not via a beta release. These are proactive measures to further enhance the security of Gravity Forms as a whole going forward.

Note To Developers

Please be sure to view the changelog below. We have deprecated some developer focused features, and removed backwards compatibility for features in versions of WordPress prior to v3.3. If you have developer Add-Ons or customizations for Gravity Forms, now is the time to be testing.

The complete changelog can be found below.

Gravity Forms v2.0 Beta 1 Changelog

• Added the gform_disable_print_form_scripts filter.
• Added support for the entries per page screen option in the entry list.
• Added support for conditional logic on multi-input fields (specifically Name and Address field).
• Added support for future conditional logic changes where order of various GF JS events can be specified.
• Added sorting on the form list for the entry count, view count and conversion columns.
• Added support for reCAPTCHA 2.0.
• Added support for Rich Text Editor on Paragraph and Post Body fields.
• Added the gravityforms_cron daily task. Performs self-healing, adds empty index files, deletes unclaimed export files and deleted orphaned entries.
• Added new filter: gform_addon_feed_settings_fields.
• Security enhancement: Updated the confirmation message to pass through wp_kses_post() before being displayed after submission and before being saved in the form confirmation settings. Use the gform_sanitize_confirmation_message to disable. Validation will fail for users with the unfiltered_html capability if the gform_sanitize_confirmation_message filter returns true and a ‘fix it’ button will be displayed.
• Security enhancement: Hardened security within the admin pages.
• Security enhancement: Updated the sanitization of form and field settings to check the unfiltered_html capability before allowing unfiltered html.
• Security enhancement: Updated fields to ensure that values are sanitized before saving.
• Security enhancement: Fixed potential information leakage in the entry detail and results pages.
• Security enhancement: Fixed the encoding of the form confirmation settings.
• Accessibility enhancement: Added alternative content for AJAX form iframe.
• Accessibility enhancement: Added ARIA invalid and required attributes to donation, email, hidden, name, number, password, phone, post custom field, post excerpt, post tags, post title, price, select, text, textarea and website fields.
• Accessibility enhancement: Fixed an accessibility issue with list field when styling was called with an inline element.
• Accessibility enhancement: Fixed an accessibility issue with onkeypress attributes not accompanying onclick attributes.
• Styling enhancement: Improved RTL support.
• Styling enhancement: Improved responsive/adaptive support.
• Styling enhancement: Improved vertical alignment.
• Updated the payment results to display results for days with zero results when date range is not set.
• Updated form editor to display placeholder content all fields have been removed.
• Updated multi-page form validation. If any invalid fields are found when submitting the final page of a form, the form will jump to the first page with an invalid field.
• Updated the form list and entry list to use WP_list_Table.
• Updated the entry detail page to display the Entry Info, Notifications and Notes boxes as WordPress meta boxes. Added support for screen options.
• Updated the value column in the lead_detail table to longtext to fix an issue with entry search.
• Updated the form admin toolbar styles.
• Updated the form switcher and the page titles for form-specific pages.
• Updated the entry search filter styles to display the filter below the entry list on smaller screens.
• Updated GFCommon::is_valid_email() to use is_email() instead of the PHP FILTER_VALIDATE_EMAIL Filter. Use the is_email WordPress filter to adjust behavior.
• Updated the settings page to use the GF_MIN_WP_VERSION constant as the minimum WordPress version.
• Updated the tooltips so they stay open as long as the mouse is hovering.
• Updated GFCommon::get_product_fields() to improve performance when saving the product info meta.
• Updated the way GFFormsModel::save_lead() handles a failure to save the entry to the _rg_lead table.
• Fixed an issue with the base URL in the Web API developer tools UI.
• Fixed the inconsistent widths in the page content below the toolbar.
• Fixed an issue with the styles on the entry detail page for narrow screens.
• Fixed an issue with the form settings pages where the non-minified version of the admin.css file is loaded instead of the minified file.
• Fixed JavaScript error on form preview page caused by viewport meta tag value.
• Fixed missing label attribute in date field.
• Fixed “_wrapper” not being appended to all custom form CSS classes when more than one CSS class was provided.
• Fixed an issue with the export page where large numbers of entries may cause the export process to hang.
• Deprecated GFFormsModel::get_field_value_long().
• Deprecated array access to the field object. Use the object operator instead e.g. $field->id instead of $field[‘id’]. The deprecation notice will be triggered only once.
• Removed backwards compatibility for Thickbox for versions of WordPress prior to 3.3.
• Removed backwards compatibility in GFCommon::replace_variables_prepopulate() for versions of WordPress prior to 3.3.
• Removed caching from GFFormsModel::get_lead_field_value().
• Removed styling for “Add Form” button for versions of WordPress prior to 3.5.
• Removed textarea fallback for the visual editor for versions of WordPress prior to 3.3.

Gravity Forms API Changelog

• Added “less than or equal” to the list of supported operators in the entry search.

Gravity Forms Add-On Framework Changelog

• Added aliases support to field select settings field to recommend the default field choice based on field label.
• Added $_supports_feed_ordering property to GFFeedAddOn. When enabled, users can sort feeds on the feed list page to determine what order they are processed in.
• Added Customizer to supported admin_page types for enqueueing scripts.
• Security enhancement – Added value checks to the validation of radio, checkbox, select, select_custom, text, textarea, field_select, checkbox_and_select and feed condition settings. Added “fix it” buttons.
• Updated Add-On feed table schema to support feed ordering.
• Updated GFFeedAddOn::maybe_process_feed() to update entry object if the returned value from the GFFeedAddOn::process_feed() call is an array that contains an entry ID.
• Updated all protected methods in GFAddOn, GFFeedAddOn and GFPaymentAddOn to be public methods.
• Fixed issue where no other script enqueue rules would run if first rule was a callback.
• Fixed an issue with the payment results page summary, chart and table where transactions are ignored if they don’t complete before midnight on the same day the entry is submitted.
• Fixed an issue where add-on framework tables don’t get deleted when a site is deleted in multisite.

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