Gravity Forms 文件

Upgrade/Add-on Issues

Having an issue where you can』t upgrade Gravity Forms or its add-ons? Are you seeing a message that says you need to register or that the add-on browser is not available and these issues don』t resolve within twenty-four hours? Your web server might be having issues contacting our servers and it is most likely due to a blacklisted IP address.
Read the following guide on our blog about Blocked IP Addresses
You can also test with logging enabled to see if any messages are being returned if your site is having issues contacting our servers.

Updating or Adding A Payment Method

Introduction「Payment Method Expiring」 WarningHow do I update my payment method?Screenshots

Introduction

Each license you own is linked to one subscription, which is linked to one payment method. Payment methods are not stored or managed as part of your account, but as part of the license. As such, they are updated in the Licenses section of your account area. You must enter the payment method each time you complete a new subscription, and from that point on renewals will be handled automatically using the on-file payment method for that license.

「Payment Method Expiring」 Warning

Our billing system will email you when your card is about to expire. Additionally, we will email if an attempt to renew your license fails. In that case, you have a few extra days to update the payment method before the system will retry again. Don』t delay! If you fail too many renewal attempts, your license key will be canceled and cannot be restarted!

If you stored a credit card on multiple licenses subscriptions, note that you will have to update each one separately by repeating the process below for all such licenses.

How do I update my payment method?

Rocketgenius (the team behind Gravity Forms) does not store details of your payment method.
We use industry leading secure payment gateways and processors that utilize verified tokens for passing around subscription purchase approvals. All pages where payment method details are requested are hosted directly by the payment processor. In this way, your credit card numbers and PayPal credentials are not stored by us, not exposed to any of our employees, and are not transmitted through our servers. All that is shown as part of your account is incomplete details, such as the first and last credit card numbers.

Log in to your Gravity Forms account page, select the license you would like to manage then click the Manage License button.Each License is linked to its own payment method. Look for the Update option listed after the next payment date.To switch payment method between card or Paypal, click Change Payment Method. If you have no payment method attached to your license, the button will say Add Payment Details. Complete the form for the payment method chosen and click Update.

You will need to complete this process separately for each license that you want to update, even if the card is the same on multiple licenses.

Screenshots

Manage License option

Add payment details action.

Error 『Unexpected T_STRING』 when installing Gravity Forms

IssueProbable CauseRemedyNotes

Issue
When trying to install the current official Gravity Forms plug-in, an error is encountered with a message similar to the following:

Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in https://s22280.pcdn.co/.../../../wp-content/plugins/gravityforms/gravityforms.php on line..

Probable Cause
This error typically occurs because of a PHP version conflict, likely due to your server running an older version of PHP.
Remedy
Update your PHP version (or check with your web host).
Notes
Review the Gravity Forms System Requirements for what we recommend to get the optimal experience when running Gravity Forms.
Although Gravity Forms can operate with some older versions, there are major disadvantages in doing so:

sub-optimal performance
you may exclude yourself from receiving support
testing may not have been done on lesser unsupported versions
you are exposing yourself to security vulnerabilities

You should update to a more recent version.
Review this php.net notice to see the PHP versions that are officially supported by the vendor, including their 「end of active development」 and 「end of life」 dates.

Twilio Feed Meta

IntroductionUsageProperties

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

fromNumber string
Phone number that the message will be sent FROM.

toNumber string
Phone number that the message will be sent TO.

smsMessage string
The SMS message that will be sent. Can contain merge tags.

shortenURL boolean
Should Bitly automatically shorten all URLs? Default is false.

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.

Twilio Change Log

2.8 | 2020-09-152.7 | 2020-05-062.6 | 2019-08-072.5 | 2018-04-122.4 | 2017-08-022.3 | 2017-04-282.2 | 2016-08-312.1 | 2015-04-202.0 | 2014-12-111.1 | 2014-03-111.0 | 2011-11-010.2 | 2011-03-31

2.8 | 2020-09-15

Added support for Gravity Forms 2.5.
Adding logging statements for URL shortening during feed processing.
Updated the Bitly URL shortening service to the latest version to prevent intermittent failures while shortening URLs.

2.7 | 2020-05-06

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added support for feed duplication.
Fixed an issue with the From and Send To dropdowns in the feed settings not having default choices.

2.6 | 2019-08-07

