GetResponse Change Log

GetResponse Change Log

1.6 | 2021-05-061.5 | 2020-09-031.4 | 2020-03-191.3 | 2020-01-221.2 | 2018-04-021.1 | 2016-08-311.0 | 2015-05-14

1.6 | 2021-05-06

Added additional logging information for update and create contact API requests.
Fixed an issue where the add-on icon is missing on the Form Settings page for Gravity Forms 2.5.
Fixed an issue where contact is not created when Preventing IP Address Storage is enabled under Personal Data settings.

1.5 | 2020-09-03

Added support for Gravity Forms 2.5.
Added the gform_getresponse_limit_pre_get_custom_fields filter allowing the maximum number of custom fields which are retrieved to be overridden.
Added support for MAX (360/Enterprise) accounts using the .pl endpoint.
Fixed an issue where values are not added to a multi_select type custom field when multiple choices are selected for the Multi Select field.

1.4 | 2020-03-19

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added the gform_getresponse_contact filter.
Fixed a PHP 7.4 notice which occur when the API is initializing and the settings are empty.

1.3 | 2020-01-22

Added support for GetResponse API version 3.
Added support for GetResponse Enterprise.
Updated labels on the add-on settings page to reflect current GetResponse account types.

1.2 | 2018-04-02

Added security enhancements.
Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.
Fixed strings for translations.

1.1 | 2016-08-31

Added feed duplication support.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Added gf_getresponse() for easily getting a GetResponse instance.
Added Spanish (es_ES) translation.
Updated feed processing to abort if email is empty or invalid.
Fixed fatal error when GetResponse API is loaded by another plugin.

1.0 | 2015-05-14

It's all new!

General Tab

General Tab

IntroductionSettingsSource Code

Introduction
The following settings are available for use on a field』s General tab. The gform_field_standard_settings hook can also be used to add custom settings at the positions indicated below.
Settings can be enabled for a field which extends the GF_Field class by overriding the get_form_editor_field_settings() method.
Settings

Position: 0

label_setting
The Field Label setting allows the user to define a label for the field.

Position: 10

description_setting
The Description setting allows the user to define the field description.

Position: 20

product_field_setting
The Product Field Mapping setting allows the user to select which Product field the current Option field is associated with.

Position: 25

product_field_type_setting
The Field Type setting allowing the product field to be set to a specific type: Single Product, Drop Down, Radio Buttons, User Defined Price, Hidden, or Calculation.

Position: 37

shipping_field_type_setting
The Field Type setting allowing the Shipping field to be set to a specific type: Single Method, Drop Down, Radio Button.

Position: 50

base_price_setting
The Price setting allows the user to specify the product』s base price.

Position: 75

disable_quantity_setting
The Disable quantity field setting allows the user to remove the quantity input from the field displayed on the front-end. A default value of 1 will be used, unless a separate Quantity field is added.

Position: 100

option_field_type_setting
The Field Type setting allowing the Option field to be set to a specific type: Drop Down, Checkboxes, or Radio Buttons.

Position: 125

donation_field_type_setting – Deprecated
The Field Type setting allowing the donation field to be set to a specific type: Drop Down, Radio Buttons, or User Defined Price.

Position: 150

quantity_field_type_setting
The Field Type setting allowing the quantity field to be set to a specific type: Number, Drop Down, or Hidden.

Position: 200

content_setting
The Content setting allows the user to enter HTML or text to be displayed for the field.

Position: 225

next_button_setting
The Next Button settings allow different button text or a custom image to be used for the button.

Position: 237

previous_button_setting
The Previous Button settings allow different button text or a custom image to be used for the button.

Position: 250

disable_margins_setting
The Disable default margins setting allows the content margins to be set to align the content with other fields.

Position: 300

post_custom_field_type_setting
The Field Type setting allowing the Post Custom field to be set to a specific type: Single line text, Paragraph Text, Drop Down, Multi Select, Number, Checkboxes, Radio Buttons, Hidden, Date, Time, Phone, Website, Email, File Upload, or List.

