Author 诗语

Textarea Field

IntroductionExampleUses

Introduction
The textarea type field, part of the Settings API, renders a textarea element.
Example
The following example shows a section with a textarea type field. The text specified in the default_value property for the textarea will display until the user enters new text and saves/submits.
array(
'title' => esc_html__( 'This is the title for Section 4', 'sometextdomain' ),
'fields' => array(
array(
'type' => 'textarea',
'name' => 'mytextarea',
'label' => esc_html__( 'This is my textarea', 'sometextdomain' ),
'default_value' => 'This is some default text that will show in the textarea',
'tooltip' => esc_html__( 'This is the tooltip for the textarea', 'sometextdomain' ),
'class' => 'large',
),
),
),

The code above will render the textarea field similar to the following:

Uses

settings_textarea()

Stripe Change Log

4.1.14.1 | 2021-06-304.0 | 2021-04-213.9 | 2020-12-163.8 | 2020-09-283.7 | 2020-07-163.6 | 2020-07-143.5 | 2020-05-213.4 | 2020-02-193.3 | 2019-12-183.2 | 2019-09-253.1 | 2019-09-183.0 | 2019-09-042.9 | 2019-08-152.8 | 2019-08-072.7 | 2019-04-172.6 | 2019-02-112.5 | 2018-04-092.4 | 2018-02-052.3 | 2017-04-282.2 | 2017-01-052.1 | 2016-09-232.0 | 2016-01-071.9 | 2015-10-091.8 | 2015-08-061.7 | 2015-06-231.6 | 2015-04-201.5 | 2014-11-191.4 | 2014-10-161.3 | 2014-09-241.2 | 2014-08-061.1 | 2014-07-291.0 | 2014-05-28

4.1.1

Updated the stripe API SDK methods.
Updated the styling for the disconnect alert messaging.
Fixed an issue where if future usage is set to 'on_session' and a user enters a 3DS card, they get an infinite loop and can't submit the form.

4.1 | 2021-06-30

Updated error messages when API isn't connected to be more informative.
Fixed an issue where the merge tags are replaced with fixed values when the subscription name is longer than the 200 character limit by Stripe.
Fixed an issue where an empty validation message appears if feed conditional logic is set.
Fixed an issue where an empty validation message appears as soon as a customer types in the credit card field.
Fixed an issue where the credit card icon overlaps with the placeholder text in the credit card field.
Fixed an issue where the form fails validation if the plan (price) or product, created by the add-on, is archived in the Stripe account.

4.0 | 2021-04-21

Added a warning notice when deprecated credit card field is still being used.
Added right-to-left language support to the Credit Card field in the form editor in Gravity Forms 2.5.
Updated styling on disconnect UI to look less like an error.
Fixed an issue where the add-on icon is missing on the Form Settings page for Gravity Forms 2.5.
Fixed an issue where the cardholder name sub-label setting is not correctly toggling in Gravity Forms 2.5.
Fixed an issue where HTML is output incorrectly when Stripe has not yet been set up.
Fixed an issue where authentication may not complete after attempting a connection with Stripe.

3.9 | 2020-12-16

Added support for the gform_ip_address filter.
Fixed an issue with the plugin settings where the default API mode is not set. Default is set to "test".
Fixed an issue where card details for the Stripe Card field is not rendered when the form also contains the default credit card field.
Fixed an issue where multiple feed specific callbacks can be processed for an entry at the same time.
Fixed an issue where an empty validation error can be applied to the Stripe Card field when some Stripe API errors occur.
Fixed an issue with the Stripe card field preview in the form editor.

3.8 | 2020-09-28

Added support for Gravity Forms 2.5.
Updated to support 50 metadata mappings.
Updated the Stripe SDK to version 7.36.1.
Fixed fatal errors which could occur if the Stripe API returned an error such as the payment amount not meeting the minimum amount for the currency.
Fixed subscription issues when a coupon is used.
Fixed stripe card field preview in the form editor.
Fixed an issue where the js.stripe.com/v3 script could be enqueued when not required.
Fixed an issue which results in charging the wrong amount when creating a subscription plan using a plan name that already exists on stripe.
Fixed an issue where an "Unable to authorize card. No response from Stripe.js." validation error occurs for forms using the Stripe Card and Invisible type reCAPTCHA fields.

3.7 | 2020-07-16

Fixed an issue where connecting to Stripe in live mode would revert to test mode.

3.6 | 2020-07-14

