Gravity Forms 文件

Post Category

SummaryCommon SettingsGeneral SettingsAdvanced SettingsMerge TagsUsageModifiers

Note: This field cannot be used with the Advanced Post Creation Add-On. If utilizing that plugin for post creation, use a standard field type instead.

Summary

The Post Category field allows the user to select a category for the post they are creating. This field works in tandem with the other Post fields to allow you to create a form that can generate post data from a user submission. It is available under the Post Fields section within the form editor.

Post Category field as displayed in the Field Library

Post Category field as displayed in the Form Editor.

Common Settings

This field uses only common field settings for the 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.

General Settings

SettingDescriptionField TypeSelect the type of field from the available form fields.CategorySelect which categories are displayed. You can choose to display all of them or select individual ones.Display PlaceholderCheck this option to enable a default instructional option as the first option rather than having the first option default to a category.

Advanced Settings

SettingDescriptionVisibilitySelect the visibility for this field. Field visibility set to Everyone will be visible by the user submitting the form. Form field visibility set to Admin Only will only be visible within the Gravity Forms administration tool. Setting a field to Admin Only is useful for creating fields that can be used to set a status or priority level on submitted entries. See Note.

Note: This is especially useful for the Category field as it allows the admin to specify a default category for posts created through this form without this field being visible to users.

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.

Post Body

SummaryCommon SettingsGeneral SettingsMerge TagsUsageModifiers

Note: This field cannot be used with the Advanced Post Creation Add-On. If utilizing that plugin for post creation, use a standard field type instead.

Summary

The Post Body field allows users to submit data that is then used as the body content for a post. It is available under the Post Fields section within the form editor. This field works in tandem with the other Post fields to allow you to create a form that can generate post data from a user submission. The Post Body field can be formatted using the Create Post content template option.

Post Body field as displayed in the Field Library

Post Body field as displayed in the Form Editor.

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.

General Settings

SettingDescriptionPost StatusSelect the post status that will be used for the post that is created by the form entry. Available options are Draft, Pending Review, and Published.Default Post AuthorSelect the author that will be used for the post that is created by the form entry.Use logged in user as authorSets the post author to the WordPress user that submitted the form.Post CategorySelect the category that will be used for the post that is created by the form entry.Create Content TemplateCheck this option to format and insert form fields into the Post Content.

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.

Post Body CSS Selectors

ContainerInput

Container
example: post body container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_post_content {border: 1px solid red;}
example: post body container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_post_content {border: 1px solid red;}
example: post title container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_post_content {border: 1px solid red;}
Input
example: post body input (input) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_post_content input {border: 1px solid red;}
example: post body input (input) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_post_content input {border: 1px solid red;}
example: post body input (input) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_post_content input {border: 1px solid red;}

{post_edit_url} Merge Tag

SummaryUsageNotesSee Also

Summary
Displays the edit URL for the post which was created during submission.
Usage
{post_edit_url}
Notes
Only relevant when the form uses fields from Post Fields panel.
This merge tag can be used in areas such as notifications and confirmations after the entry has been saved. Because of this timing, they cannot be used as a field』s default value.
See Also
The {entry} merge tag.

How to Populate WebMerge Documents using the Webhooks Add-On

IntroductionConfiguring the WebhookNameRequest URLRequest MethodRequest FormatRequest HeadersRequest BodyField ValuesWebhook ConditionAlternative Method

Introduction

Using the Gravity Forms Webhooks Add-On it is possible to populate WebMerge documents when a form is submitted.

Note: This article assumes you have installed and activated the Webhooks Add-On and have created a document in your WebMerge account. If not, you will need to do so before any of the functionality in this article can be used.

Configuring the Webhook

To configure webhooks for a form go to your Form Settings and click on the Webhooks tab and then click the Add New button.

Next, you』ll need to configure the request that is being made.

Name

Enter a name for your feed. This can be anything you want as it is only used for identification purposes on the feeds list page and in the add-on log.

Request URL

Enter the Merge URL from your WebMerge documents Merge tab. e.g. https://www.webmerge.me/merge/12345/abcde

When performing a test request append the test=1 query string parameter to the URL so the merge does not count against your accounts merge credits e.g. https://www.webmerge.me/merge/12345/abcde?test=1

Request Method

