Author 詩語

Adding Row Spans in the 2.5 Form Editor

IntroductionQuickstart GuideSetup the FieldsAdd a CSS Class to the Spanning FieldAdd a CSS Span Property to your ThemeWant to learn more about CSS Grid?

Introduction
The article shows you how to line up fields so that one column field takes up the same vertical space as a multiple fields in an adjacent column. Hard to describe, so let』s show a picture!

This technique is for Gravity Forms 2.5 and later only.
Quickstart Guide

Add a Name field and Textarea field side by side in the form.
Add an Email field and Phone field side by side in the form.
Add a Custom CSS class to the Textarea field under Field Settings > Appearance > Custom CSS ie gform-field-row--span-three
Save the Form and Add the form to your website.
Add the following CSS to your website:
.gform-field-row--span-three {
grid-row: span 3;
}

Setup the Fields
In our example, we are setting up a two column view, where the leftmost column will hold multiple fields, and the right most column will hold one field that takes up the same vertical space as the left column.
In the column editor, drag and drop side-by-side the first field for the leftmost column, and then the field that will end up spanning multiple rows on the right column. This will automatically set the width of those two fields to half the grid each.

In our example, that means adding a Name field and a Textarea field side-by-side in the editor
Next, drag and drop side-by-side the two fields that will eventually fill the rest of the leftmost column. Putting them next to each other in columns will ensure they are half-width each. They will be 「reflowed」 into the left column with some CSS later.

In our example, this is adding an Email field and a Phone field side-by-side in the row below the first two fields.
Add a CSS Class to the Spanning Field
To bring the fields into the alignment we desire, you will need to add a custom CSS style to the field, and then set some properties for it in your theme file.
Taking advantage of the Custom CSS Class settings, go into the Textarea field in the form and select it to then click the tab for Appearance. This will reveal the Custom CSS Class setting 1. In this field, add a CSS Class name that you will remember. For example, span-three-rows or row-span-three or gform-field-row--span-three. It is up to you, just remember what you chose for later.

In our example, we will use gform-field-row--span-three, adding it to the Custom CSS for the Textarea field under Field Settings, Appearance, Custom CSS Class. Save the form.
Add a CSS Span Property to your Theme
Now that we have named the element, we need to tell the Theme file how to treat it, in this case specifically using the span property. The easiest way will be to add this to the Customizer in Theme Options. There are other ways to add CSS to your theme. The following line is what you will add to your Theme』s CSS:
.gform-field-row--span-three {
grid-row: span 3;
}

Here』s how this works: the .gform-field-row--span-three identifies the class and makes the action specific to any objects with that class. The grid-row is a CSS Grid property, and the span 3 is telling the CSS to span 3 grid rows for any object with the class gform-field-row--span-three. Simple!

Add the CSS snippet above to the Additional CSS section of the Customizer.
NOTE: We added an extra CSS property to correct the spacing of the fields in our theme. In this case, our theme was adding specific CSS to target the .gfield class. We corrected that by making it consistent throughout the theme at 1em bottom margin for all fields. You might not need to do this as each theme will supply their own styling to the forms.
Want to learn more about CSS Grid?
If you』d like to learn more about CSS Grid and how Gravity Forms is using it in version 2.5, check out these articles:

Official Documentation for CSS Grid
Comprehensive Guide to Grid by CSS Tricks

An alternative to using Custom CSS Class Settings is to inspect your form after configuring and putting it into a page, and then seeing what the field id is for the Textarea field so you can specifically target just that field with your CSS.

Accessibility Checklist for Gravity Forms

IntroductionLimitationsYour WordPress ThemeGeneral SettingsForm SettingsForm Fields To AvoidField SettingsGeneralAppearanceAdvancedAdding a form to a page

Introduction

What steps do I need to take to create an accessible form with Gravity Forms? 

This questions can seem daunting when you are starting work on your project. The good news is that Gravity Forms is built to comply with WCAG 2.1 AA, the global standard for web accessibility. This article takes you through a number of the settings and form fields to help educate you as to what to use (and what to avoid) to move your particular form towards the best possible outcome for all users.

This is a checklist, written as a short and easy to use way check your forms. If you want to know about the 「why」, please read the accessibility documentation in the Knowledge Base.

Limitations

This checklist is an aid to help you get your form as accessible as possible, but it is not a guarantee.

