Gravity Forms 文档

Partial Entries Change Log

1.6.11.6 | 2020-09-241.5 | 2020-05-111.4 | 2019-08-071.3 | 2018-12-191.2 | 2018-03-271.1 | 2018-01-291.0 | 2016-09-231.0-beta-2 | 2016-03-301.0-beta-1 | 2016-03-17

1.6.1

Added the gform_partialentries_pre_update filter to allow modifying the partial entry data before it is updated.
Fixed an issue that was causing an unsaved change notice to display each time partial entries was enabled or disabled in the form settings.

1.6 | 2020-09-24

Added support for Gravity Forms 2.5.

1.5 | 2020-05-11

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Fixed an issue where values for fields located in sections or pages which are hidden by conditional logic are being saved to the partial entry.

1.4 | 2019-08-07

Added security enhancements.
Added support for anti-spam honeypot validation prior to creation of partial entry.
Fixed "?gf_token" being saved as the value of the resume_url entry meta when a draft submission has not been saved.

1.3 | 2018-12-19

Updated minimum Gravity Forms version to 2.3.
Fixed issues with conditional logic evaluation when the entry is saved during form submission.
Fixed a PHP notice with Gravity Forms 2.3+ when save and continue is enabled for the form.
Fixed an issue where a completed entry could be overridden by a partial entry when an expired resume token is used.
Fixed a PHP notice which could occur during submission if the form contains one or more product fields.
Fixed issue where entry count did not match list of entries in certain scenarios.

1.2 | 2018-03-27

Added security enhancements.
Fixed an issue preventing automatic upgrades.

1.1 | 2018-01-29

Added Author URI to plugin header.
Added support for Gravity Forms 2.3.
Updated Plugin URI in plugin header to be https.
Updated the feed conditional logic progress choices to support the "is" operator.
Updated the "Complete" choice of the "Progress" entry meta item to support the "is not" operator.
Updated text "Enable Condition" to "Enable" in making Add-Ons consistent.
Updated partial-entries.js to include heartbeat.js as a dependency.
Fixed the handling of the "No Duplicates" field setting where validation fails on submission if a partial entry contains a duplicate value. The "No Duplicates" setting is now ignored when saving partial entries. Partial entries are now ignored when checking for duplicates on final submission - only complete entries are checked.
Fixed a PHP notice while viewing the entry list with WordPress 4.8.3.
Fixed a PHP notice during partial entry creation if the form includes a fileupload type field.

1.0 | 2016-09-23

Added the form_partialentries_post_{$event} hook enabling custom actions to be performed once a partial entry has been saved or updated.
Updated to set entry meta (e.g. Quiz Score Total) when a partial entry is saved/updated.
Fixed issues with saving partial entries and with submitting the form when one of the fields has the "No Duplicates" setting enabled.
Fixed an issue with the form submission where previously saved values are not deleted when subsequently hidden by conditional logic.
Fixed an issue which caused the form to be validated twice during page changes.
Fixed an issue which caused GFFormDisplay::is_last_page() to return an incorrect result causing payment add-ons to perform credit card field validation on the wrong page.

1.0-beta-2 | 2016-03-30

Added support for Gravity Forms 2.0-beta-2.
Added the Last Saved date and link to the entry detail page.
Added the gform_pre_render filter before creating the partial entry.
Added support for notification events (sending notifications when the partial entry is saved and updated).
Added logging statements.
Fixed PHP warning on notifications list and edit pages.
Fixed an issue with the warning message.
Fixed the text domains used for some of the translatable strings.

1.0-beta-1 | 2016-03-17

All new!

Paragraph Text

SummaryCommon SettingsAdvanced SettingsMerge TagsUsageModifiers

Summary

The Paragraph Text field allows a user to enter text in a textarea form field. It is available under the Standard Fields section within the form editor.

Paragraph Text field as displayed in the Field Library

Paragraph Text field as displayed in the Form Editor.

Common Settings

This field uses only common field settings for the General and Appearance settings. For a description of each of the common field settings, refer to this article. Below you will find description of specialty settings that are particular to this field.

Advanced Settings

SettingDescriptionUse the Rich Text EditorCheck this option to enable the rich text editor on this field. Note that if you already have entry data associated with this field, you will not be able to enable the rich text editor.

Merge Tags

For more information on the use of merge tags, refer to these articles.

Usage

{Field Name:2}

Modifiers

This merge tag does not have any modifiers.

Paragraph Text Field CSS Selectors

