Gravity Forms 文档

Managing Gravity Forms and Add-Ons with WP-CLI

Installing Gravity Forms or an Add-OnExamplesParametersUpdating Gravity Forms or an Add-OnExamplesParametersRunning the Database SetupExamplesParametersChecking for UpdatesExamplesParametersGetting the VersionExamplesParameters

By using the CLI Add-On and the following root commands you can easily install and update Gravity Forms and official Add-Ons from the command line.
Installing Gravity Forms or an Add-On
wp gf install
Examples
# Using the install command without supplying a license key.
$ wp gf install
Error: A valid license key must be specified either in the GF_LICENSE_KEY constant or the --key option.

# Install Gravity Forms, replacing the installed version.
$ wp gf install --force
Downloading installation package from http://...
Unpacking the package...
Installing the plugin...
Removing the old version of the plugin...
Plugin updated successfully.
Success: Installed 1 of 1 plugins.

# Installing Gravity Forms using the specified license key.
$ wp gf install --key=abc123
Downloading installation package from http://...
Unpacking the package...
Installing the plugin...
Plugin installed successfully.
Success: Installed 1 of 1 plugins.

# Install the Gravity Forms Polls Add-On using the specified license key.
$ wp gf install gravityformspolls --key=abc123
Downloading installation package from http://...
Unpacking the package...
Installing the plugin...
Plugin installed successfully.
Success: Installed 1 of 1 plugins.

# Using an invalid add-on slug or license key.
$ wp gf install something --key=abc123
Error: There was a problem retrieving the download URL, please check the key.

Parameters

Argument
Description

[]
The plugin slug.Accepted values: gravityforms or a Gravity Forms Add-On slug.Default: gravityforms.

[--key=]
A valid Gravity Forms license key.

[--version=]
The version to be installed.Accepted values: auto-update, hotfix, or beta.Default: hotfix.

[--force]
Overwrites the installed version of the plugin, without prompting for confirmation.

[--activate]
Activates the plugin immediately after install.

[--activate-network]
Network activates the plugin immediately after install.

Updating Gravity Forms or an Add-On
wp gf update
Examples
# Attempting to update without Gravity Forms being active.
$ wp gf update
Error: Gravity Forms is not active.

# Attempting to update Gravity Forms without a license key.
$ wp gf update
Error: A valid license key must be saved in the settings or specified in the GF_LICENSE_KEY constant or the --key option.

# Attempting to update Gravity Forms when an update is not available.
$ wp gf update
Success: Plugin already updated

# Successfully updating Gravity Forms using the specified license key.
$ wp gf update --key=abc123
Downloading installation package from http://...
Unpacking the package...
Installing the plugin...
Removing the old version of the plugin...
Plugin updated successfully.
Success: Installed 1 of 1 plugins.
Success: Database upgraded.

# Successfully updating the Gravity Forms Polls Add-On.
$ wp gf update gravityformspolls
Downloading installation package from http://...
Unpacking the package...
Installing the plugin...
Removing the old version of the plugin...
Plugin updated successfully.
Success: Installed 1 of 1 plugins.
Success: setup gravityformspolls

Parameters

Argument
Description

[]
The plugin slug.Accepted values: gravityforms or a Gravity Forms Add-On slug.Default: gravityforms.

[--key=]
A valid Gravity Forms license key.

[--version=]
The version to be installed.Accepted values: auto-update, hotfix, or beta.Default: hotfix.

Running the Database Setup
wp gf setup
Examples
# Successfully running the database setup for a new install.
$ wp gf setup
Success: setup gravityforms

# Failing to run the database setup for an existing install.
$ wp gf setup
Error: Use the --force flag to force the database setup.

# Successfully running the database setup for an existing install.
$ wp gf setup --force
Success: Database upgraded.

# Successfully running the database setup for the Gravity Forms Polls Add-On.
$ wp gf setup gravityformspolls
Success: setup gravityformspolls

# Forcing the setup on a multisite network
$ for url in $(wp site list --fields=url --format=csv | tail -n +2); do echo Running setup for site: $url; wp gf setup --force --url=$url; done
Running setup for site: https://one.site.local/
Success: Database upgraded.
Running setup for site: https://two.site.local/
Success: Database upgraded.