Added security enhancements.
Updated the Stripe card field scripts to use the credit card field input ID as the selector when mounting Stripe Elements.
Fixed a JavaScript error which could occur in some environments for the Stripe Card field scripts when using the form total as the payment amount.

3.5 | 2020-05-21

Added error messages to the Stripe Card field when no Stripe feed activated or Stripe Checkout is enabled.
Added accessibility enhancements to the Stripe Card Element so the screen readers can announce validation errors.
Added the gform_stripe_payment_intent_pre_create filter to allow modifying the payment data before creating a new payment intent.
Fixed the Stripe Checkout redirection issue for AJAX embedded forms.
Fixed the card type input of the Stripe Card field saving the brand slug returned by Stripe.js instead of the full brand name.
Fixed an issue where the credit card info is not updated after the customer replaces card details in multi-page forms.
Fixed an issue where the Stripe feed list would display a misleading configuration message in certain situations.
Fixed an issue with Stripe Elements where some amounts can lose precision when converted to the smallest unit of the currency.
Fixed PHP 7.4 notices on the settings and feed configuration pages.
Fixed a JavaScript error which could occur in some environments for the Stripe Card field scripts when using the form total as the payment amount.

3.4 | 2020-02-19

Added security enhancements.
Added support for Strong Customer Authentication (SCA) to the Stripe Card field (Stripe Elements) payment collection method.
Deprecated the Gravity Forms Credit Card Field.
Fixed an issue with Stripe feeds conflicting with feeds from other payment add-ons in the browser.

3.3 | 2019-12-18

Added security enhancements.
Fixed a PHP fatal error which can occur if the customer specified by the gform_stripe_customer_id filter can't be retrieved.
Fixed an issue where the Checkout session could fail to be created when the gform_stripe_customer_id filter returns a valid id and the customer email is supplied by the feed field mapping.
Fixed an issue where PHP fatal error is thrown when Stripe account is deleting test data.

3.2 | 2019-09-25

Fixed an issue where delayed feeds aren't triggered when a subscription trial has ended.
Fixed an issue which can prevent the redirect to Stripe Checkout occurring on some sites.

3.1 | 2019-09-18

Added the gform_stripe_discounted_line_items_name filter to change the default name for the custom line item of a discounted Stripe Checkout payment.
Added the gform_stripe_fulfillment filter to allow performing extra actions when a Stripe Checkout payment is fulfilled (it is charged or the subscription has started).
Added support for the webhook event "charge.captured" so when an authorized payment is charged, the entry payment status will change to "Paid".
Fixed an issue when some products with $0 unit price are removed from the line items for Stripe Checkout, the session fails to be created.
Fixed an issue when the product line items contain one with $0 unit price, Stripe Checkout can't create the session.
Fixed an issue where the Entry ID is missing from the payment description with Stripe Checkout.
Fixed an issue where GF Coupons discounts aren't applied to Stripe Checkout.
Fixed an issue where the merge tags in the subscription name don't work when the payment collection method is Stripe Card field or Credit Card field.
Fixed an issue where the confirmation page redirection causes PHP fatal errors when users are redirected back to the site from Stripe Checkout.

3.0 | 2019-09-04

Updated to use the new Stripe Checkout, which supports Apple Pay and Strong Customer Authentication (SCA/PSD2).
Added the gform_stripe_session_data filter to allow modifying the payment data for Stripe Checkout.
Added the gform_stripe_success_url filter to allow changing the URL that users will be sent to after completing the payment on Stripe.
Added the gform_stripe_cancel_url filter to allow changing the URL that users will be sent to after canceling the payment on Stripe.
Added the gform_stripe_url_port filter to allow changing the URL port if it's not 80.
Added the validation to webhooks signing secret fields.

2.9 | 2019-08-15

Fixed an issue where the incorrect API mode is chosen when authorizing payments.
Fixed an issue where form submissions are broken when the Stripe feeds are enabled by conditional logic.

2.8 | 2019-08-07

Added security enhancements.
Added a simpler and more secure way of connecting your Stripe account with Stripe Connect.
Added feed-level Stripe Connect. Users can connect to different Stripe accounts in feed settings.
Added the gform_stripe_connect_enabled filter to allow the disabling of Stripe Connect in order to use the legacy connection settings.
Fixed an issue cancelling subscriptions when using the gform_stripe_subscription_cancel_at_period_end filter with Stripe API version 2018-08-23 or newer.
Fixed an issue where the payment amount doesn't display correctly in the Stripe Checkout modal.
Fixed an issue when a Stripe Card field is on the page of a multi-page form, users cannot go back to the previous page by clicking on the "Previous" button.

