Author 诗语

Date Field CSS Selectors

Date Field CSS Selectors

Date Picker Input TypeInput FieldIcon ImageDate Field Input TypeMonthContainerInput FieldSub-LabelDayContainerInput FieldSub-LabelYearContainerInput FieldSub-Label

Date Picker Input Type
Input Field

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

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

example: date – input field (input) – applies just to specific date field input (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .datepicker {border: 1px solid red}

Icon Image

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

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

example: date – icon image (img) – applies just to specific date field input (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_input_datepicker_icon {border: 1px solid red}

Date Field Input Type
Month
Container
Contains the month input field and sub-label

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

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

example: date – month container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_month {border: 1px solid red}

Input Field

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

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

example: date – month input field (input) – applies just to specific form field (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_month input {border: 1px solid red}

Sub-Label

example: date – month sub-label (label) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_month label {color: red}

example: date – month sub-label (label) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_month label {color: red}

example: date – month sub-label (label) – applies just to specific sub-label (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_month label {color: red}

Day
Container
Contains the day input field and sub-label

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

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

example: date – day container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_day {border: 1px solid red}

Input Field

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

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

example: date – day input field (input) – applies just to specific form field (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_day input {border: 1px solid red}

Sub-Label

example: date – day sub-label (label) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_day label {color: red}

example: date – sub-label (label) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_day label {color: red}

example: date – sub-label (label) – applies just to specific sub-label (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_day label {color: red}

Year
Container
Contains the month input field and sub-label

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

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

example: date – year container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_year {border: 1px solid red}

Input Field

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

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

example: date – year input field (input) – applies just to specific form field (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_year input {border: 1px solid red}

Sub-Label

example: date – year sub-label (label) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield .gfield_date_year label {color: red}

example: date – year sub-label (label) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield .gfield_date_year label {color: red}

example: date – year sub-label (label) – applies just to specific sub-label (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield .gfield_date_year label {color: red}

Date

Date

SummaryCommon SettingsGeneral SettingsMerge TagsUsageModifiers

Summary

The Date field allows you to present a field that captures date data using the jQuery UI date picker. It is available under the Advanced Fields section within the form editor.

Date field as displayed in the Field Library

Date field as displayed in the Form Editor.

Common Settings

This field uses only common field settings for the Appearance and Advanced 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

SettingDescriptionDate Input TypeDate Picker will let users select a date from a calendar.Date Field will let users free type the date.Date Drop Down will let users select date from drop downs.IconAllows you to set an icon which will be listed beside the date field. Options include: No Icon, Calendar Icon, Custom IconDate FormatSelect the format you would like to use for the date input. Available options are MM/DD/YYYY and DD/MM/YYYY.

Merge Tags

For more information on the use of merge tags, refer to these articles.

Usage

{Field Name:2:modifier}

Notes:

The field name is optional.The second parameter defines the ID of the field that will be output in this tag.Within the third parameter, you can define an optional modifier to use. Only one modifier can be used per merge tag.

Modifiers

ModifierDescription:yearOutputs only the year used in the field.:monthOutputs only the month used in the field.:dayOutputs only the day used in the field.:ymdOutputs the date formatted as year/month/day. Example: 2016/10/31.:dmyOutputs the date formatted as day/month/year. Example: 31/10/2016.

Defining Minimum Add-On Requirements

Defining Minimum Add-On Requirements

WordPress RequirementsWordPress VersionWordPress PluginsPlugin NamePHP RequirementsPHP VersionExtensionsExtension VersionFunctionsGravity Forms RequirementsGravity Forms Add-OnsAdd-On NameAdd-On VersionCustom Requirements

As of Gravity Forms 2.2, add-ons can now easily define requirements that are needed before the add-on can be used. Defining requirements is as simple as overriding the minimum_requirements function in the GFAddOn class.
1234567891011class Example_AddOn extends GFAddOn {     public function minimum_requirements() {        return array(            'wordpress' => array(                'version' => '4.6.2',            )        );    } }
WordPress Requirements
Using the wordpress array key, requirements based on the WordPress installation can be defined.
12345array(    'wordpress' => array(        // WordPress-related requirements go here.    ))
WordPress Version
Within the wordpress requirement, the version key can be used to define a specific WordPress version to be used as a minimum requirement. Versions higher than this number will succeed, while lower versions will fail.
12345array(    'wordpress' => array(        'version' => '4.6.2'    ))
WordPress Plugins
12345array(    'plugins' => array(        'rest-api/plugin.php',    ),)
Plugin Name
12345array(    'plugins' => array(        'jetpack/jetpack.php' => 'Jetpack by WordPress.com',    ),)
PHP Requirements
Requirements related to PHP versions, extensions, or even available functions can be defined by using the php array key.
12345array(    'php' => array(        // PHP-related requirements go here.    ))
PHP Version
12345array(    'php' => array(        'version' => '5.6',    ))
Extensions
1234567array(    'php' => array(        'extensions' => array(            'curl',        ),    ),)
Extension Version
123456789array(    'php' => array(        'extensions' => array(            'curl' => array(                'version' => '1.0',            ),        ),    ),)
Functions
1234567array(    'php' => array(        'functions' => array(            'openssl_random_pseudo_bytes',        ),    ),)
Gravity Forms Requirements
Gravity Forms Add-Ons
12345array(    'add-ons' => array(        'gravityformsmailchimp',    ),)
Add-On Name
1234567array(    'add-ons' => array(        'gravityformsstripe' => array(            'name' => 'Gravity Forms Stripe Add-On',        ),    ),)
Add-On Version
1234567array(    'add-ons' => array(        'gravityformspaypal' => array(            'version' => '5.0',        ),    ),)
Custom Requirements
123array(    array( $this, 'custom_requirement_callback' ),)

Delete Entry Data after Submission

Delete Entry Data after Submission

By default, Gravity Forms was designed to record all data submitted to it, so there isn』t an override to stop Gravity Forms from storing entry data upon submission. The reason for this is the entry must be saved so the data is available when notifications are sent and feed based add-ons, like PayPal and User Registration, are processed.
That said, Gravity Forms 2.4 did introduce Personal Data Settings which include the ablity to enable automatic deletion of entries after a specified number of days.
Bear in mind when entries are deleted, files associated with the entry are also deleted. If you want to keep the files, use the gform_field_types_delete_files filter.
There are also a number of third-party add-ons which can be used to delete entries either as the form submission ends or at a scheduled date/time:

Gravity Flow
Entry Automation by ForGravity
Gravity Perks – Disable Entry Creation by Gravity Wiz
Gravity Forms Encrypted Fields by PluginOwl
Gravity Forms Utility by Gravity+
Wider Gravity Forms Stop Entries by Jonny Allbut

If you would prefer not to use one of the above solutions you can use custom code in the theme functions.php file or a custom functionality plugin that will wait until the data is recorded, and then go in and remove the entry that was just created. To do so, you would use the following code which works with Gravity Forms 1.8 and newer:
123456// Target submissions from form ID  1.// Change gform_after_submission_1 to reflect your target form ID, or use gform_after_submission to target all forms.add_action( 'gform_after_submission_1', 'remove_form_entry' );function remove_form_entry( $entry ) {    GFAPI::delete_entry( $entry['id'] );}
The following code is applicable to Gravity Forms 1.7 and earlier only.
123456789101112131415161718192021222324252627282930add_action('gform_after_submission_1', 'remove_form_entry', 10, 2);function remove_form_entry($entry, $form){    global $wpdb;     $lead_id = $entry['id'];    $lead_table = RGFormsModel::get_lead_table_name();    $lead_notes_table = RGFormsModel::get_lead_notes_table_name();    $lead_detail_table = RGFormsModel::get_lead_details_table_name();    $lead_detail_long_table = RGFormsModel::get_lead_details_long_table_name();     //Delete from detail long    $sql = $wpdb->prepare(" DELETE FROM $lead_detail_long_table                            WHERE lead_detail_id IN(                                SELECT id FROM $lead_detail_table WHERE lead_id=%d                            )", $lead_id);    $wpdb->query($sql);     //Delete from lead details    $sql = $wpdb->prepare("DELETE FROM $lead_detail_table WHERE lead_id=%d", $lead_id);    $wpdb->query($sql);     //Delete from lead notes    $sql = $wpdb->prepare("DELETE FROM $lead_notes_table WHERE lead_id=%d", $lead_id);    $wpdb->query($sql);     //Delete from lead    $sql = $wpdb->prepare("DELETE FROM $lead_table WHERE id=%d", $lead_id);    $wpdb->query($sql); }
The expected behavior would be that the entry would not exist in the Gravity Forms database tables after submission. If you are having issues with this script, please read up on our gform_after_submission hook.

Delete Entry Data after Submission

Delete Entry Data after Submission

By default, Gravity Forms was designed to record all data submitted to it, so there isn』t an override to stop Gravity Forms from storing entry data upon submission. The reason for this is the entry must be saved so the data is available when notifications are sent and feed based add-ons, like PayPal and User Registration, are processed.
That said, Gravity Forms 2.4 did introduce Personal Data Settings which include the ablity to enable automatic deletion of entries after a specified number of days.
Bear in mind when entries are deleted, files associated with the entry are also deleted. If you want to keep the files, use the gform_field_types_delete_files filter.
There are also a number of third-party add-ons which can be used to delete entries either as the form submission ends or at a scheduled date/time:

Gravity Flow
Entry Automation by ForGravity
Gravity Perks – Disable Entry Creation by Gravity Wiz
Gravity Forms Encrypted Fields by PluginOwl
Gravity Forms Utility by Gravity+
Wider Gravity Forms Stop Entries by Jonny Allbut

If you would prefer not to use one of the above solutions you can use custom code in the theme functions.php file or a custom functionality plugin that will wait until the data is recorded, and then go in and remove the entry that was just created. To do so, you would use the following code which works with Gravity Forms 1.8 and newer:
// Target submissions from form ID 1.
// Change gform_after_submission_1 to reflect your target form ID, or use gform_after_submission to target all forms.
add_action( 'gform_after_submission_1', 'remove_form_entry' );
function remove_form_entry( $entry ) {
GFAPI::delete_entry( $entry['id'] );
}

The following code is applicable to Gravity Forms 1.7 and earlier only.
add_action('gform_after_submission_1', 'remove_form_entry', 10, 2);
function remove_form_entry($entry, $form){
global $wpdb;

$lead_id = $entry['id'];
$lead_table = RGFormsModel::get_lead_table_name();
$lead_notes_table = RGFormsModel::get_lead_notes_table_name();
$lead_detail_table = RGFormsModel::get_lead_details_table_name();
$lead_detail_long_table = RGFormsModel::get_lead_details_long_table_name();

//Delete from detail long
$sql = $wpdb->prepare(" DELETE FROM $lead_detail_long_table
WHERE lead_detail_id IN(
SELECT id FROM $lead_detail_table WHERE lead_id=%d
)", $lead_id);
$wpdb->query($sql);

//Delete from lead details
$sql = $wpdb->prepare("DELETE FROM $lead_detail_table WHERE lead_id=%d", $lead_id);
$wpdb->query($sql);

//Delete from lead notes
$sql = $wpdb->prepare("DELETE FROM $lead_notes_table WHERE lead_id=%d", $lead_id);
$wpdb->query($sql);

//Delete from lead
$sql = $wpdb->prepare("DELETE FROM $lead_table WHERE id=%d", $lead_id);
$wpdb->query($sql);

}

The expected behavior would be that the entry would not exist in the Gravity Forms database tables after submission. If you are having issues with this script, please read up on our gform_after_submission hook.

Deleting Cached Entry Data

Deleting Cached Entry Data

This snippet will allow the cached entry data for products to be deleted when viewing an entry. Note that the cached data should only be removed if absolutely necessary, as it will impact performance.
add_action( 'gform_entry_detail_content_before', function ( $form, $entry ) {
GFFormsModel::refresh_product_cache( $form, $entry );
}, 10, 2 );

Deprecated Gravity Forms Database Tables

Deprecated Gravity Forms Database Tables

The following database tables have been deprecated as of Gravity Forms 2.3, and should not be utilized by any custom code or third-party plug-ins etc.

wp_rg_form
wp_rg_form_meta
wp_rg_form_view
wp_rg_incomplete_submissions
wp_rg_lead
wp_rg_lead_detail
wp_rg_lead_detail_long
wp_rg_lead_meta
wp_rg_lead_notes

For more detail on the Gravity Forms 2.3 upgrade process, refer to this article.

Coupons Change Log

Coupons Change Log

3.0 | 2020-09-292.11 | 2020-09-282.10 | 2020-05-112.9 | 2019-8-142.8 | 2018-11-302.7 | 2018-11-022.6 | 2017-04-262.5 | 2017-02-222.4 | 2017-01-052.3 | 2016-07-292.2 | 2015-07-272.1 | 2015-04-202.0 | 2015-03-301.1 | 2014-09-241.0 | 2014-07-15

3.0 | 2020-09-29

Added a custom icon to the Coupon field for Gravity Forms 2.5.
Updated empty coupons list verbiage.
Fixed the alignment of the coupon amount tooltip in the add new coupon page.
Fixed compatibility issues with PHP 8.

2.11 | 2020-09-28

Added support for Gravity Forms 2.5.
Fixed a rounding issue with the form total for some discounts when used with the PayPal Commerce Platform Add-On.
Fixed PHP notices which occur when exporting the coupon field value for entries created since version 2.9.3.

2.10 | 2020-05-11

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added support for dynamic population.
Added the label visibility and description placement settings to the field appearance tab.
Fixed a notice with PHP 7.4 which occurs when configuring a new coupon.
Fixed an issue where a coupon using an integer based code would prevent a product field with a matching ID from appearing in the order summary table.

2.9 | 2019-8-14

Added the gform_coupons_can_apply_coupon PHP filter enabling custom logic to be used to determine if the coupon code can be applied.
Added the gform_coupons_post_delete_coupon JS action hook which is triggered after a coupon is deleted from the field.
Fixed an issue which can result in negative values for total fields.
Fixed issue where conditional logic generates error if the input being evaluated does not have an ID attribute (e.g. List field inputs).

2.8 | 2018-11-30

Added support for GF 2.4 conditional logic.

2.7 | 2018-11-02

Added $entry as the fourth parameter of the gform_coupons_discount_amount filter.
Added GPL to plugin header.
Updated the Start Date and End Date datepickers on the edit coupon page to use the YYYY-MM-DD format.
Updated Plugin URI and Author URI to use https.
Fixed Euro currency formatting of the flat amount when the edit coupon page is displayed.

2.6 | 2017-04-26

Added security enhancement.
Added translations.
Fixed code style.

2.5 | 2017-02-22

Added security enhancement.
Added 'isCoupon' flag when adding coupons to order summary; allows 3rd parties to more reliable identify coupons in the order summary.

2.4 | 2017-01-05

Added gform_coupons_is_valid_code to override coupon code alphanumeric checking in Gravity Forms 2.2.2.
Updated coupons.js to use the gform_product_total filter with a later priority.
Updated how default label for new fields is set.
Fixed wrong domain for translating the "Coupon" button.
Fixed an issue with the formatting of the percentage coupon amount when a decimal comma based currency is in use.

2.3 | 2016-07-29

Added Dutch translation (nl_NL). Credit: Maarten Emmerink.
Updated gform_coupon_script dependencies to include gform_gravityforms.
Updated Coupon Code validation to only allow alphanumeric characters.
Updated bulk actions and feed action links.
Fixed issue where "undefined" was output before coupon markup when applying a coupon.
Fixed front-end JS error when attempting to remove an applied coupon if the coupon code includes special characters.

2.2 | 2015-07-27

Added GF_Field_Coupon::get_value_export() to return entry value formatted as {couponName} ({couponCode}: {discount}). Multiple codes will be comma separated e.g. $50 OFF (50OFF: -$50.00), 25% OFF (25OFF: -$10.00). Used for entry exports and some framework based add-ons since GF 1.9.12.4.
Added required and custom validation message settings.
Updated Spanish (es_ES) translation.
Updated minimum Gravity Forms version to 1.9.5.
Updated scripts and stylesheets to use minified files by default unless SCRIPT_DEBUG is active or query param gform_debug is set, e.g. domain.com/?gform_debug.
Updated to alert if a Total field is not present when adding the Coupon field.
Fixed an issue with one of the field validation messages not being translatable.
Fixed an issue with the coupons not being included in the product info when notifications are sent after submission.
Fixed an issue with duplicate coupon codes being allowed to be created.
Fixed an issue with the coupon field where removed coupons were not removed from the hidden coupon detail input resulting in the appearance that the coupon was reapplied when returning to the page containing the coupon field.
Fixed an issue with the upgrade routine which caused it run even if a pre-framework version hadn't been installed.

2.1 | 2015-04-20

Added Spanish (es_ES) translation.
Updated gform_coupon_script deps to include gform_json.
Fixed a low severity security vulnerability in the admin area which could be exploited by authenticated users with form administration permissions.

2.0 | 2015-03-30

Added Add-on Framework integration.
Added support for using the coupon field with conditional logic.
Added support for placeholders.
Added POT file.
Added a bulk action to the feed page for resetting the coupon usage count.
Added the visibility setting to the fields advanced tab.
Added the capability to view the plugin page.
Added text domain/path to header.
Added gform_coupons_discount_amount PHP hook to support modifying the discount amount.
add_filter( 'gform_coupons_discount_amount', 'add_logged_in_user_bonus_discount', 10, 3 );
function add_logged_in_user_bonus_discount( $discount, $coupon, $price ) {
if( is_user_logged_in() ) {
$discount += 5;
}
return $discount;
}
Added gform_coupons_discount_amount JS hook.
gform.addFilter( 'gform_coupons_discount_amount', function( discount, couponType, couponAmount, price, totalDiscount ) {
// you would need to write your own JS-version of is_user_logged_in()
if( is_user_logged_in() ) {
discount += 5;
}
return discount;
} );
Fixed an issue with the ajax request for applying coupons not functioning for logged out users.
Fixed an issue with feed processing which in some situations could prevent the coupon usage count being updated.
Fixed an issue with the field label for attribute.
Fixed an issue with the usage count being lost when updating an existing coupon.
Fixed an issue where pasting the coupon code using right-click caused the Apply button to not enable.
Fixed issue where existing coupon code was not saved when editing an entry.
Fixed issue with some translation text domain strings being misspelled.

1.1 | 2014-09-24

Updated plugin updated method so that it takes advantage of proxy manager to get around the blacklisted IP issue.
Updated several instances of domain used for translations from gravityformscoupon to the correct domain of gravityformscoupons.
Updated javascript in DisableApplyButton function since the button remained disabled for some users.
Fixed issue with product info cache not including coupon on certain situations.
Fixed issue with text domain of some strings.
Fixed another issue with duplicate coupon codes being allowed to be created.
Fixed issue with duplicate coupon codes being allowed to be created.
Fixed fatal error when plugin is activated without Gravity Forms active.
Fixed issue where existing coupon code was not saved when editing an entry.
Fixed issue with start and expiration date not taking the configured WP timezone into account.
Fixed issue where translations were not being applied on the front end.
Fixed issue with coupon not being applied when form failed validation.
Fixed issue with coupon being marked as "undefined" after a submission when clicking the back browser button.

1.0 | 2014-07-15

Fixed issue with applying fixed amount coupon code with currencies other than US dollar.
Fixed issue where changing an existing coupon from being form specific to 'any form' resulted in an 'Invalid coupon.' message on any form other than the original.

Coupons Feed Meta

Coupons Feed Meta

IntroductionUsageProperties

Introduction
The Feed Object meta for the Coupons add-on is an associative array containing the properties which determine the type of coupon and discount available.
$feed['meta'] = array(
'gravityForm' => 0,
'couponName' => 'test100',
'couponCode' => 'TEST100',
'couponAmountType' => 'percentage',
'couponAmount' => 100,
'startDate' => '',
'endDate' => '',
'usageLimit' => 20,
'isStackable' => false,
'usageCount' => 2,
);

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

Properties

gravityForm string
The form ID this coupon was created for. An ID of 0 indicates the coupon can be used with ALL forms.

couponName string
The coupon name.

couponCode string
The the value users should enter to apply this coupon to the form total.

couponAmountType string
The coupon amount type. Possible values: flat or percentage.

couponAmount string
The coupon amount.

startDate string
The date when the coupon should start.

endDate string
The date when the coupon should expire.

usageLimit integer
The number of times the coupon can be used.

isStackable boolean
Can this coupon be used in conjunction with another coupon? Default is false.

usageCount integer
The number of times this coupon has been used since the count was last reset.

Create a New Form

Create a New Form

IntroductionCreating a New Form

Introduction

This short article gives you a quick overview of the Form Editor, which is the primary environment for creating a form with Gravity Forms.

Creating a New Form

Log into your WordPress admin, and look for the Forms menu with the Gravity Forms 「G」 in the left hand navigation area.

Log into your WordPress admin, and look for the Forms menu with the Gravity Forms 「G」 in the left hand navigation area.

Under the Forms item you will see an option that says New Form. Clicking that will it to start the form creation process.

You will then be presented with a dialog box asking for the Title and Description of your new form.

You must give your form a name before you can begin, but you can change that name later if needed. The name is used so you can find your form easily later on.

Once you』ve filled out the field(s), finalize by clicking the Create Form button.

You will now be presented with a blank Form Editor screen, ready for your upcoming Form masterpiece!

Screenshot: The Gravity Forms Form Editor, as shown for a new form.

This article shows the new 「Block Editor」 we introduced in Gravity Forms version 2.5. If your Editor screen looks quite different, it means you are using an older version of Gravity Forms. The fields, settings, operations and terms are basically the same, but you will find that the layout will look quite different. We recommend you update to the most current version, it』s awesome!

Getting to know the Form Editor is covered in our next article.

next article: The Form Editor >