Gravity Forms v2.0 Release Candidate 1 is now available via the downloads page. If you already have Gravity Forms v2.0 Beta installed you may update via automatic update.

The public release of Gravity Forms v2.0 is imminent. We strongly suggest developers test their customizations and 3rd party add-ons with this release as soon as possible in preparation for the public release via automatic update to all users.

Along with this update we have published documentation for the Gravity Forms field framework. The field framework allows developers to create and manage new field types in Gravity Forms.

This is a major feature release. For a complete rundown of what is new in Gravity Forms v2.0 check out the Beta 1 release announcement.

What’s New in Gravity Forms v2.0 Release Candidate 1

• Added Curaçao to the countries list.
• Added English (South Africa) translation. Credit: Ross McKay.
• Added “gform_form_list_columns” filter for modifying columns of form list table.
• Added “gform_form_list_column_{column_name}” action for displaying a custom column on the form list table.
• Added gform_merge_tag_data filter for modifying data used to replace merge tags.
• Added support for processing object-based merge tags via new $aux_data parameter in GFCommon::replace_variables().
• Added support for passing auxilary data via the $data parameter to notifications in GFAPI::send_notifications().
• Updated Chinese (China) translation. Credit: Edi Michael.
• Updated entry detail page to refresh the cached entry array when an action is performed which includes reloading the entry (i.e. updating the entry).
• Updated English translations (AU, GB, NZ). Credit: Ross McKay.
• Updated GFEntryDetail::maybe_display_empty_fields() to use GFEntryDetail::get_current_entry() if an entry is not passed.
• Fixed an issue with the conditional logic dependency check when configuring a new choice if there is a conditional logic rule based on the field placeholder.
• Fixed an issue with some credit card fields using the old (pre 1.9) inputs configuration which could cause php notices in some situations.
• Fixed caching of the form array for the entry detail page.
• Fixed the init values for the entry filter.
• Fixed an issue with the page navigation textbox on the entry list where the requested page doesn’t load on pressing the enter key.
• Fixed an issue with the entry list when no fields on the form support the entry list page. E.g. List fields.
• Fixed an issue with the merge tags for the Paragraph field.
• Fixed an issue introduced in 2.0-beta-1 where upgrades from some installations of 1.9.x and 2.0-beta-x may not have completed the upgrade of the detail table – long values may still be in the detail_long table.
• Fixed an issue with the width of the Product field quantity input when using the 3 column classes.
• Removed a duplicate gform_admin_pre_render filter from the entry detail page.

API Updates in Gravity Forms v2.0 Release Candidate 1

• Fixed an issue with GFFormsModel::save_lead() where fields hidden by conditional logic get saved when updating an existing entry outside the entry detail context e.g. during submission if the entry had previously been created using the Partial Entries Add-On.

Add-On Framework Updates in Gravity Forms v2.0 Release Candidate 1

• Added GFPaymentAddOn::complete_authorization() to update entry with authorization details.
• Updated GFPaymentAddOn::process_capture() to use GFPaymentAddOn::complete_authorization() if payment was authorized and a capture transaction did not occur.

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