Parameters

Argument
Description

[]
The plugin slug.Accepted values: gravityforms or a Gravity Forms Add-On slug.Default: gravityforms.

[--force]
Runs the setup regardless of whether it has been run before.

Checking for Updates
wp gf check-update
Examples
# Successfully getting the available Gravity Forms versions.
$ wp gf check-update
+-------------+---------+
| type | version |
+-------------+---------+
| auto-update | 2.3 |
| hotfix | 2.3.0.4 |
+-------------+---------+

# Successfully getting the available Gravity Forms Polls Add-On versions in yaml format.
$ wp gf check-update gravityformspolls --format=yaml
---
-
type: auto-update
version: 3.1
-
type: hotfix
version: 3.1.4

Parameters

Argument
Description

[]
The plugin slug.Accepted values: gravityforms or a Gravity Forms Add-On slug.Default: gravityforms.

[--format=]
Defines the format in which the updates will be listed.Accepted values: table, csv, json, yaml, and count.Default: table.

Getting the Version
wp gf version
Examples
# Attempting to get the version when Gravity Forms is not installed.
$ wp gf version
Error: Gravity Forms is not installed. Use the wp gf install command.

# Successfully getting the Gravity Forms version.
$ wp gf version
2.3.0.4

# Attempting to get the add-on version using an invalid slug.
$ wp gf version something
Error: Invalid plugin slug: something

# Successfully getting the Gravity Forms Polls Add-On version.
$ wp gf version gravityformspolls
3.1.4

Parameters

Argument
Description

[]
The plugin slug.Accepted values: gravityforms or a Gravity Forms Add-On slug.Default: gravityforms.

Making a Field Read-only

IntroductionNative (Code) SolutionThird Party Plugin Solution

Introduction

Sometimes making a field read-only can be useful, allowing you to then utilize that field for dynamic display of various messages. If you want to change a field to be read-only, you currently need to use JavaScript to do so. The following filter and function will help you accomplish this.

Native (Code) Solution

First, you will need to add a custom class to your field to easily target the field. In this tutorial, we will be using a class name of gf_readonly to correctly target the field, but you can modify the code example in the next step to use a custom class if you prefer to do so.

Then, you will need to apply the readonly attribute to your field. To do so, you will use JavaScript to target the field. The examples below can be placed within your active theme』s functions.php file or within a functionality plugin.

Targeting a Paragraph Text field

// update '1' to the ID of your formadd_filter( 'gform_pre_render_1', 'add_readonly_script' );function add_readonly_script( $form ) {    ?>                                

Mailgun Change Log

1.3.11.3 | 2020-09-291.2 | 2020-04-301.1 | 2018-11-151.0 | 2018-11-05

1.3.1

Fixed an issue where the links in the notification page were not redirecting the user to the correct mailgun documentation pages.

1.3 | 2020-09-29

Added support for Gravity Forms 2.5.

1.2 | 2020-04-30

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added support for sending result notes.
Added gform_mailgun_send_email_failed hook to allow developers to take additional actions when email sending fails.
Fixed a PHP fatal error that occurs on the notification configuration page when the API request fails.
Improved logging to include notification id, notification name, and entry id in the sending process.
Fix merge tags not being replaced in the From Name.

1.1 | 2018-11-15

Add support for choosing Mailgun regions.
Fix issue with merge tags not being replaced in BCC and Reply To headers.

1.0 | 2018-11-05

It's all new!

Obtaining Your Mailgun API Key

When using the Mailgun Add-On in Gravity Forms, you』ll need to be able to authenticate your site with Mailgun. This is done using an API key assigned by Mailgun. In this article, we』ll show you how to obtain your Mailgun API key.

Log into your Mailgun account.
From the top right navigation menu, click on your name and then Security.
Under API Keys, locate the Private API Key field. Click on the eye icon to the right of the field to display your API key.

That』s all there is to it! From here, you can continue setting up the Mailgun Add-On or start sending form notifications using Mailgun.

Mailchimp Feed Setting Reference

SummaryFeed SettingsNoteLimitations

Summary

