Author 诗语

Viewing Poll Results

Where can I see the Poll Results?Poll Results DisplayNoteResults FilterResetting Poll Results

Where can I see the Poll Results?

As a site administrator, you can view results from a poll by navigating to the Form with the poll in it, and clicking the Poll Results link at the top of the form editor. Poll results can be viewed either through the form builder or the Entries page.

Poll Results Display

Within this page, you will see the current results for your particular poll. In the right sidebar, you also have the ability to set filter conditions to further slice your poll data.

Poll results can be displayed to visitors of your site via the Poll Shortcode

Note

If you delete a poll field from your form the poll data will be irreversibly deleted as well.

Results Filter

The filter section displayed in the right hand sidebar allows you to limit which entries are included in your results display.

Include results if allows you filter the entries that make up your results display, based on criteria such as the content of a particular form field, or other submission metadata.

Start date and End date limit your results display to those submission made within a certain date range.

Resetting Poll Results

You can learn about resetting results by reading this article.

Using the Signature Add-On

IntroductionPre-RequisitesConfiguring the Signature FieldEntry DetailsHow Does It Work?

Introduction
The Signature Add-On for Gravity Forms allows you to capture signatures online by allowing users to sign your forms using touchscreen devices, touch pads, or a mouse by adding a new field to the Advanced Fields toolbox in the Form Editor.
Quickly and easily integrate signature capabilities into your forms without the end user having to install any special browser plugins.
With the Gravity Forms Signature Add-On you can provide a very simple user interface for allowing users to sign your forms online. It captures signature information as it is drawn and sends data to your web server where this information is converted into a PNG image and stored on your server. This happens on-the-fly as soon as the user signs the field canvas.
The Signature Add-On works on all major desktop and mobile browsers. This includes IE, FireFox, Safari, Chrome, Opera, iOS, Android, Blackberry, and WebOS.
Pre-Requisites
Setup the Signature Add-On
Configuring the Signature Field
After installing the Signature Add-On you will see a new field type added to the Advanced Fields toolbox in the Form Editor when creating or editing a Gravity Form.

In your WordPress admin dashboard, go to New Form under the Forms navigation or edit an existing form from Forms.
Add a Signature field to your form from the Advanced Fields toolbox.
Edit this new Signature field and configure the field options to your liking. Under Appearance you can change the color, size, background, border, and style.
Save your form.
Capture signatures!

Entry Details
When you view the Entry Details for a Form Entry that contains a Signature field, you will see the signature included in the entry details. The signature will be presented as a thumbnail image and you can click on the thumbnail to see the full size version of the signature itself.
For security reasons it is not automatically included as part of the {all_fields} merge tag output. You can include signatures in your email notifications by inserting the merge tag for your Signature field in the message of your notification.
How Does It Work?
The Gravity Forms Signature Add-On is powered by the well established signature capture software SuperSignature. The SuperSignature technology and source code has been licensed by rocketgenius, inc. for redistribution as an official Gravity Forms Add-On.

Using the Quiz Add-On

IntroductionPre-RequisitesOverviewAdding a Quiz FieldDefine Quiz Field SettingsConfigure Your Form-level Quiz SettingsDisplay Your QuizQuiz ResultsQuiz Merge Tags

Introduction

The Gravity Forms Quiz Add-On allows you to quickly create quizzes that are automatically scored and graded when the form is submitted.

The Quiz Add-On provides the special Quiz Field which is the building block of your quiz. A quiz to be graded either on a simple Pass/Fail scale or using a letter-grade system that you can customize. And remember, the Quiz Add-On allows you to add as many Quiz Fields as you would like to ANY form you choose!

Pre-Requisites

Download and install the Quiz Add-On (you may require the appropriate type of Gravity Forms license to access the add-on, refer to this page).Have a target form ready for where your quiz will go.

Overview

To get a quiz up and running, you will need to complete the following steps:

Add a quiz field to your form.Define all the required settings for your Quiz fieldRepeat steps 1 and 2 to add all the Quiz fields you require.Configure the form level quiz-related settings you want. Embed your Quiz form on a page or post. Check the Quiz results

Once you have your form with Quiz fields up and running, your attention will shift to

Adding a Quiz Field

If you have met the pre-requisites, the Quiz field is available under the Advanced Fields section within the Field Library on the Form Editor. Drag it onto the Layout Space.

Define Quiz Field Settings

The Quiz field comes with a lot of settings to help you define different question types, answer scoring and the behaviors. Refer to the Quiz Field User Guide for a full list of the available settings.

Configure Your Form-level Quiz Settings

There are form level settings that control the behavior of all quiz fields on your form.

Such as randomizing the presentation of quiz questions, and what type of grading you would like to use. When you add a Quiz Field to your form, a new section will automatically be added to the Form Settings that introduces Quiz Settings related to grading. Visit the Configure Quiz Settings article for details.

Display Your Quiz

The Gravity Forms Quiz Add-On offers a few methods to display your quiz form, such as the standard form shortcode, function, and a widget. Check out this list of articles for more information on adding a form to your site.

The Quiz Confirmation messages that you configure in the Quiz Settings will automatically be displayed after the Form Confirmation message when the form is submitted.

Quiz Results

This article reviews quiz results and where to find them.

Quiz Merge Tags

You can view quiz-specific merge tags in this article. For more information on the general use of merge tags, refer to these articles.

Viewing Quiz Results

Where can I see the Quiz Results?Quiz Results DisplayResults FilterQuiz ScoringResetting Results

