Author 诗语

Trello Change Log

2.0 | 2021-07-071.4 | 2020-09-091.3 | 2020-05-051.21.11.0

2.0 | 2021-07-07

Updated authentication method for enhanced security. Important: Manual re-authentication in the add-on suggested.
Fixed an issue where the Add-on icon is missing on the Form Settings page for Gravity Forms 2.5.
Deprecated old authentication method. Authentication will continue to work until removed.

1.4 | 2020-09-09

Added support for Gravity Forms 2.5.

1.3 | 2020-05-05

Added security enhancements.
Added translations for Hebrew, Hindi, Japanese, and Turkish.
Updated Javascript files, stylesheets to use minified versions.
Updated labels to be stored by ID instead of by color.
Fixed error message for when a file cannot be attached to a card.
Fixed issue of wrong variable being used in upgrade function.

1.2

Fixed fatal error which could occur if no boards are returned when initializing the API.

1.1

Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Fixed an issue where a due date of Jan 1, 1970 was set on the card if the mapped date field was empty.

1.0

It's all new!

Troubleshooting Mailchimp error 「Unable to add/update subscriber」

IntroductionHow To Capture More InfoChecking Error CodesExample

Introduction

Any issue that occurs while attempting to add or update a Mailchimp subscriber will often generate the same generic message

Unable to add/update subscriber: Invalid Resource

The error message is also saved as a note on the entry.

How To Capture More Info

Recreate the error with Gravity Forms logging enabled (see this article). The error will be saved to the Mailchimp error log, as well as a hopefully more detailed error message from the Mailchimp service.

For some Mailchimp errors, additional information is sent if a specific field has thrown an error. These errors are also saved to the Mailchimp Add-On log.

Checking Error Codes

You can cross-check any error code captured against Mailchimp』s Error Glossary

If the logged information does not help figure out why the error occurred, a developer could add specific debug statements into the site code to try and track the error.

But if you still cannot see any easy resolution, submit a ticket to Gravity Forms Support for technical assistance.

Example

This screenshot shows an example snippet from the error log.

Note how the log identifies what exactly was sent, and what the returned error was. In this case, it is clarifying that when using the Mailchimp Address field, Mailchimp expects that you pass a complete address, including street address and zip code (If you only want to collect the city/state, create a text audience field and merge tag in Mailchimp to map to your Gravity Forms city/state field).

Troubleshooting a Missing 『Feeds』 Menu Item

Check that the plugin is activatedCheck your WordPress user capabilitiesCheck for conflictsLook for errors

When trying to create an add-on feed, you』ll need to access the Feeds page. What if you don』t see the menu item? In this article, we』ll show you how to troubleshoot the issue.
Check that the plugin is activated
While it seems crazy, be sure that the add-on is activated by accessing the Plugins page in the WordPress dashboard. It』s fairly common that people install WordPress plugins and simply forget to activate it. Checking that the plugin is activated is a great way to save yourself from a potentially embarrassing support ticket.
Check your WordPress user capabilities
WordPress uses various user roles and capabilities to determine what users are allowed to do. As Gravity Forms strides to seamlessly integrate within WordPress as much as possible, it also uses roles and capabilities.
Your user simply may not have access to a capability that Gravity Forms is checking for. The easiest way to check over your current capabilities, as well as modify them if needed, is the 3rd party User Role Editor plugin.
Check for conflicts
Gravity Forms is developed to avoid plugin conflicts as often as possible, but with millions of WordPress plugins on the market, we can』t possibly test with every one of them.
Deactivating all other WordPress plugins and switching to a default theme such as Twenty Fifteen will help you narrow down if there is a conflict. If the issue resolves itself, slowly begin to re-activate plugins until the issue appears again.
Look for errors
If you』re still not seeing the menu item, look for errors that may be appearing when WP_DEBUG is enabled. These errors can provide more information as to what the issue may be.

Trello Feed Meta

IntroductionUsageProperties