Added security enhancements.
Fixed an issue with the shortened URL where long URLs with more than one parameter get truncated.
Fixed an issue where merge tags are escaped which breaks URLs with parameters.
Fixed issue where long messages (longer than 1600 characters) are not successfully sent.
Fixed an issue where messages with merge tags can't be sent.
Fixed an issue where only the first URL in the message can be shortened.

2.5 | 2018-04-12

Added security enhancements.
Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.
Updated Twilio PHP SDK.
Fixed warning regarding the number of characters allowed for a message to display 1600 instead of 160.
Fixed Twilio PHP SDK not being included with final build.

2.4 | 2017-08-02

Added gform_twilio_message filter to modify the SMS message arguments before it is sent.
Added support for using merge tags in the To Number feed setting.
Added support for using test Twilio credentials.
Fixed a PHP warning for the From setting on the edit feed page if the API request for the numbers returned an error.
Fixed URLs not shortening in message if multiple merge tags are used.
Updated Twilio PHP SDK.
Updated URL shortened to use latest Bitly API.

2.3 | 2017-04-28

Added security enhancements.
Added translations.

2.2 | 2016-08-31

Added conditional logic support to the feed settings.
Updated to use the newer /Messages endpoint instead of /SMS/Messages.
Updated feed From Number setting) to use the select_custom field type allowing use of Alphanumeric sender IDs (Not supported by all countries.)
Updated minimum Gravity Forms version to 1.9.11.
Fixed an issue with the upgrade routine which caused it run even if a pre-framework version hadn't been installed.

2.1 | 2015-04-20

Updated the gform_twilio_set_to_phone_number filter to include $feed_id as the third parameter.
Updated logging.
Fixed a low severity security vulnerability in the admin area which could be exploited by authenticated users with form administration permissions.
Fixed an issue with URLs from processed merge tags not being shortened.
Fixed an issue with merge tag replacement in the message.
Fixed issue when shorten urls is checked and urls with spaces cause the Bitly url to be incomplete.
Fixed issue where a validated Twilio number was required even for non-trial Twilio accounts.
Fixed issue where a Bitly key was required in order to create a feed. Now feeds can be created without a Bitly key, but the "shorten URL" option requires it.

2.0 | 2014-12-11

Added integration with Add-On Framework.
Added text domain/path to header.
Updated POT file.
Updated required version of Gravity Forms to 1.8.17.
Updated code to new standards.

1.1 | 2014-03-11

Added new filter "gform_twilio_set_to_phone_number" to modify the TO phone number set in the admin.
add_filter("gform_twilio_set_to_phone_number", "change_to_number", 10, 2);
function change_to_number($to, $entry){
//grab phone number out of field 2, sample format "+17571234567"
$phone = !rgblank($entry["2"]) ? $entry["2"] : $to;
return $phone;
}
Added logging.
Updated to not send entries marked as spam.
Updated the URL to Bitly's API to use api.bit.ly instead of api.j.mp so the default short domain in the user's Bitly setting is used.
Fixed issue where RG_CURRENT_PAGE constant was not available when GF is deactivated.
Fixed issue on feed page that displayed only the first Twilio incoming phone number.
Fixed notices.
Fixed issue with merge tags with new lines on feed page.
Cleaned up extra parse_request add_hook with function that didn't exist.

1.0 | 2011-11-01

Added URL shortening support.
Changed Bitly short URL to http://j.mp.
Removing formatting characters from TO number when sending request to Twilio.

0.2 | 2011-03-31

Added feedback on settings page.
Added integration with PayPal so that SMS messages can be sent only when payment is received.
Added helper text and tooltips.

Troubleshooting the Zapier Add-On

Getting StartedAssumptionsEnabling LoggingTools > Site Health TestsAuthorization header is missingSSL ErrorsZapier Settings aren』t available in Gravity FormsUnable to view Forms at Zapier or unable to create Zaps or FeedsOther Issues that can impact Zapier Communication

Getting Started

We』ve put together this troubleshooting guide to help if you run into issues connecting Zapier to your Gravity Forms with the Zapier Add-On.

Assumptions

If you』ve run into an issue communicating with Zapier, it will more than likely happen when first authenticating the REST API connection at Zapier. To help rule out the most common problems, we do make the following assumptions regarding your Website and WordPress installation:

WordPress, Gravity Forms and the Zapier Add-On are all upgraded to the most currently released versionsSSL Certificate Installed and Configured on your WordPress website and operating properlyWebsite accessible to the internet

The authentication from Zapier to Gravity Forms uses REST API with Basic Authentication so your website must be accessible for that connection to occur. If you are running your WordPress website in any of the following configurations:

Behind a Firewall or regionally blocked accessCloudFlare or Caching or another methodology that involves some form of redirection or off-loading of contentSecurity Login plugins or redirected login to a Single Sign-On authorityWordFence or other restriction of access plugins that directly block REST API.htpasswd or other password protection plugins that restrict access to your site

You will need to either Whitelist the REST API endpoints for Gravity Forms and/or possibly add additional rules to those plugins or applications to allow Zapier to connect to your website in an unrestricted way.

Enabling Logging

You can determine what is happening with REST API by Enabling Logging for Gravity Forms API and checking the log files while you』re attempting to connect at Zapier. You can get good details on interpreting the log in our Troubleshooting REST API article.

The log will contain entries for every time that Zapier reaches out to your website attempting to authenticate, when creating or editing a zap, and when enabling and disabling a Zap within your Zapier Account dashboard.

If you reach out to Gravity Forms Support for help, we will require logging to be enabled for both Gravity Forms API and the Zapier Add-On.

Tools > Site Health Tests

With the most recent versions of WordPress, you can determine if your website has issues right in your WordPress Admin dashboard. This is the first place you should look if you』re having issues connecting from Zapier.

Go to Tools > Site Health in your WordPress Dashboard. A series of tests will be run against your installation to determine if your website is operating properly.

The tests we focus on are for the Authorization header:

Successful Authorization header test from Tools > Site Health

REST API:

Successful REST API test from Tools > Site Health

and SSL (HTTPS):

Successful HTTPS/SSL test from Tools > Site Health

If any of the above tests are failing or have errors, you will need to reach out to your Server Host for assistance in correcting the issues.

The following resources may be helpful to provide to your Server Host for troubleshooting:

WordPress .htaccess rewrite rules (will usually help with Authorization issues)WordPress REST API Connection FAQ

Authorization header is missing

If you』re receiving an error like the following in your Tools > Site Health under Security:

Authorization Header Test with an error.

This will mean that Basic Authentication will not work properly. If Basic Authentication is failing, you will need to reach out to your Server Host to resolve.

SSL Errors

If you』re seeing errors in the SSL sections like the following:

SSL Errors in Tools > Site Health

This will indicate that either your SSL isn』t properly configured, or is missing some necessary configuration steps. You will need to reach out to your Server Host to correct as SSL is required for Zapier to make a connection to your site. WordPress Site Health will attempt to provide a recommended solution for you, but there are some good resources below:

WordPress HTTPS and SSL Support FAQ

Zapier Settings aren』t available in Gravity Forms

If you have a membership or roles & capabilities plugin like Members installed, you will need to provide access to the Zapier capabilities in order to see the Settings under Forms > Settings > Zapier. Check our Roles & Capabilities documentation as that will show you which capabilities must be active to see those settings.

Unable to view Forms at Zapier or unable to create Zaps or Feeds

This usually indicates that you』re using an account that doesn』t have the correct access to the Gravity Forms settings. Verify the following:

Using an account in the REST API settings that doesn』t have the gravityforms_edit_forms capability.Only using 『READ』 access in your Forms > Settings > REST API account

Both of these are common issues and easy to correct. Switch your accounts to Admin Accounts in the Forms > Settings > REST API keys and make sure you』re using 『read/write』 access as defined in our REST API documentation.

Other Issues that can impact Zapier Communication

Attempting the connection on a website that isn』t running SSL or isn』t public to the internet. This can include websites hidden behind .htpasswd or other login methods.Having Authentication, REST API or SSL errors in your Tools > Site Health report (see above).Incorrect settings in your .htaccess files that are causing bad redirections or adding trailing backslashes to your REST API requests.Having some service in-between your website and REST API on your WordPress installation that is changing the content of the REST API requests. These issues usually will let Zapier see your site and seem to be working but Feeds won』t be created or you won』t be able to create Zaps.

We can help you troubleshoot to determine if any of the above issues are the problem you』re experiencing. Open a support ticket and we』ll help you troubleshoot the issue.

Troubleshooting Payment Feeds Not Processing

Updates Are ImportantCheck Conditional LogicCheck the Payment/Recurring AmountEnable Logging

Of course, payments being properly processed is the most important part of selling anything. When it』s not working as expected, it can be frustrating. In this article, we will show you how to troubleshoot issues with payment feeds.

A feed to the payment service must be present and active at the time of form submission in order to send payment data. Entries created without an active feed will not be sent to the payment service. Creating a feed afterwards will not process any entries previously submitted.