Select the POST choice as the request method.

Request Format

Select the JSON choice as the request format.

Request Headers

There are no request headers to configure when integrating with WebMerge.

Request Body

Select the Select Fields choice.

Field Values

Configure rows for each of your documents merge fields. Click the add item icon (+) to add new rows.

You can find the keys to use on your WebMerge documents Test tab, they are the labels above each test value input, ignoring the JSON merge field at the end.

For the values you can select from the form fields, entry meta, or Add Custom Value which will display a text input which also supports Merge Tags.

Webhook Condition

If WebMerge document population should be conditional based on the value of a form field select the Enable Condition checkbox and then configure the rules which should be met for this request to be sent.

Alternative Method

If you don』t have an Elite or legacy Developer license and would prefer not to upgrade your existing license, you can still populate WebMerge documents by using one of the following methods:

Pro license holders can use the Zapier Add-On. See the WebMerge Gravity Forms support article for an example.Anyone can use the gform_after_submission filter in the theme functions.php file or a custom functionality plugin. See the Populate a Living Will from Gravity Forms article by WebMerge for more details.

Poll

SummaryCommon SettingsPoll Specific SettingsMerge TagsUsageModifiers

Summary

The Poll field is available when using the Polls add-on. This field will allow you to create polls to collect data from users. It is available under the Advanced Fields section within the form editor. Please note that you will need to have the Polls add-on installed and activated before this field type is made available.

Poll field as displayed in the Field Library

Poll field as displayed in the Form Editor.

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.

Poll Specific Settings

SettingDescriptionDescriptionAdds text that can be displayed with the poll question, and its appearance is controlled by the description placement option under the Appearance settings tabPoll QuestionWithin this field, you will provide the question that you would like to ask the user.Poll TypeAllows you to select how the poll is displayed.For Poll Types see note 1.Bulk Add / Predefined ChoicesClicking the Bulk Add / Predefined Choices allows you to select a category and customize the predefined choices or paste your own list to bulk add choices. See note 2.Enable 「other」 choiceCheck this option to add a text input as the final choice of your poll. This allows the user to specify a value that is not a predefined choice.Randomize order of choicesRandomizes the choices when displayed to the user.

Poll Types: Drop Down; Radio Button; Checkbox (multi-select)See this article for more information.

Merge Tags

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

Usage

{Field Name:2}

Notes:

The first of these merge tag parameters is optional and is simply the field name for easier identification.The second parameter defines the field ID within the form. In the example above, it would be field ID 2.If accessing a specific option within the field, it can be accessed by separating the values with a period. For example, 2.3 would be the value of the 3rd choice from field ID 2.

Modifiers

This field does not have any modifiers.

Polls Change Log

3.9 | 2021-09-083.8 | 2021-04-293.7 | 2020-10-153.6 | 2020-09-303.5 | 2020-05-133.4 | 2019-08-073.3 | 2019-06-133.2 | 2019-03-223.1 | 2016-08-313.0 | 2016-04-142.4 | 2015-10-082.3 | 2015-04-202.2 | 2014-10-162.1 | 2014-09-242.0 | 2014-02-281.5 | 2013-06-061.4 | 2013-04-301.3 | 2013-04-231.21.1 | 2012-10-03

3.9 | 2021-09-08

Fixed an issue where the polls blocks enqueue breaks the Gutenberg editor in WordPress 5.8.x and later.
Fixed an issue where the polls shortcode renders the form even when it is not active.
Fixed markup errors when poll choices are randomized in Gravity Forms 2.5.

3.8 | 2021-04-29

Added an icon for the form editor in Gravity Forms 2.5.
Fixed an issue where script tags are being output above the document head element.
Fixed an issue where the polls editor block generates error notices in the browser.
Fixed compatibility issues with PHP 8.

3.7 | 2020-10-15

Added security enhancements.

3.6 | 2020-09-30

Added support for Gravity Forms 2.5.
Fixed an issue where the label tag is corrupt when using Jetsloth image choices and enabling shuffle choices setting.

3.5 | 2020-05-13

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Updated Javascript files, stylesheets to use minified versions.
Fixed PHP notices which occur on the entry detail page with PHP 7.4.
Fixed a PHP notice which can occur when a third-party add-on triggers the gform_entry_field_value filter without passing a field object.
Fixed a compatibility issue with the Poll block and WPGraphQL Gutenberg.

