SummaryUsageNotes
Summary
Displays the total score for the survey. Scoring must be enabled on the survey field for it to be tallied.
Usage
{survey_total_score}
Notes
Quiz and Survey related merge tags can only be used in confirmations and notifications.For more information, Refer to our Survey Add-On documentation.
2.0 | 2021-04-211.13 | 2021-02-101.12 | 2020-09-281.11 | 2020-07-141.10 | 2020-05-201.9 | 2019-08-071.8 | 2018-04-091.7 | 2017-05-161.6 | 2017-01-051.5 | 2016-08-311.4 | 2016-08-021.3 | 2015-08-241.2 | 2015-07-221.1 | 2015-05-081.0 | 2015-05-04
2.0 | 2021-04-21
Added a mechanism to cache API requests for private group and channel lists for 1 hour to improve performance.
Updated the feed settings screen to remove the "Invite to Team" action as it's no longer supported by Slack for standard workspaces, and included a notice for existing feeds.
Fixed an issue where the feed settings are not displaying the full collection of private groups or channels for Slack workspaces with more than 100 of either set.
Fixed an issue where the add-on icon is missing on the Form Settings page for Gravity Forms 2.5.
Fixed an issue where private groups and channels are not showing up in the feed settings.
Fixed an issue where the Connect to Slack button is hidden if the auth token is invalid or revoked.
1.13 | 2021-02-10
Added a notification to alert site admins that re-authentication with Slack is required before 24 February 2021.
Updated the add-on to communicate with Slack using its new API endpoints.
1.12 | 2020-09-28
Added support for Gravity Forms 2.5.
Removed support for legacy tokens.
1.11 | 2020-07-14
Added security enhancements.
1.10 | 2020-05-20
Added translations for Hebrew, Hindi, Japanese, and Turkish.
Updated Javascript files, stylesheets to use minified versions.
1.9 | 2019-08-07
Added security enhancements.
1.8 | 2018-04-09
Added GPL to plugin header.
Added security enhancements.
Added support for legacy tokens.
Fixed entry URL containing HTML entities in message.
Updated Plugin URI and Author URI to use https.
1.7 | 2017-05-16
Removed "Select a Channel" option from Channels feed setting when inviting to team.
Updated initial authentication process.
1.6 | 2017-01-05
Added gform_slack_invite filter for modifying invite user parameters.
Added support for auto-inviting to specific channels when inviting users to team.
Added support for mapping first and last name when inviting users to team.
Fixed strings for translations.
Fixed an issue with the request failed message when a WP_Error occurs.
1.5 | 2016-08-31
Added upgrade routine to automatically define team name when a valid authentication token exists.
Updated team name plugin setting to automatically add team name when adding a valid authentication token.
Updated invite to team feature to only be available when API user is an admin.
Updated wording from IM to Direct Message within the feed settings.
Removed duplicate conditional logic setting.
1.4 | 2016-08-02
Added ability to invite users to team.
Added conditional logic to feed settings.
Added default feed name when creating a new Slack feed.
Added feed duplication support.
Added the gform_slack_process_message_shortcodes filter for enabling the processing of shortcodes placed in the message.
Added visual icon to "Send To" feed settings field.
Updated API library naming to prevent conflicts with third-party Slack API libraries.
1.3 | 2015-08-24
Added support for custom message usernames using gform_slack_username hook.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Fixed PHP warning related to attachments.
1.2 | 2015-07-22
Added support for attaching images to messages.
Added gf_slack() for easily getting a Slack instance.
Added support for custom message icons.
1.1 | 2015-05-08
Added support for sending messages to private groups and users.
Added Spanish (es_ES) translation.
Prevent empty messages from being posted to room.
1.0 | 2015-05-04
It's all new!
SummaryCommon SettingsGeneral SettingsAppearance SettingsMerge TagsUsageModifiers
Summary
The Time field allows users to submit a time as hours and minutes. This field automatically validates that the information entered was formatted correctly. It is available under the Advanced Fields section within the form editor.
Time field as displayed in the Field Library
Time field as displayed in the Form Editor.
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
SettingDescriptionTime FormatSelect the format you would like to use for the time field. Available options are 12 hour (i.e. 8:30 pm) and 24 hour (i.e. 20:30).Custom Sub-LabelEnter values in this setting to override the sub-label for each field.
Appearance Settings
SettingDescriptionSub-Label PlacementSimilar to the Description Placement option, but instead changes the sub-label placement.
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.
Modifiers
This field does not have any modifiers.
IntroductionSettings1. Stripe Credit Card Field (Stripe Elements)DescriptionBenefitsPre-Requisites2. Stripe Payment Form (Stripe Checkout):DescriptionBenefitsPre-Requisites3. Gravity Forms Credit Card Field (deprecated)
Introduction
Gravity Forms Stripe Add-On version v2.6 increased the number of options available for processing credit cards using Stripe. This article gives a brief overview of those payment collection methods.
Settings
The option 「Payment Collection Method」 is set via the Stripe Add-On Settings page.
1. Stripe Credit Card Field (Stripe Elements)
Description
The Stripe Credit Card field is hosted on Stripe』s servers and displayed on your form using an iframe. Your Gravity Form collects all data except the credit card (and optionally, the Cardholder Name) fields, which are collected securely by Stripe and transmitted over HTTPS connection to their processing servers. Those Stripe collected details are not stored with your entry data.
Benefits
Reduces your responsibility for handling and securing sensitive payment information as that process is handled by Stripe.is SCA ready as of version 3.3.1.can help you meet your PCI compliance requirements, such as Stripe』s easier PCI compliance process, Pre-filled SAQ A.
Pre-Requisites
the Stripe Add-On must be installed and active.have selected Stripe Credit Card field as your payment collection method within the Stripe settings.the checkout page must be a secure https:// address.
Then the field is available under the Pricing Fields section of the Gravity Forms Editor.
Note: Stripe.com will render the inputs for the card details only if your form has an active Stripe feed configured. Also if your Stripe feed has conditional logic, you will want to configure the Stripe Card field with the same logic.
2. Stripe Payment Form (Stripe Checkout):
Example of the Stripe Checkout form.
Description
Form submission will trigger the opening of a Stripe hosted form to collect all the payment details directly within Stripe』s domain, including required data such as email, billing address, or any other verification fields as demanded by your payment processing flow.
Note: This collection method will not make a credit card field available in the list of available Pricing fields to add to a form as a credit card field is not required for this collection method.
Benefits
Reduces your responsibility for handling and securing sensitive payment and customer information, as none of the payment form collected data is stored by your Gravity Forms databases.is SCA ready.can support additional payment methods like Apple Pay or Google Pay.can help you meet your PCI compliance requirements, such as Stripe』s easier PCI compliance process, Pre-filled SAQ A.
Pre-Requisites
have the Stripe Add-On installed and active.have Stripe Payment form (Stripe Checkout) selected as your payment collection method within the Stripe settings.when using this method, you configure the payment collection form and fields via your Stripe account, and not within the Gravity Forms editor.If any of your form notifications is intended to be sent when the payment is done, you would need to change the notification Event setting from the default 「Form is submitted」 to 「Payment Completed」 if you use a Products and Services feed, or 「Subscription Created」 for Subscription feeds.to support Apple Pay or Google Pay, you must login to your Stripe account, go to Settings → Checkout and Payment Links, and then toggle the desired payment options as shown here:
3. Gravity Forms Credit Card Field (deprecated)
This collection method has been deprecated in Stripe Add-On version 3.4. Refer to this document for more information.
IntroductionExampleUses
Introduction
The text type field, part of the Settings API, renders a text input.
Example
The following example shows a section with two text boxes.
The first text box is required and upon submission, the function validate_mytextfield specified in the feedback_callback property will be called to check additional conditions.
The second text box only displays based on the result of the dependency property. If the field mytextfield_name (the first text box) has a value of showtestfield2 or test, the second text box will display.
array(
'title' => esc_html__( 'This is the title for Section 1', 'sometextdomain' ),
'description' => esc_html__( 'This is a description of the purpose of Section 1', 'sometextdomain' ),
'fields' => array(
array(
'type' => 'text',
'id' => 'mytextfield_id',
'name' => 'mytextfield_name',
'label' => esc_html__( 'This is my text field', 'sometextdomain' ),
'required' => true,
'value' => 'This is the data specified for the value property',
'default_value' => 'This is the data specified for the default value property',
'class' => 'medium',
'tooltip' => esc_html__( 'This is my tooltip', 'sometextdomain' ),
'tooltip_class' => 'tooltipclass',
'feedback_callback' => array( $this, 'validate_mytextfield' ),
),
array(
'type' => 'text',
'name' => 'mytextfield2_name',
'label' => esc_html__( 'This is my second text field', 'sometextdomain' ),
'dependency' => array( 'field' => 'mytextfield_name', 'values' => array( 'showtextfield2', 'test' ) ),
),
)
),
The code above will render the text boxes similar to the following:
Uses
settings_text()
IntroductionPre-RequisitesSetup StripeSetup Your FormSetup Stripe FeedsViewing Sales ResultsAbout Payment Collection MethodsStripe Subscription CancellationsStripe Add-On HooksAdd-On Framework Hooks
Introduction
Gravity Forms and Stripe allows you to quickly and easily implement credit card payments with WordPress. With the Stripe Add-On you can capture one time credit card payments or setup recurring payment subscriptions.
If you are familiar with our other Gravity Forms Add-Ons, or even if you』re not, you』ll be right at home getting started with the Stripe Add-On!
Pre-Requisites
Gravity Forms v2.4+
WordPress v3.8+
SSL Certificate Installed and Configured
Download and install the add-on
A Stripe account
Because of the secure nature of capturing credit card information, you will be required to purchase and 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 Stripe
Learn how to setup the Stripe Add-On in our Setting Up the Stripe Add-On article.
Setup Your Form
Refer to the Setting Up a Stripe Compatible Form article for detailed instructions on how to setup your form to be compatible with the Stripe Add-On.
Setup Stripe Feeds
Now that you have configured the Stripe Add-On to work with your Stripe account, and you have a form configured and ready to interact with Stripe, it』s time to bring it all together by configuring the form to integrate with Stripe. Just like all of Gravity Forms Add-Ons, this integration is done by creating a feed.
Review our Creating a Feed for the Stripe 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.
About Payment Collection Methods
The Stripe Add-On offers multiple methods to collect payment information. Each method offers a different split of responsibilities between your form and Stripe as pertains to the collection and storage of payment related information. See this help article for more information on the payment collection methods offered.
Stripe Subscription Cancellations
When setting up a Stripe Subscription, please keep in mind that the only way to currently cancel a subscription is via the WordPress Admin or the Stripe admin. You can cancel an existing subscription by viewing the entry associated with the subscription and choosing the cancel option for the Stripe subscription.
Stripe Add-On Hooks
The Stripe Add-On provides hooks that can be used to modify the default functionality or extend it. For more information, review the Stripe Add-On Hooks.
Add-On Framework Hooks
Because the Stripe 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 Stripe.
Pre-RequisitesSetup
Pre-Requisites
Gravity Forms v1.9+
WordPress v3.5+
Download and install the add-on
Setup
Setting up the Gravity Forms Survey Add-On is easy. Once you have installed and activated the plugin, you』re done!
Now you』re ready to begin using the Survey Add-On.
IntroductionUsageProperties
Introduction
The Feed Object meta for the Slack add-on is an associative array containing the properties which determine how the add-on should process the form submission.
$feed['meta'] = array(
'feed_name' => 'Your Feed Name',
'message' => 'Entry #{entry_id} ({entry_url}) has been added.',
'feed_condition_conditional_logic' => true,
'feed_condition_conditional_logic_object' => array(
'conditionalLogic' => array(),
),
);
Usage
We recommend accessing the $feed meta using the rgar() or rgars() functions, e.g.;
$conditional_logic_enabled = rgars( $feed, 'meta/feed_condition_conditional_logic' );
Properties
feed_name string
The feed name which appears on the add-ons feeds tab.
send_to string
The type of channel Slack will send the message to: Possible values: channel, group or user.
channel string
The ID of the Slack channel this feed will post a message to when processed.
group string
The ID of the Slack private group this feed will post the message to.
user string
The ID of the Slack user this feed will post the message to.
message string
The message that will be posted to Slack. Can contain merge tags.
feed_condition_conditional_logic boolean
Is the feed condition (conditional logic) setting enabled. Default is false.
feed_condition_conditional_logic_object array
An associative array containing the conditional logic rules. See the Conditional Logic Object for more details.
ContainerTotal Price
Container
example: total field container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_total {border: 1px solid red;}
example: total field container (div) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_total {border: 1px solid red;}
example: total 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 .ginput_container_total {border: 1px solid red;}
Total Price
example: total price (span) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_total .ginput_total {color: red;}
example: total price (span) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_total .ginput_total {color: red;}
example: total price (span) – 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 .ginput_container_total .ginput_total {color: red;}
IntroductionWhat is SCA (Strong Customer Authentication)?How does this affect Stripe?So will all my transactions through Stripe now work with financial institutions using SCA?I don』t need any of the security of SCA, does this affect me?
Introduction
Version 3 of the official Gravity Forms Stripe Add-On made a number of changes to bring our add-on into line with Stripe』s updates around Strong Customer Authentication (SCA) and their new API. This article gives you the basics regarding SCA.
What is SCA (Strong Customer Authentication)?
SCA is a requirement of the EU Revised Directive on Payment Services (often referred to as just PSD2), that affects payment service providers within the European Economic Area. It is intended to ensure that electronic payments are performed with multi-factor authentication, to increase the security of electronic payments.
How does this affect Stripe?
This directive affects all payment gateways that want to collect payments from financial institutions who will be requiring SCA. To that end, Stripe has updated their API to ensure they can meet these requirements. Stripe has a suite of documentation to describe the implications for them and their customers.
So will all my transactions through Stripe now work with financial institutions using SCA?
It will depend upon the collection method you use. Payments collected using:
Stripe Checkout method in Stripe Add-On version 3.0 or higher
Stripe Credit Card field (also called Stripe Elements) in Stripe Add-On version 3.3.1 or higher
…are both SCA ready.
Collecting information using the Gravity Forms Credit Card field does not comply with SCA requirements.
I don』t need any of the security of SCA, does this affect me?
Not in practice, no, but do note that the 3.0 update also modified the flow for Stripe Checkout, and removed some existing Stripe Add-On hooks. Review this guide to see a list of those changes.