2.7 | 2019-04-17

Fixed an issue that authorization errors weren't displayed for Stripe Checkout.
Fixed the amount decimal issue for Stripe Checkout.
Fixed an issue that no error message for the Stripe Card when no feed is activated.
Fixed an issue that when the Stripe API Publishable Key is empty or invalid, the form submission would fail but there was no error showed up for the Stripe Card field.
Fixed an issue that the Stripe Card field disappears after form validation failed in AJAX mode.
Fixed an issue that Cardholder Name in the Stripe Card field is always empty if it's not on the last page of a multi-page form.
Fixed an issue that Stripe Checkout modal should not be trigger when the form total is zero.
Added support for calculating all product fields as the form total in Stripe Checkout.
Added support to deactivate Stripe feeds when the Stripe Card field is deleted.
Added support to frontend feeds regardless of the payment collection method.
Added support for the currency filter gform_currency_pre_save_entry. Added a new JS filter gform_stripe_currency.
Updated webhook event logging statement to include the webhook API version.
Fixed Stripe Card field not rendering for forms embedded in front-end pages.
Fixed the credit card field button not being displayed in the form editor for existing installs.

2.6 | 2019-02-11

Added support for Stripe Checkout.
Added support for Stripe Credit Card (Stripe Elements).
Added support for the charge.expired event; changing the entry payment status from Authorized to Voided when an authorization expires.
Added the gform_stripe_entry_not_found_status_code filter enabling the status code to be overridden.
Reverted the callback error 'entry_not_found' to return a header status code of 200.
Fixed processing of "invoice.payment_succeeded" and "invoice.payment_failed" events with Stripe API version 2018-05-21.
Fixed a refund transaction being recorded in the sales tab when an authorized charge is manually released via the Stripe.com dashboard.
Fixed plan creation with Stripe API version 2018-05-21.
Fixed trials for new subscriptions with Stripe API version 2018-05-21.

2.5 | 2018-04-09

Updated callback error 'entry_not_found' to return a header status of 404.
Updated Stripe API library to version 5.9.2.
Fixed security issue.
Fixed subscriptions not being processed when using Stripe API version 2018-02-05 or newer.

2.4 | 2018-02-05

Added GPL to plugin header.
Added the gform_stripe_subscription_params_pre_update_customer filter allowing the subscription parameters to be overridden before the customer is subscribed to the plan.
Added support for webhook signing secrets.
Updated Plugin URI and Author URI to use https.
Updated webhook processing to use the API mode specified in the received event.
Updated Stripe API library to version 5.1.3.
Fixed API mode used to retrieve webhook event when signing secret is configured.
Fixed the card type validation message containing "false" in some situations.

2.3 | 2017-04-28

Added the gform_stripe_charge_pre_create filter.
Added translations.
Fixed spinner appearing when the previous button on the last page of a multi-page non-AJAX form is clicked.
Fixed Stripe.js request being made when the previous button on the last page of a multi-page form is clicked.
Fixed a fatal error which could occur if an older version of the Stripe API library is loaded by another plugin.

2.2 | 2017-01-05

Added $meta_key as the fifth parameter of the gform_stripe_field_value filter, containing the custom meta key currently being processed.
Updated string "Stripe Receipt" so it could be translated.
Updated Stripe API library to version 4.3.0.

2.1 | 2016-09-23

Added the gform_stripe_subscription_cancel_at_period_end filter.
Added the gform_stripe_charge_authorization_only filter.
Added the gform_stripe_customer_id filter.
Added logging of error retrieving Stripe Event object.
Added the gform_stripe_customer_after_create hook allowing custom actions to be performed between the customer being created and subscribed to the plan.
Updated included Stripe API library to latest version.
Updated subscription process to define subscription when customer is created if gform_stripe_customer_after_create filter is not defined.
Updated to only repopulate the card field within the last four digits on successful form submission.
Fixed a JavaScript error which occurred when the frontend scripts were included when the form had an active feed but no credit card field.
Fixed an issue where entry ID was not correctly populated in charge metadata.
Fixed an issue where entry ID was not correctly populated in customer metadata (for subscription feeds).
Fixed an issue which caused the credit card field required indicator to be missing when the form is displayed after a validation failure.
Fixed an issue with the card type validation.
Fixed an issue with the trial property from the $submission_data not being used.
Fixed an issue with the trial property from the $submission_data not being used when generating the plan id.
Fixed issue when sending empty meta data.
Fixed issue which could occur when saving an incomplete submission.

2.0 | 2016-01-07

