File Upload Field CSS Selectors

File Upload Field CSS Selectors

Single File UploadContainerInputMulti-File UploadContainerUpload Instruction TextValidation MessageFile Selection Button

Single File Upload
Container
example: file upload container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_fileupload {border: 1px solid red;}
example: file upload container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_fileupload {border: 1px solid red;}
example: file upload container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_fileupload {border: 1px solid red;}
Input
example: file upload input (input) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_fileupload input {color: red;}
example: file upload input (input) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_fileupload input {color: red;}
example: file upload input (input) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_fileupload input {color: red;}
Multi-File Upload
Container
example: multi-file upload container (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_fileupload {border: 1px solid red;}
example: multi-file upload container (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_fileupload {border: 1px solid red;}
example: multi-file upload container (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_fileupload {border: 1px solid red;}
Upload Instruction Text
example: file upload container (span) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_fileupload .gform_drop_instructions {color: red;}
example: file upload container (span) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_fileupload .gform_drop_instructions {color: red;}
example: file upload container (span) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_fileupload .gform_drop_instructions {color: red;}
Validation Message
example: file upload validation message (div) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_fileupload .validation_message {color: red;}
example: file upload validation message (div) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_fileupload .validation_message {color: red;}
example: file upload validation message (div) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_fileupload .validation_message {color: red;}
File Selection Button
example: file selection button (input) – applies to all forms
1body .gform_wrapper .gform_body .gform_fields .gfield .ginput_container_fileupload .gform_button_select_files {color: red;}
example: file selection button (input) – applies just to form ID #1
1body .gform_wrapper_1 .gform_body .gform_fields .gfield .ginput_container_fileupload .gform_button_select_files {color: red;}
example: file selection button (input) – applies just to specific container (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
1body .gform_wrapper_1 .gform_body .gform_fields #field_XX_X.gfield .ginput_container_fileupload .gform_button_select_files {color: red;}

{all_fields} Merge Tag

{all_fields} Merge Tag

SummaryUsageModifiers:admin:value:empty:noadmin:nohidden

Summary
Displays a preformatted HTML table containing all of the submitted values.
Usage
{all_fields}
{all_fields:[modifier1],[modifier2],[…]}
Modifiers
You may append multiple modifiers using comma as a delimiter. They are not order sensitive.
Examples:
{all_fields:value,empty}
{all_fields:admin,value}
:admin
Uses the fields』 Admin Labels (if specified) rather than the default field labels.
Example: {all_fields:admin}
:value
Displays the actual value rather than the corresponding value label. This typically applies to fields with multiple inputs such as checkboxes, radio buttons and drop downs.
Example: {all_fields:value}
:empty
Shows fields for which no value was submitted.
:noadmin
Hides field output of fields set to a Visibility of Admin Only.
:nohidden
Hides field output of fields using the Hidden field type. It doesn』t affect to fields set to a Visibility of Hidden.

Field Types

Field Types

The following field types are available when creating settings using the Settings API:

Dynamic Field Map
Creates a set of fields that allow the user to map their form fields to custom keys (fields) entered by the user.

Checkbox
Creates a checkbox field.

Checkboxed Select
Creates a complex field where a hidden drop-down field is displayed when the checkbox is checked.

Custom Field
Learn how to create custom field types.

Field Map
Creates a set of fields that allow the user to map their form fields to a custom field selected from a predefined list.

Field Select
Creates a drop down field populated with fields from the form.

Generic Map
Creates a set of fields that allow the user to map custom keys to custom values, based on submission or other data.

Hidden
Creates a hidden field.

Radio Button
Creates a radio button field.

Select
Creates a select/drop-down field.

Save Button
Creates a save button.

Select Custom
Creates a select/drop-down field which also allows users to enter a custom value.

Simple Condition
Creates a complex set of fields allowing users to specify a condition (i.e. Country is Brazil).

Text
Creates a text field.

Textarea
Creates a textarea field.

Field Object

Field Object

IntroductionUsagePropertiesBasic PropertiesPost FieldsAdvanced FieldsNumberDatePhoneName and AddressFile UploadCAPTCHAOtherPricing FieldsAdd-On FieldsField JSON

Introduction

The Field object contains all settings for a particular field. It is part of the Form Object and is available in most Gravity Forms hooks. It can be manipulated to dynamically change the way the field is displayed.

Usage

12// returns the label of the first field on the form$form['fields'][0]->label;

1234// displays the types of every field in the formforeach ( $form['fields'] as $field ) {   echo $field->type . '
';}

Properties

Basic Properties

adminLabel string When specified, the value of this property will be used on the admin pages instead of the label. It is useful for fields with long labels. Applies to: All fieldsadminOnly bool Determines if this field should only visible on the administration pages. A value of 1 will mark the field as admin only and will hide it from the public form. Useful for fields such as 「status」 that help with managing entries, but don』t apply to users filling out the form. Applies to: All fieldsallowsPrepopulate bool Determines if the field』s value can be pre-populated dynamically. 1 to allow field to be pre-populated, 0 otherwise. Applies to: All fieldschoices array Contains the available choices for the field. For instance, drop down items and checkbox items are configured with this property. Applies to: select, checkbox, radio, post_category

123$choices = $field->choices;$choices[0]['text'] = 'Drop down item 1';$field->choices = $choices;

Each choice in the array has the following Properties:text string The text to be displayed to the user when displaying this choice.value string The value to be stored in the database when this choice is selected. Note: This property is only supported by the Drop Down and Post Category fields. Checkboxes and Radio fields will store the text property in the database regardless of the value propertyisSelected bool Determines if this choice should be selected by default when displayed. The value 1 will select the choice, 0 will display it unselected.Conditional Logic array Controls the visibility of the field based on values selected by the user.content string Content of an HTML block field to be displayed on the form Applies to: htmlcssClass string Custom CSS class to be added to the

  • tag that contains the field. Useful to apply custom formatting to specific fields. Applies to: All fieldsdefaultValue string Contains the default value for the field. When specified, the field』s value will be populated with the contents of this property when the form is displayed. Applies to: hidden, text, website, phone, number, date, textarea, email, post_title, post_content, post_excerpt, post_tags, post_custom_fielddescription string Field description. Applies to: All fieldsenableChoiceValue bool Determines if the field (checkbox, select or radio) have choice values enabled, which allows the field to have choice values different from the labels that are displayed to the user Applies to: checkbox, select and radioerrorMessage string Contains the message that is displayed for fields that fail validation Applies to: All fields except html, section and hiddenid integer Field IdinputName string Assigns a name to this field so that it can be populated dynamically via this input name. Only applicable when allowsPrepopulate is set to 1. Applies to: All fields except section and captchaisRequired bool Determines if the field requires the user to enter a value. 1 marks the field as required, 0 marks the field as not required. Fields marked as required will prevent the form from being submitted if the user has not entered a value in it. Applies to: All fields except section, html and captchalabel string Field label that will be displayed on the form and on the admin pages Applies to: All fieldsnoDuplicates bool Determines if the field allows duplicate submissions. 1 to prevent users from submitting the same value more than once, 0 to allow duplicate values. Applies to: hidden, text, website, phone, number, date, time, textarea, select, radio, email, post_custom_fieldsize string Determines the size of the field when displayed on the page Applies to: All fields except html, section and captchaPossible values: small, medium, largetype string The type of field to be displayed Applies to: All fieldsPossible values: html, hidden, section, text, website, phone, number, date, time, textarea, select, checkbox, radio, name, address, fileupload, email, post_title, post_content, post_excerpt, post_tags, post_category, post_image, post_custom_field, captcha

    Post Fields

    postCustomFieldName string The name of the Post Custom Field that the submitted value should be assigned to. Applies to: post_custom_fielddisplayAllCategories bool Determines if all categories should be displayed on the Post Category drop down. 1 to display all categories, 0 otherwise. If this property is set to 1 (display all categories), the Post Category drop down will display the categories hierarchically. Applies to: post_categorydisplayCaption bool Controls the visibility of the caption metadata for Post Image fields. 1 will display the caption field, 0 will hide it. Applies to: post_imagedisplayDescription bool Controls the visibility of the description metadata for Post Image fields. 1 will display the description field, 0 will hide it. Applies to: post_imagedisplayTitle bool Controls the visibility of the title metadata for Post Image fields. 1 will display the title field, 0 will hide it. Applies to: post_imageinputType string Contains a field type and allows a field type to be displayed as another field type. A good example is the Post Custom Field, that can be displayed as various different types of fields. Applies to: post_custom_field

    Advanced Fields

    Number

    numberFormat string Specifies the format allowed for the number field. Applies to: numberPossible values: decimal_dot, decimal_commadecimal_dot: 9,999.99decimal_comma: 9.999,99rangeMin float Minimum allowed value for a number field. Values lower than the number specified by this property will cause the field to fail validation. Applies to: numberrangeMax float Maximum allowed value for a number field. Values higher than the number specified by this property will cause the field to fail validation. Applies to: number

    Date

    calendarIconType string Determines how the date field displays it』s calendar icon Applies to: datePossible values: calendar, custom, nonecalendar: Displays the standard calendar icon shipped with Gravity Formscustom: Allows administrators to specify a custom iconnone: Disables the calendar iconcalendarIconUrl string Contains the URL to the custom calendar icon. Only applicable when calendarIconType is set to custom Applies to: datedateFormat string Determines how the date is displayed Applies to: datePossible values: mdy, dmymdy: 01/25/2010dmy: 25/01/2010

    Phone

    phoneFormat string Determines the allowed format for phones. If the phone value does not conform with the specified format, the field will fail validation. Applies to: phonePossible values: standard, internationalstandard: Phone must be in the format: 「(###)### – ####」international: Phone can be in any format

    Name and Address

    nameFormat string Determines the format of the name field Applies to: namePossible values: normal, extended, simplenormal: Displays first and last name fieldsextended: Displays prefix, first, last and suffix fieldssimple: Displays one name fieldaddressType stringDetermines the type of address to be displayed.   Applies to: addressPossible values: international, us, canadianinternational: State input is displayed as a text field and the country drop down is displayedus: State input is displayed as a drop down with US states and the country drop down is hiddencanadian: State input is displayed as a drop down with Canadian provinces and the country drop down is hiddendefaultCountry string Contains the country that will be selected by default. Only applicable when addressType is set to international Applies to: addressdefaultProvince string Contains the province that will be selected by default. Only applicable when addressType is set to canadian Applies to: addressdefaultState string Contains the state that will be selected by default. Only applicable when addressType is set to us Applies to: addresshideAddress2 bool Controls the visibility of the address 2 field. A value of 1 will hide the address 2 field, 0 will display it. Applies to: addresshideCountry Controls the visibility of the country drop down. A value of 1 will hide the country drop down, 0 will display it. Only applicable when addressType is set to international Applies to: addresshideState bool Controls the visibility of the state field. A value of 1 will hide the state field, 0 will display it. Applies to: addressinputs array For fields with multiple inputs (i.e. Name, Address), this property contains a list of inputs. This property also applies to the checkbox field as checkboxes are treated as multi-input fields (since each checkbox item is stored separately). Applies to: name, address, checkbox

    1234$inputs = $field->inputs;$inputs[0]['label'] = 'First Name';//sets the label for the first input$field->inputs = $inputs

    Each input has the following properties.id float The input id. Input Ids follow the following naming convention: 「FIELDID.INPUTID」 (i.e. 5.1), where FIELDID is the id of the containing field and INPUTID specifies the input field. For example, inputs for the name field are numbered as follows:FIELDID.2 Name Prefix input id (i.e. 4.2)FIELDID.3 First Name input id (i.e. 4.3)FIELDID.6 Last Name input id (i.e. 4.6)FIELDID.8 Name Suffix input id (i.e. 4.8)label string Input labelname string When the field is configured with allowsPrepopulate set to 1, this property contains the parameter name to be used to populate this field (equivalent to the inputName property of single-input fields)

    File Upload

    allowedExtensions string Contains a comma delimited list of file extensions that are allowed to be uploaded. (i.e. jpg,gif,png) Applies to: fileupload, post_image

    CAPTCHA

    captchaType string Determines the type of CAPTCHA field to be used Possible values: recaptcha, simple_captcha, mathNOTE: simple_captcha and math CAPTCHA fields are only available when the 「Really Simple CAPTCHA」 plugin is installedcaptchaTheme string Determines the theme to be used for the reCAPTCHA field. Only applicable to the recaptcha captcha type. Possible values: red, white, blackglass, cleansimpleCaptchaSize string Determines the CAPTCHA image size. Only applicable to simple_captcha and math captcha types. Possible values: small, medium, largesimpleCaptchaFontColor Determines the image』s font color, in HEX format (i.e. #CCCCCC). Only applicable to simple_captcha and math captcha types.simpleCaptchaBackgroundColor string Determines the image』s background color, in HEX format (i.e. #CCCCCC). Only applicable to simple_captcha and math captcha types.

    Other

    enablePasswordInput bool Determines if a text field input tag should be created with a 『password』 type Applies to: textmaxLength integer Specifies the maximum number of characters allowed in a text or paragraph field.enableEnhancedUI bool When set to true, the Chosen jQuery script will be applied to this field, enabling search capabilities to Drop Down fields and a more user-friendly interface for Multi Select fields. Applies to: select, multiselect

    Pricing Fields

    basePrice float Base price for a single product field. Applies to: singleproductdisableQuantity bool Specifies if the quantity field on single product fields should be displayed or hidden. Applies to: singleproductproductField integer Available only on Option fields. Specifies which product field the current option field is linked to. Applies to: optionenablePrice bool Specifies if a price can be entered for each field choice. This option is automatically turned ON for pricing fields when using Drop Down, Radio Button or Checkbox input types. Applies to: checkbox, select, radio

    Add-On Fields

    See the following pages for details about fields added by add-ons:

    CouponDropbox Upload

    Field JSON

    This example shows how a field object would look when formatted as JSON for use by the Gravity Forms CLI Add-On.

    12345678910111213141516{    "type": "select",    "label": "My Dropdown",    "choices": [{        "text": "Choice 1",        "value": "one"    }, {        "text": "Choice 2",        "value": "two"    }],    "id": "2",    "visibility": "visible",    "formId": "14",    "pageNumber": 1,    "isRequired": false}

    • Field Merge Tags

    Field Merge Tags

    SummaryUsageParametersExampleModifiersAdditional Information

    Summary

    Displays the value submitted for the field with the specified field_id. If no value was submitted, the merge tag will not display anything. Adding optional modifiers are also available to display other data related to the field.

    Usage

    {[descriptor]:[field_id]}

    {:[field_id]}

    {[descriptor]:[field_id]:[modifier]}

    Parameters

    ParameterDescription[descriptor]Optional. A user defined value for readability. By default when using the merge tags widget, this will be the field name. Since this is optional, {:[field_id]} will work also.[field_id]Required. This is the value of the field_id, which may be a single number for the field, or a multi-part number for multi-part fields that have more than one field within them, such as the Name field. See Example below.[modifier]Optional. A list of possible modifiers are listed below. Some modifiers may be combined by comma-separating them. See :admin modifier below for example.

    Example

    {text:4} will select field ID 4. {name:5.3} will target the 3rd part of the field ID 5, such as the first name within a name field. If in doubt as to how to determine your field ID, use the merge tag dropdown widget to select the field by name and the proper ID will be inserted for you.

    Modifiers

    ModifierDescription:labelDisplays the field label. Can be used with the :admin label. {phone:1:label} or {phone:1:admin,label}:adminOutputs the field admin label when combined with the label modifier. Since Gravity Forms 2.4.18.7.{phone:1:admin,label} or {phone:1:label,admin}:urlApplies only to fields of type List. Displays the list field content in a format that is URL friendly.i.e. col1_row1|col2_row1,col1_row2|col2_row2{List:5:url}:valueApplies only to fields of type Drop Down, Checkbox and Radio Button. Displays the selected item』s value. Applicable if the field was configured with 『enable values』.{Field:5:value}:idApplies only to the fields of type Category.Displays the selected category』s id rather than label.{Category:5:id}:priceApplies only to Pricing fields of type Drop Down and Radio Button, and the Total field. Displays the selected product』s price in numeric format (i.e. 500).{Product:5:price}:currencyApplies only to Pricing fields of type Drop Down and Radio Button, and the Total field.Displays the selected product』s price in currency format (i.e. $500.00).{Product:5:currency}:qtyApplies only to drop down and radio button pricing fields.Displays the selected product』s quantity.:numericConverts the number string or currency value as a decimal-formatted number.{Field:5:numeric}

    Additional Information

    Refer to individual field type user guides for field specific information on merge tags or modifiers.

    Accessibility Warning Showing on Field

    Accessibility Warning Showing on Field

    SummaryDescriptionAdvice Regarding Specific FieldsMultiselectGoogle reCAPTCHA V2DatepickerSubmit/Next Page ButtonIntroduced InFurther InformationExample Screenshots

    Summary

    This article provides information regarding accessibility warning messages you may receive for a particular field on your form. The message is presented in the Field Settings pane of the Form Editor. See screenshots at bottom for some examples.

    Description

    To ensure your form can be completed by all your visitors. it is important to try and limit your form to using fields that work for everyone. People who use assistive technology for example, may find some form fields have hard to navigate, or some fields are hard to understand when read back by a screen reader or voice recognition software.

    If your forms must comply with accessibility guidelines like WCAG, section 508 or the ADA, then please be aware that some form fields with accessibility issues can』t be used. From Gravity Forms 2.5 onwards we present a warning message for the most common of those, and have listed some alternatives here.

    Advice Regarding Specific Fields

    Multiselect

    The Multiselect field is difficult for people using assistive technology like a screen reader or voice recognition software, as they are not able to properly select multiple options. The better choice is using checkboxes.

    A warning will be displayed in the Form Editor when Field Label Visibility is marked as hidden.

    Google reCAPTCHA V2

    The Google Support website has a page is dedicated to the accessibility of reCAPTCHA V2 through the use of an audio challenge. The can present other challenges for your visitors though.

    Firstly, this is not an option for deafblind users. Secondly, reCAPTCHA only offers an English audio challenge and expects an English answer to it, which makes it harder for non-native English speakers to understand the challenge or increases the likelihood of typing the answer with a spelling mistake.

    There is also a cognitive and cultural accessibility issue. Not everyone understands the visual challenges.If you have a form that is vital for your visitor to fill out, don』t put the burden of proving they are human on them.

    An alternative could be to use a third-party reCAPTCHA V3 add-on. If you choose V3, also consider the privacy impact for your users and whether you need to comply with your GDPR policy as well.

    Support for reCAPTCHA V3 will be added in a future update of Gravity Forms.

    Datepicker

    The date field provides the option of displaying a datepicker, but note this datepicker is not keyboard or screen reader accessible at the moment. Therefore we provide an accessible alternative of having the date input fields be text only.

    Hints on what the exact date format your field expects is given by placeholders and by additional text, connected to the input field with aria-describedby. Then the date format is announced and visible.

    For more info, this external article has a good discussion of accessible datepickers.

    Submit/Next Page Button

    The presentation of the submit (and next page) buttons can be controlled by conditional logic. The best accessibility choice is to use a visibly disabled button. This is a well known form pattern, people know what it means.

    Completely hiding the submit button can have a negative impact on the accessibility of a form for a few reasons, mostly cognitive:

    Visitors do not see the submit button at first. This is unexpected behavior, which can discourage visitors that are not that web savvy, and increase anxiety around the task of trying to complete the form.You send the visitor on a quest: what do I need to fill out to get this form submitted?Blind visitors do not get informed when the button later (conditionally) appears and the form can be submitted.For accessibility it』s always best to stick to form conventions and give the visitor all the information they need.

    Introduced In

    These warning messages were added in Gravity Forms 2.5. The warning messages contain a link to this article.

    Further Information

    Refer to the Accessibility area of our documentation site for more helpful advice on improving your form』s accessibility.

    Example Screenshots

    These images show a few examples of the type of warning you may see.

    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()

    Field Map Field

    Field Map Field

    IntroductionParametersExampleHelpersget_field_map_fields()get_field_value()Uses

    Introduction

    The field_map type field, part of the Settings API, allows the user to map their form fields to fields you define, e.g. fields you will be sending to a third-party service such as a CRM.

    Parameters

    name string Required. Name of the field. Use it to retrieve saved data.label string Required. Field label. Will be displayed in the UItype string Required. Field type. Must be set to field_map for the Field Map fieldtooltip string Optional. Defaults to blank (no tooltip). Displays a question mark icon and a tooltip next to the field label.field_map arrayRequired. Array that defines the fields to be mapped.Each item in the field_map array has the following properties:name stringRequired. Name of the field to be mapped. To be used when retrieving the selected value.label stringRequired. Label to be displayed in the UI.required boolOptional. Defaults to false. Possible values are true or false. Marks this field as required, which means it must be mapped to a form field.default_value stringOptional. Defaults to blank (nothing is pre-selected). Allowed values are field IDs. When specified, the form field drop down is pre-selected with the appropriate field.validation_callback (function)Optional. Defaults to nothing (no callback). Calls a function during validation allow for custom validation logic. The example in the existing documentation page is good.

    Example

    array(
    'title' => esc_html__( 'This is the title for Section 1', 'sometextdomain' ),
    'fields' => array(
    array(
    'name' => 'contactStandardFields',
    'label' => esc_html__( 'Map Fields', 'sometextdomain' ),
    'type' => 'field_map',
    'field_map' => $this->standard_fields_for_feed_mapping(),
    'tooltip' => '

    ' . esc_html__( 'Map Fields', 'sometextdomain' ) . '

    ' . esc_html__( 'Select which Gravity Form fields pair with their respective third-party service fields.', 'sometextdomain' )
    ),
    ),
    ),

    Here』s the function being used to define the fields for the field_map property.

    public function standard_fields_for_feed_mapping() {
    return array(
    array(
    'name' => 'first_name',
    'label' => esc_html__( 'First Name', 'sometextdomain' ),
    'required' => true,
    'field_type' => array( 'name', 'text', 'hidden' ),
    'default_value' => $this->get_first_field_by_type( 'name', 3 ),
    ),
    array(
    'name' => 'last_name',
    'label' => esc_html__( 'Last Name', 'sometextdomain' ),
    'required' => true,
    'field_type' => array( 'name', 'text', 'hidden' ),
    'default_value' => $this->get_first_field_by_type( 'name', 6 ),
    ),
    array(
    'name' => 'email_address',
    'label' => esc_html__( 'Email Address', 'sometextdomain' ),
    'required' => true,
    'field_type' => array( 'email', 'hidden' ),
    'default_value' => $this->get_first_field_by_type( 'email' ),
    ),
    );
    }

    The above code would render the following:

    Helpers

    The following functions may come in helpful when interacting with the field_map field type during feed processing.

    get_field_map_fields()

    Retrieves the individual field_map fields from the meta property of the Feed Object for the supplied field name.

    $contact_standard_fields = $this->get_field_map_fields( $feed, 'contactStandardFields' );

    $feed Feed Object
    The Entry Object to be checked.

    $name string
    The name property of the field_map field to retrieve the mapped fields for.

    Returns array
    An array containing the field names as the keys to the mapped form field ID or entry meta key.

    get_field_value()

    Retrieves the specified form field or entry meta value. See Accessing Mapped Field Values During Feed Processing for more details.

    $first_name = $this->get_field_value( $form, $entry, $contact_standard_fields['first_name'] );

    Uses

    settings_field_map()field_map_table_header()field_map_title()get_mapped_field_name()settings_field_map_select()get_field_map_choices()

    Feed Object

    Feed Object

    IntroductionUsagePropertiesAdd-on ArticlesGF Feed Add-OnsGF Feed Add-OnsGF Payment Add-Ons

    Introduction

    The Feed Object ($feed) is an associative array containing all the properties which determine if and how the form submission is processed by an add-on. For example, the feed for a payment add-on determines the type of payment transaction which occurs and what values are sent to the payment gateway.

    1234567$feed = array(    'id'         => 5,    'form_id'    => 10,    'is_active'  => true,    'meta'       => array(),    'addon_slug' => 'gravityformsslack',);

    Usage

    We recommend accessing the $feed properties using the rgar() or rgars() functions e.g.

    12$meta = rgar( $feed, 'meta' );$conditional_logic_enabled = rgars( $feed, 'meta/feed_condition_conditional_logic' );

    Properties

    PropertyTypeDescriptionidintegerThe feed ID.form_idintegerThe form ID this feed was created for. An ID of 0 indicates the feed applies to ALL forms.is_active booleanIs the feed active or inactive. Default is true.feed_orderintegerThe order the feed will be displayed in the feeds list for the form. Also applies to submission time feed processing. Not all add-ons support feed ordering.metaarrayFeed meta is an associative array. The available properties vary from add-on to add-on. Please see the Add-on Articles below for the individual propertiesaddon_slugstringThe slug belonging to the add-on used to create the feed, including the gravityforms prefix. See the Gravity Forms Add-On Slugs article for a list of possible slugs.event_typestringFor future usage.

    Add-on Articles

    GF Feed Add-Ons

    GF Feed Add-Ons

    GF Payment Add-Ons

    ActiveCampaign Feed MetaAgile CRM Feed MetaAWeber Feed MetaBreeze Feed MetaCampaign Monitor Feed MetaCampfire Feed MetaCapsule CRM Feed MetaCleverReach Feed MetaCoupons Feed MetaDropbox Feed MetaEmma Feed Meta

    Freshbooks Feed MetaGetResponse Feed MetaHelp Scout Feed MetaHighrise Feed MetaHipChat Feed MetaiContact Feed MetaMad Mimi Feed MetaMailChimp Feed MetaSlack Feed MetaTrello Feed MetaTwilio Feed MetaUser Registration Feed MetaZapier Feed MetaZoho CRM Feed Meta

    Authorize.net Feed MetaPayPal Payments Pro Feed MetaPayPal Standard Feed MetaStripe Feed Meta

    Can Gravity Forms Do…?

    Can Gravity Forms Do…?

    A very common question we see is 「can Gravity Forms do X?」
    Gravity Forms is a very flexible and powerful WordPress plugin. We keep a basic feature list here, and our library of help documents and user guides provides many more details. Additionally, our Customer Support Team are always available to try and help you get you an answer regarding product capabilities.
    For other features, check out our Add-ons, which provide many ways to extend Gravity Forms or to interact with other popular services.
    Additionally, we provide a robust development API, so don』t forget to search our third party add-on library or other common repositories for add-ons developed by third parties to work with Gravity Forms. Someone else may very well have already developed what it is you are thinking of!
    If the feature you want isn』t covered by our core software or any available add-ons, but you have some software skills yourself, then maybe you can develop it yourself. Consult our developer documentation.
    Still want a new feature or integration, but can』t develop it yourself? Consider hiring an developer (we do not provide custom development services). See this article for a few starting options.