Slack Feed Meta

Slack Feed Meta

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.

Slack Change Log

Slack Change Log

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!

Single Line Text

Single Line Text

SummaryCommon SettingsInput MaskMerge TagsUsageModifiers

Summary

The Single Line Text field allows users to submit a single line of text. This basic field can be used for anything where no more than a single line of input is required. It is available under the Standard Fields section within the form editor.

Single Line Text field as displayed in the Field Library

Single Line Text 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.

Input Mask

Single Line Text and Post Custom Field are the only fields that have the Input Mask setting. You can learn more about input masks in this article.

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.

Single Line Text Field CSS Selectors

Single Line Text Field CSS Selectors

ContainerInputMaximum Characters Counter

Container

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

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

example: single line 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_text {border: 1px solid red}

Input

example: standard text field (input) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_text input[type=text] {border: 1px solid red}

example: standard text field (input) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_text input[type=text] {border: 1px solid red}

example: standard text field (input) – applies just to specific text 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 .ginput_container_text input[type=text] {border: 1px solid red}

Maximum Characters Counter

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

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

example: standard text field (input) – applies just to specific text 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 .ginput_container_text .charleft {border: 1px solid red}

Signature

Signature

SummaryCommon SettingsAppearance SettingsEntry DetailsMerge TagsRelated Filters

Summary

The Signature field for Gravity Forms allows you to capture signatures online by allowing users to sign your forms using touchscreen devices, touch pads or mouse. It is available under the Advanced Fields section within the form editor.

Signature field as displayed in the Field Library

Signature field as displayed in the Form Editor.

Common Settings

For a description of each of the common field settings, refer to this article. Below you will find descriptions of specialty settings that are particular to this field.

Appearance Settings

SettingDescriptionBackground ColorSelect the background color of the Signature field.Border ColorSelect the border color of the Signature field.Border WidthSelect the border width of the Signature field from a dropdown.Border StyleSelect the border style of the Signature field from a dropdown.Pen ColorSelect the pen color of the Signature field.Pen SizeSelect the pen size of the Signature field from a dropdown.Field WidthSelect the field width of the Signature field.

Entry Details

When you view the Entry Details for a Form Entry that contains a Signature field, you will see the signature included in the entry details. The signature will be presented as a thumbnail image and you can click on the thumbnail to see the full size version of the signature itself.

Merge Tags

For security reasons it is not automatically included as part of the {all_fields} merge tag output. You can include signatures in your email notifications by inserting the merge tag for your Signature field in the message of your notification.

Related Filters

The following filter was added to Gravity Forms in support of the signature field:

gform_signature_show_in_all_fields

Signature Change Log

Signature Change Log

4.1.24.1.14.1 | 2021-09-014.0 | 2020-09-233.9 | 2020-05-183.8 | 2019-07-313.7 | 2019-03-193.6 | 2018-12-183.5 | 2018-04-093.4 | 2018-01-293.3 | 2016-10-263.2 | 2016-10-263.1 | 2016-06-163.0 | 2016-04-142.4 | 2016-01-062.3 | 2014-10-162.2 | 2014-04-142.1 | 2014-01-312.0 | 2014-01-291.3 | 2013-03-071.2 | 2012-09-131.1 | 2012-08-301.0 | 2012-07-02

4.1.2

Fixed an issue where the signature field has no width when other forms fields use conditional logic.

4.1.1

Fixed an issue where the signature field does not work correctly for mobile/touch devices.
Fixed an issue where the lock reset button is not hidden when clicking the signature reset button when a signature is present and the screen is resized.
Fixed an issue where a conditionally hidden signature field's width is not updated or responsive.
Updated SuperSignature to version 1.5.0.4.

4.1 | 2021-09-01

Fixed JavaScript errors on the edit entry page that prevent the signature field from being edited.
Fixed an issue that causes the signature field to throw a JavaScript error on the front-end when the data input doesn't exist.
Fixed an issue where script tags are output above document head element.
Fixed a fatal error which can occur when saving the signature in some hosting environments.