Added support for sending notifications on payment/subscription events. Configured on the edit notification page using the 'Event' setting.
Added the gform_stripe_api_mode filter, e.g.
add_filter( 'gform_stripe_api_mode', function ( $api_mode ) {
return 'live';
} );
Added support for mapping a Coupon field when configuring a subscription feed.
Updated minimum Gravity Forms version to 1.9.14.17.
Updated billing cycle to include days.
Fixed an issue with zero decimal currencies.
Fixed an issue with the validation messages.
Fixed an issue with validation not returning an error if the stripe js response is empty or doesn』t contain an id.
Fixed an issue in authorize_product() and subscribe() where the entry currency was not being used.

1.9 | 2015-10-09

Updated feed list and edit pages to display configure settings message if the api keys for the selected mode are invalid.
Fixed an issue with credit card field validation when the field is marked as required.

1.8 | 2015-08-06

Updated Stripe Receipt drop down to only list email or hidden type fields.
Updated to use object notation when accessing $field.
Updated minimum Gravity Forms version to 1.9.10.19.
Fixed an issue which allowed feeds to be created with only partially configured metadata.
Fixed PHP notice related to the Metadata setting on the feed edit page.
Fixed php notice when saving a feed without any custom metadata.

1.7 | 2015-06-23

Added the ability to pass custom metadata to Stripe.
Added logging of API key validation failure (key is obfuscated).
Added $feed as the fifth parameter of the gform_stripe_charge_description filter.
Updated instructions on the settings tab for configuring Stripe webhooks.
Updated form submission to ensure form is only submitted once.

1.6 | 2015-04-20

Fixed a low severity security vulnerability in the admin area which could be exploited by authenticated users with form administration permissions.
Fixed issue where jQuery JSON library wasn't getting included.
Fixed issue that caused credit card field to get validated even when payment amount was zero.

1.5 | 2014-11-19

Added capability support and Member plugin integration.
Updated POT file.
Added Spanish (es_ES) translation.
Fixed a text domain typo in class-gf-stripe.php.
Fixed issue that prevents the form from being submitted if jQuery is put into no-conflict mode by subsequent plugins.
Created POT file.
Updated translation strings to using gravityformsstripe instead of gravityforms.

1.4 | 2014-10-16

Added text domain/path to header.
Added function gf_stripe to easily get a Stripe instance.
Updated to have the file class-gf-stripe.php and organized code into this file and stripe.php.
Updated protected functions to be public.
Updated key validation so that is is more forgiving with conflicts by trimming response before using it.

1.3 | 2014-09-24

Fixed conflict with the PayPal Add-On.
Fixed issue with email receipt feature displaying a warning when 'Do not send receipt' option was selected.
Fixed Notice message.

1.2 | 2014-08-06

Fixed issue when validating the live publishable key.

1.1 | 2014-07-29

Added receipt email feature so that Stripe receipts can be sent.
Updated key validation so that keys are trimmed before being validated and saved.
Updated API include statement so that it checks if API has already been included.
Fixed scripts from being output on every page of admin.
Fixed issue where credit card field generated validation error when navigating form.
Fixed issue with javascript error caused by the admin.js not being enqueued.
Fixed issue causing notification and confirmation to be sent blank.
Fixed issue with credit card validation.
Fixed issue where credit card was failing validation even when feed condition was not met.

1.0 | 2014-05-28

Initial release.

Survey Change Log

3.7 | 2021-04-293.6 | 2020-09-303.5 | 2020-05-133.4 | 2019-08-073.3 | 2018-12-033.2 | 2017-05-163.1 | 2016-08-313.0 | 2016-04-142.6 | 2015-10-082.5 | 2015-02-162.4 | 2014-10-162.3 | 2014-09-242.1 | 2014-02-282.0 | 2014-02-111.0.41.0.31.0.21.0.1 | 2013-06-211.0 | 2013-06-121.0.beta21.0.beta1

3.7 | 2021-04-29

Added right-to-left language support for the Rating, Rank, and Likert survey field types.
Fixed an issue where script tags are output above the document head element.
Fixed an issue with Likert Survey field on mobile when the labels are hidden.
Fixed CSS styles for better compatibility with Gravity Forms 2.5.
Fixed a deprecated usage of jQuery ready event.

3.6 | 2020-09-30

Added support for Gravity Forms 2.5.
Fixed an issue where survey dropdown field is not displayed properly if the field type was single line text with a mask before it was changed to dropdown.

3.5 | 2020-05-13