This article references the Mailchimp feed settings. The Creating a Feed for the Mailchimp Add-On article gives an example of a feed and how it』s created.

Feed Settings

SettingDescriptionNameEnter a feed name to uniquely identify this setup.Mailchimp AudienceSelect the Mailchimp audience you would like to add your contacts to.Map FieldMap each of the Mailchimp fields to the desired form field that will contain that information. In Mailchimp these are the fields that display in the user profile information. You can add new fields to the profile under Audience -> Manage Audience -> Settings -> Audience fields and Merge tags. See note 1.

SettingDescriptionGroupsUsed to add users to your Mailchimp groups. See Adding Mailchimp Subscriptions to Groups for more information.Marketing PermissionAllows you to set a condition to opt users into different marketing types. If an existing user is found and already opted-in for a Marketing Permission, they will stay opted-in. See note 2.OptionsIf you select Double Opt-In, then all audience subscribers will be sent a confirmation email via Mailchimp』s service before they are finalized as included in the audience. The Mark subscriber as VIP checkbox sets the VIP flag.Tags Using text and merge tags, you can assign tags to the entered subscriber. Multiple tags can be set as a comma separated list. This new integration with Mailchimp』s tags was launched with Mailchimp Add-On v4.4. For more information on tags, refer to Mailchimp』s documentation.NoteAssign a note to the entered subscriber. This is sent to Mailchimp so the note is added to the member details. This is only visible to the Mailchimp account owner. Supports merge tags.Conditional Logic If unchecked, every successful form submission will be sent to Mailchimp. If you wish to set specific conditions for sending form data to Mailchimp, then check the 「Enable Condition」 box and fill out your required criteria.

Note

Map each of the Mailchimp fields to the desired form field that will contain that information. In Mailchimp these are the fields that display in the user profile information. You can add new fields to the profile under Audience → Manage Audience → Settings → Audience fields and Merge tags.Requires GDPR fields to be enabled for the Mailchimp audience. This is done under Audience → Manage Audience → Settings → Audience name and campaign defaults. Also the audience is required to have at least one member; if the audience does not have any members, add a temporary user (you can delete it after).

Limitations

Once a user has unsubscribed from Mailchimp, they cannot be resubscribed to an Audience through the Mailchimp Add-On and the Mailchimp API. They would only be able to resubscribe using Mailchimp』s subscribe forms. This is a limitation of the Mailchimp API.

Mailchimp Feed Meta

IntroductionUsagePropertiesGroups

Introduction
The Feed Object meta for the Mailchimp add-on is an associative array containing the properties which determine how the add-on should process the form submission.
1234567$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.:
1$conditional_logic_enabled = rgars( $feed, 'meta/feed_condition_conditional_logic' );

Properties

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

mailchimpList string
The API List ID for the Mailchimp list this feed will subscribe the user to when processed.

mappedFields_EMAIL string
The ID of the field containing the user』s email address.

mappedFields_FNAME string
The ID of the field containing the user』s first name.

mappedFields_FNAME string
The ID of the field containing the user』s first name.

mappedFields_{tag} string
The ID of the field containing the value for the list field.
There would also be properties for any other List fields and *|MERGE|* tags configured for your list, they all begin mappedFields_ and then end with the tag, e.g. mappedFields_MMERGE3.

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.

Groups
If the Mailchimp List has any groups configured, the following properties will be added for each group. {GROUPID} is a 13 character unique ID generated by the add-on to identify the group.

mc_group_{GROUPID}_enabled boolean
Should the user be added to the group.

mc_group_{GROUPID}_decision string
Should the user always be added to the group or only if the configured condition is met. Possible values: if or always.

mc_group_{GROUPID}_field_id string
The ID of the field containing the value which should be compared against mc_group_{GROUPID}_value.

mc_group_{GROUPID}_operator string
Operator to be used when evaluating this rule. Possible values: is, isnot, >, <, contains, starts_with, or ends_with. mc_group_{GROUPID}_value string The value required for the user to be added to the group.

Remove an Application from your Mailchimp Account

IntroductionStepsReference

Introduction

Our Mailchimp Add-On now uses an upgraded OAuth authentication method, which upon connection and validation, creates an authorized app within your Mailchimp account.