There are a number of external factors that can affect accessibility, and some areas of accessibility research differ in their views of exactly what is needed, but this article will help you lock down some of the most common settings and options that can affect accessibility. If you have strict compliance requirements, we recommend you bolster the knowledge provided in our documentation with the expertise of an accessibility consultant or advisor. That』s what we did!

Additionally, note that form elements from plug-ins are not included in this checklist, such as those added by the Gravity Forms payment add-ons.This checklist was written for Gravity Forms 2.5, and we will look to periodically update it when there are accessibility improvements or changes in the forms.

Your WordPress Theme

First a word about the WordPress theme you are using. The color contrast between the text and the background is important. Your visitors must be able to read the content in a form. 

Gravity Forms ships with it』s own stylesheet (CSS). The color contrast is optimised for a white background color, but your theme may have a darker background color that makes text unreadable when you use the Gravity Forms stylesheet. Check the color contrast ratio between the text and it』s background. It is recommended that ratio be 4.5:1 or higher.

Don』t disable the whole stylesheet only for the color contrast. Remember that the CSS also controls the look and feel of the form elements and the way error messages are displayed, which can also affect accessibility. 

Depending on your theme, it may be possible to adjust or overrule some of the CSS using the customizer, or in the CSS of your theme. If needed, discuss options with your site developer or contact the theme provider for advice.

General Settings

Go to the Gravity Forms settings page under Dashboard > Settings and set:

Output Default CSS: 「On」.Output HTML5: 「On」.

Form Settings

For a newly created form, go to the Form Settings tab and check the following settings that are important for accessibility:

Label Placement: 「Top aligned」Sub-Label Placement: 「Above Inputs」.Validation Summary: 「On」.Required Field Indicator: Ensure the option to show a required field indicator is selected.Form button: Choose 「Text」. Use descriptive text.Form button Conditional Logic: Do not enable conditional logicEnable legacy markup: 「Off」.

Form Fields To Avoid

The following field types can create accessibility issues, and are not recommended for use in an accessible form.

MultiselectHTML blocks with text that contains essential informationSection breaks with text that contains essential informationreCAPTCHA V2 (an accessible alternative is the honeypot option, as can be found in the form settings).

Field Settings

The form fields settings can be found in the right hand sidebar when you create or edit a form. If a setting is not mentioned here, it has no known accessibility issues. 

General

Field Label: always fill out the Field label, explain clearly to the user what needs to be filled out.Input mask: do not use an input mask. Leave that box unchecked.

Appearance

Field Label Visibility: always use a visible label, never hide it.Sub-Label Placement: above input.Custom Validation message: if possible, write meaningful to-the-point custom error messages. Enhanced User Interface: do not enable the enhanced User Interface for dropdowns.Multi-File Upload: do not enable Multi-File Upload with the File Upload field. Using single file upload is ok.

Advanced

Rich text Editor: Do not enable the Rich text editor.Autocomplete: Enable autocomplete for name, address and email fields. The default fields for these fields have the autocomplete values already filled out. 

Adding a form to a page

Add the block for a form to the page and select the block settings:

Form settings: enable the Form Title.Advanced settings: do not set a positive tabindex. Keep the tabindex value -1. This means that no tabindex will be set.Do not add more than one of the same form to a web page. Each form on the page must be unique.

Adding a Form Using a Template (or Saved) File

One of the quickest ways to get a form up and running is to import a completed form from a saved/exported form file. From there you can use it as is, or even modify it for any special requirements you have.
Check out these resources:
1. Our help guide to show you how to import a form file.
2. This helpful page full of templates contains a list of common pre-built forms we have put together to satisfy many common uses. You can download them as a JSON file and import them to your own site.
3. If you want to export your own form (for example, to save a backup or migrate it to another site), follow this guide.

gform_updates

DescriptionUsageParametersExamplesSource Code

Description
Triggered after the display of the update or invalid key notice for Gravity Forms.
Usage
1add_action( 'gform_updates', 'my_function', 10, 0 );

Parameters
There are not any parameters available for this action.