Added security enhancements.
Updated Javascript files, stylesheets to use minified versions.
Updated Javascript events to use standard Gravity Forms events for consistency.
Fixed an issue where the "n of n items shown" message from the form editor can be displayed on the front-end when the Rank field choices are populated via a filter.
Fixed an issue with the label styles used by the field general settings in the form editor.

3.4 | 2019-08-07

Added security enhancements.
Updated Likert field entries page filters for Gravity Forms 2.4+.

3.3 | 2018-12-03

Added security enhancements.
Added "value" modifier to Likert field merge tag to return column text only.
Updated compatibility issue with conditional logic and Gravity Forms 2.4.

3.2 | 2017-05-16

Added Chinese (China) translation. Credit: Edi Michael.
Updated minimum Gravity Forms version to 2.0.
Updated strings for translations.
Updated Likert CSS for better mobile display.
Updated low resolution PNG icons with scaleable vector graphics (SVG).
Fixed Survey field settings referencing incorrect icon URLs.
Fixed an issue with the Likert field markup.
Updated inline image in rank field so that it is applied via CSS instead.
Fixed an issue with the locations the gform_merge_tags hook was being used to include the merge tags.

3.1 | 2016-08-31

Fixed an issue with Likert field column labels which contain HTML displaying the HTML markup for mobile devices.
Fixed issue exporting Likert field values if the row label included trailing spaces.
Fixed an issue validating/saving the multi-row Likert field which could occur if the field has had ten or more rows defined and then one or more rows removed causing a mismatch between the ids used in the front-end input name attributes and the ids in the field inputs property.
Fixed an issue with how the empty Likert field value was handled in the {all_fields} output.
Fixed an issue which caused the Likert field value to be lost when editing the entry.
Fixed an issue which could prevent field values of 0 being displayed on the entry detail page.

3.0 | 2016-04-14

Added support for Gravity Forms v2.0.
Added GF_Field_Rating.
Added GF_Field_Rank.
Added GF_Field_Survey.
Added GF_Field_Likert.
Added DocBlocks.
Added support for using the Rating type field with conditional logic.
Added support for exporting the choice text when using the 2015 batch & future feed add-ons. Requires Gravity Forms 1.9.15.12.
Added label and description placement setting to the Survey field.
Updated minimum Gravity Forms version to 1.9.17.
Updated to use object notation when accessing the field object.
Updated the styles to adapt better to different screen sizes.
Updated the score merge tag to support returning the Likert row score e.g. {score:id=1.5} would return the score for field 1 row 5.
Updated Likert field preview in form editor to display only the first five rows.
Increased width of input boxes for weighted score values.
Fixed an issue with the tooltip in the rank field where text can get cut off if certain special characters are included in the choice label.
Fixed an issue with the merge tag values in the query string of a redirect confirmation.
Fixed an issue with empty Likert fields being displayed on the entry detail page when 'show empty fields' is not selected.
Fixed a typo in the Rank type fourth choice string.
Fixed an issue with the Likert field in entry exports when the field rows are changed after entries are saved.
Fixed an issue with some untranslatable strings.
Fixed an issue with the display of Likert field values for some entries on the entry list when the field rows are changed after entries are saved.
Fixed an issue with the Likert field label for attribute.

2.6 | 2015-10-08

Fixed an issue with the input ID attributes for the Likert and Rating type fields.
Fixed an issue in the form editor where removing a likert row didn't remove the corresponding input property.
Fixed an issue which caused survey merge tags to be replaced during form render.
Fixed an issue with the Likert field row specific merge tag which caused all the rows to be included in the output instead of just the specified row.

2.5 | 2015-02-16

Added support on the results page for score averages by row in multi-row Likert fields (requires Gravity Forms 1.9).
Added Spanish (es_ES) translation.
Updated front-end script dependency to include jquery-touch-punch on mobile devices enabling touch support for the Rank field.
Updated POT file.
Fixed an issue with the processing of merge tags for multi-row Likert fields which would prevent the field being included in notifications/confirmations when using Gravity Forms 1.9.
Fixed two untranslatable strings in the form editor.
Fixed a notice in the entry detail page for imported forms.
Fixed an issue under PHP 5.2 where score for multi-row likert field was not displayed correctly in email notification if any row was not answered.
Fixed an issue where score for multi-row likert field was not displayed correctly in email notification if any row was not answered.

2.4 | 2014-10-16

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

2.3 | 2014-09-24