4.0 | 2020-09-23

Added security enhancements.
Added the gform_signature_url, gform_signature_url_permission_granted, and gform_signature_url_require_login filters.
Added support for Gravity Forms 2.5

3.9 | 2020-05-18

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added the label visibility and description placement settings to the field appearance tab.
Updated Javascript files to use minified versions.
Fixed signing issue with Windows touch devices.

3.8 | 2019-07-31

Added a check to GFSignature::display_signature() to only use mime_content_type() if the signature image file is local.
Added security enhancements.
Added the gform_signature_delete_file_pre_delete_entry filter to disable deletion of the signature file or trigger deletion at a later time.

3.7 | 2019-03-19

Fixed signature field not appearing on single page forms or multi-page forms embedded without AJAX.
Fixed signature field disappearing on multi-page forms embedded via AJAX when rotating mobile device.
Fixed extra lines added to signature when signing with Chrome on Android.
Fixed issue where signature was clipped when rotating on mobile devices.

3.6 | 2018-12-18

Added responsive support to Signature field.
Fixed fatal error when displaying the signature image on some servers.
Fixed PHP warning message.
Updated SuperSignature to version 1.5.0.3 and used unhexed version.

3.5 | 2018-04-09

Added security fixes.
Added query parameter to return signature as transparent image.
Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.

3.4 | 2018-01-29

Added compatibility with Gravity Forms 2.3.
Updated IeModalFix init option to only be set for IE browsers; fixes issue with FireFox with 3+ paths on a signature.
Fixed a JavaScript error which could occur in the form editor with Gravity Forms 2.3-beta.
Fixed an issue where the field could be populated with the value from another form on the same page if both fields have the same ID.
Fixed an issue where the signature file could remain after the entry was permanently deleted.

3.3 | 2016-10-26

Updated initialization options for signature to set different values based on MAC or PC to fix issues with touch not working.

3.2 | 2016-10-26

Updated field appearance settings label classes for consistency with GF2.0+.
Fixed issue where signing with more than three lines corrupted the signature.
Fixed a fatal error if Html2RGB() has already been defined by the theme or another plugin.

3.1 | 2016-06-16

Added the gform_signature_init_options filter.
Updated to include the ss_orig.js script in the footer.
Updated the signature container markup to use the height from the init options.
Updated script to be initialized via get_form_inline_script_on_page_render() rather than inline with the input markup.
Fixed an issue when signing on a Windows touch machine with chrome.
Fixed an issue with the required field validation when updating an existing entry outside the entry detail context e.g. from a Gravity Flow user input step.
Fixed a JavaScript error which could occur when the signature init script is included on a page and the field input is not e.g. the Gravity Flow user input step when the field is not editable.
Fixed an issue with the border width style in the admin and on the front-end for old IE.
Fixed a JavaScript issue which affected multi-page AJAX enabled forms when loading the next page.

3.0 | 2016-04-14

Added support for Gravity Forms 2.0.
Added GF_Field_Signature.
Updated SuperSignature to version 1.5.0.8.
Fixed an issue where the old signature file was not deleted when using the 'sign again' link.
Fixed an issue where the signature files would remain when permanently deleting all the entries for a form.
Fixed an issue which prevented the signature canvas being displayed after deleting the existing signature when editing an entry.
Fixed some strings in the form editor which were untranslatable.
Fixed an issue with the borderStyle setting.
Updated to only include the deleteSignature script on the entry detail edit page.
Updated location of Signature field settings so they are now located on the Appearance tab.
Updated SuperSignature; fixing a vertical offset issue with the touch point/capture location when the WP admin bar is present on a mobile device.
Removed Browser.php.

2.4 | 2016-01-06