Where can I see the Quiz Results?

As a site administrator, you can view results from a quiz by navigating to the Form with the quiz in it, and clicking the Quiz Results link at the top of the form editor.

If you have multiple Add-Ons installed that support results, you will need to hover over the 「Results」 item and then select 「Quiz Results」.

Quiz Results Display

The quiz results are divided into a few sections within a dashboard style layout. What data you see is also dependent on which type of Quiz Grading you have enabled.

SectionDescriptionTotal EntriesQuantity of all the entries you have received for this quiz.Average ScoreAverage score as calculated across all entries received. Average PercentageAverage percentage score as calculated across all entries received.Score FrequenciesDisplays a frequency bar chart showing the spread of each quiz score. Grade FrequencyIf using letter grades, will show the frequency of each letter grade across all entries received. Individual BreakdownsThe bottom area shows each quiz field on your form, and the frequency of each answer provided.

Results Filter

The filter section displayed in the right hand sidebar allows you to limit which entries are included in your results display.

Include results if allows you filter the entries that make up your results based on other factors, such as a particular form field, or other submission metadata. For example, you could filter just those of a certain Quiz Percentage or Grade.

Start date and End date limit your results display to those submission made within a certain date range.

Quiz Scoring

Under normal scoring, a correct answer counts as 1, and an incorrect answer as 0. As such, the percentage will be the percentage of correct answers.

When using weighted scoring, you can specify different scores for each possible answer. For example, you could make one question worth 3 points for the right answer, or even make wrong answers be a negative score. This has a significant effect on scoring, especially when adding checkboxes (multiple choice) into the quiz.

Refer to our guide to Quiz Scoring for the complete rules and some detailed examples.

Caveat: Quiz results are calculated dynamically on request, As such, if you change the correct answer (or the weighted score) on a question, all past Quiz Results will be re-calculated when viewed again, which may vary from what was previously presented in the results dashboard, or to the user at the time they completed the quiz.

Resetting Results

You can learn about resetting results by reading this article.

Using the Square Add-On

IntroductionPrerequisitesSetup SquareSetup Your FormSetting up a Square FeedViewing Sales ResultsImportant NotesSquare Add-On HooksAdd-On Framework Hooks

Gravity Forms and Square are offering a 「Free Processing Promotion」 for new Square customers that can save you credit card fees for up to 180 days. Go here for details.
Introduction
The official Gravity Forms Square Add-On allows you to quickly and easily capture one-time credit card payments with WordPress and your Square account.
Prerequisites

You will of course need Gravity Forms and the official Gravity Forms Square Add-On installed and activated.
SSL Certificate Installed and Configured
A Square account (a Square Sandbox account is also recommended, but optional)

Because of the secure nature of capturing credit card information, you will be required to install an SSL certificate on your web site if you have not already done so. You will also need to configure your WordPress site to work properly with SSL.
Contact your web host if you need assistance purchasing and configuring an SSL certificate.
If you need assistance configuring your WordPress site to work with SSL, we recommend the WordPress HTTPS (SSL) Plugin which you can find here: http://wordpress.org/extend/plugins/wordpress-https/
Setup Square
Learn how to setup the Square Add-on in our Setting Up the Square Add-on article.
Setup Your Form
Refer to the Setting up a Square Compatible Form article for detailed instructions on how to setup your form to be compatible with the Square Add-on.
Setting up a Square Feed
Now that you have configured the Square Add-on to work with your Square account, and you have a form configured, it』s time to bring it all together by configuring the form to send it』s submissions to Square. Just like all of our Gravity Forms Add-ons, this is done by creating a feed.
Review our Creating a Feed for the Square Add-on article for step-by-step instructions.
Viewing Sales Results
After creating a feed and making your first sale, you can view the results on the Sales Results page.  Review Viewing Sales Results article for more information.
Important Notes

The currency setting for your Square Account must match your Gravity Forms Currency Setting. if not matched, you will get an error when you attempt to connect to your Square account.

Square Add-On Hooks
The Square Add-On provides hooks that can be used to modify the default functionality or extend it. For more information, review the Square Add-On Hooks.
Add-On Framework Hooks
Because the Square Add-On is built using the Add-On Framework it also inherits any hooks available in the framework methods it uses such as:
gform_{$SHORT_SLUG}_field_value for changing a field value before it is passed to Square.

Using real form entries as Zapier test data

SummaryBackgroundCode Snippet

