Author 诗语

Enabling No Conflict Mode

Having issues where creating a form doesn』t show both the title and description field? Or are you unable to add or move elements on the form builder?
You might be experiencing an issue where scripts from other plugins and themes are being loaded on Gravity Forms administration pages. This causes the errors you are experiencing.
There is an easy fix to get around these issues, but it is still recommended you troubleshoot using our theme and plugin conflict steps to isolate the issue and report it to the proper developer.
To temporarily resolve the issue, go to Forms > Settings and enable No Conflict mode. This should stop third party scripts from writing to Gravity Forms administration pages and allow you to do the things you need.
We recommend finding the source of this issue as it could cause further problems later on. Please follow the Theme and Plugin Conflict troubleshooting steps.

Please note: No Conflict mode only applies to the Gravity Forms administration pages, such as the form editor, it will not help resolve front-end issues.

Entry List Page

Form SelectorFilter ToolbarEntry Quick ToolbarEntry ActionsBulk ActionsEntry ColumnsFurther Info

The Entry list page allows you to browse all entries generated by form submissions. From this screen you can browse, sort, and modify your entry with a variety of options.

Form Selector

You can click on the arrow next to the current form title to select the form for which you want to display the entries list.

Filter Toolbar

The filter toolbar allows you to filter which entries you would like to view: All, Unread, Starred, Spam, and Trash. In the parenthesis beside each filter label is the number of entries currently applicable to that filter.

Entry Quick Toolbar

Each entry item has an entry toolbar that displays when you hover over the first cell of an entry row. This quick toolbar will allow you to view the entry, mark the entry as read, mark the entry as spam, or send the entry to the trash to be deleted later.

Entry Actions

With the exception of the Star action, the following entry actions are available per entry in the Entry Quick Toolbar. The Star action is available to the left of each entry item.

ActionDescriptionStarThe Star icon to the left of each entry item enables you to flag important entries. Using the filters toolbar, you can then browse all starred entries for the current form by selecting the Starred link in the filter toolbar.ViewView the entry details.Mark as Read/UnreadMuch like email, marking an entry as read is useful when you would like to indicate that the entry has been acknowledged without having to view the entry detail view. You may also mark the entry as unread.SpamMark the entry as spam.TrashSend the entry to the Trash. Please note, you are responsible for emptying your Trash. The Trash is not automatically deleted. Deleting entries from the Trash will delete those entries permanently along with any files uploaded to them.

Bulk Actions

Using bulk actions you may apply the same action to multiple entries at once. To use bulk actions you must first select the checkbox next to each entry item you would like to modify. Then select the desired action from the bulk action select box, and click 「Apply.」

ActionDescriptionMark as Read/UnreadMark all selected entries as read/unread.Add/Remove StarAdd/remove the star indicator for the selected entries.Resend NotificationsResend the default entry notifications or forward the notifications on to a specified email address.Bulk PrintPrint multiple selected entries all at once.SpamMark the selected entries as spam.TrashSend the selected entries to the Trash.

Entry Columns

One of the features of the Entries screen is the ability to pick and choose which columns should appear in the list based on available form fields. To select the columns, simply click the Edit icon on the right of the entries list table header. This will display the Select Columns window.

The Select Columns window consists of two panels, Active Columns and Inactive Columns. Simply drag the columns you would like to appear on the entries list from the Inactive Column to the Active Column to configure your entries list the way you see fit.

Further Info

For information on the entries detail view, refer to this user guide section.

{entry_id} Merge Tag

SummaryUsageNotesSee Also

Summary
Displays the entry ID of the submission.
Usage
{entry_id}
Notes
This merge tag can be used in areas such as notifications and confirmations after the entry has been saved. Because of this timing, they cannot be used as a field』s default value.
See Also
The {entry} merge tag.

{entry_url} Merge Tag

SummaryUsageNotesSee Also

Summary
Displays a URL that will take you to detail page for the submitted entry.
Usage
{entry_url}
Notes
This merge tag can be used in areas such as notifications and confirmations after the entry has been saved. Because of this timing, they cannot be used as a field』s default value.
Clicking through to the URL requires the user to be logged in with appropriate permissions.
See Also
The {entry} merge tag.