3.4 | 2019-08-07

Added security enhancements.

3.3 | 2019-06-13

Added Poll block.
Added the gform_polls_results_ajax_response filter, including form specific version, enabling the results Ajax response to be overridden.
Fixed PHP notice after Gravity Form 2.4.7 adding tab capabilities check.

3.2 | 2019-03-22

Fixed deprecation notices under Gravity Forms > 2.3.
Fixed strings for translations.
Fixed an issue with the locations the gform_merge_tags hook was being used to include the merge tags.

3.1 | 2016-08-31

Updated field general settings label classes for consistency with GF2.0+.
Fixed an issue with the "other" choice feature on the radio type field when saving the form.
Fixed a layout issue in the form editor when the 'Randomize order of choices' setting is enabled.

3.0 | 2016-04-14

Added support for Gravity Forms 2.0.0.
Added GF_Field_Poll.
Fixed an issue with the AWeber integration.

2.4 | 2015-10-08

Updated minimum Gravity Forms version to 1.9.
Fixed some PHP warnings which could appear when using the polls shortcode action with a form that doesn't have any poll fields.
Fixed an issue with the calculation of results which can lead to inconsistent results being displayed in certain situations on sites with high volume. Props: Antonis Zachopoulos.
Fixed a notice in WP4.3 with Widget constructor deprecation.
Fixed an issue with the placeholder for the select type poll field.
Fixed an issue which caused poll merge tags to be replaced during form render.

2.3 | 2015-04-20

Added Spanish (es_ES) translation.
Added support for rendering polls in admin pages. Requires Gravity Forms 1.9.
Added support for the shortcode builder.
Fixed issue where "Other" choice displayed twice in front-end poll results.
Fixed a low severity security vulnerability.
Fixed defaults for the shortcode builder.
Fixed issue where confirmation text wasn't getting displayed on AJAX forms.

2.2 | 2014-10-16

Added support for Gravity Forms 1.9 form editor drag and drop.
Added function gf_polls to easily get a Poll instance.
Added text domain/path to header.
Updated protected functions to be public.
Updated to have the file class-gf-polls.php and organized code into this file and polls.php.
Updated version to use a variable.
Fixed notices.

2.1 | 2014-09-24

Fixed the field title in the Form Editor.
Fixed a PHP warning when overriding a page redirect with the Poll results.
Fixed an issue with the resending of notifications from the entry detail page where the choice values were being displayed instead of the choice text.
Updated a few text strings so they may be translated.
Updated POT file.
Fixed translation text domain in several instances to be gravityformspolls.

2.0 | 2014-02-28

Added integration with the Campaign Monitor Add-On, MailChimp Add-On, AWeber Add-On, and Zapier Add-On.
Added Add-On Framework integration.
Added support for the poll entries tab in the Contacts Add-On.
Added the gform_polls_percentage_precision hook so the percentages on the front-end results can be rounded to a custom number of decimal digits.
Updated label of some form settings items.
Updated Drop Down Poll field to display the "Select one" option at the top of the list instead of the bottom.
Updated GFPolls::merge_tag_filter() to public static.
Fixed view results link for forms with no entries.
Fixed an issue where poll merge tags would appear in the list of merge tags available during pre-submission.
Fixed Strict notices under PHP 5.4.
Fixed permissions for settings pages.

1.5 | 2013-06-06

Requires Gravity Forms > 1.7.4.2
Added a "Select one" option to the dropdown poll field
Added the gform_polls_cron_schedule filter so the frequency of the cron job can be modified.
Notes: The wp_cron job will take over the calculation of the results if 5 seconds is not long enough at the time of form submission/update.
The default schedule is set to hourly to avoid heavy loads on the server but the frequency can be changed by using the gform_polls_cron_schedule filter.
The format follows the same format required by the WordPress cron_schedules filter
Important: the Polls Add-On must be deactivated and reactivated in order to reschedule the task.
Example usage:
add_filter( 'gform_polls_cron_schedule', 'cron_add_twice_hourly' );
function cron_add_twice_hourly() {
// Adds once weekly to the existing schedules.
$schedule['twicehourly'] = array(
'interval' => 1800, // number of seconds in the interval
'display' => __( 'Twice Hourly' )
);
return $schedule;
}
Changed the calculation of the cookie expiration to take into account the browser's timezone if possible.
Fixed an issue with results not being displayed when double quotes were inside field choices labels.
Fixed an issue with results not being displayed in no conflict mode.
Fixed an issue with poll submissions taking too long or timing out when there are already a large number of entries. When the results calculation takes more than 5 seconds then a cached version of the results will be displayed until the background process has finished calculating the new results.
Fixed issue with repeat voting when the poll shortcode cookie attribute is not used.
Removed some deprecated jQuery calls.