Position: 350

post_tag_type_setting
The Field Type setting allowing the Post tags field to be set to a specific type: Single line text, Drop Down, Checkboxes, or Radio Buttons.

Position: 400

captcha_type_setting
The Type setting allowing the Captcha field to be set to a specific type: reCAPTCHA, Really Simple CAPTCHA, or Math Challenge.

Position: 450

captcha_size_setting
The Size setting allowing the Captcha field size to be set to Small, Medium, or Large.

Position: 500

captcha_fg_setting
The Font Color setting allowing the Captcha fields font colour to be configured using a color picker or by entering the hex code.

Position: 550

captcha_bg_setting
The Background Color setting allowing the Captcha fields background colour to be configured using a color picker or by entering the hex code.

Position: 600

captcha_theme_setting
The Theme setting allow the Captcha fields theme to be set to light or dark.

Position: 650

post_custom_field_setting
The Custom Field Name setting allowing the user to specify which custom field the submitted value should be stored in.

Position: 700

post_status_setting
The Post Status setting allowing the user to specify what status the post created from the form submission should be assigned: Draft, Pending Review, or Published.

Position: 750

post_author_setting
The Default Post Author setting which determines which user should be set as the post author.

Position: 775

post_format_setting
The Post Format setting which can be used to specify which post format will be used for the post that is created by the form entry.

Position: 800

post_category_setting
The Post Category setting used to define which category the post created from the form submission should be assigned to.

Position: 825

post_category_field_type_setting
The Field Type setting allowing the Post Category field to be set to a specific type: Drop Down, Checkboxes, Radio Buttons, or Multi Select.

Position: 850

post_category_checkbox_setting
The Category setting defines which categories are available for selection by the user. They can choose to display all of them or select individual ones.

Position: 875

post_category_initial_item_setting
The Display placeholder settings enables a placeholder to be configured for the Post Category field.

Position: 900

post_content_template_setting
The Create content template setting provides a way for a template to be defined for the post content.

Position: 950

post_title_template_setting
The Create content template setting provides a way for a template to be defined for the post title.

Position: 975

customfield_content_template_setting
The Create content template setting provides a way for a template to be defined for the post custom field.

Position: 1000

post_image_setting
The Image Metadata settings are used to enable inputs for the image title, caption and description on the Post Image field.

Position: 1025

post_image_featured_image
The Set as Featured Image setting allows the file uploaded via the Post Image field to be set as the post』s featured image.

Position: 1050

address_setting
This includes the Address Type setting, input sub-labels, the ability to show/hide the individual inputs, Default Country (if International type is chosen), Default State (if United States is chosen), Default Province (if Canadian is chosen).

Position: 1100

name_format_setting – Deprecated
The Name Format setting provides the ability to change the Name field configuration from advanced to extended.

Position: 1125

name_setting
The Name Fields settings allow the individual field inputs to be enabled/disabled and the sub-labels configured.

Position: 1150

date_input_type_setting
The Date Input Type setting provides a drop down allowing the field to be configured as Date Field, Date Picker, or Date Drop Down.

Position: 1200

date_format_setting
The Date Format setting provides a list of available date formats from which to choose.

Position: 1225

customize_inputs_setting
The Customize Fields settings provide a way to customize the input sub-labels and enabled/disable the inputs.

Position: 1250

file_extensions_setting
The Allowed file extensions setting allows the file extensions which can be uploaded via the file upload field to be restricted.

Position: 1260

multiple_files_setting
The Enable Multi-File Upload setting determines if the field should use a single file type input or if the plupload scripts should be used to enable multiple files to be uploaded. When enabled you will also be able to limit the number of files which can be uploaded using the field.

Position: 1267

file_size_setting
The Maximum File Size setting enables the size of files uploaded using the File Upload field to be limited.