Entry Creator Merge Tag

SummarySinceUsageMeta Keys

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

Meta Key
Description
Usage

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

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

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

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

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

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

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

Entry Date Merge Tags

SummarySinceImportantDefault UsageModifiers:time:format:human:diff:raw:timestamp

Summary
The entry date merge tags can be used in notifications, confirmations, and with some add-ons to output the date and/or time the entry was created, updated, and paid. They cannot be used in field settings.
Since
Support for these merge tags was added in Gravity Forms 2.5. They were previously only available when using selected third party add-ons from certified developers.
Important
The date_created, date_updated, and payment_date are stored in the entry and database using UTC in the YYYY-MM-DD HH:MM:SS format. The values will be formatted for output using the timezone, date, and/or time formats from the WordPress General Settings screen.
For the examples below the value stored in the entry for specified property is 2021-04-21 10:30:15 UTC, the timezone is set to Europe/London, the date format is set to F j, Y, and the time format is set to g:i a.
Default Usage
Outputs the specified date.

Merge Tag
Output

{date_created}
April 21, 2021

{date_updated}
April 21, 2021

{payment_date}
April 21, 2021

Modifiers
:time
Adds at [time] to the output.

Merge Tag
Output

{date_created:time}
April 21, 2021 at 11:30 am

{date_updated:time}
April 21, 2021 at 11:30 am

{payment_date:time}
April 21, 2021 at 11:30 am

:format
Define a custom format for the output using the WordPress and PHP date/time formatting characters.
The format must be defined after :format, with a colon, like this :format:m/d/Y.
If you want to use a colon in your output, it must be escaped with a backslash, like this :.

Merge Tag
Output

{date_created:format:m/d/Y}
04/21/2021

{date_created:format:Y-m-d}
2021-04-21

{date_created:format:d/m/Y at H:i:s}
21/04/2021 at 11:30:15

{date_updated:format:m/d/Y}
04/21/2021

{date_updated:format:Y-m-d}
2021-04-21

{date_updated:format:d/m/Y at H:i:s}
21/04/2021 at 11:30:15

{payment_date:format:m/d/Y}
04/21/2021

{payment_date:format:Y-m-d}
2021-04-21

{payment_date:format:d/m/Y at H:i:s}
21/04/2021 at 11:30:15

:human
If the entry is less than a day old, it will output a relative vale using the [time] ago format. If you want to customize the format, use the :diff and :format modifiers instead.

Merge Tag
Output

{date_created:human}
15 mins ago

{date_updated:human}
15 mins ago

{payment_date:human}
15 mins ago

If the entry is more than a day old, it will output the date using the default date format. If the :time modifier is also used, it will output [date] at [time] using the default date and time formats.

Merge Tag
Output

{date_created:human}
April 21, 2021

{date_created:human:time}
April 21, 2021 at 11:30 am

{date_updated:human}
April 21, 2021

{date_updated:human:time}
April 21, 2021 at 11:30 am

{payment_date:human}
April 21, 2021

{payment_date:human:time}
April 21, 2021 at 11:30 am

:diff
Outputs how long ago the entry was created, updated, or paid.
The default format is %s ago, where %s is replaced by the time difference in seconds, minutes, hours, days, weeks, months, or years.

Merge Tag
Output

{date_created:diff}
1 second ago

{date_created:diff:format:%s has passed since the form was submitted}
5 hours has passed since the form was submitted

{date_updated:diff}
1 day ago

{date_updated:diff:format:%s has passed since the entry was updated}
3 days has passed since the entry was updated

{payment_date:diff}
1 week ago

{payment_date:diff:format:payment was completed %s ago}
payment was completed 1 month ago

Using the :time and :human modifiers with this modifier is not supported.
:raw
Outputs the value as it is stored in the entry and database. This value is also available using the Entry Merge Tag.

Merge Tag
Output

{date_created:raw}
2021-04-21 10:30:15

{date_updated:raw}
2021-04-21 10:30:15

{payment_date:raw}
2021-04-21 10:30:15

This modifier cannot be used with other modifiers.
:timestamp
Outputs the value as a Unix timestamp; the number of seconds since the Unix epoch on January 1st, 1970 at UTC.

