Author 诗语

Campaign Monitor Feed Meta

IntroductionUsageProperties

Introduction
The Feed Object meta for the Campaign Monitor 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',
'resubscribe' => false,
'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.

client string
The Campaign Monitor client ID the contacts will be added to.

contactList string
The Campaign Monitor 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_{custom_field_name} 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_ and then end with the custom field name (no spaces), e.g. listFields_ipaddress.

resubscribe boolean
Should the subscriber be re-added to the active list if they are in an inactive state or have previously been unsubscribed? 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.

Breeze Change Log

1.5 | 2020-09-241.4 | 2020-03-301.3 | 2018-04-091.2 | 2017-05-161.1 | 2016-05-161.0 | 2016-05-12

1.5 | 2020-09-24

Added support for Gravity Forms 2.5.

1.4 | 2020-03-30

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added support for feed duplication.
Fixed PHP 7.4 notices which occur on the feed configuration page when creating a new feed.
Fixed a PHP fatal error which occurs when accessing an existing feed after the add-on is connected to a different Breeze account.

1.3 | 2018-04-09

Added security enhancements.
Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.
Fixed a PHP warning regarding http_build_query.

1.2 | 2017-05-16

Updated plugin description to be consistent with other Gravity Forms add-ons.
Fixed strings for translations.
Fixed an issue where a due date of Jan 1, 1970 was set on the card.

1.1 | 2016-05-16

Fixed a fatal error when using Gravity Forms 1.9.x.

1.0 | 2016-05-12

It's all new!

Capsule CRM Change Log

1.6 | 2021-05-061.5 | 2020-09-161.4 | 2020-03-311.3 | 2018-04-091.2 | 2018-01-301.1 | 2016-07-291.0 | 2015-07-28

1.6 | 2021-05-06

Added a form settings menu icon for Gravity Forms 2.5.
Updated instructions on the add-on settings page to better describe where to locate your personal access token.

1.5 | 2020-09-16

Fixed a PHP fatal error which can occur if a request to the Capsule CRM API fails.
Fixed an issue where escaped HTML could be included in the name, description, and detail properties of cases, opportunities, persons, and tasks.
Fixed an issue where some error logging statements were echoing to the screen instead of writing to the add-on log.

1.4 | 2020-03-31

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Updated stylesheets to use minified versions.
Updated feed processing to log error explaining why address is not added to object.

1.3 | 2018-04-09

Added security enhancements.
Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.
Updated header to be consistent with other add-ons.

1.2 | 2018-01-30

Updated API library to work with version 2.0 of Capsule CRM API.
Added gform_capsulecrm_case filter to modify the case object before it is created.
Added gform_capsulecrm_opportunity filter to modify the opportunity object before it is created.
Added gform_capsulecrm_person filter to modify the person object before it is created/updated.
Added gform_capsulecrm_task filter to modify the tasks object before it is created.
Fixed a fatal PHP error which would occur if a WP_Error is returned when making a request to the Capsule CRM API.
Fixed PHP notice.
Fixed strings for translations.

1.1 | 2016-07-29

Added feed duplication support.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Updated Capsule CRM API library to use WordPress API functions.
Updated feed processing to abort person creation if email is empty or invalid.
Updated available field types for mapping to the person first name, last name, and email.
Fixed php warnings related to Milestone setting if only one milestone exists.

1.0 | 2015-07-28

It's all new!

Campfire Change Log

1.2.2 | 2018-04-101.2.1 | 2018-01-301.2 | 2017-06-131.1 | 2016-07-291.0 | 2015-07-29

1.2.2 | 2018-04-10

Fixed issue preventing feed from being saved.
Added security enhancements.

1.2.1 | 2018-01-30

Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.

1.2 | 2017-06-13

Added more debug log statements.
Added official translations.
Fixed issue with credentials on Settings page not accurately reflecting validity.
Fixed issue with can_duplicate_feed function not having the needed parameter.

1.1 | 2016-07-29

Added feed duplication support.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Updated Campfire API library to use WordPress API functions.

1.0 | 2015-07-29

It's all new!

Breeze Feed Meta

IntroductionUsageProperties

Introduction
The Feed Object meta for the Breeze add-on is an associative array containing the properties which determine how the add-on should process the form submission.
$feed['meta'] = array(
'feedName' => 'Breeze Feed 1',
'feed_condition_conditional_logic' => true,
'feed_condition_conditional_logic_object' => array(
'conditionalLogic' => array(),
),
);

