Author 詩語

Authorize.Net Feed Meta

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.

Authorized Gravity Forms Sellers

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.

Setting Up the Trello Add-On

Pre-RequisitesSetupUpgrading from Earlier VersionRe-Authenticating to Trello

Pre-Requisites

Download and install the add-onA Trello account

Setup

Before you can begin creating a feed for the Trello Add-On, you will first need to authorize it to access your Trello account.

Log into your WordPress Admin dashboard.

Go to Forms > Settings > Trello. You』ll be presented with a button to Authorize with Trello. Click the button to authenticate with your Trello account.

You will be presented with a notice advising you are being Redirected to Trello.

If you are not already logged into your Trello Account, you will be asked to login to Trello. Login to Trello.

Once you are logged into your Trello Account, the next dialogue asks you 「Would you like to give the following application access to your account?」. This dialogue will include:

Application Name: Gravity FormsTrello Account you are logged into and your User NameWhat permissions Gravity Forms is requesting to your Trello Account, and The boards and workspaces Gravity Forms will have access to.

Click Allow to authorize Gravity Forms to access your account.

You will be redirected back to your website from Trello.

You will now be returned to your Gravity Forms Trello Settings and will see a successful connection to Trello.

Once you have authorized the Trello Add-On, you』re ready to begin creating a feed for the Trello Add-On.

Upgrading from Earlier Version

If you are upgrading from a version of the Trello Add-On earlier than 2.0, you』ll need to re-authenticate to Trello. This will not impact any of your existing feeds.

You will see a warning in your Gravity Forms Admin screen: Gravity Forms Trello requires re-authentication. Please disconnect and re-connect to continue using this add-on.

Re-Authenticating to Trello

Go to Forms > Settings > Trello and click De-Authorize Trello.

After clicking, you』ll receive the Settings Updated notice and the button will change to Click here to Authenticate your Trello Account. Continue with the steps above to Authenticate your Trello account.

Autoresponder (deprecated)

IntroductionUsageProperties

Introduction
The AutoResponder object contains the settings for the user』s notification, such as destination email field, email subject and body. It is defined as an associative array.

The AutoResponder object is deprecated as of Gravity Forms 1.7. It is replaced by the Notifications Object.

Usage
12$form['autoResponder']['bcc'];     //returns the BCC email address$form['autoResponder']['subjec']; //returns the email subject

Properties

toField string
Id of an email field on the form whose value should be used as the destination email address.

from string
If specified, forces the email to be sent from this address. If not specified, the email address configured in WordPress will be used.

replyTo string
Contains the email address to be used as the reply to email address.

bcc string
Contains the email address to be used as the bcc email address.

subject string
Contains the subject of the email.

message string
Contains the body/content of the email.

disableAutoformat boolean
Determines if the email message should be formatted so that paragraphs are automatically added for new lines. 1 disables auto-formatting, 0 enables auto-formatting

Setting Up the AWeber Add-On

UsesPre-RequisitesRetrieve AWeber Authorization CodeSetup Your AWeber FeedsReady To Go!

Uses
The Gravity Forms AWeber Add-On gives you an easy way to integrate all of your online forms with the AWeber opt-in email marketing service. Collect and add subscribers to your email marketing lists automatically when a form is submitted.

Automatically add subscribers to your email lists when a form is submitted.
Control opt-in and only add subscribers when a certain condition is met.
Automatically sends a double opt-in message to insure only legitimate subscribers are added. (Because the AWeber Add-On uses the API for integration, all submissions will be double opt-in. This is an AWeber restriction.)

Pre-Requisites

Download and install the add-on
An AWeber account

Retrieve AWeber Authorization Code
You will need to retrieve your AWeber Authorization Code to allow Gravity Forms to send data to AWeber. Refer to this article for how to retrieve and enter your authorization code.
Setup Your AWeber Feeds
Now you need to add a feed. Adding an AWeber feed will connect your submitted form data to your AWeber account. For step by step instructions, refer to this article.
Ready To Go!
Now that you have setup an AWeber feed, when the form you selected is submitted, it will automatically send the data you have selected to the AWeber list you have mapped it to. Run a few tests to see it in action!

AWeber Change Log

2.11 | 2020-09-212.10 | 2020-03-112.9 | 2019-08-072.8 | 2018-11-022.7 | 2018-04-022.6 | 2017-10-262.5 | 2017-04-282.4.2 | 2016-11-302.4.1 | 2016-09-022.4 | 2016-07-292.3 | 2015-08-072.2 | 2015-04-202.1 | 2014-11-212.0 | 2014-11-191.4 | 2013-03-051.3 | 2012-06-271.2 | 2012-03-121.1 | 2012-01-18

2.11 | 2020-09-21

Added support for Gravity Forms 2.5.
Fixed an issue where the contact is not created if there are blank tags.

2.10 | 2020-03-11

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Fixed PHP 7.4 notices which occur when saving the settings for the first time.

2.9 | 2019-08-07

Added security enhancements.

2.8 | 2018-11-02

Added the filter gform_aweber_app_id enabling the app id used to authorize the add-on with AWeber to be overridden.
Added support for tags.

2.7 | 2018-04-02

Added security enhancements.
Added License GPL to plugin header.
Updated Plugin URI and Author URI to https.

2.6 | 2017-10-26

