Gravity Forms All Fields Template

The Gravity Forms {all_fields} merge tag provides a super simple way to output all of the submitted form data but it’s notoriously difficult to customize.

This plugin provides templating support for the {all_fields} merge tag. Huh? It means you can replace the markup generated by the merge tag with the contents of a file. This tutorial offers a solid starter template file too!

Getting Started

This tutorial assumes you’re running a recent version of Gravity Forms, that you already have the {all_fields} merge tag implemented wherever you want, and that you ♥ Gravity Wiz.

	Download, install, and activate the plugin.
	Download the sample template directory/file. Add the folder to your active theme’s root directory: /wp-content/themes/{your-theme}/
	Customize the template as desired.

Template and Merge Tag Options

This plugin provides a few handy modifiers for controlling which template will be used to render the {all_fields} merge tag.

Note: All template paths are relative to your theme’s root directory.

Default Templates

Merge Tag	Template
{all_fields}	/gravity-forms/all-fields.php

Form-specific Template

Providing a form-specific template requires not changes to the merge tag. Simply append the targeted form ID to your template’s name. This template will now only be used with the merge tag is used in the context of the specified form.

Merge Tag	Template
{all_fields}	/gravity-forms/all-fields.php /gravity-forms/all-fields-1.php

Custom Template

You may want to create a custom template that should only be applied to specific instances of the merge tag. The “template” modifier allows you to specify a custom template suffix.

Merge Tag	Template
{all_fields:template[custom]}	/gravity-forms/all-fields-{template}.php /gravity-forms/all-fields-custom.php

No Template

You may want to create a generic template that applies to all instances of the merge tag by default and then disable that template to use the default Gravity Forms merge tag output in a few specific instances.

Merge Tag	Template
{all_fields:notemplate}	No template

Field Filtering Modifier

These modifiers allow you to control which fields are output in the {all_fields} merge tag without having to touch any code.

Merge Tag	Description
{all_fields:include[1,2]}	Include a field that is not included by default (i.e. HTML fields).
{all_fields:exclude[3,4]}	Exclude a field that is included by default.
{all_fields:filter[1,2]}	Only include the specified field IDs. This takes precedence over both the ‘include’ and ‘exclude’ modifiers.
{all_fields:include[1,2],exclude[3]}	The :include and :exclude modifiers can be combined.

GF Nested Forms Support

To filter which fields from a child form display in your {all_fields} merge tag you can use the :filter modifier and the [Nested Form Field ID].[Child Field ID] format (e.g., 4.3; where 4 is the Nested Form field ID and 3 is the child field ID from the child form.

You can use the :include, :exclude, and :filter modifiers on the Nested Form field to filter which child fields should be displayed.

Merge Tag	Description
{all_fields:filter[1,2,3.4,3.5]}	In this example, 1 and 2 are field IDs on the parent form. 3 is the Nested Form Field ID and 4 and 5 are field IDs on the child form.
{Nested Form:1:filter[4,5]}	Show fields 4 and 5 from the child form for this Nested Form field.

Customizing the Template

Ok, don’t let this section intimidate you. Here’s the TLDR; Loop through $items, use $item['label'] for the field label, and $item['value'] for the field value. Here’s the simplest template you could have:

You’ll most likely want to use the sample template above as a starting point though as it takes care of a requirements to better align the template with Gravity Forms default All Fields functionality.

Digging Deeper

The {all_fields} template works like any other WordPress template with one exception. There is a special $items array available to you.

Each $item contains a label, value, and field property. The label and value are the exact label and value that the default {all_fields} merge tag would output. The field is the input-type-specific GF_Field object for the current field. This is useful when you want to alter the way a field is displayed depending on the field you’re working with.

Lastly, you have access to the current entry via the $entry variable and the current form via the $form variable. For more details on these variables, see the parameters section below.

Parameters

• $items array

  An array of items, each item containing the Gravity-Forms-formatted field label, field value and field object for the given field. The field label and field value are the same values that Gravity Forms outputs in the default {all_fields} merge tag.

  • label string

    The label of the current item/field.

  • value string

    The display value of the current item/field.

  • field GF_Field

    The input-type-specific GF_Field object for the current item/field.

• $entry Entry Object

  The current Gravity Forms Entry object.

• $form Form Object

  The current Gravity Forms Form object.

Questions? Feedback?

What questions do you have? What features are missing? We’d like to make this into a more robust plugin and your feedback will be a big part of shaping the final product.