Position: 1275

columns_setting
The Enable multiple columns setting is used with the List field to allow multiple columns to be configured instead of the default single column.

Position: 1287

maxrows_setting
The Maximum Rows setting enables the number of rows the user can dynamically add to the front-end List field to be limited.

Position: 1300

time_format_setting
The Time Format setting allows the field to be set to use the 12 or 24 hour format.

Position: 1325

phone_format_setting
The Phone Format setting allows the Phone field format to be configured. The default formats are (###) ###-#### (standard) and International. The gform_phone_formats filter can be used to add additional formats.

Position: 1350

choices_setting
This setting allows you to customize the fields available choices, their values and if relevant their prices. It also allows you to choose from a predefined set of data. Without this section, the field is limited to the default choices of 「First Choice」, 「Second Choice」 and 「Third Choice」.

Position: 1362

other_choice_setting
The Enable 「other」 choice setting can be used to add a final choice to the radio button field with a text input allowing the user to enter their own custom choice text.

Position: 1368

email_confirm_setting
The Enable Email Confirmation setting allows a second email input to be displayed for confirmation, and also allows custom labels to be configured for each input.

Position: 1375

password_strength_setting
The Enable Password Strength setting enables a drop down to be displayed allowing the password fields minimum strength to be set.

Position: 1387

The Password fields Minimum Strength drop down will be located here.

Position: 1400

number_format_setting
The Number Format setting provides a drop down allowing the format to be set to decimal_dot, decimal_comma, or currency.

Position: 1415

sub_labels_setting
The Sub-Labels setting enables the labels for the fields individual inputs to be configured.

Position: 1425

Position: 1430

credit_card_setting
The Supported Credit Cards setting provides checkboxes for each of the available credit card types allowing the field validation to be configured to only allow certain types.

Position: 1435

credit_card_style_setting
The Card Icon Style setting provides a drop down allowing the icon style to be set to use the standard icons or the 3D icons.

Position: 1440

input_mask_setting
The Input Mask setting allows you to provide a visual guide allowing users to more easily enter data in a specific format such as dates and phone numbers.

Position: 1450

maxlen_setting
The Maximum Characters setting allows you to limit the maximum number of characters which can be entered in a text input or textarea.

Position: 1500

range_setting
The Range setting provides inputs allowing the minimum and maximum values for a number field to be defined.

Position: 1550

calculation_setting
This setting provides a way to enable calculation support for the field and the calculation formula to be defined.

Position: 1600

rules_setting
The Rules settings allow the field to be set as required and the duplicate_setting to be made available.

duplicate_setting
The No Duplicates setting allows the no duplicates validation to be enabled for the field.

Position: -1

Source Code
The above settings are located in GFFormDetail::forms_page() in form_detail.php.

GetResponse Feed Meta

GetResponse Feed Meta

IntroductionUsagePropertiesCustom Field Properties

Introduction
The Feed Object meta for the GetResponse 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',
'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.

campaign string
The ID of the GetResponse campaign this feed will add the contact to.

fields_name string
The ID of the form field containing the contact name.

fields_email string
The ID of the form field containing the contact email.

custom_fields array
A multidimensional array containing the GetResponse custom fields. 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' => 'address_one',
'value' => '3.1',
)

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

key string
The GetResponse custom field name. Custom field names can only contain up to 32 lowercase alphanumeric characters and underscores.

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

Common Questions About Gravity Forms

Common Questions About Gravity Forms

What is Gravity Forms?What are the requirements to run Gravity Forms?Where can I get custom development?Do you have a trial version?How can I submit a feature request? When will you have feature X?Where do I put custom CSS and PHP?Does Gravity Forms work properly on Microsoft Internet Explorer?Will Gravity Forms work with my Theme?