Summary
This article provides a code snippet that you can use to fetch actual form submissions from your entries table to see when you are testing out your Zapier Zap. This is to address a need that some Zapier users have requested with the release of the official Gravity Forms Zapier Add-On v4.
Background
It may seem like this ability existed before version 4, but in actual fact it was a somewhat happenstance. There was no way for Zapier to fetch sample data on demand so they listened for it instead. The Gravity Forms Zapier Add-On would send sample data to the zap URL when you saved the feed or when you saved changes to the form.
While the integration was never designed to use form submissions (entries) as sample data it was possible that if the form happened to be submitted at the time Zapier was listening for the sample data they would also pick up the real entry data as well.
The new version of the Gravity Forms app that is available on Zapier.com does not listen for incoming sample data. We have setup a registered API endpoint where the app can request the sample data on demand, but both the Zapier app and Gravity Forms add-on require updates to utilize it. This code snippet is a work around in the meantime.
Code Snippet
Add this to your theme』s functions.php file, or within any custom functions plugin you may be using.
This code snippet will override the response of the REST API request which gets the sample data with the latest real form entry.
/**
* Replaces the Gravity Forms Zapier sample entry response with the latest real entry, if available.
*
* @param WP_REST_Response $response The response to be returned.
* @param WP_REST_Server $server The current instance of the REST API server.
* @param WP_REST_Request $request The request which is currently in progress.
*/
add_filter( 'rest_post_dispatch', function ( $response, $server, $request ) {
if ( ! function_exists( 'gf_zapier' )
|| $response->get_status() !== 200
|| $request->get_method() !== 'GET'
|| empty( $request['form_id'] )
|| $request->get_route() !== "/gf/v2/forms/{$request['form_id']}/sample-entry"
|| ! GFAPI::current_user_can_any( 'gravityforms_view_entries' )
) {
return $response;
}

$entries = GFAPI::get_entries( $request['form_id'], array( 'status' => 'active' ), array(), array( 'page_size' => 1 ) );
if ( empty( $entries[0]['id'] ) ) {
return $response;
}

$form = GFAPI::get_form( $request['form_id'] );
$feed = array( 'meta' => array( 'adminLabels' => false ) );

return rest_ensure_response( gf_zapier()->get_body( $entries[0], $form, $feed ) );
}, 10, 3 );

If you need the entry data to use the field admin labels change 'adminLabels' => false to 'adminLabels' => true.

Updating or Adding A Payment Method

Introduction「Payment Method Expiring」 WarningHow do I update my payment method?Screenshots

Introduction

Each license you own is linked to one subscription, which is linked to one payment method. Payment methods are not stored or managed as part of your account, but as part of the license. As such, they are updated in the Licenses section of your account area. You must enter the payment method each time you complete a new subscription, and from that point on renewals will be handled automatically using the on-file payment method for that license.

「Payment Method Expiring」 Warning

Our billing system will email you when your card is about to expire. Additionally, we will email if an attempt to renew your license fails. In that case, you have a few extra days to update the payment method before the system will retry again. Don』t delay! If you fail too many renewal attempts, your license key will be canceled and cannot be restarted!

If you stored a credit card on multiple licenses subscriptions, note that you will have to update each one separately by repeating the process below for all such licenses.

How do I update my payment method?

Rocketgenius (the team behind Gravity Forms) does not store details of your payment method.
We use industry leading secure payment gateways and processors that utilize verified tokens for passing around subscription purchase approvals. All pages where payment method details are requested are hosted directly by the payment processor. In this way, your credit card numbers and PayPal credentials are not stored by us, not exposed to any of our employees, and are not transmitted through our servers. All that is shown as part of your account is incomplete details, such as the first and last credit card numbers.

Log in to your Gravity Forms account page, select the license you would like to manage then click the Manage License button.Each License is linked to its own payment method. Look for the Update option listed after the next payment date.To switch payment method between card or Paypal, click Change Payment Method. If you have no payment method attached to your license, the button will say Add Payment Details. Complete the form for the payment method chosen and click Update.

You will need to complete this process separately for each license that you want to update, even if the card is the same on multiple licenses.

Screenshots

Manage License option

Add payment details action.

User Registration Change Log

4.9 | 2021-10-214.8 | 2021-04-284.7 | 2021-01-284.6 | 2020-09-304.5 | 2020-05-144.4 | 2019-09-254.3 | 2019-08-074.2 | 2019-07-104.1 | 2019-05-154.0 | 2018-12-193.9 | 2018-01-293.8 | 2017-10-263.7 | 2017-02-203.6 | 2017-01-053.5 | 2016-11-043.4 | 2016-08-313.3 | 2016-04-193.2 | 2016-03-083.1 | 2016-01-273.0 | 2016-01-202.0.2 | 2014-12-082.0.12.0 | 2014-11-051.9 | 2014-05-291.8 | 2014-03-311.7 | 2013-09-051.6 | 2013-06-191.5 | 2013-04-011.4 | 2012-03-271.3 | 2012-02-091.2.11 | 2011-11-011.2.101.2.9 | 2011-10-031.2.81.2.71.2.6.31.2.6.21.2.6.1 | 2011-07-201.2.6 | 2011-07-161.2.51.2.41.2.31.2.21.2.1 | 2011-04-291.2 | 2011-04-271.11.0 | 2011-03-231.0.beta5.31.0.beta5.21.0.beta5.11.0.beta51.0.beta41.0.beta3.21.0.beta31.0.beta1

4.9 | 2021-10-21

Fixed a typo in the text domain.
Fixed an issue that prevented the login widget from saving in the block-based widget editor.
Fixed an issue that prevented the sorting of files in the multi-file upload field.
Fixed an issue where Multi-File Upload fields don't correctly map to user meta values.
Fixed an issue where the login form was not styled correctly when using Gravity Forms 2.5.
Fixed an issue where the {set_password_url} merge tag can output an invalid URL on multisite.
Fixed an issue where user-submitted data doesn't get saved to the profiles of users activated via BuddyPress or BuddyBoss.

4.8 | 2021-04-28

Fixed an issue with untranslated strings on the activation page.
Fixed an issue where the values of BuddyPress fields that are mapped to form fields are not saved on user activation.
Fixed a fatal error which can occur during user activation.
Fixed an issue where the add-on icon is missing on the form settings pages in Gravity Forms 2.5.

4.7 | 2021-01-28