This article shows how to revoke that access, by describing how to remove the app from your authorized list.

Steps

To remove an application from your list of authorized applications, follow these steps.

Log in to mailchimp.com with a web browser.Click your profile icon and choose Account.Click the Extras drop-down menu and choose API keys.In the Authorized applications section, click the 「X」 next to the application you need to remove.

Reference

For more information, see this Mailchimp article.

Conditional Audience Subscriptions in Mailchimp

In some scenarios, you may want different users subscribed to different Mailchimp Audiences based on their form selections. In this article, we will show you how to configure different subscriptions based on the form options chosen.

Note: This article assumes that you have already set up your audiences and have a basic familiarity with the Mailchimp Add-On. If not, take a look at the Mailchimp setup guides.

Create a Radio Button field and add your audiences as choices.

For each of your audiences, you will need to create a new feed. Within the form editor, hover over Settings and click on Mailchimp.Click Add New and begin setting up your feed, selecting one of your audiences. If you need more information on creating feeds, take a look at our Creating a Feed for the Mailchimp Add-On article.Within your feed settings, click the checkbox labeled Enable Condition to enable Conditional Logic. Using conditional logic will allow you to only use this feed when a particular parameter exists. In this case, it is the setting you want to use for this audience.

Inside the conditional logic settings, select the field that you want to use for the audience selection, as well as the selection that a user will need to select for the audience to be used. In the example below, if the user selects Team Sports from the Audience field, that user will be added to Team Sports Audience in Mailchimp.Click Save Settings to save your feed configuration.Now this feed will only process if the conditional logic settings are met. You can create additional feeds for your other audiences like Video Games and Hunting using these same instructions.

Mailchimp Change Log

5.0 | 2021-09-294.9 | 2021-04-284.8 | 2020-09-094.7 | 2020-03-244.6 | 2019-03-224.5 | 2018-12-194.4 | 2018-10-294.3 | 2018-03-274.2 | 2017-04-034.1 | 2017-01-034.0 | 2016-12-203.7.5 | 2016-11-293.7.4 | 2016-09-163.7.3 | 2016-05-063.7.2 | 2016-03-113.7.1 | 2015-09-233.7 | 2015-08-243.6 | 2015-04-203.5 | 2015-02-033.4 | 2015-02-023.3 | 2015-01-303.2 | 2014-12-083.1 | 2014-11-213.0 | 2014-11-042.2 | 2013-06-192.1 | 2013-03-262.0 | 2013-03-071.9 | 2012-11-281.8 | 2012-10-241.7 | 2012-07-031.6.3 | 2012-03-131.6.2 | 2012-03-011.6.1 | 2012-01-201.6 | 2012-01-051.5 | 2011-06-231.4 | 2011-04-251.3.41.3.31.3.2 | 2011-02-061.3.1 | 2010-12-151.3 | 2010-12-151.2 | 2010-12-151.11.0.beta-21.0.beta-10.2 | 2010-12-150.1 | 2010-12-15

5.0 | 2021-09-29

Updated the authorization flow to connect to the Mailchimp API via Oauth.

4.9 | 2021-04-28

Fixed an issue where conditional logic is not correctly identifying matching selections when forms contain a multi-select field.
Fixed an issue where the add-on icon is missing on the form settings screen in Gravity Forms 2.5.

4.8 | 2020-09-09

Added support for Gravity Forms 2.5.
Fixed birthday merge fields no longer being sent in the correct format expected by the Mailchimp API.

4.7 | 2020-03-24

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added support for feed duplication.
Updated stylesheets to use minified versions.
Updated strings containing MailChimp to Mailchimp and list(s) to audience(s).
Fixed a PHP error which could occur when using the http_request_timeout filter with WP 5.1+.

4.6 | 2019-03-22

Added support for Marketing Permissions (GDPR) fields.

4.5 | 2018-12-19

Fixed new tags not being added when updating existing list member.

4.4 | 2018-10-29

Added support for MailChimp contact tags.

4.3 | 2018-03-27

