GravityForms 2.0 Released Featuring reCAPTCHA 2.0, Security Hardening, and More

After more than a year in development, Gravity Forms 2.0 is available for download. This release contains a number of new features and developer enhancements.

Conditional logic is now supported by more fields and can be used on multi-input fields such as Name and Address. The underlying code contains improvements that provide the foundation for upcoming Add-ons that will utilize conditional logic.

Conditional Logic Support Added to the Name Field
Conditional Logic Support Added to the Name Field

GravityForms 2.0 uses responsive table elements that are built-into WordPress on the form list and entry list screens making the GravityForms admin easier to browse on mobile devices. Column sorting has also been added to tables such as the forms page.

Responsive Table Listings
Responsive Table Listings

A screen options drop-down menu is available on pages that have multiple listings to give users more control over how many entries are displayed at once. The GravityForms toolbar design has also been updated to match the horizontal navigation menu found within the Themes and Plugins area of the WordPress backend.

Screen Options UI Added to The Form Listings Screen
Screen Options UI Added to The Form Listings Screen

The reCAPTCHA field now utilizes reCAPTCHA 2.0. Users who want to take advantage of this anti-spam feature need to update their API keys on the GravityForm’s settings page. However, during testing, I noticed the API keys I configured a few years ago didn’t need to be updated and I was able to add a reCAPTCHA 2.0 field to my forms.

reCAPTCHA 2.0 Support in GravityForms 2.0
reCAPTCHA 2.0 Support in GravityForms 2.0

Last but not least, GravityForms 2.0 contains a number of security hardening enhancements. Carl Hancock, Co-Founder of Rocketgenius says, “The security improvements are a direct result of multiple third-party code reviews and security audits.”

Developers are encouraged to read the full changelog as a few deprecated features and backwards compatibility items have been removed. GravityForms 2.0 is available for new customers and those who manually update. Existing customers will be able to automatically update to 2.0 next week.

13 Comments


  1. Still no native support for Custom Post Types? :(

    Report


    1. Post creation wasn’t the focus of this release. But enhanced post creation functionality is something that is in development. It’s not something we want to solve with the existing Post Fields that are in Gravity Forms. We have something much better in the works.

      Report


      1. I get that Carl.

        As your loyal fan with a Dev license, the one thing that really keeps nagging at me is the non-native support of custom post types.

        I have a license to Formidable Forms as well and the thing that kept me going on using GravityForms is loyalty.

        Eventually you’d really have to put in CPTs and it should be soon. That’s the major thing that you don’t that is sending people to your competitors.

        So all in all, hopefully it’s soon :)

        Report


      2. We have been in no rush to add CPT support because it’s already available to Gravity Forms users in the form of a 3rd party add-on in the wordpress.org repository and has been for a long time.

        See:

        https://wordpress.org/plugins/gravity-forms-custom-post-types/

        There are a TON of 3rd party Gravity Forms Add-Ons freely available in the WordPress.org plugin repository. Far more than we provide as first party add-ons.

        We try to avoid stepping on the toes of 3rd party developers when possible, otherwise it would deter people from developing add-one for Gravity Forms which we do not want and our users do not want.

        However, sometimes it does happen. It has in a few other instances and will eventually with the custom post type support.

        We don’t prioritize features to market because our competition has them. If there is a feature that we haven’t added but have said we will be it’s typically due to the fact what we have planned for the feature is bigger than what the user is anticipating. We do it on our terms.

        In this case the 3rd party add-on is actually one that who’s developer also happens to be a Gravity Forms core developer.

        There is an entire worked of Gravity Forms Add-Ons available freely in the WordPress.org plugin repository. Page after page of add-ons of you search for Gravity Forms in the repository. There are also a lot of commercial add-ons for Gravity Forms. We have the largest ecosystem of 3rd party add-ons of any WordPress forms plugin available.

        If there is something we don’t do as a core feature or an official add-on there is likely a 3rd party add-on that already exists and many times it is freely available on the WordPress.org plugin repository.

        Report


  2. Technically it hasn’t been a year in development. What has changed is our versioning methodology.

    Previously we purposely didn’t increment the version to 2.0 despite the fact some 1.9.x releases (of which there were many over the last year) included features as well as maintenance, bug and security patches. This is why the current 1.9.x release is 1.9.19.6.

    We’ve changed how we are handling version numbers going forward. Feature releases will be vX.X, maintenance releases will be vX.X.X and interim builds (a bit like WordPress nightly builds) are vX.X.X.X.

    Only maintenance releases and feature releases are deployed via automatic update. Interim builds are only available via our support site until it’s pushed out via automatic update.

    So the next feature release will be 2.1, then 2.2 and so on. Which is more in line with how WordPress does things from a versioning standpoint.

    Report


    1. I arrived at my conclusion because the 1.9 release post was published in January 2015. Using that logic, I figured 2.0 was in development for at least a year and a half. You know more about GravityForms development than I do :) I do like the new versioning structure which is similar to WordPress’. Makes things easier on me.

      Report


      1. Yep, the versioning was confusing. Exactly why we stepped back and changed it :)

        Report


  3. Congratulations to you Carl and all the team behind this! There is quit extensive changes and new features in the add-on framework, does this mean that all the official add-ons will receive an update too?

    Report


    1. All of our own Add-Ons have been migrated to use the Add-On Framework. The updates to the Add-On Framework in Gravity Forms v2.0 are primarily for planned updates to existing add-ons, new add-ons that are in active development, and feedback from the 3rd party developer community.

      So we won’t be releasing updates for all of our Add-Ons specifically due to the release of GF 2.0 but there will be Add-On updates coming related to new features as well as entirely new Add-Ons that we will be releasing.

      We do have something else in the works that will require releasing all of our existing Add-Ons but I won’t let that cat out of the bag just yet… :)

      Report


  4. A repeater field would be a great feature in core.

    Report

Comments are closed.