What is Gravity Forms?
Gravity Forms is a plugin for WordPress. It allows you to quickly create data collection forms, polls and surveys for your WordPress website. This article explains more, or refer to our home page.
What are the requirements to run Gravity Forms?
Refer to this article.
Please note: If your site is hosted by the WordPress.com service you will need to be on their Business plan, with a custom domain configured and the Hello Dolly plugin installed, before they will allow you to install Gravity Forms.
Where can I get custom development?
Check out this article.
Do you have a trial version?
We do not have any trial version, but we do offer the following resources to help interested prospective purchasers:
– full user documentation
– a fully-functioning online demo
– reviewable Terms of Service
– a talented team of Support Engineers via our contact us form.
How can I submit a feature request? When will you have feature X?
We have a selection of proposed features that are either open for comment or voting to all active Gravity Forms license holders. Go to Gravity Forms Support page, and then choose 「View Our Roadmap」 to navigate to the Feature Roadmap page.
You can vote or comment on ideas listed there, or raise your own request via the (+) button at the bottom right.
Where do I put custom CSS and PHP?
Custom CSS rules for your forms belong at the end of your theme stylesheet. Action hooks and filters belong in your theme』s functions.php file. You can find more information in the documentation section here: https://docs.gravityforms.com/page/Where-Do-I-Put-This-Code
Does Gravity Forms work properly on Microsoft Internet Explorer?
Browser support for viewing WordPress pages is covered here. Internet Explorer will be no longer supported by Microsoft in 2021, and we will stop testing core and add-on updates on IE11 at that time.
Will Gravity Forms work with my Theme?
We can』t ensure that Gravity Forms will work with all available themes for WordPress. We code Gravity Forms using WordPress best practices and can ensure that Gravity Forms works with the latest Twenty * themes (Twenty Nineteen, Twenty Twenty, etc.) from Automattic.
Any theme which follows WordPress best practices should be fine. However, if there is an issue when using Gravity Forms with your theme, we will ask you to activate a default WordPress theme (one of the Twenty * themes) and see if the issue persists. If it does not, you will need to contact the author of your theme for troubleshooting.

Common Issues With Formatting

Common Issues With Formatting

Why aren』t my form styles being loaded properly?Why is my form showing up with list bullets?How do I align my form fields into columns?Why does the word 「none」 appear next to my form inputs in IE?

Why aren』t my form styles being loaded properly?
Most of the time this is due to embedding the form via the php function call directly into the theme files or into a third-party widget. When embedding the form via this method, you also have to manually enqueue the CSS and scripts required for the forms to display and function properly.
You can find more information on this topic in the documentation here:

Embedding a Form
gravity_form_enqueue_scripts

Why is my form showing up with list bullets?
This is usually due to the form inheriting styles from your theme. You can add the following CSS declaration to your theme stylesheet and it should remove the bullet styling plus any stray borders that appear on occasion.
body .gform_wrapper form .gform_body ul,
body .gform_wrapper form .gform_body ul li {
list-style-type: none !important;
list-style-image: none !important;
list-style: none !important;
background-image: none !important;
background: none !important;
padding: 0 !important;
margin: 0 !important;
border: none !important
}
body .gform_wrapper form .gform_body ul > li:before {
content: "";
}

How do I align my form fields into columns?
Gravity Forms includes several 「helper」 CSS classes we call CSS Ready Classes. They allow you to easily create column style layouts without having to write custom CSS rules.
You can find out more about these classes in the CSS Ready Classes article.
Why does the word 「none」 appear next to my form inputs in IE?
We have seen this several times and it has always been related to the usage of the DDBelatedPNG.js script. This script was designed to add transparent PNG image support for IE6. Both IE6 and the DDBelatedPNG script are at the end of life and therefore the script shouldn』t be necessary any longer. Removing the script reference from the page solves the issue.

Examples

Examples

Getting and Manipulating FormsGetting All FormsGetting a Single FormUpdating a FormGetting and Manipulating EntriesGetting All EntriesGetting a Single EntryUpdate an Entry