Updated API library to support PHP 7.

2.5 | 2017-04-28

Added security enhancements.
Added translations.

2.4.2 | 2016-11-30

Fixed strings for translations.

2.4.1 | 2016-09-02

Added the hook gform_aweber_post_subscriber_created

2.4 | 2016-07-29

Updated to support feed duplication with Gravity Forms 1.9.15+.
Updated the choices for the Email Address field to only list email and hidden type form fields.
Fixed an issue with custom fields returned by the AWeber API which don't have labels.
Fixed fatal error which could occur during feed processing if the configured account ID for the feed becomes invalid.
Fixed fatal error which could occur if the configured account ID for the feed becomes invalid.

2.3 | 2015-08-07

Added form and field specific versions of the gform_aweber_field_value filter.
Updated minimum Gravity Forms version to 1.9.3.
Updated feed processing to use GFAddOn::get_field_value(), if available, when retrieving mapped field values.
Updated 'Opt-In Condition' setting label to 'Conditional Logic'.
Fixed an issue with the feed list page if the AWeber auth code was not valid.
Fixed an issue with the upgrade routine which caused it run even if a pre-framework version hadn't been installed.

2.2 | 2015-04-20

Added hook to allow args to be changed before sending submission to AWeber.
add_filter('gform_aweber_args_pre_subscribe', 'add_ip', 10, 4);
function add_ip( $args, $form, $entry, $feed ){
$args['ip_address'] = $entry['ip'];
return $args;
}
Added support for the middle name input when preparing Name field values.
Updated how Address field values are prepared to also support Gravity Forms 1.9 method for getting country code.
Updated logging statements.
Fixed a low severity security vulnerability in the admin area which could be exploited by authenticated users with form administration permissions.
Fixed issues when upgrading causing feeds not to get created.

2.1 | 2014-11-21

Fixed error when creating new feeds.

2.0 | 2014-11-19

Added integration with Add-On Framework.
Added text domain/path to header.
Added the gform_aweber_field_value filter so the field value can be modified before sending to AWeber.
Updated required version of Gravity Forms to 1.8.17.
Updated POT file.
Updated to not process entries marked as spam.
Fixed an issue where non-string field values would cause the AWeber create subscriber process to fail.

1.4 | 2013-03-05

Added PayPal integration to subscribe user to AWeber only when payment is received.
Updated the AJAX Url to resolve conflicts with sites running over HTTPS.
Fixed issue where spaces after closing php tag caused problems with WP 3.5 release.

1.3 | 2012-06-27

Added logging support.
Added new conditional logic options (greater than, less than, contains starts with, ends with) and support for other conditional fields
Fixed notices.
Fixed issue with API throwing errors on some PHP installations.

1.2 | 2012-03-12

Fixed issue with Full Name field not being sent to AWeber when mapped to custom fields.

1.1 | 2012-01-18

Updated PHP API and using it to subscribe users instead of relying on email
Added support for field mapping
Added hook to allow custom Ad Tracking text to be assigned to the subscriber
add_filter("gform_aweber_ad_tracking", "aweber_ad_tracking", 10, 4); //site wide ad tracking
OR
add_filter("gform_aweber_ad_tracking_20", "aweber_ad_tracking", 10, 4); //form specific ad tracking
function aweber_ad_tracking($ad_tracking, $entry, $form, $feed){
return "Custom Ad Tracking";
}

IMPORTANT: $_collectionMap property in api/aweber.php line 82 has been made public to resolve errors on some PHP installations. When updating API, make sure to re-apply change.

AWeber Feed Meta

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.

$_async_feed_processing

DescriptionPropertiesUsageLocation

Description
The $_async_feed_processing property allows you to define a feed as asynchronous. By using this property, the feed will be processed asynchronously instead of at the same time other feeds are.
Properties
Class: GFFeedAddOn
Access: protected
Type: boolean
Defaults to: false
Usage
123class ExampleFeedAddOn extends GFFeedAddOn {    protected $_async_feed_processing = true;}
Location
includes/addon/class-gf-feed-addon.php

$_requires_credit_card

DescriptionPropertiesUsageLocationUsed By

Description
The $_requires_credit_card property allows you to easily define if a credit card field is required by a payment add-on. If this is set to true, the user will not be able to create any payment feeds without a credit card field present in the form.
Properties
Class: GFPaymentAddOn
Access: protected
Type: boolean
Defaults to: false
Usage
123class ExamplePaymentAddOn extends GFPaymentAddOn {    protected $_requires_credit_card = true;}
Location
includes/addon/class-gf-payment-addon.php
Used By
GFPaymentAddOn::before_delete_field()
GFPaymentAddOn::feed_list_message()
GFPaymentAddOn::init_admin()

$_supports_callbacks

DescriptionPropertiesUsageLocationUsed By

Description
The $_supports_callbacks property defines if your payment add-on supports callbacks. By enabling this property within your payment add-on, you can easily receive and process callbacks.
Properties
Class: GFPaymentAddOn
Access: protected
Type: boolean
Defaults to: false
Usage
123class ExamplePaymentAddOn extends GFPaymentAddOn {    protected $_supports_callbacks = true;}
Location
includes/addon/class-gf-payment-addon.php
Used By
GFPaymentAddOn::upgrade_payment()