Fixed user permissions so users with the promote_users capability can now view the Pending Activations screen.
Fixed an issue where script tags were being output above document head element.
Fixed styling issues on the Pending Activations screen in Gravity Forms 2.5.
Fixed an issue where both success and error message where displayed when activating a user from the Pending Activations screen.
Fixed a typo in the tooltip for the Password setting on the feed configuration page.
Fixed an issue where MySQL throws an error on Entry Detail and Pending Activations screens.
Fixed an issue where the login form does not display non-standard authentication errors.
Fixed a fatal error which occurs on form population if the Consent field is mapped on the Update feed and the entry which last updated or created the user has been deleted.

4.6 | 2020-09-30

Added translations for Japanese.
Added support for Gravity Forms 2.5.
Updated the activation page query string to use the "gfur_activation" parameter instead of "page" to fix an issue with WordPress 5.5 where a 404 not found error occurs. Existing activation links will automatically redirect to the new page.
Fixed an issue where the password can fail validation on login if the user object is cached when the user is created and feed processing is delayed by the user activation feature or a payment add-on such as PayPal Standard.
Fixed an issue where the set password URL included in the notification sent on the user is activated event becomes invalid when the user is activated via the front-end activation page.
Fixed a validation error which occurs when using the update type feed and the submitted email address uses a different case to the users current email.
Fixed an issue that prevents the dropdown to select notification type in the "Send Email?" setting of a create user feed from displaying in certain situations.
Fixed an issue during user update for passwords containing quotes which results in a password validation error on login.
Fixed an issue during user creation for passwords containing quotes which results in a password validation error on login.
Fixed an issue where feed processing aborts early when the activation feature is enabled and the gform_user_registration_validation and gform_user_registration_check_email_pre_signup_activation filters are being used to allow multiple accounts to use the same email address.

4.5 | 2020-05-14

Added security enhancements.
Added translations for Hebrew, Hindi, and Turkish.
Added gform_user_registration_pending_activation_expiration filter that allows the expiration period for the pending activation users to be overridden.
Added support for sending notifications when the pending activation is deleted.
Updated the settings on the feed configuration page. See Creating a Feed for the User Registration Add-On for the available settings.
Updated the new user emails to be sent by wp_new_user_notification() instead of gf_new_user_notification().
Updated the default activation page template.
Updated Javascript files, stylesheets to use minified versions.
Fixed an issue introduced in v4.4.6 where WordPress does not send the new user email for new feeds.
Fixed a database error on multisite installations related to the WordPress signups table.
Fixed a notice with PHP 7.4 when creating a new feed.
Fixed a PHP notice being displayed when a custom meta value is not a string.
Fixed a PHP compatibility warning in PHP 7.1+ when getting the set password URL due to using $this within a plain function.

4.4 | 2019-09-25

Added support for Stripe Checkout to display the "User Registration Options" section in the feed.
Fixed an issue where a site cannot be updated when the subscription is canceled on a multisite install.
Fixed a PHP warning which occurs when an invalid form ID is used with the gravityform shortcode.

4.3 | 2019-08-07

Added security enhancements.

4.2 | 2019-07-10

Added security enhancements.

4.1 | 2019-05-15

Added gform_userregistration_associate_entry_with_user filter to add change if newly created user should be set as entry creator.
Updated minimum Gravity Forms version to 2.2.6.
Updated feed settings to display Set Post Author setting when form has Advanced Post Creation feeds.
Updated Login widget to set logout redirect to current page when logout redirect URL setting is left empty.
Fixed entry not being associated to newly created user when submitter is not logged in.
Fixed an issue with pending activation for duplicate emails.
Fixed PHP notice after Gravity Form 2.4.7 adding tab capabilities check.
Fixed an issue preventing the personal data retention policy from deleting entries.
Fixed an issue that the consent field didn't reflect user metadata correctly.
Fixed an issue populating checkbox fields from BuddyPress checkboxes types fields when processing the update type feed on form display.
Fixed issues processing multi-select fields when mapped to BuddyPress multi select box fields during submission for both feed types and on form display for the update type feed.
Fixed a PHP 7.3 warning when the update type feed is populating the form and it contains a file upload field.

4.0 | 2018-12-19

Added support for data retention in Gravity Forms 2.4.
Fixed an issue with login widget when using special characters in password.
Fixed an issue where the username, email, and password fields may not be validated on multi-page forms if the feed conditional logic is not met when the page containing those fields is submitted.
Fixed a deprecated function notice with PHP 7.2 when processing update type feeds on form display.
Fixed BuddyPress overriding the role after the user is created.
Fixed text domains for string translations.
Fixed the user_nicename being saved to the _usermeta table instead of the _users table.
Fixed an issue with the login form submission when the password contains the less than character.
Fixed a fatal error which occurred if the GFFormDisplay class is not available when getting the login form HTML.
Fixed an issue introduced in 3.9 which prevents the Pending Activations from being listed when the database tables are utf8 encoded instead of the newer utf8mb4.

3.9 | 2018-01-29

Added support for Gravity Forms 2.3.
Added GPL to the plugin header.
Added the "Preserve current email" choice to the email address mapping drop down on the update type feed.
Updated URIs in plugin header to use https.
Updated username validation message to match WordPress' equivalent validation message.
Updated strings in pending activations so they could be translated.
Fixed an issue which can prevent pending activations from being listed due to collation mismatch after installing the add-on after upgrading MySQL from 5.5 to 5.6.
Fixed a PHP warning related to the login form/widget logged in/out links.

3.8 | 2017-10-26

