Checking this option will enable data to be passed to the form and pre-populate this field dynamically. Data can be passed via Query Strings, Shortcode and/or Hooks. After checking this option, you will need to specify the name of the parameter you will be using to pass data to this field.
For more detailed information on how to dynamically populate a field and known limitations please see our documentation on dynamic population.
IntroductionUsageProperties
Introduction
The Feed Object meta for the AWeber 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',
'listFields_email' => '2',
'listFields_fullname' => '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.
account string
The AWeber account ID the contacts will be added to.
contactList string
The AWeber list ID the contacts will be added to.
listFields_email string
The ID of the field containing the user』s email.
listFields_fullname string
The ID of the field containing the user』s full name.
listFields_cf_{custom_field_id} string
The ID of the field containing the value for the custom field.
There would be properties for any custom fields configured for your list, they all begin listFields_cf_ and then end with the custom field ID, e.g. listFields_cf_1.
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.
1.4 | 2020-09-161.3 | 2020-03-261.2 | 2018-04-091.1 | 2016-01-271.0 | 2015-07-28
1.4 | 2020-09-16
Added support for Gravity Forms 2.5.
Fixed a fatal error which occurs during form submission if the field mapped to the contact email address is empty.
Fixed contact tags property including empty and duplicate items.
1.3 | 2020-03-26
Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added tooltip to the Tags setting on the feed configuration page.
Added support for feed duplication.
Updated stylesheets to use minified versions.
Updated feed processing error logging statement and entry note to use the API returned error message when a 400 error occurs.
Fixed PHP 7.4 notices which occur when the API is initializing and the settings are empty.
Fixed the width of the Feed Name setting on the feed configuration page.
1.2 | 2018-04-09
Added security enhancements.
Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.
Updated analytics tracking code.
Fixed strings for translations.
1.1 | 2016-01-27
Added feed duplication support. Requires Gravity Forms 1.9.14.26 or greater.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Updated action feed settings field with icons.
Updated Agile CRM API library to use WordPress API functions.
Updated available field types for mapping to the contact first name, last name, and email.
Fixed an issue with the settings page incorrectly indicating the api credentials are valid when the response was a 500 error.
Fixed an issue with the request failed message if a WP_Error occurs.
Fixed an issue with how the full address field value is formatted when sent to Agile.
Fixed a fatal error when the AgileCRM class has already been included by another plugin.
Fixed an issue with the contact tags being overwritten when the feed is configured to update and append.
1.0 | 2015-07-28
It's all new!
IntroductionUsagePropertiesProduct Transaction PropertiesSubscription Transaction Properties
Introduction
The Feed Object meta for the Authorize.Net add-on is an associative array containing the properties which determine what type of transaction should occur and what values are sent to Authorize.Net.
12345678$feed['meta'] = array( 'feedName' => 'Your Feed Name', 'transactionType' => 'product', '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.
transactionType string
The type of transaction which should occur when the feed is processed. Possible values: product or subscription.
billingInformation_email string
The ID of the field containing the customer』s email.
billingInformation_address string
The ID of the field containing the first line of the customer』s address.
billingInformation_address2 string
The ID of the field containing the second line of the customer』s address.
billingInformation_city string
The ID of the field containing the city of the customer』s address.
billingInformation_state string
The ID of the field containing the state of the customer』s address.
billingInformation_zip string
The ID of the field containing the zip of the customer』s address.
billingInformation_country string
The ID of the field containing the country of the customer』s address.
enableReceipt boolean
Send Authorize.Net email receipt? Default is false.
apiSettingsEnabled boolean
Override the default API settings? Default is false.
overrideMode string
Which mode should this feed use when overriding the default API settings. Possible values: production or test.
overrideLogin string
The API login ID to use when overriding the default API settings.
overrideKey string
The API transaction key to use when overriding the default API settings.
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.
Product Transaction Properties
The following properties are only applicable when the transactionType is set to product.
paymentAmount string
What to use for the payment amount. Possible values: form_total or a product field ID
Subscription Transaction Properties
The following properties are only applicable when the transactionType is set to subscription.
recurringAmount string
What to use for the recurring amount. Possible values: form_total or a product field ID
billingCycle_length integer
How often should the recurring payment occur. Minimum values: 7 days or 1 month. Maximum values: 365 days or 12 months.
billingCycle_unit string
What unit to use with the billingCycle_length. Possible values: day or month.
recurringTimes integer
How many times the recurring payment should be made. The default (0) is to bill the customer until the subscription is canceled.
setupFee_enabled boolean
Should a setup fee be charged? Default is false.
setupFee_product string
The ID of the product field containing the amount the user should be charged for the setup fee.
trial_enabled boolean
Should the recurring charge occur immediately or after a trial period? Default false.
trial_product string
What is the source of the amount the user should be charged during the trial. Possible values: enter_amount or a product field ID.
trial_amount string
The amount the user should be charged during the trial if enter_amount is selected for the trial_product.
update_post_action string
Change the post status when a subscription is canceled? Possible values: draft or delete.
SummaryUsageProperties:id:return_typeNotesKnown Issues
Summary
Allows for files uploaded to the media library to be inserted into the post.
Usage
{apc_media:[id]:[return_type]}
Properties
:id
The File Upload field ID.
:return_type
Format uploaded files should be returned in: ids or urls.
Notes
By default, the merge tag inserts the IDs of the uploaded files. This can be changed to insert the URLs of the uploaded files by defining urls as the third parameter, e.g. {apc_media:12:urls}.
When using the merge tag with a multi-file upload field, file IDs or URLs will be output as a comma separated list.
Known Issues
Since the original Gravity Forms file upload path is not stored with the file in the media library, this merge tag is only available for use during the initial form submission process.
IntroductionUsagePropertiesCustom Field Properties
Introduction
The Feed Object meta for the Agile CRM add-on is an associative array containing the properties which determine how the add-on should process the form submission.
$feed['meta'] = array(
'feedName' => 'Agile CRM Feed 1',
'createContact' => true,
'contactCustomFields' => array(),
'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.
createContact boolean
Create new contact. Default is false.
createTask boolean
Create new task. Default is false.
contactStandardFields_first_name string
The ID of the form field containing the contact』s first name.
contactStandardFields_last_name string
The ID of the form field containing the contact』s last name.
contactStandardFields_email_address string
The ID of the form field containing the contact』s email.
contactCustomFields array
A multidimensional array containing the Agile CRM custom fields. See Custom Field Properties.
contactTags string
A comma separated list of tags to be assigned to the contact. Merge tags supported.
updateContactEnable boolean
Should an existing contact be updated if found? Default is false.
updateContactAction string
The update action. Should the contact details be replaced or appended. Possible values: replace or append.
taskSubject string
The task subject line. Merge tags supported.
taskDaysUntilDue integer
The number of days until the task is due.
taskPriority string
The task priority. Possible values: HIGH, NORMAL or LOW.
taskStatus string
The task status. Possible values: YET_TO_START, IN_PROGRESS or COMPLETED.
taskType string
The task type. Possible values: CALL, EMAIL, FOLLOW_UP, MEETING, MILESTONE, SEND, TWEET or OTHER.
taskCreateNote boolean
Should a note be created for the task? Default is false.
taskNoteSubject string
The task note subject. Merge tags supported.
taskNoteDescription string
The task note description. Merge tags supported.
taskAssignToContact boolean
Should the task be assigned to the created contact? 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.
Custom Field Properties
array(
'key' => 'title',
'value' => '3',
)
Each custom field is an associative array containing the following properties:
key string
The Agile CRM custom field key. Possible values: title, company, email_work, email_personal, phone_work, phone_home, phone_mobile, phone_home_fax, phone_work_fax, phone_other, address_home, address_postal, address_office, website_url, website_skype, website_twitter, website_linkedin, website_facebook, website_xing, website_feed, website_google_plus, website_flickr, website_github, website_youtube or 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 key. Only used when the custom field key is set to gf_custom.
Only Purchase from Authorized MethodsWhy You Should Not Purchase From An Unofficial Channel
Only Purchase from Authorized Methods
If you』re wondering if the deal you』ve located is a valid one for Gravity Forms, or you』ve found a site that is offering a discounted version of Gravity Forms that isn』t sold directly on our site, it』s likely not the real deal. These are the only authorized methods for purchasing Gravity Forms:
Licenses that are sold on our site, which will always link to the gravityforms.com to initiate purchase.
Starter licenses bundled as a special offer with GoDaddy Pro Managed WordPress Hosting bundled with [GoDaddy Pro Managed WordPress Hosting]
Starter licenses bundled as a special offer with the GravityFlow third party plug-in.
Licenses sold through an official Gravity Forms affiliate, which will always link to gravityforms.com for the purchase process.
For more information on GravityFlow Starter Licenses, visit GravityFlow.
For more information on Go Daddy licenses, visit Go Daddy
Any other deals you find are not legitimate, but are someone repackaging our code. Often such sites will include something like this in their footer:
DISCLAIMER: All items listed in the Nobuna directory are developed by third-party developers and redistributed by Nobuna under the terms of the General Public License (GPL). Nobuna is not associated with nor is endorsed by the developers of any products featured on this website.
Why You Should Not Purchase From An Unofficial Channel
You will not be eligible for Support from us.
Unauthorized sites may not provide updates. You may end up missing out on security and feature updates.
Unauthorized sites may not provide refunds. We certainly do when you buy through our official channels.
Unauthorized sites can bundle their own code in the package, making your website vulnerable to data extraction or other hacking.
Because those shysters ripped off our carefully designed products with malicious intent, and the desire to profit without putting in any of the hard work, customer compassion, or careful thought that we pride ourselves on. They may dress it up with 「open source」 language, or try to fool you into thinking they are somehow partnered with us (burying their caveats in tiny fine print and fancy language), but they are most definitely not the hard-working folks of Gravity Forms, and any money they receive does not get re-invested into the product.
DescriptionUsageParametersExamplesSource Code
Description
Triggered after the payment details are displayed within a Gravity Forms entry.
Usage
1add_action( 'gform_payment_details', 'my_function', 10, 2 );
Parameters
$form_id integer
The current form ID.
$entry array
The current entry.
Examples
1234function my_function() { //Do something here}add_action( 'gform_payment_details', 'my_function', 10, 2 );
Source Code
This action hook is located in entry_detail.php.
General OptionsGF_THEME_IMPORT_FILEGF_LICENSE_KEYMulti-Site Specific OptionsGF_RECAPTCHA_PRIVATE_KEYGF_RECAPTCHA_PUBLIC_KEYGF_IMPORT_FILECreating a Form Import JSON File
General Options
The following options are available for general use.
GF_THEME_IMPORT_FILE
Setting this option allows you to specify a Form JSON file from which a set of default forms can be pre-generated when a theme containing this option is activated. This option should be specified in your theme』s functions.php file. Follow these steps to create a Form JSON file for use with this option.
1define( 'GF_THEME_IMPORT_FILE', 'path/to/gf_import.json' );
Note: The path is relative to your theme root.
GF_LICENSE_KEY
Setting this option before installing Gravity Forms on a single site WP installation or before creating new sites on a multisite install will automatically pre-populate your Gravity Forms license key for those new installations.
1define( 'GF_LICENSE_KEY', 'YOUR-LICENSE-KEY-HERE' );
Multi-Site Specific Options
The following options are available when using WordPress Multi-Site. All of the options below should be defined in your wp-config.php.
GF_RECAPTCHA_PRIVATE_KEY
GF_RECAPTCHA_PUBLIC_KEY
Setting these options will automatically pre-populate your ReCAPTCHA public and private keys when a new site is created on your Multi-Site install.
12define( 'GF_RECAPTCHA_PUBLIC_KEY', 'YOUR-KEY-HERE' );define( 'GF_RECAPTCHA_PRIVATE_KEY', 'YOUR-KEY-HERE' );
GF_IMPORT_FILE
Setting this option allows you to specify a Form JSON file from which a set of default forms can be pre-generated when a new site is created on your Multi-Site install. Follow these steps to create a Form JSON file for use with this option.
1define( 'GF_IMPORT_FILE', 'http://www.domain.com/path/to/gf_import.json' );
Creating a Form Import JSON File
The following steps explain how to create a Form JSON file from which a set of default forms can be pre-generated when used with the GF_IMPORT_FILE or GF_THEME_IMPORT_FILE option.
Create the initial set of forms you want to replicate.
Navigate to the Import/Export tool and select 「Export Forms」.
Select the forms you want to auto-replicate when a new site is created.
Click 「Export」 to export them to an JSON file.
Place the JSON file somewhere on your web server, such as your wp-content/uploads/ folder, or somewhere easily accessible.
Replace the URL in the example code above with the URL to your Form JSON file.
Pre-RequisitesSetupActiveCampaign Add-On HooksAdd-on Framework Hooks
Pre-Requisites
Download and install the add-on
An ActiveCampaign account
Setup
Log into your WordPress admin dashboard.
On the left side navigation menu, hover over Forms and click on Settings.
From this page, click the ActiveCampaign tab.
Enter your API URL and API Key. These are obtained from ActiveCampaign on your Account Settings page.
Click Update Settings. If you』ve entered your account information correctly, you will be notified by a green check mark beside each box. If you do not see green check marks next to the credentials, please double check this information and try again.
Once you have entered your API keys, you』re ready to begin creating a feed for the ActiveCampaign Add-On.
ActiveCampaign Add-On Hooks
The ActiveCampaign Add-On provides hooks that can be used to modify the default functionality or extend it. For more information, review the ActiveCampaign Add-On Hooks.
Add-on Framework Hooks
Because the ActiveCampaign Add-On is built using the Add-On Framework it also inherits any hooks available in the framework methods it uses such as:
gform_short_slug_field_value for changing a field value before it is passed to ActiveCampaign.