Merge Tag
Output

{date_created:timestamp}
1619001015

{date_updated:timestamp}
1619001015

{payment_date:timestamp}
1619001015

This modifier cannot be used with other modifiers.

Entry Detail

Entry DataEntry NotesEntry SummaryNotificationsPrint

The Entry detail page allows you to view the information created for the entry. From this screen you can view the info, add notes, print, and enable notifications.

Entry Data

This information varies, depending on the type of fields you selected for your form.

SettingDescriptionShow empty fieldsBy default, empty fields are not shown on the entry page. If you check this box, it enables you to see the empty fields.

Entry Notes

With Entry Notes, you can add notes to your entries, allowing you to keep important, related information right with the correlating entry.

SettingDescriptionAdd NoteThis action adds the note to your entry. Beside the Add Note button, you can select who you would like to email the note to.

Entry Summary

Contains a quick summary of various entry details.

SettingDescriptionMove to TrashFrom here you can move your entry to the trash, emptying the trash will permanently delete the entry and any files uploaded to it.EditFrom here you can edit your original entry.

Notifications

This allows you to resend notifications, for more information please visit Resend Notifications.

Print

This option allows you to print out a hard copy of your entry.

SettingDescriptionInclude NotesSelect the fields that you would like to enable, as well as set any custom labels.

{entry} Merge Tag

SummaryUsageModifiers:id:created_by:date_created:currency:payment_status:payment_date:payment_amount:transaction_id

Summary
Can be used in areas such as notifications and confirmations to display entry properties after the entry has been saved. Because this relies on the entry being saved, it cannot be used as a field』s default value.
Usage
{entry:[modifiers]}
Modifiers
:id
The entry ID of the submission.
:created_by
The ID of the WordPress user who submitted the form.
:date_created
The UTC date and time the entry was created in the yyyy-mm-dd hh::mm::ss format.
:currency
The currency code used for this submission.
:payment_status
The current payment status of the entry (ie 「Authorized」, 「Paid」, 「Processing」, 「Pending」, 「Active」, 「Expired」, 「Failed」, 「Cancelled」, 「Approved」, 「Reversed」, 「Refunded」, 「Voided」).
:payment_date
The UTC date and time, in the yyyy-mm-dd hh::mm::ss format, when the payment add-on processed the entry.
:payment_amount
The payment amount without currency formatting.
:transaction_id
The ID of the transaction returned by the payment gateway.

Entry Object

IntroductionUsagePropertiesStandardPricing PropertiesPost CreationField ValuesList FieldCheckboxes FieldAdd-On Field ValuesEntry JSON

Introduction
The Entry object contains all properties of a particular entry (i.e. date created, client IP, submitted field values, etc…). It is formatted as an associative array with field Ids being the key to that field』s data.
Usage
rgar( $entry, 'date_created' ); // returns the entry date
rgar( $entry, '1' ); // returns the value associated with field 1 (This would be for fields with single input like Text, Number, Drop Down, etc...)
rgar( $entry, '1.3' ); // returns the value associated with the first name portion of a simple name field 1
rgar( $entry, '1.6' ); // returns the value associated with the last name portion of a simple name field 1
rgar( $entry, '2.4' ); // returns the value associated with the state input for the address field 2
rgar( $entry, '5.1' ); // returns the field label for a single product that has id 5
rgar( $entry, '5.1' ); // returns the field label for a single product that has id 5
GFCommon::to_number( rgar( $entry, '5.2' ) ); // returns the field price, without currency symbol, for a single product that has id 5
rgar( $entry, '5.3' ); // returns the field quantity for a single product that has id 5

Properties

Standard

id integer
The entry』s Id.

form_id string
The ID of the form from which the entry was submitted.

created_by integer
ID of the user that submitted the form if a logged in user submitted the form.

date_created string
The date and time that the entry was created, in the format 「yyyy-mm-dd hh:mi:ss」 (i.e. 2010-07-15 17:26:58)

is_starred bool
Indicates if the entry has been starred (i.e marked with a star). 1 for entries that are starred and 0 for entries that are not starred.