example: standard paragraph field (textarea) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield textarea {border: 1px solid red}

example: standard paragraph field (textarea) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield textarea {border: 1px solid red}

example: standard paragraph field (textarea) – applies just to specific paragraph field (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield textarea {border: 1px solid red}

Paragraph Text Field CSS Selectors

ContainerInputMaximum Characters Counter

Container

example: paragraph text field container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_textarea {border: 1px solid red}

example: paragraph text field container (div) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_textarea {border: 1px solid red}

example: paragraph text field container (div) – applies just to specific indicator (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .ginput_container_textarea {border: 1px solid red}

Input

example: paragraph text field (textarea) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_textarea textarea {color: red}

example: paragraph text field (textarea) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_textarea textarea {color: red}

example: paragraph text field (textarea) – applies just to specific indicator (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .ginput_container_textarea textarea {color: red}

Maximum Characters Counter

example: paragraph text field (textarea) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_textarea .charleft {color: red}

example: paragraph text field (textarea) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_textarea .charleft {color: red}

example: paragraph text field (textarea) – applies just to specific indicator (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .ginput_container_textarea .charleft {color: red}

Page Break

SummaryCommon SettingsStart Paging MarkerGeneral SettingsPage Break MarkerGeneral SettingsNext Button and Previous Button SettingsEnd Paging MarkerGeneral SettingsPrevious Button SettingsMerge Tags

Summary

The Page field allows the creation of multi-page forms. The Page field is available under the Standard Fields section within the field library sidebar of the form builder.

Adding a Page field will automatically add three new markers to your form:

a Start Paging marker at the top of your form. a Page Break marker in the position you dragged to.an End Paging marker at the bottom of your form.

Each one of these sections offer different settings, all of which are explained here.

Page field as displayed in the Field Library

Common Settings

This field uses only common field settings for the Appearance and Advanced settings. For a description of each of the common field settings, refer to this article. Below you will find description of specialty settings that are particular to this field.

Start Paging Marker

The Start Paging field will always appear at the top of your form (after a Page Break field is added to your form). This field is used to specify general options that define the behavior of your multi-page form.

General Settings

SettingDescriptionProgress IndicatorSelect which type of visual progress indicator you would like to display. Available options are Progress Bar, Steps or None.StyleSelect which progress bar style you would like to use. Select custom to choose your own text and background color.Page NamesName each of the pages on your form. Page names are displayed with the selected progress indicator.Display completed progress bar on confirmationCheck this box if you would like the progress bar to display with the confirmation text.

Page Break Marker

The Page Break field specifies exactly where one page ends and the next page begins. You can add as many Page Break fields as you need and each carries settings that will customize the behavior for that page only. Setting here affect the page laid out before the page break field.

General Settings

Next Button and Previous Button Settings

SettingDescriptionDefaultIf selected, you can enter a text string into that will show on the relevant page button.ImageIf selected, you can enter the path to an image you would like to use as the page button.

End Paging Marker

The End Paging field occurs at the bottom of your form. It provides an option to modify the Previous button, which appears on the last page.

General Settings

Previous Button Settings

See the same options above in the Page Break marker.

Merge Tags

This field does not support merge tags.

Option

SummaryCommon SettingsGeneral SettingsField Types OptionsAppearance SettingsMerge TagsUsageModifiers

Summary

The Option field allows the creation of options for products created by a Product. Option fields have special functionality which displays how much selecting the option will add (or subtract) from the total. It is available under the Pricing Fields section within the form editor.

Option field as displayed in the Field Library

Option field as displayed in the Form Editor.

Important: If your choice labels contain any HTML or special characters such as ampersands, commas, hyphens or brackets of any type, you MUST enable the show values feature and give each choice a simple and unique value which does not contain any special characters. Failure to configure values could cause issues for features such as calculations, conditional logic, dynamic population, and validation.

Common Settings

This field uses only common field settings for the Advanced settings. For a description of each of the common field settings, refer to this article. Below you will find description of specialty settings that are particular to this field.

General Settings

SettingDescriptionProduct Field MappingSelect which product this field is tied to. This option is only available when there are two or more products. When only one product exists, Option and Quantity will automatically apply to that product.Field TypeSelect the type of field from the available form fields. See Field Types Options below.

Field Types Options

SettingDescriptionDrop DownThe Drop Down field type will display as a drop down field on your form.CheckboxesThe Checkboxes field type will display as a group of checkbox fields on your form.Radio ButtonsThe Radio Buttons field type will display your product options as radio buttons.

Appearance Settings

SettingDescriptionEnable enhanced user interfaceBy selecting this option, the Chose jQuery library will become active, allowing drop downs to be searched.

Merge Tags

For more information on the use of merge tags, refer to these articles.

Usage

{Field Name:2}

Modifiers

This merge tag does not have any modifiers.

Option Field CSS Selectors

ContainerDrop DownItems

Container
example: option field container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield_price .ginput_container_select {border: 1px solid red;}
example: option field container (div) – applies just to form ID #1
body .gform_wrapper_1 .gform_body .gform_fields .gfield_price ginput_container_select {border: 1px solid red;}
example: option field container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield_price ginput_container_select {border: 1px solid red;}
Drop Down
example: option field drop down (select) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield_price .ginput_container_select select {border: 1px solid red;}
example: option field drop down (select) – applies just to form ID #1
body .gform_wrapper_1 .gform_body .gform_fields .gfield_price .ginput_container_select select {border: 1px solid red;}
example: option field drop down (select) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield_price .ginput_container_select select {border: 1px solid red;}
Items
example: option field items (option) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield_price .ginput_container_select select option {border: 1px solid red;}
example: option field items (option) – applies just to form ID #1
body .gform_wrapper_1 .gform_body .gform_fields .gfield_price .ginput_container_select select option {border: 1px solid red;}
example: option field items (option) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield_price .ginput_container_select select option {border: 1px solid red;}

Obtaining and Saving your FreshBooks API Credentials

Note: As of September 2016, FreshBooks has released a new version of their service. Currently, the Gravity Forms FreshBooks Add-On only works with the previous FreshBooks Classic version and will not work with their updated API.

To begin using the FreshBooks Add-On, you will first need to obtain and save your FreshBooks API settings. In this article, we will show you how to get started with obtaining your FreshBooks API credentials, as well as saving them inside the settings page.

Log into your FreshBooks account.Click on My Account at the top right of the page.Click on FreshBooks API.You should now see your API URL as well as your Authentication Token. Make note of these as you will be inputting them into the FreshBooks Add-On shortly.Log into your WordPress admin dashboard and hover over Forms, then click on Settings.

Click on the FreshBooks tab.

You will see two fields, Site Name and Authorization Token. Within the Site Name field, enter only the beginning of your API URL. For example, if your full API URL reads https://exampleuser.freshbooks.com/api/2.1/xml-in, simply enter exampleuser into this field. In the Authorization Token field, enter the authorization token that you obtained from FreshBooks.Click the Update Settings button to save your changes.

You have now successfully configured the FreshBooks Add-On for Gravity Forms to communicate with the FreshBooks API. You』re now ready to setup a feed within the FreshBooks Add-On.

Obtaining Prior Versions of Gravity Forms

Warning: We do not recommend downgrading Gravity Forms or a Gravity Forms Add-On to a prior version.

If you are experiencing an issue with a recent update, the recommended solution is to restore to your last good backup. This is the best guarantee to recover your previous state, instead of trying to rollback to a prior version of Gravity Forms which can create interworking issues with already upgraded database tables, third party add-ons etc.

Commonly, issues you may be experiencing after an update can be due to a conflict with a theme or plugin, or may already have been corrected with a hotfix release. For this reason, opening a ticket with the Support Team to check may be a better initial option than starting a downgrade process.

We always recommend running the most up-to-date version of Gravity Forms and it』s add-ons, to guard against security vulnerabilities, known bugs, and ensuring compatibility with WordPress core. Check out this article for more on the importance of staying up to date.

If you do need access to a prior version of Gravity Forms for testing or other purposes, please identify what you need and why in your Support request so we can review your issue. Note that providing access to previous versions is not guaranteed, and will be evaluated by the Support team on a case-by-case basis.

Obtaining Your Stripe API Keys (for version 2.7 and earlier)

The instructions in this article are only applicable to Stripe version 2.7 and below.
To use the Stripe Add-On, you will need to first obtain your Stripe API keys. We will show you exactly how to find them with the steps below.

Log into your Stripe account.
Verify that you are in test mode (for the purpose of integration).

Click on Developers in the left-hand menu.
Under Developers, click on API keys. You will see your test API keys. Note these as they will be needed to complete the setup.

Now that you have obtained your API keys, refer to the Setting Up the Stripe Add-On article for further instructions.