Added drag and drop support to the field button in the form editor (GF 1.9).
Added Spanish (es_ES) translation.
Updated POT file.
Updated GFSignature::maybe_save_signature() to public.
Updated signature script to latest version.
Fixed a fatal error if Browser.php was already included by another plugin.
Fixed an issue with the delete signature confirmation message.
Fixed signature appearing as a black image in some email clients.
Fixed issue a JavaScript error in the form editor in some languages.
Fixed issue with causing mixed content warning when Force SSL was enabled in the admin.
Fixed issue when multiple Html2RGB() functions were defined.
Fixed issue with folder path causing signature not to be saved correctly on same servers.

2.3 | 2014-10-16

Added function gf_signature to easily get a Signature instance.
Added text domain/path to header.
Added support for save and continue in Gravity Forms 1.9.
Added new filter: gform_signature_show_in_all_fields
add_filter( 'gform_signature_show_in_all_fields', '__return_false' );
Updated protected functions to be public.
Updated to have the file class-gf-signature.php and organized code into this file and signature.php.
Updated version to use a variable.
Updated to display signature image in {all_fields} tag.

2.2 | 2014-04-14

Updated Super Signature script to latest to resolve issues with Kindle Fire HD.
Fixed issue with IE11 when using the latest version of the Super Signature script.

2.1 | 2014-01-31

Downgraded super signature script to previous version due to an issue with IE11.

2.0 | 2014-01-29

Added Add-On Framework integration.
Updated super signature script to 1.5.0.2.
Updated masked input JS library to 1.3.1.
Fixed issue creating signature image when output buffer wasn't empty.
Fixed issue with signature being deleted when editing the entry.

1.3 | 2013-03-07

Fixed issue with signature file name being displayed on the print page instead of the signature image.
Updated signature script to version 1.3.0.0.

1.2 | 2012-09-13

Added ability to add a signature in the entry detail page when a signature does not already exist.

1.1 | 2012-08-30

Fixed issue with custom validation message not getting displayed.
Fixed issue with signature URL not being created correctly when resending notifications.
Fixed conflict with IE8.
Fixed issues when signing on IE9.
Fixed issue where editing entry resulted in removal of signature from lead.
Updated edit entry functionality to support previewing, downloading and deleting signature from lead.

1.0 | 2012-07-02

Fixed issue when signing on IE 9.
Fixed issue with jQuery being included in the ss_orig.js file.
Added support for ManageWP.
Fixed issue with signature files not being deleted when lead is deleted.
Fixed duplicate field size setting.
Updated field size setting to an open text input instead of a drop down.
Fixed conflict with datepicker field.
Fixed issue with multi-page forms where signature was not maintaining its value from page to page.

Setting Up the Signature Add-On

Setting Up the Signature Add-On

Pre-RequisitesSetup

Pre-Requisites

WordPress v4.9+
Gravity Forms v1.9.14+
PHP 5.6+ with GD library support
Download and install the add-on

The Gravity Forms Signature Add-On requires your web server』s PHP configuration to have the GD library installed and working properly. The GD library is used to create the signature image file on the server.
Setup
Setting up the Gravity Forms Signature Add-On is easy. Once you have installed and activated the plugin, you』re done!
Now you』re ready to begin using the Signature Add-On.

Creating a Form Shortcode

Creating a Form Shortcode

SummaryBut I Just Want To Add A Form!Example Form ShortcodeParametersHow To Find The Form IDAdding a Shortcode Using the Shortcode BlockPossible ErrorsShortcode Actions

Summary
WordPress shortcodes allow users to perform certain actions as well as display predefined items within WordPress pages and posts. The Gravity Forms form shortcode is the primary method used to display a Gravity Form on your site.
The form 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. Shortcodes are added when you use a standard WordPress editor to add the form to the page. Refer to the next section below if you just want further information on adding a form to your site.
But I Just Want To Add A Form!
The information contained here is not needed to add a form to your site, as the standard Add Form functions contained within the page editor will construct the shortcode for you without any manual editing required. This article is just a handy explainer for those curious as to what these shortcodes mean. If you simply want information on the process of adding a form to your post or page, refer to this documentation section.
Example Form Shortcode
1[gravityform id="1" title="false" description="false" ajax="true" tabindex="49" field_values="check=First Choice,Second Choice"]
Parameters
The following parameters are shown within the sample shortcode above.