Examples
1234function my_function() {    //Do something here}add_action( 'gform_updates', 'my_function', 10, 0 );
Source Code
This action hook is located in update.php.

Advanced Tab

IntroductionSettingsSource Code

Introduction
The following settings are available for use on a field』s Advanced tab. The gform_field_advanced_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

admin_label_setting
The Admin Field Label setting allows the user to define an admin label for the field.

Position: 25

Position: 35

Position: 50

Position: 100

Position: 125

default_value_setting
The Default Value setting allows a default value to be defined for the field using a text input.

Position: 150

default_value_textarea_setting
The Default Value setting allows a default value to be defined for the field using a textarea.

Position: 155

name_prefix_choices_setting
The Prefix Choices setting allows the choices for the Name field prefix input to be customized.

Position: 175

default_input_values_setting
The Default Value setting allowing default values of the field inputs to be defined.

Position: 185

copy_values_option
This setting provides the ability to allow the user to use the values they entered into another address field to populate the current field during form submission. Example: Copying Billing Address to the Mailing Address field.

Position: 200

Position: 225

Position: 250

captcha_language_setting
The Language setting provides a drop down allowing the reCaptcha language to be set.

Position: 300

Position: 325

add_icon_url_setting
The Add Icon URL setting allows an image URL to be defined for use with the List field add row button.

Position: 337

delete_icon_url_setting
The Delete Icon URL setting allows an image URL to be defined for use with the List field delete row button.

Position: 350

password_field_setting
The Enable Password Input setting configures the field to use a password type input.

Position: 375

force_ssl_field_setting
Includes a Force SSL setting which allows the page containing the form to be forced to be secure when this field exists.

Position: 400

visibility_setting
The Visibility settings allow the field to be displayed on the front-end form or only on the entry detail page when editing the entry.

Position: 425

rich_text_editor_setting
Provides a Use the Rich Text Editor setting allowing the RTE to be enabled for the Paragraph and Post Body fields.

Position: 450

prepopulate_field_setting
This setting allows dynamic population to be enabled for the field and parameter names to be configured for the relevant field inputs.

Position: 500

conditional_logic_field_setting
This setting allows conditional logic to be enabled for the field and the individual rules to be defined.

Position: 525

conditional_logic_page_setting
This setting allows conditional logic to be enabled for the page and the individual rules to be defined.

Position: 550

conditional_logic_nextbutton_setting
This setting allows conditional logic to be enabled for the next button and the individual rules to be defined.

Position: -1

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

ActiveCampaign Change Log

1.9.11.9 | 2021-05-131.8 | 2020-09-071.7 | 2020-03-111.61.51.41.3.11.31.21.1.21.1.11.11.0

1.9.1

Updated the API auth test so the existing gform_activecampaign_request_timeout filter can be used to increase the request timeout period.
Fixed an issue where the add-on log uses the "Invalid API URL" message for request failures of any kind.

1.9 | 2021-05-13

Fixed an issue that causes the plugin settings to always show the API URL and Key as invalid even when they are correct.

1.8 | 2020-09-07

Added support for Gravity Forms 2.5.

1.7 | 2020-03-11

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Fix PHP notices thrown on the feed list and edit page in PHP 7.4.

1.6

Added support for adding notes to contacts.
Updated feed settings with improvements to user experience.
Fixed issue where field values hidden by conditional logic were overriding visible values when mapped to the same Active Campaign field.

1.5

Added filter to prevent mapped, blank fields from overriding existing data.
Example:
add_filter( 'gform_activecampaign_override_empty_fields', '__return_true' );
Added filter do allow different field types to be mapped to Active Campaign's email field.
Example:
add_filter( 'gform_activecampaign_supported_field_types_email_map', function( $field_types ) {
return array( 'email', 'hidden', 'text' );
});
Added filter to change the timeout value when sending requests to Active Campaign and updated default value to 20 seconds.
Example:
add_filter( 'gform_activecampaign_request_timeout', function(){ return 30; //Changes timeout to 30 seconds } );
Added security enhancements.
Added GPL to plugin header.
Updated feed setting styles.
Updated Plugin URI and Author URI to use https.
Updated feed list to prevent feed creation when valid API URL is not provided.
Fixed issue where non-mapped fields would override existing data with blank values.
Fixed strings for translations.
Fixed PHP notice when editing a feed when no ActiveCampaign forms are available.

1.4

Added the gform_activecampaign_contact_pre_sync filter for overriding the contact properties before sending them to ActiveCampaign.
Added feed duplication support.
Updated API library naming to prevent conflicts with third-party ActiveCampaign API libraries.
Fixed an issue with the request failed message if a WP_Error occurs.

1.3.1

Fixed PHP warning related to Double Opt-In Form setting.

1.3

Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Updated 'Opt-In Condition' setting label to 'Conditional Logic'.
Updated admin stylesheet to use minified file by default unless SCRIPT_DEBUG is active or query param gform_debug is set, e.g. domain.com/?gform_debug.

1.2

Added merge tags support for contact tags.
Added the gform_activecampaign_tags filter.
Removed the gform_activecampaign_enable_tag_mapping filter, the tags setting is now permanently displayed.

1.1.2

Added additional logging statement to process_feed().
Updated the form field drop down for the Email Address to include hidden fields.
Updated feed processing to abort if value of mapped Email Address field is invalid or empty.

1.1.1

Added gf_activecampaign() for easily getting an ActiveCampaign instance.
Fixed PHP warnings during feed processing.

1.1

Added Double Opt-In support.
Added Spanish (es_ES) translation.

1.0

It's all new!

Adding/Removing Countries From the Country Select Field

Removing a CountryAdding a Country

In some instances, you may need to add or remove a particular country to or from the country selection field in Gravity Forms. Here』s how to do it.

Doing so will require using a filter within your code. This code would be placed within your theme』s functions.php file, or ideally, within it』s own plugin.

Removing a Country

add_filter( 'gform_countries', 'remove_country' );
function remove_country( $countries ) {
$key = array_search( 'United States', $countries );
unset( $countries[ $key ] );
return $countries;
}

As you can see from the above snippet, the _gform_countries_ filter is being called, and replacing the default information with the return value of the remove_country function.

Adding a Country

add_filter( 'gform_countries', 'add_country' );
function add_country( $countries ) {
$countries[] = 'Custom Country';
sort( $countries );
return $countries;
}

In this example, the _gform_countries_ filter is being called, and replacing the default information with the add_country function, which is adding an additional country to the array. From here, we then sort the listing, and return the $countries array.

Accessibility Guide for Content Providers

IntroductionWhy should you make your form accessible? And what is Web Accessibility?About Guidelines and Legal ImplicationsSettings for Optimal AccessibilityGeneral SettingsForm SettingsAdding Form Block to a PageLabels, Placeholders and DescriptionsWhy?ExamplesTabindexUse of ColorHTML Blocks and Section BreaksAbout NamingGive Users an Idea About What to ExpectreCAPTCHAsForm ValidationWhat is Required?Custom Validation MessagesRecommended Resources

Introduction
With Gravity Forms you have a great tool to create accessible web forms. In this documentation we want to help you:

Set up a form with accessibility in mind.
What to look out for to safeguard the accessibility of your forms.

To help you make your forms work for as many people as possible, we give you guidelines and best practices on this page. Please read our Accessibility Checklist for Gravity Forms.

Why should you make your form accessible? And what is Web Accessibility?
With form accessibility we mean that a form is usable by as many people as possible, on as many different devices as possible.
Like:

A web developer who uses a desktop computer, keyboard and a mouse.
A blind woman who uses a desktop computer, keyboard and a screen reader.
A blind and deaf user, who uses a desktop computer, keyboard, a screen reader and a braille display.
A traveler who uses a smartphone in the train with slow WiFi.
An elderly person, who uses an iPad in bright sunlight.
A child that broke her arm and uses only the keyboard.

You can come up with a lot of ways to use the internet. The W3C listed a few user personas.
As for disabled people: the estimate is that approximately 20% of all people have some sort of disability. That』s 20% of your form users. And as the population is growing older, this number will increase.
We are all different and situations differ too. It』s not only disabled people that use the web differently than you may expect. If you make your forms accessible, all users will benefit.
To help you make your forms work for as many people as possible, we give you guidelines and best practices on this page.
If you are a theme or plugin developer, please also check the Developers Documentation on Form Accessibility.
About Guidelines and Legal Implications
For Gravity Forms we follow the global guidelines for web accessibility: the Web Content Accessibility Guidelines, version 2.1, level AA (WCAG 2.1 AA). Some countries have WCAG 2.0 AA as legal requirement or have a special set of guidelines. If you want to know which guidelines and legal regulations apply for your country and for your type of website, please consult with your government. The W3C maintains a list of regulations per country: Web Accessibility Laws & Policies.
Settings for Optimal Accessibility
General Settings
After installing go to the Forms > Settings page and set:

Output HTML5: 「On」.
Output Default CSS: 「On」.

Form Settings
After creating a new form, go to the Settings, Form Settings and set:

Label Placement: 「Top aligned
Sub-Label Placement: 「Above Inputs」.
Validation Summary: 「On」.
Required Field Indicator: Do not remove the option to show a required field indicator.
Form Button > Input Type: Choose 「Text」.
Form Button > Button Text: Use descriptive text (see 「About Naming」).
Form Button > Conditional Logic: Do not enable conditional logic.
Form Options > Enable Legacy Markup: 「Off」.

Adding Form Block to a Page
When you add  the block for a form to a page, under the Block Settings set:

Form settings: Enable the Form Title.
Advanced settings: Do not set a positive tabindex. Keep the tabindex value -1. This means that no tabindex will be set.

Labels, Placeholders and Descriptions

A label tells the user what they need to fill out and must always be visible.
Place the label above or next to the input.
Keep a label about the input fields only, don』t put links or other HTML inside them.
The placeholder is used for a suggestion on how to fill out an input field.
The description can be used to give extra information about the input field.
The label should always be meaningful and visible. The placeholder and description are optional.

Why?

When the label is always visible, people don』t forget what they have to fill out.
When the form inputs are filled with autocomplete, the users can better check if the input is added to the right input field when the label stays visible.
People read from top to bottom. Placing a label below the input may cause confusion about which label belongs to which input.
When a user starts typing the placeholder disappears, so if the placeholder is used as the only label, the user can get confused on what to fill out.
If you use links inside a label, assistive technology, like a screen reader user may get confused about what to fill out, keep the label text to the point. Use the description to add extra information.
Gravity Forms makes sure that the description is also read out for people with a screen reader. Use that field to give extra information.

Examples
Label: Name
Placeholder: For example Jane Doe

Label: Date
Description: Please use format dd/mm/yyyy to enter the date.

Tabindex
Avoid using a positive tabindex on form controls.
Some users can』t use a mouse, for example because they are blind or don』t have fine motor skills. Then they can use the keyboard to navigate a website. If you use the tab key you can jump from focusable element to focusable element (like a link, button or a form element).
If you add a positive tabindex to a form element, that element will be the first that gets focus on a page. In fact you are hijacking the natural focus order. That can be very annoying for someone who is navigating the site with a keyboard and just wants to access the main menu and not subscribe to your newsletter.
Give the user control and don』t decide for them.
Use of Color
Usually the colors of your forms are determined by the WordPress theme you are using. If you want to change the colors in the customizer, please keep a few things in mind:

The color contrast between text and its background and borders and their background must be sufficient. This is explained in the Accessibility Documentation for Developers.
Don』t refer to or give meaning to color. Like: 「Press the green button to continue」.

Not everybody has perfect eyesight. By giving text and borders a good color contrast against its background, you are assured most people can find and read it, even with an iPad in the sun.
8% of all men and 0.4% of all women are color blind. They could miss the reference to the color.
HTML Blocks and Section Breaks
Make sure an HTML block or Section Break doesn』t contain content that is essential for filling out the form. Assistive technology, like a screen reader may miss this content as it』s not announced when the fill out a form.
Use the description field with an input to add essential information. As the description field will be read out for blind users by their screen readers.
About Naming
Make links, labels and buttons easy to understand on their own. Don』t let your users guess, or have to read all around a link or button to see what』s happening. Use descriptions if more information is needed to fill out an input.
For example:

Give a button a clear text. 「Submit」 is very generic. What about 「Subscribe」?
Give a link a describing text. 「Click here」 is not really useful. What about 「our privacy statement」 as link text? Write your sentences so that the link text stands out on its own, without forcing the user to read around the text to know why they should click here.
Give a clear description with a new password, like: Please enter password of more than 8 characters long.

Give Users an Idea About What to Expect
Do you have a form with multiple steps? That』s a good idea to break a long form into manageable pieces for the user. But don』t keep users in the dark about how much steps it takes to fill out a form.
If you use page breaks, also set a visible progress bar.
People with an anxiety disorder (and actually, everyone else too) will feel much more comfortable if they know what to expect. Inform users on the amount of steps. Give them a way to return to previous steps to double check if everything is filled out properly.
Give buttons and links a descriptive text so it』s clear what to expect when a user clicks a button or link.
reCAPTCHAs
Accessibility best practice: CAPTCHAs and reCAPTCHAs can be very challenging to fill out for people who are blind or have a cognitive disability or aren』t that web savvy.
Please consider if you really need them. You may need to find another way to prevent spam. Enabling the Anti-spam honeypot can be an option for your site or use a spam protector plugin.
Googles reCaptchas V3 may be an option, but also can violate the privacy of your users. It』s complicated.
First of all: don』t put the burden of preventing spam on your users, you may block real users from filling out your form.
Form Validation
What is Required?
Not all users know what the asterisk () means. So if you indicate a required fields with an asterisk (), put a line above the form with an explanation or add (required) within the label.
Custom Validation Messages
Use the Custom Validation Messages with the form inputs to provide meaningful error messages. A text like 「This field is required」 can be improved on, for example 「Please enter your full name」.
Carefully written error messages are essential. Giving informative feedback on an omission or mistake will keep user irritation to a minimum.
Give the user all the help you can offer to fill out a form, including your contact information if you really want the user to be able to fill out the form.
Recommended Resources

Website Forms usability: Top 10 recommendations
Forms that Work (book)
Designing Good Questions by GOV.UK
The Question Protocol: How to Make Sure Every Form Field is Necessary

Adding a Form Using Blocks

SummaryAdding A Form To Your Page or PostUsing Add Block in Gravity Forms 2.4.9+Using Add Block and the Gravity Forms Gutenberg Block Add-OnBlock OptionsForm TitleForm DescriptionAdvanced > PreviewAdvanced > AJAXAdvanced > Field ValuesAdvanced > Tabindex

NOTE: This article refers specifically to the block-based page editor environment released with WordPress 5.0. For information on embedding a form using the classic WordPress editor, see this article.
Summary
With the full release of WordPress 5.0, we now have a completely new editor environment (referred to during the beta period as the 「Gutenberg Editor」). With progress comes a few casualties though, and indeed, the faithful 「Add Form」 button, that served us so well in the 「classic」 post editor, has now departed (as has the entire top bar of editor chrome).
RIP, classic button.
Adding A Form To Your Page or Post
Using Add Block in Gravity Forms 2.4.9+
You can add a form to a page or post by using the block function that is a part of Gravity Forms core. This article assumes that you have already created a form. See Create A New Form for instructions.

Open the page or post you wish to add a form to.
Click the plus sign to add a new block.
In the Search for a block field, type gravity.
Under Embeds, click on Form. This will insert the Gravity Forms block.
Click the Select a Form drop down and choose your form. This will insert the selected form.

For additional ways to add forms using the block editor, refer to this article.
Using Add Block and the Gravity Forms Gutenberg Block Add-On
Our Gravity Forms Gutenberg Block Add-On has been available during the beta and release candidate stages of WP5. If you are still using an older Gravity Forms core version, it is available for download to active license holders of all levels using any of the standard Gravity Forms add-on download and install mechanisms. This add-on has all of the same functionality as the Gravity Forms core block editor as well as support for conditional logic.
At the moment, the two form blocks are not interchangeable. Future updates will improve the interoperability between the two.
Block Options

Form Title
Will toggle appearance of the form title on or off.
Form Description
Will toggle appearance of the form description on or off.
Advanced > Preview
Toggles whether the full form is shown within the editor block, or just a marker for it.
Advanced > AJAX
Toggles embedding the form on the front-end using AJAX, allowing for confirmations and changing between form pages to happen without page reloads.
Advanced > Field Values
Specifies the default field values in an ampersand (&) separated list. For example, to set default values for fields with the parameters 「dropdown」 and 「email」 you would use [email protected]&dropdown=First Choice. If the block preview is also enabled in the Advanced tab of the block settings you will see the default values update in real time in the editor while editing the page or post.
For more detailed information on how to dynamically populate a field please see our documentation on dynamic population.
Advanced > Tabindex
Sets the tab index of the form element on the page.

2Checkout Change Log

2.0.12.0 | 2020-12-231.1 | 2020-05-061.0 | 2018-12-17

2.0.1

Fixed PHP 8 compatibility issues.

2.0 | 2020-12-23

Added support for 2Checkout API version 6.0.
Added support for Gravity Forms 2.5.

1.1 | 2020-05-06

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Updated Javascript files to use minified versions.
Fixed an issue where the API credentials settings could show as valid when an authentication error is returned by the 2Checkout API.

1.0 | 2018-12-17

Initial release.