Adding tabbing support for likert fields.
Updated the ratings field UI in the form editor to display the choices in the more natural order of worst at the top to best at the bottom instead of the reverse. The front-end UI is not affected.
Fixed issue where score for multi-row likert field was always 0 if any row was not answered.
Fixed the field title in the Form Editor.
Fixed a strict notice preventing the results to be displayed in PHP 5.4+.
Fixed an issue with the dynamic population parameter names for multi-row Likert fields reverting to default values after re-opening the field settings.
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.

2.1 | 2014-02-28

Fixed issue when exporting entries.

2.0 | 2014-02-11

Added integration with the Add-On Framework.
Added integration with the Campaign Monitor Add-On, MailChimp Add-On, AWeber Add-On, and Zapier Add-On.
Fixed entries tab for the Contacts Add-On.
Fixed entry editor; scripts and styles now loaded.

1.0.4

Added support for survey entries tab in the Contacts Add-On.
Fixed an issue where survey merge tags would appear in the list of merge tags available during pre-submission.
Added support for decimal score values in the Likert field.

1.0.3

Added total score to entry meta.
Added total score entry meta to the results filters and to the conditional logic filters for notifications and confirmations. Only available for likert fields with scoring enabled.

1.0.2

Requires Gravity Forms version 1.7.6.6+.
Implemented the Add-On Framework.
Added weighted scoring for likert fields.
Added score merge tags.

1.0.1 | 2013-06-21

Fixed an issue with multi-row likert fields having more than 9 rows. The submitted value for every tenth row would not be saved.

1.0 | 2013-06-12

Changed the validation of required multi-row likert fields to require responses for all rows.
Fixed an issue with entries export where the choice value could be exported instead of the label.
Fixed an issue with results not being displayed when double quotes are inside field choices labels.
Fixed an issue with results not being displayed in no conflict mode.
Fixed an issue with multi-row likert fields and rank fields not retaining selected values when stepping back a page on multi-page forms.
Fixed an issue with multi-row likert fields not importing correctly.
Fixed an issue with rank fields not working on some pages of multi-page ajax-enabled forms.

1.0.beta2

Added gform_form_pre_results filter so the form object can be manipulated before the results are calculated for the admin results page.
Added required field setting to likert and rating fields.
Added tooltips for the field settings.
Fixed an issue where the plugin couldn't be activated on servers with shorttags disabled.
Fixed merge tags for likert multple rows and rating fields.

1.0.beta1

Initial version.

Slack Update for New API

SummaryEffect of Deprecation on Versions 1.12 and PriorUpgrade ProcessTeam Invite Feature Deprecation

Summary

On Feb 24th, 2021, Slack will be deprecating their older API methods in favor of their updated Conversations API.
Users of the official Gravity Forms Slack Add-on will need to update to version v1.13 or later to use the new API methods..
Failure to update will affect feed settings after the Slack API deprecation date of Feb 24.
The 「Team Invites」 feature offered in previous versions will no longer work as of this update. Refer to this section.

Effect of Deprecation on Versions 1.12 and Prior
Users who do not upgrade will no longer be able to modify their Slack feed settings after February 24th, as the API endpoints used to list channels and group IMs will not be accessible. Upgrading will restore expected functionality to the feed settings.
Upgrade Process
Users who update to the new version will need to re-authenticate with their Slack service. You do that by disconnecting and reconnecting.

Disconnect from Slack using the 「Disconnect」 button in the Slack Add-On Settings page.
Connect to Slack again using the normal process described here.

After that, functionality should continue to work as it previously did with no changes needed, except the Team Invite feature, as described below.
Team Invite Feature Deprecation
Previous versions of our Slack Add-On offered the Team Invite feature, which relied on a legacy API endpoint and the admin scope of a legacy API token.
Under the new Slack API and tokens, the endpoints offered for this feature are now only available to Slack Enterprise Grid accounts.
As of this update, this feature will no longer function within our Slack Add-On.

Total

SummaryCommon SettingsMerge TagsUsageModifiers

Summary

The Total field specifies where the order total should be displayed in the form. As the user selects products and options, the total will automatically update. It is available under the Pricing Fields section within the form editor.

Total field as displayed in the Field Library

Total field as displayed in the Form Editor.

Common Settings

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

Merge Tags

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

Usage

{Field Name:2:modifier}

Modifiers

ModifierDescription:priceUsed to denote that the amount displayed by the merge tag should be formatted as currency.

Submission Data Object

IntroductionUsagePropertiesLine ItemOptionHooks

Introduction
Submission Data ($submission_data) is an associative array containing all the payment related properties for the entry being processed by an add-on which extends the GFPaymentAddOn class. It is generated by GFPaymentAddOn::get_submission_data() during form validation.
Usage
We recommend accessing the properties in $submission_data using the rgar() function e.g.
1$payment_amount = rgar( $submission_data, 'payment_amount' );