id
The id of the form to be embedded. (required)
title
Whether or not to display the form title. Defaults to 『true』. (optional)
description
Whether or not to display the form description. Defaults to 『true』. (optional)
ajax
Specify whether or not to use AJAX to submit the form.
tabindex
Specify the starting tab index for the fields of this form.
field_values
Specify the default field values. See also this article for detailed information on dynamic population.

How To Find The Form ID
In order to use a form shortcode, you will need the form ID. Here is how you can determine the ID of your form:

Log into your WordPress admin dashboard.
On the left side navigation menu, hover over Forms and click on Forms.
Find the form you need the ID for, and click on it.
The form ID is listed to the right of the form name.

Adding a Shortcode Using the Shortcode Block
If you are using the WP5+ block editor, and want to add a form using the shortcode instead of the Gravity Forms block, there is actually a Shortcode block (under the Widgets category), which once added will accept a standard Gravity Forms shortcode.
To do this, follow these steps:

Note the form ID of the form you wish to insert on the page.
Within the new block-based editor, bring up the (+) or 「add new block」 dialog where you would like to position it on the page.
Use the search bar to find the Shortcode block and add it. See screenshot.
Insert a valid Gravity Forms shortcode inside the shortcode block. Don』t forget to add the specific form ID you noted within the id=X argument. See screenshot.
Preview your form, and make sure everything checks out!

Possible Errors
If you use the id for a form that does not exist, the following message will be displayed:
1Oops! We could not locate your form.
Shortcode Actions
Other plug-ins can extend the abilities of your Gravity Forms shortcode. Refer to this article for information on additional shortcode functionality that comes with our official User Registration plugin.

Shipping

Shipping

SummaryCommon SettingsGeneral SettingsNotesMerge TagsUsageModifiers

Summary

The Shipping field allows a shipping fee to be added to the form total. It is available under the Pricing Fields section within the form editor.

Shipping field as displayed in the Field Library

Shipping field as displayed in the Form Editor.

Important: If you use a choice based field type and 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 conditional logic.

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

SettingDescriptionField TypeSelect the type of field from the available form fields. For Field Types see note 1.PriceEnter the base price for this product. This option is only available when the Single Method field type is selected.

Notes

Field Types Single MethodThe Single Method field type will display just the shipping price.Drop DownThe Drop Down field type will display as a drop down field on your form. When this option is selected, the General tab will refresh with options to specify multiple shipping prices.Radio ButtonsThe Radio Buttons field type will display as a field of radio buttons on your form. When this field type is selected, the General tab will refresh with options to specify multiple shipping prices.

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.

Shipping Field CSS Selectors

Shipping Field CSS Selectors

ContainerLabelPrice

Container
example: shipping field container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_singleshipping {border: 1px solid red;}
example: shipping field container (div) – applies just to form ID #1
body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_singleshipping {border: 1px solid red;}
example: shipping 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_singleshipping {border: 1px solid red;}
Label
example: shipping field label (label) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield_shipping .gfield_label {border: 1px solid red;}
example: shipping field label (label) – applies just to form ID #1
body .gform_wrapper_1 .gform_body .gform_fields .gfield_shipping .gfield_label {border: 1px solid red;}
example: shipping field label (label) – 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_shipping .gfield_label {border: 1px solid red;}
Price
example: shipping price (span) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_singleshipping .ginput_shipping_price {color: red;}
example: shipping price (span) – applies just to form ID #1
body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_singleshipping .ginput_shipping_price {color: red;}
example: shipping 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_singleshipping .ginput_shipping_price {color: red;}