Getting and Manipulating Forms
Obtaining and updating information is a quite simple process when using the GFAPI class. Below, you will see example on how you can easily retrieve and modify forms using the Gravity Forms API.
Getting All Forms
You may want to simply get information on all forms within Gravity Forms. It can be done as simply as this:
123
This will store your results within the $form variable. To view information on your results, you may call something like this:
1var_dump( $forms );
If you were to do so, you will see something like this:
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677array(1) {  [0]=>  array(13) {    ["title"]=>    string(4) "Test"    ["description"]=>    string(0) ""    ["labelPlacement"]=>    string(9) "top_label"    ["descriptionPlacement"]=>    string(5) "below"    ["button"]=>    array(3) {      ["type"]=>      string(4) "text"      ["text"]=>      string(6) "Submit"      ["imageUrl"]=>      string(0) ""    }    ["fields"]=>    array(0) {    }    ["version"]=>    string(9) "1.9.11.15"    ["id"]=>    int(1)    ["notifications"]=>    array(1) {      ["55a3dddb74f59"]=>      array(7) {        ["id"]=>        string(13) "55a3dddb74f59"        ["to"]=>        string(13) "{admin_email}"        ["name"]=>        string(18) "Admin Notification"        ["event"]=>        string(15) "form_submission"        ["toType"]=>        string(5) "email"        ["subject"]=>        string(32) "New submission from {form_title}"        ["message"]=>        string(12) "{all_fields}"      }    }    ["confirmations"]=>    array(1) {      ["55a3dddb75292"]=>      array(8) {        ["id"]=>        string(13) "55a3dddb75292"        ["name"]=>        string(20) "Default Confirmation"        ["isDefault"]=>        bool(true)        ["type"]=>        string(7) "message"        ["message"]=>        string(64) "Thanks for contacting us! We will get in touch with you shortly."        ["url"]=>        string(0) ""        ["pageId"]=>        string(0) ""        ["queryString"]=>        string(0) ""      }    }    ["is_active"]=>    string(1) "1"    ["date_created"]=>    string(19) "2015-07-13 15:48:43"    ["is_trash"]=>    string(1) "0"  }}
As you can see above, the $forms variable contains an array with data on all forms within it. From here, you would be able to use that data as you need to. For example, if you wanted to display the title of the first form, you would do the following:
123
Getting a Single Form
Getting a single form is just as easy as getting all forms. Below is an example on doing so:
1234
To display the results of this, simply do the following:
1var_dump( $form );
This would show that the $form variable contains the following array:
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374array(13) {  ["title"]=>  string(4) "Test"  ["description"]=>  string(0) ""  ["labelPlacement"]=>  string(9) "top_label"  ["descriptionPlacement"]=>  string(5) "below"  ["button"]=>  array(3) {    ["type"]=>    string(4) "text"    ["text"]=>    string(6) "Submit"    ["imageUrl"]=>    string(0) ""  }  ["fields"]=>  array(0) {  }  ["version"]=>  string(9) "1.9.11.15"  ["id"]=>  int(1)  ["notifications"]=>  array(1) {    ["55a3dddb74f59"]=>    array(7) {      ["id"]=>      string(13) "55a3dddb74f59"      ["to"]=>      string(13) "{admin_email}"      ["name"]=>      string(18) "Admin Notification"      ["event"]=>      string(15) "form_submission"      ["toType"]=>      string(5) "email"      ["subject"]=>      string(32) "New submission from {form_title}"      ["message"]=>      string(12) "{all_fields}"    }  }  ["confirmations"]=>  array(1) {    ["55a3dddb75292"]=>    array(8) {      ["id"]=>      string(13) "55a3dddb75292"      ["name"]=>      string(20) "Default Confirmation"      ["isDefault"]=>      bool(true)      ["type"]=>      string(7) "message"      ["message"]=>      string(64) "Thanks for contacting us! We will get in touch with you shortly."      ["url"]=>      string(0) ""      ["pageId"]=>      string(0) ""      ["queryString"]=>      string(0) ""    }  }  ["is_active"]=>  string(1) "1"  ["date_created"]=>  string(19) "2015-07-13 15:48:43"  ["is_trash"]=>  string(1) "0"}
Updating a Form
If you want to update a form, you will first need to obtain the form object for that form, make the appropriate changes, then update that form. Your code would look something like this:
12345$form_id = '1';$form = GFAPI::get_form( $form_id );$form['title'] = 'New Title';$result = GFAPI::update_form( $form );return $result;
In the example above, we are defining the ID of the form that we want to update, then getting the form object for that form. Next, we define the new title for the form. We now will take the form object that we have modified, and call GFAPI::update_form, passing the new form object which will assign the result to the $result variable. Finally, we return the result.
Getting and Manipulating Entries
In addition to obtaining and editing forms, you may also do the same with entries when using the Gravity Forms API.
Getting All Entries
1234
In the above example, we are simply getting up to 20 entries for the specified form and assigning the array to the $entry variable. If you want to display the contents of this, you may do the following:
1var_dump( $entry );
Which would then output something similar to the following:
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263array(1) {  [0]=>  array(29) {    ["id"]=>    string(1) "1"    ["form_id"]=>    string(1) "1"    ["date_created"]=>    string(19) "2015-07-20 20:50:52"    ["is_starred"]=>    int(0)    ["is_read"]=>    int(0)    ["ip"]=>    string(12) "192.168.50.1"    ["source_url"]=>    string(48) "http://local.wordpress.dev/?gf_page=preview&id=1"    ["post_id"]=>    NULL    ["currency"]=>    string(3) "USD"    ["payment_status"]=>    NULL    ["payment_date"]=>    NULL    ["transaction_id"]=>    NULL    ["payment_amount"]=>    NULL    ["payment_method"]=>    NULL    ["is_fulfilled"]=>    NULL    ["created_by"]=>    string(1) "1"    ["transaction_type"]=>    NULL    ["user_agent"]=>    string(82) "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0"    ["status"]=>    string(6) "active"    [1]=>    string(13) "Testing Field"    [2]=>    string(13) "Second Choice"    ["3.1"]=>    string(12) "First Choice"    ["3.3"]=>    string(12) "Third Choice"    ["4.3"]=>    string(4) "John"    ["4.6"]=>    string(3) "Doe"    ["3.2"]=>    string(0) ""    ["4.2"]=>    string(0) ""    ["4.4"]=>    string(0) ""    ["4.8"]=>    string(0) ""  }}
If you want to return more than twenty entries you would need to specify a larger page_size in the $paging parameter, see the following for more detail: GFAPI::get_entries
Getting a Single Entry
Just as it is possible to get all entries using the Gravity Forms API, you may also obtain information on a single entry.
1234
In the example above, the results are stored within the $entry entry variable. If you would like to see the object contained within it, you may run the following:
1var_dump( $entry );
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960array(29) {  ["id"]=>  string(1) "1"  ["form_id"]=>  string(1) "1"  ["date_created"]=>  string(19) "2015-07-20 20:50:52"  ["is_starred"]=>  int(0)  ["is_read"]=>  int(0)  ["ip"]=>  string(12) "192.168.50.1"  ["source_url"]=>  string(48) "http://local.wordpress.dev/?gf_page=preview&id=1"  ["post_id"]=>  NULL  ["currency"]=>  string(3) "USD"  ["payment_status"]=>  NULL  ["payment_date"]=>  NULL  ["transaction_id"]=>  NULL  ["payment_amount"]=>  NULL  ["payment_method"]=>  NULL  ["is_fulfilled"]=>  NULL  ["created_by"]=>  string(1) "1"  ["transaction_type"]=>  NULL  ["user_agent"]=>  string(82) "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0"  ["status"]=>  string(6) "active"  [1]=>  string(13) "Testing Field"  [2]=>  string(13) "Second Choice"  ["3.1"]=>  string(12) "First Choice"  ["3.3"]=>  string(12) "Third Choice"  ["4.3"]=>  string(4) "John"  ["4.6"]=>  string(3) "Doe"  ["3.2"]=>  string(0) ""  ["4.2"]=>  string(0) ""  ["4.4"]=>  string(0) ""  ["4.8"]=>  string(0) ""}
From here, you can get any information that you want about the specified entry.
Update an Entry
To update an entry, you will need to first get that entry, replace your desired information, and then update it with the new information. This is done like so:
1234567
Within the code example above, we are defining the $entry_id as 1, and passing it to get_entry to get the entry with ID 1. Next, we are taking the results and modifying a part of the array. Finally, we are passing the modified array to update_entry, then returning the result.