1.4 | 2013-04-30

Added gform_form_pre_results filter so the form object can be manipulated before the results are calculated for the admin results page.
Added gform_polls_form_pre_results so the form object can be manipulated before the results are calculated for the front and and entry detail page.
Fixed poll form settings appearing on the form settings tab.
Fixed poll results not appearing below the confirmation in ajax forms.

1.3 | 2013-04-23

Changed confirmation behavior to ignore a confirmation redirect when "display results" is selected.
Fixed a display issue with confirmation message for multipage and ajax enabled forms.
Fixed display issues in the confirmation when the confirmation is empty.
Fixed issue with boolean form settings in imported forms.
Added form settings tab ready for 1.7.
Added results page.
Updated load_plugin_textdomain() call to be outside the is_admin() block so that front end strings can be translated.
Changed the calculation of the ratio of each choice to use the number of entries for each field rather than the number of entries for the form. This fixes support for conditional logic.
Changed the poll results to display only the submitted poll fields. This fixes support for conditional logic.
Fixed poll results on entry detail.
Removed the "Display Confirmation" form setting. The confirmation will be displayed unless the widget or shortcode overrides.
Fixed css conflict with other add-ons on the preview page.
Added poll settings to the form settings. The widget and shortcode are now only needed for the Results display mode.
Removed poll settings from the widget by default and added gpoll_widget_override filter to display the option to override
Example usage:
add_filter('gpoll_widget_override' , 'gpoll_widget_override');
function gpoll_widget_override($form_ids){
array_push($form_ids, 7, 9);
return $form_ids;
}
Added support for legacy widgets by overriding form settings automatically and providing an option to use the form settings.
Added support for legacy shortcodes by overriding form settings.
Added checksum to shortcodes and widgets to make sure the settings aren't not interfered with.
Changed form selector in the widget to display only the forms with poll fields.
Fixed performance issue in the display_entries_field_value() function.

1.2

Fixed an issue with the display of special characters when random choice order is selected for a field. Fixed randomize choice order support for drop-down input types.
Fixed an issue with the tabindex in the widget.
Changed the way the repeating voting mechanism works to play better with caching plugins. Results are now displayed via ajax if the cookie option is set and the visitor has already voted.
Fixed an issue with multiple instances of the same form on the page.
Fixed an issue displaying checkbox values en entry detail and export.
Fixed an issue in the email notification where Disable Auto-formatting is not selected.

1.1 | 2012-10-03

Fixed an issue where results were being displayed when the cookie is set and display_results=false.
Fixed an issue during the export process.

Polls Block

IntroductionInserting the BlockPolls Block SettingsAdditional Options

Introduction

You can add a Poll or display Poll Results within a page or post using the WP5 block editor, and the 「Poll」 block that is automatically included when you install the Polls add-on.

The block editor is a feature of WordPress 5+, and the Poll Block was introduced in Polls add-on v3.3

Inserting the Block

The Poll block is inserted like any other block, and can be found under the Embeds section. Refer to this article for instructions on the various methods available to add a block.

Polls Block Settings

When adding the Poll block, there are some Mode and Appearance settings that you are able to configure. Make sure you have the Gravity Forms + Polls block selected, and the settings will show on the right side inspector.

SettingDescriptionModeChoose from the drop down to select either:Poll: display the poll fields, allowing users to enter their choices.Results: only displaying poll results, and do not accept any more submissions.StyleSpecifies the primary color of the bar chart when displaying the poll results. Default: Green.Display Results PercentagesDisplays the poll results as percentages at the left side of the bar chart. Enabled by default. See example image A.Display Number of Votes For Each SelectionDisplay the number of votes for each poll selection at the rightmost side of the bar chart for each possible answer. Enabled by default. See example image B.Display Link to Results Below FormDisplay a link below the form to the poll results within the page. That results page will also offer a link at bottom to return the user back to the poll form. Enabled by default. See example image C.Display Results Upon SubmissionDisplay the poll results immediately after form submission. Enabled by default.