Introduction
The Feed Object meta for the Trello add-on is an associative array containing the properties which determine how the add-on should process the form submission.
$feed['meta'] = array(
'feedName' => 'Trello Feed 1',
'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

feedName string
The feed name which appears on the add-ons feeds tab.

board string
The Trello ID of the board the card will be added to.

list string
The Trello ID of the list the card will be added to.

cardName string
The name to be assigned to the card. Merge tags are supported.

cardDescription string
The description to be assigned to the card. Merge tags are supported.

cardDueDate string
The ID of the date field or a custom value. Possible values: The ID of a Date type field or gf_custom

cardDueDate_custom integer
The number of days after today, used when the value of cardDueDate is gf_custom.

cardLabels array
array(
'green' => true,
'red' => false,
'yellow' => false,
'purple' => false,
'orange' => false,
'blue' => false,
);

An associative array of labels with the color as the key to a boolean indicating if the label should be applied to the card.

cardMembers array
array(
'TRELLO_MEMBER_ID_HERE' => true,
);

An associative array with the member ID as the key to a boolean indicating if the member should be assigned to the card.

cardAttachments array
array(
'10' => true,
'11' => false,
);

An array of file upload fields. The field ID is the key with a boolean value indicating if the files for that field should be attached to the card.

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.

Troubleshooting a Missing Settings Page

Check that the add-on is activatedEnsure you have the correct user capabilitiesEliminate possible conflictsCheck for errors

Most add-ons are managed from their own settings pages. These settings pages are typically accessible by accessing the primary Gravity Forms Settings page, then clicking on the tab appropriate for your add-on.
If you do not see the settings page, here』s a few steps to troubleshoot the issue:
Check that the add-on is activated
This seems like a no-brainer, but individuals regularly install WordPress plugins and simply forget to activate them. Check on your Plugins page within the WordPress admin to ensure that the add-on you』re trying to access settings for is activated.
Ensure you have the correct user capabilities
Settings within Gravity Forms are dependent upon the permissions allowed to the user attempting to access them. Simply put, if the user you』re logged in as doesn』t have permission to do something, the option typically won』t even appear.
To check and/or modify your user capabilities, the 3rd party User Role Editor plugin can be used.
Eliminate possible conflicts
To narrow down the issue, be sure to deactivate all other plugins, and switch to a default theme like Twenty Fifteen. By doing so, you can better locate where the issue is coming from.
If the issue goes away with other plugins and/or themes deactivated, slowly begin re-activating things until the issue appears again.
Check for errors
Sometimes, there might be an error occurring within the Gravity Forms code, or a conflict with another plugin or theme. If you see any PHP errors on your site with WP_DEBUG turned on, they may be causing the issue.

Troubleshooting API Key Validation Issues

Check Your KeyCheck The Add-On VersionsInstall the Debugging Add-OnEnable Logging

Note: This article refers to issues validating 3rd party API keys in add-ons. If you』re having trouble activating your Gravity Forms license key, contact support.
Check Your Key
This sounds obvious, but is often overlooked. As there are often multiple keys required, be sure that you have the correct key in the correct field. Also be sure that you』re not using an old key that has since been changed.
Check The Add-On Versions
Because services can change how their APIs operate from time to time, be sure that you are using the most recent version of the add-on. If not, you could be attempting to access an API that has since changed.
Install the Debugging Add-On
The Debugging add-on can often reveal a plugin or theme conflict. Be sure to test with the Debugging add-on to ensure that there is not an issue being caused by another plugin or theme.
Enable Logging
If you are continuing to have issues and you are certain that everything is configured properly by following the previous steps, testing with logging enabled is the next step.
Simply enable logging of all messages for the add-on, then try configuring the add-on again. Once done, check the logs within the Forms > Settings > Logging or Forms > System Status pages for any errors; particularly those relating to the response from the external service.
If you』re not able to see an issue within the logs, include the links to the logs in with your support ticket and we will be happy to help.

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.

The Importance of Updates

Risks of neglecting updatesKeeping everything up to date

Often times when running a website, individuals will only make the changes they need and neglect the general maintenance of the site, including things such as updates. As described in our article on security practices, keeping WordPress as well as any plugins of themes is critical to your site』s health.
Risks of neglecting updates

The biggest risk you face by not keeping everything up to date is security issues. Many times, updates are pushed out to solidify the security of the code. By neglecting updates, critical security flaws can be introduced and cause issues such as a fully compromised website or allow execution of unwanted code. Simply keeping everything up to date at all times will largely prevent issues.
Lack of compatibility is also a concern if one thing is updated, but not others. For example, if you updated WordPress to the next major version, but not Gravity Forms, you can sometimes run into bugs as something Gravity Forms may have been using in the older version, may not be present or changed in the newer version.
A large majority of the code placed in minor updates, is simply to correct a bug that may exist. Failing to update your plugins can expose you to those bugs and sometimes lead to an overall poor experience.

Keeping everything up to date

Check for updates often. Simply logging into your WordPress admin dashboard and checking to see if updates are available will greatly assist you with keeping everything up to date.
Add license keys for Gravity Forms and other premium plugins. Without a valid license keys saved in the plugin settings, WordPress is unable to check for updates on your behalf.
Use a management tool. If you have multiple sites that you need to maintain, logging into each of them daily to check for updates can be a bit of a pain. Tools such as WP Remote can allow you to check multiple sites for available updates with a single click of a button.
Enable automatic updates. What』s better than logging into sites daily to check for updates? Automatic updates! The WordPress codex has an excellent article on enabling automatic updates both within WordPress core, as well as for plugins. You can find it at the Enabling Automatic Background Updates article.

Maintaining updated software by far one of the most important aspects of running a successful website. With the knowledge you have gained in this article, you should be able to easily maintain current copies of all software running on your site.

Upgrading to Stripe version 2.6

New FeaturesUpgrade NotesFurther Information

New Features
The Gravity Forms official Stripe add-on version 2.6 includes two new methods for collecting payment information:

Stripe Credit Card Field (Elements)
Stripe Payment Form (Checkout)

The two new methods for collecting information make the PCI compliance process easier, enhancing security because the credit card field (or the checkout form) are hosted by Stripe during the checkout process.
Upgrade Notes
When upgrading to Stripe v2.6 from a previous version, note that:

Previously created forms already using Stripe will continue to work and use the standard Gravity Forms Credit Card field.
Previously created forms already using Stripe will use the standard Gravity Forms Credit Card field even if you have chosen Stripe Payment Form (Stripe Checkout). To use the Stripe Payment Form (Stripe Checkout) Payment Collection Method instead, the Credit Card field will need to be removed from the form.
Previously created forms already using Stripe will use the standard Gravity Forms Credit Card field even if you have chosen Stripe Credit Card Field (Elements). To use Stripe Credit Card Field (Elements) instead, the Credit Card field will need to be removed from the form and the Stripe Card field added.

Further Information
For an overview of this release, refer to our blog post announcement.
For a list of changes, refer to the official change log.
For our user guides and help articles, check out the other articles contained in this section of our document site.

Survey

SummaryCommon SettingsGeneral SettingsSurvey Field Type OptionsNotesAdditional Likert OptionsAdditional Single Line Text OptionsMerge TagsUsageModifiersSurvey Specific Merge Tags

Summary

The Survey field is available when using the Survey add-on and simply allows you to create survey questions that users can answer. It is available under the Advanced Fields section within the form editor. If you do not already have the Survey add-on installed, you』ll need to do so before this field is available.

Survey field as displayed in the Field Library

Survey field as displayed in the Form Editor, displaying the Likert choice type.

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

SettingDescriptionSurvey QuestionThis is simply the question that you would like to ask the user.Survey Field TypeDetermines how the survey field will be displayed to the user. See note below for options.Columns/ChoicesThis is where you will define the individual answers for your survey field.

Survey Field Type Options

This table lists the options available for displaying your survey field to a user.

OptionMethod of ChoosingLikertSelect items from a scale of options. For example, a scale of options from Strongly Disagree to Strongly Agree. See notes. RankRank items within a list by dragging and dropping elements into a top-to-bottom order. RatingRate by stars. Each rating corresponds to a choice defined in the field settings. Radio ButtonsSelect one choice only by clicking a radio button. CheckboxesSelect one or multiple choices using checkboxes. Enable 「Select All」 creates a choice for the user to select all other choices.Single Line TextEnter one line of custom text. See notes.Paragraph TextSimilar to the Single Line Text option, but allows for multiple lines of input. Maximum Characters limits the number of characters this field is allowed to have.Drop DownDisplay choices in a dropdown box. Users can only select one.

Notes

Additional Likert Options

Enable Multiple Rows allows multiples Likert questions to be asked in the same survey, basically increasing the number of rows in the Likert table.

Enable Scoring allows different scores for each column. Aggregate scores are displayed in the results page and can be used in merge tags.

Additional Single Line Text Options

Input Mask provides a visual guide allowing users to more easily enter data in a specific format such as dates and phone numbers. For more information on input masks, refer to this article.

Merge Tags

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

Usage

{Field Name:2}

Modifiers

This field type does not have any modifiers available.

Survey Specific Merge Tags

TagDescription{survey_total_score}Displays the total score for the survey. Scoring must be enabled on the survey field for it to be tallied.{score:id=x}Displays the score for a specific survey question. Scoring must be enabled on the survey field for it to be tallied.