Updates Are Important
Your first step in troubleshooting payment or any other issues, is to make sure that your installation of WordPress, Gravity Forms, and any Gravity Forms add-ons are fully updated.
Doing this ensures that you are not encountering a bug that is in a later version, and thus eliminates possible embarrassment of an issue that could easily be fixed.
Check Conditional Logic
Within your feed, ensure that any conditional logic rules that may be in place, are actually being processed. Sometimes, conditional logic rules are are not met, which would then cause the feed to not be processed.
Check the Payment/Recurring Amount
In the event that the payment/recurring amount does not add up to a positive number, the payment feed will not process. Check to ensure that when the form is being submitted, that the product total is updated. If not, this is likely the reason that your payment feed is not processing.
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 Gravity Forms core and the add-on, then test the form. 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 payment gateway.
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.

Troubleshooting Notifications

How email notifications are sentEnsure WordPress and Gravity Forms are up to dateCheck your settingsCheck for typosAvoid spacesUse a valid From AddressAvoid using same email in From and To addressesCheck routing conditionsIs the notification enabled?Use Third-Party Transactional Email Services or SMTPSending Result NotesWordPress successfully passed the notification email to the sending server.Could not instantiate mail function.SMTP Error: connect() failedSMTP Error: Could not authenticateSMTP Error: Data not acceptedWordPress was unable to send the notification emailEnable LoggingCheck for plugin or theme conflictsContact your web hostUnderstanding E-mail Reliability

How email notifications are sent
Like most other WordPress plugins, Gravity Forms does not handle emails directly. Gravity Forms uses the wp_mail() function that is provided by WordPress to send any emails.
Once Gravity Forms hands the email off to the WordPress wp_mail() function, one of the following occurs:

WordPress directly interacts with your web server to send the email.
WordPress contacts your SMTP or external 3rd party mail server to send the email (e.g. SendGrid, Mailgun, etc.).

After WordPress hands the email off, it』s up to the mail server, as well as the recipient』s mail server, to complete the sending of the email. We don』t have any control over the delivery process once the email is passed to WordPress.
If you』re having trouble sending sending or receiving emails from Gravity Forms, this article will provide you with a few different steps to follow. In the overwhelming majority of cases, these steps have been proven to resolve a multitude of email issues.
Note: WordPress allows filtering of emails sent using wp_mail() function, this means third-party plugins or custom functions can alter any aspect of the email after Gravity Forms passes it to WordPress.
Ensure WordPress and Gravity Forms are up to date
The first thing you want to check is your WordPress and Gravity Forms versions. The version you are on could potentially have a bug in it that is fixed within a newer version. Checking that you are running the latest version is a critical step in troubleshooting any issues.
Check your settings
When configuring notifications, it』s easy to miss an error in the recipient address or elsewhere. By looking over the notification configuration carefully, a quick mistake can be easily resolved.
Check for typos
It』s easy for a small typo to turn into a big problem. Check for any typos within your notification feeds.
Avoid spaces
Within your notification, check for any spaces in the recipient』s address, or between multiple addresses. If a space exists in the setting, it can potentially cause the notification to fail.
Use a valid From Address
Within the sender, or From Email field, ensure that it is the address that the message is originating from, that must be an email address authorized by your server (e.g. an email using the same domain that your site uses).
In plain English, don』t use your visitor』s email as from address, always use your site domain in the from address.
If not, things like SPF records and/or DMARC records can cause the mail to be marked as spam and/or rejected. If you need to allow the recipient to reply another address, set it as the Reply To address instead.
Many providers as Yahoo, AOL or Gmail are known to apply this policy. For more information on the Yahoo domain issue visit the following:
Yahoo email anti-spoofing policy breaks mailing lists.
For more info on the AOL domain issue visit the following:
AOL imposes stricter email rules.
You can read also about Gmail DMARC policy changes here:
Gmail DMARC Update 2017.
These are only a few examples, applying this policy to fight against spam is becoming a standard in the email and hosting industry, therefore using a valid from address for your emails must be always in your top list when configuring your notifications settings.
Avoid using same email in From and To addresses
Far too often, we see situations where an email address is configured as both the From Address and To Address. For many mail providers, this will cause the email to be rejected as spam (or placed in a spam folder). Be sure that you use a different, valid email address in the From setting.
Check routing conditions
If you have routing configured for the notification recipient, be sure to double-check that at least one condition was successfully met. If none of the conditions were met, a notification would not be sent, as it would not have a valid recipient.
Is the notification enabled?
While doing form tests it』s common to disable notifications to prevent receiving lot of emails that we don』t really need. Sometimes you can forget to enable the notification again ( it happens more than you think ).
To check if your notifications are enabled, access the form editor, then click on *Notifications at the top menu. You should see a list of all configured notifications for that form. Be sure that all notifications are enabled and the toggle switch to the left of the notification name is green.
Use Third-Party Transactional Email Services or SMTP
Sometimes, due to server settings or e-mail reliability issues, using PHP sendmail does not work. Switching to third-party transactional email services or SMTP can be more reliable and solve many issues.
Gravity Forms provides add-ons for the following major third-party transactional email services:

Mailgun
Postmark
SendGrid

Using any of the above add-ons will make Gravity Forms to use the configured service to send the notifications, this will not affect other emails sent by WordPress or third-party plugins.
If you prefer to use a SMTP server, there are a number of SMTP plugins for WordPress. You will need to install one of the following and set it up using the details given to you by your web host or third party SMTP host.

SAR Friendly SMTP
Post SMTP Mailer/Email Log
Easy WP SMTP
Mailgun for WordPress

Sending Result Notes
Starting with Gravity Forms 2.4.15 you will see a note added to each entry, created with this version or newer, with the result for each notification sending process.
To find this note, simply go to your form Entries list, click on an entry from the list to load the entry details page, and scroll down to the Notes section.
If you see any of the following notes added to your entry, all worked as expected from Gravity Forms side of things. But something happened during email sending between WordPress and your sending server.
Check below most common results reported by WordPress.
WordPress successfully passed the notification email to the sending server.

This means that your Gravity Forms notification settings are fine, the email was passed to wp_mail() function without issues and WordPress reported successfully handing off the notification for delivery. Now the ball is in the sending server side. Only your server admin can investigate this further.
Could not instantiate mail function.

WordPress is not able to send the email because for some reason the PHPMailer class included in WordPress (used by the wp_mail() function) can』t use the PHP mail function. Most of the time this is caused by some restriction in your hosting (e.g. a spam filter was triggered in your server and the email was rejected).
SMTP Error: connect() failed

You』re using a SMTP plugin to send the emails but WordPress can』t connect to the SMTP server. Most common causes for this are incorrect settings in your SMTP plugin, your hosting is blocking the outgoing connection to the SMTP server or the SMTP server is blocking connections coming from your web server.
SMTP Error: Could not authenticate

This WordPress is able to reach the SMTP server, but it can』t authenticate. This can be caused again by incorrect details used in your SMTP plugin (double check not only the username and password but also the port and encryption used). You might also see this error when the SMTP user that you』re trying to use is not active (e.g. disabled by an admin).
SMTP Error: Data not accepted

This means that the SMTP server is rejecting your email message because it contains something not allowed by the SMTP server rules. Most of the time it can be due to from address restrictions (many SMTP servers only allow to use the email address associated to the username that you』re using to send the email), but it can be any other part of your email content.
WordPress was unable to send the notification email

In this case WordPress was unable to send the email for unknown reasons, the sending server didn』t provide any additional information. Only the sending server admin can investigate this further.
Enable Logging
By using logging, you can easily cover scenarios where the sending result note is not being added to the entry, and why they are occurring. Reviewing your logs will allow you to see where the notification might be failing, and correct the issue if it』s within the scope of Gravity Forms side of things. If you need to contact support for better understanding of the log contents, don』t turn off logging until receiving a response from support or your log files will be deleted.
Check for plugin or theme conflicts
Sometimes other plugins or themes create issues that stop notifications from working. Please go through the following instructions to test for a Plugin or Theme conflict.
Testing for a Theme/Plugin Conflict
Contact your web host
If there wasn』t a plugin or theme conflict, SMTP isn』t working for you or you』re seeing in your log any of the results described in the logging add-on section, then you will want to contact your web host and have them look at the server logs to check to see if there are any errors being written.
Often they will see if things are being blocked, by them on purpose or due to some server misconfiguration issues.
Understanding E-mail Reliability
There are a huge number of potential issues that can lead to your notifications not being sent or received, and as such, if you』ve gotten to this point, you are most likely experiencing an issue that is less common and will require the support of your server administrator to solve.
Joost de Valk has written a great summary of why there can be so many issues in e-mail reliability that we hope you will find as a good guide to help you understand the factors at play, and hopefully come to an acceptable solution for any issue you may be experiencing.
Email Reliability: use an SPF record

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 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).