Added gform_userregistration_login_form filter to allow modifying the login form object.
Added gf_login_form class to login form wrapper.
Added validation error message to login form when an invalid email address is used.
Updated user meta shortcode to retrieve multiple user meta items when output is set to CSV or list.
Fixed multi-input field not being populated, in some situations, when processing update type feeds on form display.
Fixed issue where $user_id returned by gform_user_registration_update_user_id filter was not respected when updating a user.
Fixed a fatal error which could occur with PHP 7.1 when using a login widget without logged in and/or logged out links.
Fixed a fatal error which can occur when getting the BuddyPress fields.
Fixed a notice which could occur with PHP 7.1 during update type feed processing on form display when populating Checkbox fields.
Fixed an issue populating Multi Select fields created with Gravity Forms 2.2+ when processing update type feeds on form display.

3.7 | 2017-02-20

Added security enhancements. Credit: Fletcher Horton - Horton's Art LLC.
Fixed a PHP warning when populating a form field using the value from a BuddyPress datebox type field.
Renamed the function hooked to the gform_merge_tags filter to prevent conflicts with other add-ons and custom code snippets.
Updated gf_user_registration_login_form() to allow for login form arguments to be passed directly through a parameter.

3.6 | 2017-01-05

Added logging of BuddyPress field processing.
Fixed an issue where the number field value may not use the format configured on the field.
Fixed fatal error on main settings page when running PHP 7.1.
Fixed strings for translations.
Fixed an issue with the markup for the login widgets logged in message.

3.5 | 2016-11-04

Added support for the {set_password_url} merge tag.
Updated 'User activation' notification event label to 'User is pending activation'.
Updated Pending Activations table to be responsive.
Updated to use a meta box to include the activate user button on the entry detail with Gravity Forms 2.0+.
Fixed a timing issue with the inclusion of the GF_Field_Username class which in some situations caused the username field to be initialized in the form object using the basic GF_Field object resulting in the field input being missing when the form was rendered.
Fixed feed not being passed through the gform_addon_pre_process_feeds filters in some situations.
Fixed a PHP notice which could occur when an update type feed populates checkbox type fields with values stored in ACF checkboxes.
Fixed an issue with the Login button which prevented it being translated.
Fixed an issue with the custom registration page redirect.
Fixed an issue with the default logged in message for the login shortcode.

3.4 | 2016-08-31

Added additional logging statements.
Added the gform_user_registration_user_meta_options filter to allow the options for the "Other User Meta" group in the User Meta setting on the settings page to be set before running the query against the usermeta table for existing meta keys. If the return value is not empty then the query for existing meta keys will not run.
Updated German (de_DE) translation to fix an issue in Pending Activations page when Deutsch language is selected in WP settings due to incorrect usage of double quotes in the translation file.
Fixed issue when trying to hide title, description or logged in avatar with the login shortcode.
Fixed issue when including the deprecated.php file on some installations.
Fixed a typo in the capability for the pending activations page under the Users menu.
Fixed fatal error which could occur if the BP_XProfile_Field class already exists.
Fixed fatal error which could occur if the BP_XProfile_Group class already exists.
Fixed an issue with the activation url if the WordPress Address and Site Address URLs differ.
Fixed notice generated during validation when form did not have a password field
Fixed issue with password validation.
Fixed GF_Field array access/object notation notices with Gravity Forms 2.0.

3.3 | 2016-04-19

Added support for redirect_to query parameter for login/logout form.
Added German translation. Credit: Dominik Horn - netzstrategen.
Updated wp_new_user_notification() to be gf_new_user_notification() to avoid issues where users are attempting to override the same function. Users wishing to override this function can do so by defining their own version in a theme or plugin.
Updated login widget interface.
Updated login widget editor to restore previously active tab after save.
Updated some strings on the feed settings page.
Updated 'Add Link' string in Login widget to be translatable.
Updated Chinese (China) translation. Credit: Edi Michael.
Updated Spanish (es_ES) translation.
Updated login widget to not use boolval().
Fixed an issue with the PayPal integration with Gravity Forms 2.0.
Fixed an issue where a PHP notice would appear when enqueuing scripts when not logged in.
Fixed issue with login redirect URL not populating properly.
Fixed an issue populating the Checkbox field when processing the update feed on form render.
Fixed fatal error when using "user" shortcode in list output mode and meta value is not an array.
Fixed textdomain for some strings.

3.2 | 2016-03-08

Added Chinese (China, Hong Kong, and Taiwan) translations. Credit: Jason Hoi.
Added feed settings option to send user email when site is created.
Added gform_user_registration_login_args filter to modify all login form arguments.
Added gform_user_registration_login_form_title filter to modify login form title.
Added gform_user_registration_login_form_description filter to modify login form description.
Added gform_user_registration_login_redirect_url filter to modify redirect url after success login.
Added "Nickname" option to User Settings feed settings.
Added notification events: Site is created, User activation, User is activated, User is registered, User is updated.
Added "Preserve existing Display Name" option to update user feeds.
Added support for feed duplication.
Added support for using a custom link as the custom registration page.
Added user login via widget.
Added "user" action to Gravity Forms shortcode to retrieve user object and meta data (e.g. [gravityform action="user" key="display_name"]).
Added "Username" field to Advanced Fields.
Added additional logging statements.
Added support for the {activation_url} merge tag.
Fixed a fatal error which could occur on the pending activations page when attempting to display the activation error message.
Fixed an issue pre-populating the List field when processing the update feed on form render.
Fixed an issue where the post author was not set when the entry was marked as not spam.
Fixed an issue which could prevent user activation for users created by the pre-framework version if conditional logic is configured on the feeds.
Fixed an issue with BuddyPress overriding the activation emails which prevented the add-on handling user creation when the activation link was used.
Fixed an issue with the entry id stored in the user meta being overridden when an update feed is processed.
Fixed an issue with the post author not being set.
Updated feed action feed settings field to use visual radio buttons.
Updated feed settings for PayPal Standard to only display once the transaction type is selected and to only display the update user and site settings when the subscription type is selected.
Updated user role feed settings field to be a required field.
Updated wp_new_user_notification() to support logging the result from wp_mail().