Entry Creator Merge Tag

Entry Creator Merge Tag

SummarySinceUsageMeta Keys

Summary
The entry creator merge tag can be used in notifications, confirmations, and with some add-ons to output properties of the user whose ID is stored in the entry created_by property, usually the user who was logged in at the time the entry was saved. It cannot be used in field settings. To populate fields with the values of the currently logged in user use the User Merge Tag instead.
Since
Support for this merge tag was added in Gravity Forms 2.5. It was previously only available when using some add-ons from certified developers.
Usage
{created_by:[meta_key]}
Meta Keys
Any single user meta (including custom user meta) can be displayed with this merge tag by replacing [meta_key] with the specific meta_key for which you are wanting a value.
Below are a few examples of how this merge tag can be used.

Meta Key
Description
Usage

ID
Outputs the ID of the entry creator
{created_by:ID}

first_name
Outputs the first name of the entry creator
{created_by:first_name}

last_name
Outputs the last name of the entry creator
{created_by:last_name}

display_name
Outputs the display name of the entry creator
{created_by:display_name}

user_email
Outputs the email address of the entry creator
{created_by:user_email}

user_login
Outputs the username of the entry creator
{created_by:user_login}

[custom_key]
Outputs the value of the specified meta key
{created_by:preferred_contact_method}