Added security enhancements.
Added GPL to plugin header.
Updated API library to public property in support of MailChimp block.
Updated Plugin URI and Author URI to use https.
Fixed the MailChimp API returning a validation error for list date fields set to the DD/MM/YYYY format.
Fixed existing member retaining a status of cleaned or transactional instead of changing to pending or subscribed.
Fixed birthday and date merge fields not being sent in the defined date format.
Fixed an issue with the member status on resubscription to the list.
Fixed PHP notice if the interests are not returned by the MailChimp API for the existing member.
Fixed issue with css file that was being enqueued in every page.

4.2 | 2017-04-03

Added additional logging when checking if a user's subscription status.
Added existing member object as sixth parameter of gform_mailchimp_subscription filter.
Fixed PHP warning when attempting to check for existing interests when member did not belong to any interest categories.
Fixed Fatal error that happened in certain situations.
Fixed existing interest categories not being properly associated to subscription object.
Fixed an issue with subscriptions not being created due to empty merge fields.
Fixed an issue which could prevent the feed groups being converted to interest categories when upgrading from older versions of the add-on.
Fixed inability to use double opt-in with existing members.
Fixed API response error handling; API key was incorrectly shown as valid when a 403 Forbidden error was returned.
Fixed an issue with the field value used for interest category logic evaluation.
Restored GFMailChimp::get_group_setting_key() for use when upgrading from older versions of MailChimp Add-On.
Restored double opt-in support for members who are being resubscribed to a list they are unsubscribed from.
Disabled double opt-in support for members who are being resubscribed to a list they are unsubscribed from. (Member will be automatically subscribed to the list. This is a temporary workaround for an issue with the MailChimp API.)
Re-introduced support for gform_mailchimp_keep_existing_groups filter.

4.1 | 2017-01-03

Added additional error logging when creating a subscription.
Added support for configuring a note to be added to the subscriber.
Fixed a fatal error during feed processing when a list field is mapped to an entry property.
Fixed an issue where an Invalid Resource error would occur if the subscribers merge_fields property was included in the request when empty.
Fixed an issue with the note being urlencoded during merge tag processing.
Fixed users not being subscribed due to incorrect address formatting.
Increased number of merge fields returned for a list.
Updated feed processing to bypass override empty fields check for address fields.
Updated maximum number of category interests returned by the API.
Updated maximum number of interest groups returned by API.
Updated merge fields field map to only allow Address fields to be mapped to MailChimp address merge fields.
Updated strings for translations.
Updated subscription object to use existing member status where possible.

4.0 | 2016-12-20

Added gform_mailchimp_subscription filter to modify subscription object.
Removed 3.0 upgrade page.
Removed send welcome email as feed settings option.
Updated API requests to use MailChimp API 3.0.

3.7.5 | 2016-11-29

Fixed strings for translations.

3.7.4 | 2016-09-16

Fixed an issue with multi-input fields available for use with groups logic not including the inputs (i.e. Name and Address).

3.7.3 | 2016-05-06

Updated the MailChimp API to support the WP_PROXY_HOST and WP_PROXY_PORT constants when configuring the cURL options.

3.7.2 | 2016-03-11

Fixed an issue which was preventing feed processing aborting early if there is an issue with the MailChimp API.

3.7.1 | 2015-09-23

Fixed an issue where the cached settings were not cleared when the add-on was uninstalled.
Fixed a rare issue for some server environments where several groups could be assigned the same settings key causing js issues in the feed editor.
Fixed an issue where the cached group setting keys could be lost when updating the API key on the plugin settings tab.

3.7 | 2015-08-24

Added form and field specific versions of the gform_mailchimp_field_value filter.
Added logging of group condition evaluation.
Added $transaction, either Update or Subscribe, as the fifth parameter of the gform_mailchimp_args_pre_subscribe filter.
Updated minimum Gravity Forms version to 1.9.3.
Updated 'Opt-In Condition' setting label to 'Conditional Logic'.
Updated feed processing to use get_field_value() when retrieving mapped field values, enabling support for GF_Field::get_value_export with GF 1.9.12.4 and later.
Updated to use GF_Field::is_conditional_logic_supported to determine which field types should be listed in the group condition fields drop down.
Fixed an issue with the feed list page if the API key not valid.
Fixed an issue with the location of the gform_mailchimp_args_pre_subscribe filter.
Fixed an issue with the upgrade routine which caused it run even if a pre-framework version hadn't been installed.
Remove plugin settings header and add line break after plugin settings description.