3.1 | 2016-01-27

Updated processing of post category field value to use object notation.
Updated logging around processing of user meta.
Fixed an issue with the multi select field value when saving it to the user meta.
Fixed a fatal error which could occur with PHP versions older than 5.3 when including the deprecated functions file.
Fixed an issue with the capabilities.
Fixed an issue with the choices for display name setting not being translatable.

3.0 | 2016-01-20

Added integration with Add-On Framework.
Added new filter gform_userregistration_feed_settings_fields for modifying UR feed settings.
Added gform_user_registration_check_email_pre_signup_activation filter for allowing the user to disable the check for an email being already used by a registered user.
*add_filter( 'gform_user_registration_check_email_pre_signup_activation', '__return_false' );*
Added gform_userregistration_delete_signup hook to allow custom actions to be performed when pending activations are deleted.
add_action( 'gform_userregistration_delete_signup', function( $signup ) {
// do something
} );
Usage example here
Updated Spanish (es_ES) translation.
Updated update feed so that email isn't required.
Updated maybe_prepopulate_form() and handle_existing_images_submission() so the gform_user_registration_update_user_id filter can be used to override which user is used to populate the form.
Fixed an issue which could prevent the user email being sent when manually adding a user via Users > Add New.
Fixed a fatal error which could occur when processing BuddyPress data if the mapped field was a not a form field.
Fixed a fatal error which could occur when processing uploads if the mapped field was a not a form field.
Fixed issue where activation notification was not sent for for new users and new sites in WP 4.4
Fixed an issue with passwords containing quotes.
Fixed issue where password wasn't getting sent via email.
Fixed an issue with the pending activations page including blank rows for signups which do not have an associated GF entry.
Fixed an issue with username and email validation not taking pending activations into account.
Fixed issue where BuddyPress functions were triggered when BuddyPress was not active.

2.0.2 | 2014-12-08

Fixed issue where date fields were not mapped correctly in newer versions of BuddyPress.

2.0.1

Fixed typo in a translation string in userregistration.php.
Updated POT file.

2.0 | 2014-11-05

Added support for updating file upload fields mapped to BuddyPress image fields (available via BP add-on).
Added additional logging statements.
Updated pending activation so that it doesn't rely on the password being in the entry.
Updated POT file.
Updated plugin updated method so that it takes advantage of proxy manager to get around the blacklisted IP issue.
Fixed issue where pending activations were not sorted correctly.
Fixed update feeds in Gravity Forms 1.9.
Fixed issue where BuddyPress field visibility was ignored.
Fixed warning message on plugin's page.
Fixed notice when 'create_site' feed meta was not set.
Fixed issue where "Simple" type Name fields did not map to user meta correctly.
Fixed issue where data pulled from BuddyPress was not always correctly matched since the HTML entities were already encoded.
Fixed issue whith PayPal integration where users were not getting created when payment was manually being marked as Approved on the entry detail page.
Fixed notice thrown when updating BuddyPress Last Activity meta; updated to use new version.
Fixed issue where the upgrade class wasn't included which caused ManageWP to not work with add-on.
Fixed notices thrown in the downgrade_paypal_user function.

1.9 | 2014-05-29

Added gform_user_registration_new_site_meta filter for filtering the meta used to create a new site
add_filter( 'gform_user_registration_new_site_meta', 'add_blog_template', 10, 6 );
function add_blog_template( $site_meta, $form, $entry, $feed, $user_id, $is_update_feed ) {
$signup_meta['blog_template'] = 1;
return $signup_meta;
}
Added "Preserve current role" option for "Current Site Role" setting.
Added gform_user_registration_signup_meta filter for filtering the signup meta
add_filter( 'gform_user_registration_signup_meta', 'add_blog_template', 10, 4 );
function add_blog_template( $signup_meta, $form, $entry, $feed ) {
$signup_meta['blog_template'] = 1;
return $signup_meta;
}
Added current user object to wpmu_validate_blog_signup() call to allow registering sites with the same name as the current user.
Fixed the functions used by the mwp_premium_update_notification and mwp_premium_perform_update hooks so that the new_version element in the array returns the add-on's version instead of Gravity Forms.
Fixed issue where signups table on single site installs failed to update correctly when promoting site to multisite.
Fixed issue where activation emails were sent even though manual activation was enabled.
Fixed strict notice for Non-static method GFUserSignups::install_signups().

1.8 | 2014-03-31

Added more debug statements for logging.
Added logging support and some initial debug statements.
Updated two strings in activate.php to match their equivalents in wp-activate.php (as of WP 1.8.1).
Updated signup activation to check if email address is already in use and return a message indicating such.
Updated all places where RGUserUpgrade class was manually included to use new GFUser::include_upgrade_library() method.
Fixed notice with missing variable $set_post_author.
Fixed issue on single site installs where activation email title and from name defaulted to "WordPress".
Fixed issue on Update form where pre-population didn't always work when a value was set to zero.
Fixed issue where RGUserUpgrade class was called but not included.
Fixed issue where single column list fields were not updating correctly on Update feeds.
Fixed issue where deprecated functions were used in activation process.
Fixed issue in Update feed on multi-site where email address said to already be used.