Form Heading CSS Selectors

Form Heading CSS Selectors

ContainerTitleDescription

Container
Contains the form title and description

example: the form heading section (div) – applies to all forms
1body .gform_wrapper .gform_heading { border: 1px solid red }

example: the form heading section (div) – applies just to form ID #1
1body #gform_wrapper_1 .gform_heading { border: 1px solid red }

Title

example: the form title (h3) – applies to all forms
1body .gform_wrapper .gform_heading .gform_title { color: red }

example: the form title (h3) – applies just to form ID #1
1body #gform_wrapper_1 .gform_heading .gform_title { color: red }

Description

example: the form description (span) – applies to all forms
1body .gform_wrapper .gform_heading .gform_description { border: 1px solid red }

example: the form description (span) – applies just to form ID #1
1body #gform_wrapper_1 .gform_heading .gform_description { border: 1px solid red }

Field Select Field

Field Select Field

IntroductionExampleUses

Introduction
The field_select type field, part of the Settings API, allows the user to select a form field from a drop down.
Example
The following example shows a section with a field_select type field which has been limited to only include email type form fields.
array(
'title' => esc_html__( 'This is the title for Section 1', 'sometextdomain' ),
'fields' => array(
array(
'name' => 'email',
'label' => esc_html__( 'Email Field', 'sometextdomain' ),
'type' => 'field_select',
'required' => true,
'tooltip' => '

' . esc_html__( 'Email Field', 'sometextdomain' ) . '

' . esc_html__( 'Select which Gravity Form field will be used as the subscriber email.', 'sometextdomain' ),
'args' => array(
'input_types' => array( 'email' )
)
),
),
),

The code above will render a drop down similar to the following:

Uses

settings_field_select()
get_form_fields_as_choices()
settings_select()