Image A: Display Percentage

Image B: Display Number

Image C: Display Link to Results

Additional Options

For more information on the universal settings offered on all editor blocks, see this article on block options.

Poll Widget

IntroductionInsert the Poll WidgetConfigurationAdvanced SettingsAdditional OptionsExample

Introduction

In addition to being able to insert a poll within a form, you are also able to insert a poll using a widget in your WordPress Appearance area. This can allow you to insert the poll (or the poll results) in your sidebar for example. Use of widgets may require support from your site theme. Refer to this WordPress page for more information on widgets.

Insert the Poll Widget

The Poll widget is inserted the same as any other widget, but if you』re unfamiliar with the process, here』s how to do it.

Within your WordPress admin dashboard, hover over Appearance, and click on Widgets.Click the black plus button and add the Poll widget to the desired widget area.Configure any settings you need.

Configuration

When adding the Poll widget, there are a few settings that you are able to configure.

SettingDescriptionTitleThis is simply the title that will be displayed within the widget.Select a FormIn this drop down, you will select the form that contains the poll you would like to be displayed.Display ModeWithin this drop down, you have the option of either displaying the full poll or only the results.Display form titleCheck this box to display the form title within the widget.Display form descriptionCheck this box to display the form description within the widget.Custom Field NameText value that will be used to name the custom field. Select an existing value or the 「Add New Custom Field Name」 at the end of the list to enter a new custom field name.

Advanced Settings

SettingDescriptionEnable AJAXIf you need to, you may enable AJAX submission of the poll when processed through the widget.Disable script outputIf enabled, this will disable the CSS stylesheets and Javascript from being included in the page header. If the script output is disabled, you will need to include these elsewhere to function properly.Tab Index StartDetermines where, within the widget, tab indexing will start.

Additional Options

Additional options are also available but apply to the form in it』s entirety. For more information on available features, take a look at the Poll Settings article.

Example

This short movie shows what the user experience is like for a Poll Widget on a sample site.

Poll Shortcode

SummaryParameters

Summary

The Polls shortcode uses the standard Gravity Forms shortcode but introduces a new action that tells Gravity Forms to make the form behave as a poll. The Polls shortcode can be used anywhere within WordPress where shortcodes are supported. For most users, this will primarily be within the content of a WordPress post or page.

Here is an example Poll shortcode showing passed parameters.

1[gravityform action="polls" id="1" mode="poll" style="red" cookie="1 month" show_results_link="true" display_results="true" percentages="true" counts="true" ]

Parameters

ParameterDescriptionidThe id of the form to be embedded. (required)modeYou can choose to display the poll or just the results of the poll. Supported modes: poll or results. Defaults to 『poll』. (optional)titleShows or hides the form title. Defaults to true.descriptionShows or hides the form description. Defaults to true.confirmationEnables or disables the confirmation message on the form. Defaults to false.styleThe add-on currently supports four built in styles: red, green, orange, blue. Defaults to 『green』. (optional)cookieSets a time period to restrict repeat voting, using a browser cookie. Options are 1 day, 1 week, 1 month, or a specific date in the YYYY-MM-DD date format. Defaults to an empty string, which means repeat voting is permitted.show_results_linkDisplay a link to view poll results without submitting the form. Supported values are: true, false. Defaults to 『true』. (optional)display_resultsDisplay poll results automatically when the form is submitted. Supported values are: true, false. Defaults to 『true』. (optional)ajaxEnables or disabled AJAX submission of the poll. Defaults to false.percentagesDisplay results percentages as part of results. Supported values are: true and false. Defaults to 『true』. (optional)countsDisplay number of times each choice has been selected when displaying results. Supported values are: true, false. Defaults to 『true』. (optional)tabindexSets a custom tab index on the poll. Accepts numerical values.

Most of the parameters available for the Polls shortcode action are optional. A form can be presented as a poll without including most of these parameters.