is_read bool
Indicates if the entry has been read. 1 for entries that are read and 0 for entries that have not been read.

ip string
Client IP of user who submitted the form.

source_url string
Source URL of page that contained the form when it was submitted.

post_id integer
For forms with Post fields, this property contains the Id of the Post that was created.

user_agent string
Provides the name and version of both the browser and operating system from which the entry was submitted.

status string
The current status of the entry (ie 「Active」, 「Spam」, 「Trash」).

Pricing Properties
These $entry properties are only relevant when a Gravity Forms payment gateway add-on is being used.

currency string
The currency with which the entry was submitted (ie 「USD」, 「EUR」).

payment_status string
The current payment status of the entry (ie 「Authorized」, 「Paid」, 「Processing」, 「Pending」, 「Active」, 「Expired」, 「Failed」, 「Cancelled」, 「Approved」, 「Reversed」, 「Refunded」, 「Voided」).

payment_date string
The date the payment has been received.

payment_amount integer
The amount of the fulfilled payment; this property is empty until the payment has been received. Sample value: 75

transaction_id string
ID of the transaction returned by the payment gateway

is_fulfilled bool
Indicates if the entry/order has been fulfilled. 1 for entries that have been fulfilled and 0 for entries that have not been fulfilled.

transaction_type integer
Indicates the transaction type of the entry/order. 1 for one time payments, 2 for subscriptions.

Post Creation
The following property is only relevant when the form is used to create a WordPress post.

post_id integer
The id number of the post created as result of the form submission.

Field Values

FIELD_ID string
The value for all submitted fields can be retrieved by using the Field Id as the key to the $entry array.
rgar( $entry, '1' ); // returns the value associated with field 1
rgar( $entry, '2.4' ); // returns the value associated with the state input for the address field 2

List Field
The List field type due to its complex setup compared to other field types (it has many rows and columns of data) it』s stored in serialized format, so you need to unserialize it first to access the data.
maybe_unserialize( rgar( $entry, '3' ) ); // unserialize values associated with list field 3

Checkboxes Field
The easiest way to get the checked checkboxes would be to get a comma separated string containing the selected choices without accessing each input in the entry and building the string yourself would be to use the get_value_export method of the field object, here』s an example
$field_id = 18; // Update this number to your field id number
$field = RGFormsModel::get_field( $form, $field_id );
$value = is_object( $field ) ? $field->get_value_export( $entry ) : '';

That would return a comma separated list containing the values for the selected choices, if you wanted to use the choice text then you would use the following
$value = is_object( $field ) ? $field->get_value_export( $entry, $field_id, true ) : '';

You can then convert that comma separate list to an array, if you want, using PHP』s explode() function.
Add-On Field Values
See the following pages for details about the entry values for fields added by add-ons:

Coupon
Dropbox Upload

Entry JSON
This example shows how an entry array would look when formatted as JSON for use by the Gravity Forms CLI Add-On.
{
"id":"1",
"form_id":"1",
"date_created":"2016-03-22 19:13:19",
"is_starred":0,
"is_read":0,
"ip":"192.168.50.1",
"source_url":"http://local.wordpress.dev/?gf_page=preview&id=1",
"post_id":null,
"currency":"USD",
"payment_status":null,
"payment_date":null,
"transaction_id":null,
"payment_amount":null,
"payment_method":null,
"is_fulfilled":null,
"created_by":"1",
"transaction_type":null,
"user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36",
"status":"active",
"1":"Third Choice",
"2":"This is text content"
}

Exporting a Form

When moving a form from one location to another, or even to backup your data, we have provided a tool within Gravity Forms to perform an export of your created form with just a few clicks. In this article, we will show you how to easily export any forms you have created using Gravity Forms.

First, log into your WordPress admin dashboard.
Once logged in, hover over Forms on the left side navigation menu and click on Import/Export.
Once on this page, you will notice a few different options. Click on the second option labeled Export Forms.
From here, select the checkbox next to any forms that you want to export. Then, click Download Export File.
You will then be prompted to save a JSON file containing all of your form settings. Be sure to save this is a safe place for easy access later.

Your form should now be successfully exported. If you need to import your form, you may review our article on importing forms into Gravity Forms.