Properties

form_title string
The form title.

email string
The value of the field which was mapped to the billing information Email field (not available to all add-ons).

address string
The value of the field which was mapped to the billing information Address field (not available to all add-ons).

address2 string
The value of the field which was mapped to the billing information Address 2 field (not available to all add-ons).

city string
The value of the field which was mapped to the billing information City field (not available to all add-ons).

state string
The value of the field which was mapped to the billing information State field (not available to all add-ons).

zip string
The value of the field which was mapped to the billing information Zip field (not available to all add-ons).

country string
The value of the field which was mapped to the billing information Country field (not available to all add-ons).

card_number string
The Credit Card number last 4 digits, padded with X (not available to all add-ons).

card_expiration_date array
The Credit Card expiration month and year (not available to all add-ons).

card_security_code string
The Credit Card security code (not available to all add-ons).

card_name string
The Credit Card cardholder name (not available to all add-ons).

payment_amount float
Either the form total or the value of the field mapped to the feeds payment amount or recurring amount setting.

setup_fee integer
Zero or the value of the field mapped to the setup fee setting.

trial integer
Zero, the trial amount, or the number of days the trial should last.

line_items array
An indexed array of line items with unit prices greater than or equal to zero. Created from the submitted pricing fields. See Line Item for available properties.

discounts array
An indexed array of line items with negative unit prices. e.g Coupon fields. See Line Item for available properties.

Line Item
12345678array(    'id'          => 1,    'name'        => 'Product A',    'description' => '',    'quantity'    => '1',    'unit_price'  => 10,    'options'     => array(),)
Each line item is an associative array containing the following properties.

id integer
The field ID.

name string
The product name or shipping name.

description string
Comma separated string of selected option names.

quantity integer
The quantity.

unit_price float
The total unit price for the product and any selected options or the shipping price.

options array
An indexed array of the selected product options. See Option for available properties.

is_shipping boolean
Only present if the line item is from the shipping field. Value will be true.

Option
123456array(    'field_label'  => 'Option',    'option_name'  => 'First Option',    'option_label' => 'Option: First Option',    'price'        => '10',)
Each option is an associative array containing the following properties.

field_label string
The option field admin label or choice label.

option_name string
The choice label or value if values are enabled on the field.

option_label string
The colon separated field_label and option_name.

price string
The option price.

Hooks
The Submission Data can be modified by using the gform_submission_data_pre_process_payment filter.

Setting Up the Postmark Add-On

Pre-RequisitesSetup

Pre-Requisites

Download and install the add-on
A Postmark account

Setup
Before you can start configuring your notifications to go through Postmark, you first need to do a quick bit of setup so that Gravity Forms is able to communicate with your Postmark account.

Log into your WordPress admin dashboard.
On the left side navigation menu, hover over Forms and click on Settings.
From this page, click the Postmark tab.
Enter your Account API Token and Server API Token. This is obtained from Postmark. If you are unsure of how to obtain your API key, take a look at our article on obtaining your Postmark API tokens.
Click Update Settings. If you』ve entered your account information correctly, you will be notified by green check marks beside each box. If you do not see green check marks, please double check this information and try again.

Once you have entered your API tokens, you』re ready to begin sending form notifications using Postmark.

Setting Up the Coupons Add-On

Pre-RequisitesSetup

Pre-Requisites

Download and install the add-on
At least one Product Field and one Total Field on your form

Setup
Make sure the form you want to use a coupon for contains a product field and a total field.
Once you have installed the add-on and setup your form, you』re ready to begin creating a feed for the Coupons Add-On.

Setting Up the Zoho CRM Add-On

Pre-RequisitesZoho CRM SettingsAuthentication (v1.8)Authentication (v1.7 and below)ScreenshotsA. OAuth Authentication MethodB. Email Address and Password Authentication MethodC. Third Party Service (Google Apps, Facebook, Yahoo) Authentication Method

Pre-Requisites

Download and install the add-on
A Zoho CRM account

IMPORTANT: Zoho CRM』s API Version 1.0 has been deprecated and will no longer work as of 12/31/2019. You MUST switch to the OAuth Authentication Method, which uses API Version 2.0, by this time in order for continuous operation of the Zoho CRM add-on.
Until you have switched to the OAuth Authentication option, you will see the message 「Zoho CRM』s v1 API has been deprecated. To use the v2 API, please switch your Zoho CRM Authentication method to OAuth Authentication.」 in your Dashboard.