Usage
We recommend accessing the $feed meta using the rgar() or rgars() functions, e.g.:
$conditional_logic_enabled = rgars( $feed, 'meta/feed_condition_conditional_logic' );

Properties

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

project string
The Breeze ID of the project the card will be added to.

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

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

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

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

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

cardInvitees array
array(
'USER_EMAIL_HERE' => true,
);

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

feed_condition_conditional_logic boolean
Is the feed condition (conditional logic) setting enabled. Default is false.

feed_condition_conditional_logic_object array
An associative array containing the conditional logic rules. See the Conditional Logic Object for more details.

Capsule CRM Feed Meta

IntroductionUsagePropertiesCustom Field Properties

Introduction
The Feed Object meta for the Capsule CRM 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' => 'Capsule CRM Feed 1',
'person_standard_fields_first_name' => '2',
'person_custom_fields' => 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

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

create_person boolean
Create new contact. Default is false.

create_task boolean
Create new task. Default is false.

person_standard_fields_first_name string
The ID of the form field containing the contact』s first name.

person_standard_fields_last_name string
The ID of the form field containing the contact』s last name.

person_standard_fields_email_address string
The ID of the form field containing the contact』s email.

person_custom_fields array
A multidimensional array containing the Capsule CRM custom fields. See Custom Field Properties.

person_about string
The content to be assigned to the contact』s about field. Merge tags supported.

update_person_enable boolean
Should an existing contact be updated if found? Default is false.

update_person_action string
The update action. Should the contact details be replaced or appended. Job title and company will be replaced whether replace or append is chosen. Possible values: replace or append.

create_case boolean
Assign the contact to a new case. Default is false.

create_opportunity boolean
Assign the contact to a new opportunity. Default is false.

case_name string
The case name. Merge tags supported.

case_description string
The case description. Merge tags supported.

case_status string
The case status. Possible values: OPEN or CLOSED.

case_owner string
The case owner. The users Capsule CRM username.

opportunity_name string
The opportunity name. Merge tags supported.

opportunity_description string
The opportunity description. Merge tags supported.

opportunity_milestone string
The Capsule CRM milestone ID.

opportunity_owner string
The opportunity owner. The users Capsule CRM username.

task_description string
The task description. Merge tags supported.

task_detail string
More details for the task. Merge tags supported.

task_days_until_due integer
The number of days until the task is due.

task_status string
The task status. Possible values: OPEN or COMPLETED.

task_category string
The task category. Custom task categories can be configured in the Capsule CRM account.
Default values: Call, Email, Follow-up, Meeting, Milestone, or Send.

task_owner string
The task owner. The users Capsule CRM username.

assign_task string
What the task is assigned to. Possible values: none, case, person or opportunity.

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 Capsule CRM custom field key.
The default keys are: title, organization, email_work, email_home, phone_work, phone_mobile, phone_fax, phone_home, phone_direct, address_office, address_home, address_postal, website_url, website_skype, website_twitter, website_facebook, website_linked_in, website_xing, website_feed, website_google_plus, website_flickr, website_github, and website_youtube.

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

Campfire Feed Meta

IntroductionUsageProperties