3.6 | 2015-04-20

Added filter to allow changing parameters to the API method that returns the MailChimp Lists.
Added Spanish (es_ES) translation.
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 the members existing groups being lost if no new groups were selected and gform_mailchimp_keep_existing_groups is true.

3.5 | 2015-02-03

Updated required version of Gravity Forms to 1.8.17.
Fixed an issue with Address fields where MailChimp would ignore the passed string if it did not contain the street address, city, state, or zip.

3.4 | 2015-02-02

Added support for the middle name input when preparing Name field values.
Updated required version of Gravity Forms to 1.9.
Fixed an issue causing checkbox fields not to be mapped under certain conditions.
Fixed fatal error with PHP < 5.4. 3.3 | 2015-01-30 Updated logging statements. Updated the gform_mailchimp_field_value filter to have an additional parameter which includes the name of the custom mapped field. Fixed issue causing address not to be mapped properly under certain scenarios. Fixed Notice. Fixed an issue with the concatenated string for Checkbox fields not being cleared before the next field is processed. Fixed a warning when MailChimp interest groups aren't enabled on the list. 3.2 | 2014-12-08 Added hook to allow args to be changed before sending submission to MailChimp. add_filter( 'gform_mailchimp_args_pre_subscribe', 'override_mailchimp_params', 10, 4 ); function override_mailchimp_params( $params, $form, $entry, $feed ) { // do stuff return $params; } Added hook to select whether empty mapped fields should override existing values on Mailchimp; defaults to override. add_filter('gform_mailchimp_override_empty_fields', '__return_false' ); Fixed issue where existing groups were not maintained for users already subscribed. Fixed notice messages. Fixed fatal error displayed on certain situations. 3.1 | 2014-11-21 Fixed issue where grouping assignment was not working for already subscribed users. Fixed issue where a fatal error is displayed in certain situations. Fixed issue with upgrade that caused configuration not to be copied over in certain situations. 3.0 | 2014-11-04 Added integration with Add-On Framework. Added support for sending selected checkboxes as a concatenated string. Updated POT file. Updated required version of Gravity Forms to 1.8.17. Updated to MailChimp API version 2.0. Updated files removing closing php tag at the end. Fixed a warning when MailChimp interest groups aren't enabled on the list. 2.2 | 2013-06-19 Updated phone number when set to standard format "(#########)######### - ############" to send in required format of #########-#########-############. 2.1 | 2013-03-26 Added Name (Full) as an option to the field mapping list when the form has a Name field set to Normal or Extended format. 2.0 | 2013-03-07 Fixed PHP warnings when no API key was set. Added the gform_mailchimp_field_value filter to enable the value to be modified before being sent to the MailChimp API. Added entry meta to the list of available field mappings. Fixed issue with group conditional logic not displaying all possible operators and value drop down correctly. Fixed issue with special character in main group name. Fixed issue with group conditional logic with non-selection field types. Added new hook gform_mailchimp_allow_resubscription which allows disabling support for resubscription. add_filter('gform_mailchimp_allow_resubscription', '__return_false()'); Fixed issue saving group settings in admin when sub groups have the same name. 1.9 | 2012-11-28 Updated Group logic to keep existing groups. Added filter to change logic back to overriding groups. add_filter("gform_mailchimp_keep_existing_groups", "__return_false"); Updated to treat members as if they were a new subscribe request when currently set to a status on MailChimp's side of unsubscribed, pending, cleaned. Fixed issue with special characters in MailChimp Group names causing issues when creating feed. 1.8 | 2012-10-24 Fixed issue with GetFieldValues() when used with groups; was returning full select when only options were required. Fixed notices. Fixed group names (commas in names are treated by MailChimp as a delimiter indicating multiple groups). 1.7 | 2012-07-03 Fixed issue with some Mapped Fields not being passed (Entry Date, User IP, Source Url, Form Title). Added new conditional logic options (greater than, less than, contains starts with, ends with) and support for other conditional fields. Fixed notices. Fixed issue when testing if email is already in the list. 1.6.3 | 2012-03-13 Added logging. Fixed notices. Fixed issue with single quotes on feed edit screen creating javascript errors. 1.6.2 | 2012-03-01 Fixed issue with sack script being initialized with an incorrect admin url. Fixed issue that causing conflicts with feeds created by older versions of the plugin. 1.6.1 | 2012-01-20 Fixed issue that caused warnings to be displayed on feeds created by older versions. 1.6 | 2012-01-05 Fixed issue where RG_CURRENT_PAGE constant was not available when GF is deactivated. Fixed noticed caused where $api variable not declared. Added support for MaiChimp Groups so that subscribers can be assigned to a group when added to a list. Added Form Title to the list of fields to be mapped. Updated procedure that gets the MailChimp lists so that more than 25 lists are returned (up to 100). Added integration with PayPal so that subscribers can be added only when payment is received. 1.5 | 2011-06-23 Updated API Wrapper to 1.3 (mini). Removed blank strings from POT file to prevent error messages in Poedit. 1.4 | 2011-04-25 Cleaned up notices. Fixed issue when using Opt-in condition on a field with multiple single quote characters in the label. Fixed issue when creating a feed using forms with HTML markup in field labels. 1.3.4 Cleaned up notices. 1.3.3 Added "Cancel" button to Edit page and updated "Save" and "Update" button verbiage. 1.3.2 | 2011-02-06 Fixed issue with MailChimp lists being displayed as blank values. Taking into account different data formats returned by the API. 1.3.1 | 2010-12-15 Using new MailChimp PHP API wrapper (v. 1.2.6) when authenticating via an API Key. 1.3 | 2010-12-15 Added support for authentication via MailChimp API Key. 1.2 | 2010-12-15 Fixed issue with automatic upgrade on WP 3.0. 1.1 Adding MailChimp capabilities to admin role upon plugin activation. 1.0.beta-2 Added MailChimp icon. Renamed "Contact List" to "MailChimp List". 1.0.beta-1 Changed text on list page when settings haven't been configured. Created POT file. 0.2 | 2010-12-15 Map Fields column headers to ?List Fields? and ?Form Fields? and bol. Rename button to "Save Feed" for a new feed and "Update Feed" for an existing one. Settings page subnavigation to look like "Edit Forms" subnav (i.e. All | Active | Inactive) with no pipe at the end. Try adding menu item between Entries and Settings. Move "Add Feed" to top right (like posts page) and rename to "Add new". 0.1 | 2010-12-15 Split logic from Feeds Add-On. Implemented automatic upgrade. Implemented list page checkboxes (for bulk actions). Implemented active/inactive icons on list page.

