Author 诗语

Canceling Recurring Subscriptions in Stripe

IntroductionStepsScreenshotsScreenshot A— Cancel Subscription buttonScreenshot B— Subscription status canceled

Introduction
When using recurring subscriptions with the Stripe Add-On, there are two ways to cancel a subscription. One option is from within your Stripe account, and the other from within the WordPress admin.
In this article, we will show you how to easily cancel a recurring subscription from within the WordPress admin.
Note: If you』d like to learn how to cancel subscriptions from within your Stripe account, please use this tutorial provided by Stripe.
Steps

Login to your WordPress admin dashboard.
Access the list of entries for your form by hovering over Forms on the left side menu and clicking on Entries. You should see a list of the entries collected by this form. If you do not see the entries you were expecting, make sure you are viewing the correct form. You can switch forms using the drop down on the top right of the page.
Click on the name of the entry to access it.
On the right side of the entry page, you should see a button labeled Cancel Subscription within the subscription details. Simply click it to cancel the recurring subscription. See screenshot A
The subscription status should now show as Canceled. See screenshot B.

If you have a Subscription Canceled notification configured, the customer will receive an email informing them that their subscription was been cancelled.
Screenshots
Screenshot A— Cancel Subscription button

Screenshot B— Subscription status canceled

Canceling Recurring Subscriptions

IntroductionStepsScreenshotsScreenshot A— Cancel Subscription buttonScreenshot B— Subscription status canceled

Introduction
When using recurring subscriptions within the Authorize.Net Add-On, the only way to cancel a subscription is from within the WordPress dashboard. In this article, we will show you how to easily cancel a recurring subscription.
Steps

Log into your WordPress admin dashboard.
Access the list of entries for your form by hovering over Forms on the left side menu and clicking on Entries. You should see a list of the entries collected by this form. If you do not see the entries you were expecting, make sure you are viewing the correct form. You can switch forms using the drop down on the top right of the page.
Click on the name of the entry to access it.
On the right side of the entry page, you should see a button labeled Cancel Subscription within the subscription details. Simply click it to cancel the recurring subscription. See screenshot A.
The subscription status should now show as Canceled. See screenshot B.

Screenshots
Screenshot A— Cancel Subscription button

Screenshot B— Subscription status canceled

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!

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.

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}

CAPTCHA

SummaryTypesPrerequisitesCommon SettingsGeneral SettingsThemeAdvanced SettingsMerge TagsHow To Add a Captcha Field to your Form

Summary

The CAPTCHA field allows you to add a captcha field to your form, to help protect your website from spam and bot abuse by trying to determine if the form is being submitted by a human, or defeating a form submission attempt by a scripted bot. The Gravity Forms Captcha field is available under the Advanced Fields section within the form editor.

CAPTCHA field as displayed in the Field Library

CAPTCHA field as displayed in the Form Editor.

Types

Gravity Forms supports Google』s free reCAPTCHA service. There are different types of reCaptcha, and the Gravity Forms CAPTCHA field supports:

reCAPTCHA v2 CheckboxreCAPTCHA v2 Invisible (introduced in Gravity Forms 2.4.7)

Gravity Forms also now supports reCAPTCHA v3 with the official Gravity Forms reCAPTCHA Add-On. Google』s v3 does not utilize a form field at all, so you do not need this field for v3 implementations.

In addition to reCAPTCHA, the plugin Really Simple CAPTCHA may also be installed and activated for use within Gravity Forms. If you have this plug-in installed, you will be offered the option to use this type of captcha.

Prerequisites

To communicate with the Google reCAPTCHA service of your choice, you will need a pair of API keys added to your settings. Refer to this guide for help obtaining your keys and entering them into your Gravity Forms settings.

Common Settings

This field uses only common field settings for the Appearance settings. For a description of each of the common field settings, refer to this article. Below you will find description of specialty settings that are particular to this field.

General Settings

Theme

This option is only available when using reCAPTCHA. Select the visual theme for the reCAPTCHA field from the Light and Dark options to better match your site design.

Advanced Settings

SettingDescriptionLanguageThis option is only available when using reCAPTCHA. Select the language you would like to use for the reCAPTCHA display from the available options.

Merge Tags

This field does not have any available merge tags.

How To Add a Captcha Field to your Form

Check out this excellent blog post on how to add a Captcha Field to your form and why it』s useful.

Capturing the HTTP Referrer URL on Form Submissions

IntroductionLimitationsSetupSnippetAlternative

Introduction
If you』re trying to determine what page caused a form submission to occur, sometimes obtaining the referrer URL can help. This article describes a method to do it.
Limitations
But before this, it』s important to understand the limitations. HTTP referrer is not always available, can be empty, and is influenced by the browser setup. To quote the official PHP page for $_SERVER variable on HTTP_REFERER:
「This is set by the user agent. Not all user agents will set this, and some provide the ability to modify HTTP_REFERER as a feature.In short, it cannot really be trusted.」
This means the server will pass to Gravity Forms the value stored in $_SERVER[『HTTP_REFERER』], and it can be empty, because the URL in this variable (if any) is provided by the browser, where privacy settings and extensions can prevent this information from being passed to the server. You can read more about this in the following Wikimedia』s article.
Caching is also a known cause of not receiving a proper value for $_SERVER[『HTTP_REFERER』].
So if you』re not getting any value after following the steps in this tutorial, please ensure your page is not being cached and contact with your host support to check if the server is really passing a value or not.
Setup

Create a hidden field on your form.
Add a label to it such as Referrer URL so that you』re able to keep track of it a bit easier.
Allow the field to be populated dynamically by accessing the advanced tab and enabling the checkbox.
Give it a parameter name. In this example, we』ll use refurl.

Snippet
After you have the initial setup completed, you』ll be able to use the following snippet to dynamically populate the field with the HTTP referrer URL when it』s available. Refer to this article for where to put your snippets.
add_filter( 'gform_field_value_refurl', 'populate_referral_url');

function populate_referral_url( $form ){
// Grab URL from HTTP Server Var and put it into a variable
$refurl = $_SERVER['HTTP_REFERER'];
GFCommon::log_debug( __METHOD__ . "(): HTTP_REFERER value returned by the server: {$refurl}" );

// Return that value to the form
return esc_url_raw($refurl);
}

After that, the hidden field will then be dynamically populated with the value from $_SERVER[『HTTP_REFERER』] provided by the server. Upon submission, the details will be sent with the submission.
Alternative
You can also use the {referer} merge tag as a default value for a hidden field on you form. Using the snippet approach though has the benefit of improved troubleshooting, as it includes a logging statement to capture the value being passed by the server.

Agile CRM Change Log

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!

Agile CRM Feed Meta

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.

Akismet Anti-Spam

Updates to the Akismet IntegrationMore Information

Updates to the Akismet Integration

Gravity Forms has included built-in support for the Akismet Anti-Spam plugin since version 1.6.

As of July 2021, the Akismet functionality is now provided within the official Gravity Forms Akismet Add-On.

When enabled all form submissions will be checked by Akismet. Submissions identified as spam by Akismet will have their entry status property set to spam preventing processing of notifications and add-ons.

More Information

Refer to the Akismet Add-On user guides for articles about setting up and using the Akismet Add-On.