Introduction
The Feed Object meta for the Campfire add-on is an associative array containing the properties which determine how the add-on should process the form submission.
$feed['meta'] = array(
'feedName' => 'Campfire Feed 1',
'message' => 'Entry #{entry_id} has been added. ({entry_url})',
'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.

room string
The ID of the Campfire room this feed will post a message to when processed.

message string
The message that will be posted to the Campfire room. Merge tags supported.

highlight boolean
Should the message be highlighted. 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.

Bulk Add / Predefined Choices

Custom ChoicesChoices with Label and ValuePredefined Choices

When using a field with Choices (Drop Down, Multi Select, Checkboxes, or Radio Buttons) clicking the Bulk Add / Predefined Choices in General Settings allows you to select a category and customize the predefined choices or paste your own list to bulk add choices. Choices must be separated by a single line break.

Custom Choices

With GF v1.6, it is now possible to create a set of choices and save them as a Custom Choices option.

Note: Custom Choices are saved per form and are not available across the entire site.

Enter your custom choices in the writable textarea in the Bulk Add modal window.When your custom choices are complete, click the 「Save as new custom choice」 text below the writable textarea.An input will slide down. Use this input to specify a name for your custom choice and click the 「Save」 button.

You can update your custom choice by selecting your custom choice from the 「Custom Choices」 list above the 「Predefined Choices」 list. Make any modifications to the options and then click the 「Update」 button. To delete your custom choice, follow the same steps but instead of clicking 「Update」, click 「Delete」.

Choices with Label and Value

When creating custom choices, you can save options with labels and values by using the pipe character ( | ) to separate them.

Label|ValueIf the 「show values」 setting is enabled on the field and the choices will have values that are different from the label, define each choice label and value pair using the pipe character as the separator, e.g. First|1.Label|Value|:$PriceIf it is a pricing field and you want to define the choice label, value, and price, use the pipe to separate the label and value and then a pipe and colon to separate the value and price, e.g. First|1|:$20.00.

Predefined Choices

CountriesU.S. StatesCanadian Province/TerritoryContinentsGenderAgeMarital StatusEmploymentJob TypeIndustryIncomeEducationDays of the WeekMonths of the YearHow OftenHow LongSatisfactionImportanceAgreementComparisonWould YouSize

CAPTCHA Field CSS Selectors

reCAPTCHAContainerReally Simple CAPTCHAContainerImageInput Field

reCAPTCHA
Container
Third party markup inserted dynamically – contains the ReCaptcha form fields

example: ReCaptcha container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .recaptcha_widget_div .recaptcha_area {border: 1px solid red}

example: ReCaptcha container (div) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .recaptcha_widget_div .recaptcha_area {border: 1px solid red}

Really Simple CAPTCHA
Container
Wraps the captcha images and form elements

example: captcha container (div) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_captcha_container {border: 1px solid red}

example: captcha container (div) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_captcha_container {border: 1px solid red}

Image

example: captcha image (img) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_captcha_container .gfield_captcha {border: 1px solid red}

example: captcha image (img) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_captcha_container .gfield_captcha {border: 1px solid red}

Input Field

example: captcha input field (input) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_captcha_container .gfield_captcha_input_container input {border: 1px solid red}

example: captcha input field (input) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_captcha_container .gfield_captcha_input_container input {border: 1px solid red}

Cancel a Stripe Subscription After a Specified Number of Payments

The Stripe API doesn』t allow you to set the total number of recurrences of a payment when creating the subscription but it is possible to cancel the subscription via the gform_post_add_subscription_payment hook which runs after a payment is recorded.
The Stripe API now supports specifying an end date for when subscriptions should automatically cancel, this can be set using the gform_stripe_subscription_params_pre_update_customer filter.
Note: If you delete the entry associated to the subscription this snippet will not work.
123456789101112131415161718192021add_action( 'gform_post_add_subscription_payment', function ( $entry ) {    gf_stripe()->log_debug( "Running..." );     if ( rgar( $entry, 'payment_status' ) == 'Active' ) {        $feed       = gf_stripe()->get_payment_feed( $entry );        $feed_name  = rgars( $feed, 'meta/feedName' );        $feed_names = array( 'feed name one', 'feed name two' ); // update this line         if ( in_array( $feed_name, $feed_names ) ) {            gf_stripe()->log_debug( 'Feed: ' . $feed_name . 'Entry: ' . $entry['id'] );             global $wpdb;            $count = $wpdb->get_var( $wpdb->prepare( "SELECT count(id) FROM {$wpdb->prefix}gf_addon_payment_transaction WHERE lead_id=%d", $entry['id'] ) );             if ( $count >= 3 ) { // Update this line to the Total number of payments including the first one.                $result = gf_stripe()->cancel( $entry, $feed );                gf_stripe()->log_debug( "gform_post_add_subscription_payment: Cancelling subscription (feed #{$feed['id']} - {$feed_name}) for entry #{$entry['id']}. Result: " . print_r( $result, 1 ) );            }        }    }} );
The code snippet would go in your theme functions.php file.
The gform_post_add_subscription_payment is an action hook which is called after the Stripe webhook notifies your site that a payment has been made for the subscription and the add-on has recorded the transaction and added a note to the entry.
Because it runs for all forms with a subscription feed we need to tell it only to run for the correct feed, we do this by specifying the feed names in the array on this line:
1$feed_names = array( 'feed name one', 'feed name two' );
You would then update the following line with the number of payments you want to allow:
1if ( $count >= 3 ) {
If the count retrieved from the database query matches the value you specify the cancel method will be called which will notify Stripe that the subscription for that customer should be canceled.
Stripe will then notify your site when that action has been completed and the status on the entry will update to canceled and a note will be added indicating the date it was canceled.