Mad Mimi Feed Meta

IntroductionUsagePropertiesCustom Field Properties

Introduction
The Feed Object meta for the Mad Mimi 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',
'fields_email' => '2',
'fields_firstname' => '1.3',
'fields_lastname' => '1.6',
'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.

list string
The ID of the Mad Mimi list this feed will add contacts to.

fields_email string
The ID of the field containing the user』s email address. Required.

fields_firstname string
The ID of the field containing the user』s first name.

fields_lastname string
The ID of the field containing the user』s last name.

fields_title string
The ID of the field containing the user』s title.

fields_company string
The ID of the field containing the user』s company.

fields_phone string
The ID of the field containing the user』s phone number.

fields_address string
The ID of the field containing the user』s address.

fields_city string
The ID of the field containing the customer』s city.

fields_state string
The ID of the field containing the customer』s state.

fields_zip string
The ID of the field containing the customer』s zip.

fields_country string
The ID of the field containing the customer』s zip.

custom_fields array
A multidimensional array containing the custom fields to be sent to Mad Mimi. See Custom Field Properties.

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.

Custom Field Properties
array(
'key' => 'gf_custom',
'value' => '3.1',
'custom_key' => 'address_one',
)

Each custom field is an associative array containing the following properties:

key string
The custom field key. Value: gf_custom

value string
The ID of the form field or entry meta item containing the value for this custom field.

custom_key string
The custom field name.