1.7 | 2013-09-05

Fixed issue with invalid site domain and path when creating a new site.
Fixed issue with email activation link displaying errors when mapping BBPress fields.
Fixed issue where $base global variable in wp-config.php may not have the trailing slash, causing the site url created to be bad.
Fixed bug where PayPal integration caused user to be registered regardless of being set to manual/email activation.

1.6 | 2013-06-19

Updated automatic upgrade so that it caches remote requests for 12 hours (even on plugin's page).
Updated multisite username and email validation to only apply if the correct page is being validated.
Updated to allow mapping to POST fields for Update User feed.
Fixed issue with form action on activate.php when invalid activation key provided.
Fixed issue with display name not being set correctly on an create feed.
Fixed issue were BP on single site installs was overwriting standard user meta fields (ie first name, last name, nicename).
Fixed issue where email validation allowed update feeds to use already used email addresses.
Added better support for file uploads on forms with update feeds.
Fixed issue where multisite validation on Update feeds generated error when using existing email.

1.5 | 2013-04-01

Added support for custom registration page for multi-site installs.
Fixed link location for drop down on Pending Activations page which takes user to view All pending or form-specific pending.
Fixed issue where All pending activations was returning no records.
Fixed issue where usernames with spaces were not displaying in pending activation table.
Added "back to list" link on successful activation on Pending Activations page.
Updated Pending Activations table to only show form column when viewing All Pending Activations.
Updated UI to remove tabs.
Fixed issue where update_user() function was not correctly saving the user's email.
Fixed errors when populating an update fields with values containing single quotes.
Added support for specifying user activation type (manual, by email).
Updated roles drop down on feed page to order by a custom sort (subscriber first).
Fixed issue when updating user's website meta on an update feed.
Fixed issue with mapping category fields to BuddyPress.
Fixed error on update feed form when Buddy Press is uninstalled.
Fixed issue with checkboxes not being saved correctly when unchecked from an update feed.
Fixed issue with date fields not being formatted correctly when populating fields in an update feed.
Fixed issue with plugin-upgrade.php where failed remote response generated several notices.
Added support for saving processed config in entry meta and retrieving this from get_active_config() function.
Fixed issue where multiple file upload fields were not be populated correctly (powered by update feed).
BP functions bound to gform_user_registered were not being bound in the admin as the gform_user_registered hook was not previously fired in the admin (now fires when manually activating a pending activation).
Fixed issue where "wp_" prefix was being used instead of "$wpdb->prefix" Busted!
refactored form population for update feeds.
added support for list fields for update feeds.
fixed issue with date field population for update feeds.
Fixed issue with hardcoded table prefix.
Fixed issue with AJAX call when admin is configured to force SSL.
Fixed issue where Gravity Forms was being required and failing to find plugin.
Fixed issue where values being populated back into form for update feeds were not escaping single quotes which caused errors.
Fixed issue where unescaped single quotes were causing issues on feed editor.
Fixed issue where custom meta fields with 0 as a value weren't saving to the database.
Fixed notices when form inputs array doesn't exist which caused AJAX spinner to remain and no form fields were displayed.
fixed compatability issue with BP 1.6 where BP profile function is no longer available.
added "gform_disable_registration" hook to allow add-ons to prevent User Registration from registering/updating a user.
fixed issue where using wp_get_current_user() function was failing to update users when wait for payment option was checked.
fixed issue where "Pending Activations" link displayed in feed actions for Update feeds.
fixed issue where "Send Email?" option was displaying for Update feeds.
fixed issue where "Preserve current role" option was not preserving user's role for new feeds.
fixed issue were active status was not taken into account when retrieving update feed.
Fixed issue where new feed options were not displaying immediately.
Added support for displaying all user meta keys in feed meta key drop downs.
Fixed UI to read "Action" instead of "Feed Type".
Added pending activation link to entry detail page.
Added support for multiple feeds per form.
Added support for user activation on a per feed basis.
Added support for "update" feed types.
Added new conditional logic options (greater than, less than, contains starts with, ends with) and support for other conditional fields.
Fixed notices.

1.4 | 2012-03-27

Fixed typo.
Fixed issue where users were not visible in the BP member directory.
Added support for displaying user registration notice in activity feed.

1.3 | 2012-02-09

Fixed issue when Authorize.net and PayPal feeds were configured on the same form. The PayPal feed was being used sometimes even though the PayPal condition wasn't met.
Fixed issue where inactive feeds were still being processed.
Added several additional parameters to the "gform_username" hook.
Fixed issue where translation files were only being loaded for admin.
Fixed several notices with BuddyPress integration.
Updated function for adding user properties to prevent removal of password.
Added gform_site_created hook which triggers after a site has been created.
Updated functionality to add website user property correctly.
Updated PayPal integration to support multiple PayPal feeds with the same form.
Fixed notices on the PayPal Transaction Settings for the User Registration section.
Fixed issue where RG_CURRENT_PAGE constant was not available when GF is deactivated.
Added option to feed to allow user to specify the display name of the created user.
Updated code in various places to be cleaner and more efficient.
Added option to select role of new user on new site.
Added option to select role of new user on existing site.
Updated the "Custom Registration Page" functionality to also override BP Register page.
Fixed several PHP notices.
Fixed issue where validation was being processed regardless of a registration condition.
Fixed issue where $entry object was not being passed when checking if registration condition was met.
Fixed issue where GF was calling "gform_post_submission" hook prior to add-on tying function to it.

1.2.11 | 2011-11-01

Fixed issue where password was not included on New Site Creation email.

1.2.10

Updated registration_met() function to retrieve submitted value from the lead (rather than $_POST) to be compatible with PayPal Add-On.

1.2.9 | 2011-10-03

Fixed issue where empty array values for checkboxes and multiselect fields were being displayed as part of the BP profile data.

1.2.8

Fixed issue where erroneous fields with empty inputs array were not displaying in feed fields drop down.

1.2.7

Updated custom_registration_page() function to no longer user parse_url() php function.

1.2.6.3

Users are not created if entry is marked as spam.
Marking an entry as not spam will create the user.

1.2.6.2

Updated how the BuddyPress profile data table name is retrieved.
Updated custom_registration_page() function to parse more complex URLs.

1.2.6.1 | 2011-07-20

Updated "Custom Registration Page" functionality; when activated, accessing WP's default registration page will redirect user to specified page.

1.2.6 | 2011-07-16

Updated all localization strings to ensure same domain.
Recreated localization POT file.
Updated validation to validate regardless if the registration condition is met.

1.2.5

Added cleanup routine to make sure user meta values are not stored as arrays.

1.2.4

Added new filter "gform_username" to dynamically assign a username.
add_filter('gform_username', 'auto_username');
function auto_username($username){
$username = rgpost('input_2_3') . rgpost('input_2_6');
return $username;
}

1.2.3

Escaped javascript localization strings.

1.2.2

Add new option/functionality to override WP's default registration page with a custom page.
Require BP file in get_buddypress_fields() for users who have BP active but not setup.

1.2.1 | 2011-04-29

Updated 'Email Address' field dropdown to also pull custom fields that are set to the Email input type.
Updated is_root_site() function to more reliably determine if the current blog is the root site's blog.
Fixed several notices on User Registration multisite options.

1.2 | 2011-04-27

Fixed issue with localization.
Updated UI to support longer translation verbiage.

1.1

Fixed issue where all User Registration options were displaying for PayPal Feeds even when no User Registration Feed existed for the selected form.
Fixed issue where User Registration options were not available on a PayPal Feed until after saving the PayPal Feed was saved.
Feed password field now defaults to a form password field (if available).

1.0 | 2011-03-23

Updated version to 1.0.

1.0.beta5.3

Updated reference to gforms_paypal_save_config to use the renamed hook: gform_paypal_save_config.
Localized add-on.
Added gravityformsuserregistration.pot file.

1.0.beta5.2

Added hook to allow User Registration validation messages to be updated.
Example:
add_filter("gform_user_registration_validation_message", "update_validation_msgs", 10, 2);

function update_validation_msgs($message, $form){

if($message == 'This username is already registered')
$message = 'We're sorry, this username is already registered. Try submitting with a different username.';

return $message;
}

1.0.beta5.1

Updated gf_create_user() code to abort user registration if username already exists; beneficial to prevent existing user data being overwritten if username validation is overriden.

1.0.beta5

Added support for all BP field types.
Rewrote function to better retrieve values from the $_POST and $entry object.

1.0.beta4

Fixed validation issue for multi-page forms where the site address MU registration field was being validated regardless of current page.
Fixed "Cancel" button on Edit page to return the user to the List page.
Update multisite registration validation to check if site name (domain) already exists.

1.0.beta3.2

Fixed IE issue where selecting a form on the PayPal add-on was generating an error when no User Registration feeds existed.

1.0.beta3

Added support for creating MultiSite with user registration.
Fixed issue where MultiSite was failing to return validation error for spaces in domain name.
Disabled MultiSite options on User Registration feed view for child sites.

1.0.beta1

Updated database name to be consistent with other Gravity Form Add-Ons.
Updated permission required to view User Registration menu.

{user} Merge Tag

SummaryUsageMeta Field Name Examples (non-exhaustive):first_name:last_name:display_name:user_email:user_login:ID:preferred_contact_method

Summary
Displays the value of the user meta field for the logged in user, based on the modifier used.
Usage
{user:[meta_key]}
Meta Field Name Examples (non-exhaustive)
Any single user meta (including custom user meta) can be displayed with this merge tag by replacing [meta_key] with the specific meta_key for which you are wanting a value.
Below are a few examples of how this merge tag can be used. Please note: The user must be logged in when the entry is submitted.
:first_name
Displays the first name of the currently logged in user. {user:first_name}
:last_name
Displays the last name of the currently logged in user. {user:last_name}
:display_name
Displays the Display Name of the currently logged in user. {user:display_name}
:user_email
Displays the email of the currently logged in user. {user:user_email}
:user_login
Displays the user login of the currently logged in user. {user:user_login}
:ID
Displays the ID of the currently logged in user. {user:ID}
:preferred_contact_method
Displays the value of user meta with custom meta_key. {user:preferred_contact_method}

Upgrade/Add-on Issues

Having an issue where you can』t upgrade Gravity Forms or its add-ons? Are you seeing a message that says you need to register or that the add-on browser is not available and these issues don』t resolve within twenty-four hours? Your web server might be having issues contacting our servers and it is most likely due to a blacklisted IP address.
Read the following guide on our blog about Blocked IP Addresses
You can also test with logging enabled to see if any messages are being returned if your site is having issues contacting our servers.