Zoho CRM Settings

Log into your WordPress admin dashboard.
On the left side navigation menu, hover over Forms and click on Settings.
From this page, click the Zoho CRM tab.

Authentication (v1.8)

Click the 「Connect to Zoho CRM」 button.

Click the 「Accept」 button to allow the Gravity API access to the data in your Zoho account.

Authentication (v1.7 and below)

Choose a method of authentication.
a. OAuth Authentication (recommended) Screenshot A
This authentication method is available as of Zoho CRM Add-On version 1.6 and uses Version 2.0 of Zoho CRM』s API. This new API replaces version 1.0, which will no longer work as of 12/31/2019. This option MUST be used for Zoho CRM by then and you are encouraged to switch before its end-of-life date.

Click the button to authenticate with Zoho CRM. If authenticated, the text 「Signed into Zoho CRM.」 will display with a De-authorize button.

b. Email Address and Password Screenshot B
This authentication method uses Zoho CRM』s original API, Version 1.0. This API has been deprecated and will no longer work as of 12/31/2019. You must switch to the OAuth Authentication option by then. If the OAuth Authentication option is not available, please download the latest Zoho CRM Add-On.

Enter your Zoho CRM Email Address and Password.
Click Update Settings. If you have entered your account information correctly, you will be notified by a green check mark beside each box. If you do not see green check marks, please double check this information and try again.

c. Third Party Service (Google Apps, Facebook, Yahoo) Screenshot C
This authentication method uses Zoho CRM』s original API, Version 1.0. This API has been deprecated and will no longer work as of 12/31/2019. You must switch to the OAuth Authentication option by then. If the OAuth Authentication option is not available, please download the latest Zoho CRM Add-On.

Click the button to generate an authentication token.
Enter the token.
Click Update Settings. If the token is correct, a green check mark will appear next to the button.
Once you have authenticated, you are ready to begin creating a feed for the Zoho CRM Add-On.

Note: If your Zoho CRM account is hosted in the EU, you will need to configure the add-on accordingly. See the Zoho European Hosted Accounts page for more information.
Screenshots
A. OAuth Authentication Method

B. Email Address and Password Authentication Method

C. Third Party Service (Google Apps, Facebook, Yahoo) Authentication Method

Setting up the reCAPTCHA Add-On

IntroductionSettingsSetup ProcessesGetting Your KeysAdding Your KeysSetting a threshold

Introduction

The official Gravity Forms reCAPTCHA Add-On brings Google』s reCAPTCHA v3 technology as an addition to your anti-spam toolbox. This article describes how to configure the basic settings for use.

Settings

For a full list of all the reCAPTCHA Add-On settings, refer to this guide.

Setup Processes

This guide covers the following setup processes for both v2 and v3 reCAPTCHA types.

Getting your keys (v2 or v3).Adding your keys (v2 or v3).Setting a score threshold (v3 only).

Getting Your Keys

Google reCAPTCHA keys need to be registered for each site you wish to use the service on. Follow these steps for both v2 and v3 reCAPTCHA services.

Go to Google reCAPTCHA admin. If necessary, login with your Google developer account. Click + to generate a key pair for your site. Make sure to generate the correct type of key, as v2 and v3 keys are not interchangeable.Make note of the two keys you have generated.

Adding Your Keys

To validate the communication between your site and the Google service, you will need to tell Gravity Forms this unique key pair.

Navigate to Forms → Settings → reCAPTCHA.Enter the site key and secret key you previously recorded under the v2 or v3 settings section. For v3 keys, you should immediately see a green check mark for both keys, meaning they have been validated.For v2 keys, choose the version of reCAPTCHA v2 you wish to use, Checkbox or Invisible. This is a site wide setting, and cannot be varied form to form. Note that Checkbox keys are not valid for use with invisible reCAPTCHA.For v2 keys, you will need to click the 「I am not a robot」 reCAPTCHA checkbox in order to validate the keys.

Setting a threshold

This process is applicable only to reCAPTCHA v3.

The threshold determines what Gravity Forms will do with form entries based on the reCAPTCHA v3 score they receive. Entries with a reCAPTCHA score less than or equal to this value will be classified as spam. For more information, refer to this Google article.

By default, the threshold is set to 0.5. If you wish to modify this, follow this procedure:

Navigate to Forms → Settings → reCAPTCHA.Enter the threshold value you wish. The higher the score (from 0 to 1) returned from Google, the more likely it reflects a good interaction. This threshold value will affect new entries received from that point on.