Gravity Wiz

Magically enhanced tutorials, snippets and plugins for Gravity Forms!

Gravity Forms All Fields Template

Take complete control of the Gravity Forms {all_fields} merge tag output with this lightweight plugin.

Last updated | Written by 97 Comments

  • April 11, 2019: Updated priority of template replacement to avoid conflict with other merge tags replacement plugins.

View DemoShow CodeDownload Plugin
<?php
/**
* Gravity Wiz // Gravity Forms // All Fields Template
*
* Modify the {all_fields} merge tag output via a template file.
*
* @version 0.9.4
* @author David Smith <david@gravitywiz.com>
* @license GPL-2.0+
* @link https://gravitywiz.com/gravity-forms-all-fields-template/
* @copyright 2018 Gravity Wiz
*
* Plugin Name: Gravity Forms All Fields Template
* Plugin URI: https://gravitywiz.com/gravity-forms-all-fields-template/
* Description: Modify the {all_fields} merge tag output via a template file.
* Author: Gravity Wiz
* Version: 0.9.4
* Author URI: https://gravitywiz.com
*
* Usage:
*
* {all_fields}
*
* By default, enabling this plugin will look for this template:
* <theme>/gravityforms/templates/all-fields.php
*
* Override the {all_fields} template for a specific form by specifying the form ID:
* <theme>/gravityforms/templates/all-fields-<formId>.php
*
* {all_fields:template[custom]}
*
* Specify a custom template suffix. This is useful for allowing specific forms to use the same template.
* <theme>/gravityforms/template/all-fields-custom.php
*
* {all_fields:notemplate}
*
* Will always load the default Gravity Forms {all_fields} markup.
*
* Filtering Usage:
*
* :filter
*
* Filtering will only include the specified fields and exclude all others. It cannot be combined with the include
* exclude filters.
*
* {all_fields:filter[1]}
* {all_fields:filter[1,2]}
*
* :include
*
* Including will include fields with types that are typically not supported by the {all_fields} merge tag
* (e.g., HTML fields).
*
* {all_fields:filter[3]}
* {all_fields:filter[3,4]}
* {all_fields:include[3,4],exclude[5]}
*
* :exclude
*
* Excluding will exclude specific fields from being included in the {all_fields} output.
*
* {all_fields:exclude[5]}
* {all_fields:exclude[5,6]}
* {all_fields:exclude[5],include[3,4]}
*
*/
class GW_All_Fields_Template {
private static $instance = null;
public static function get_instance() {
if( self::$instance == null ) {
self::$instance = new self;
}
return self::$instance;
}
private function __construct() {
add_action( 'init', array( $this, 'init' ) );
}
public function init() {
add_filter( 'gform_pre_replace_merge_tags', array( $this, 'replace_merge_tags' ), 9, 7 );
add_filter( 'gform_merge_tag_filter', array( $this, 'all_fields_extra_options' ), 11, 5 );
}
/**
* to exclude field from notification add 'exclude[ID]' option to {all_fields} tag
* 'include[ID]' option includes HTML field / Section Break field description / Signature image in notification
* see http://www.gravityhelp.com/documentation/page/Merge_Tags for a list of standard options
*
* include: Include a field that is not included by default (i.e. HTML fields).
* exclude: Exclude a field that is included by default.
* filter: Only include the specified field IDs. This takes precedence over both the 'include' and 'exclude' modifiers.
*
* example: {all_fields:exclude[2,3]}
* example: {all_fields:include[6]}
* example: {all_fields:include[6],exclude[2,3]}
*/
public function all_fields_extra_options( $value, $merge_tag, $modifiers, $field, $raw_value ) {
if( ! is_a( $field, 'GF_Field' ) ) {
$field = new GF_Field();
$field->type = $field;
}
if( $merge_tag != 'all_fields' && $field->type == 'form' ) {
return $value;
}
$modifiers = $this->parse_modifiers( $modifiers );
$whitelist = array( 'filter', 'include', 'exclude' );
$context = rgar( $modifiers, 'context', false );
foreach( $modifiers as $modifier => $mod_value ) {
if( ! in_array( $modifier, $whitelist ) ) {
continue;
}
if( ! is_array( $mod_value ) ) {
$mod_value = array( $mod_value );
}
/**
* Integrate w/ GP Nested Forms to allow filtering which fields are displayed for nested entries in the
* Nested Form field's value. GPNF will pass custom modifiers (e.g., context[nested],parent[fieldId]).
*/
if( $context == 'nested' ) {
$nested_form_field_id = rgar( $modifiers, 'parent', false );
if( ! $nested_form_field_id ) {
break;
}
$field_ids = array();
foreach( $mod_value as $field_id ) {
if( intval( $field_id ) == $nested_form_field_id && $field_id !== intval( $field_id ) ) {
$field_id_bits = explode( '.', $field_id );
$field_ids[] = array_pop( $field_id_bits );
}
}
} else {
$field_ids = array_map( 'intval', $mod_value );
}
switch( $modifier ) {
case 'filter':
if( in_array( $field->id, $field_ids ) ) {
$value = $this->get_all_fields_field_value( $field, $value );
} else {
$value = false;
}
break;
case 'include':
if( in_array( $field->id, $field_ids ) ) {
$value = $this->get_all_fields_field_value( $field, $value );
}
break;
case 'exclude':
if( in_array( $field->id, $field_ids ) ) {
$value = false;
}
break;
}
}
// echo '<pre>';
// $field_id = $field->id;
// print_r( compact( 'modifiers', 'field_ids', 'field_id', 'value' ) );
// echo '<pre>';
return $value;
}
public function replace_merge_tags( $text, $form, $entry, $url_encode, $esc_html, $nl2br, $format ) {
$matches = array();
preg_match_all( '/{all_fields(?::(.*?))?}/i', $text, $matches, PREG_SET_ORDER );
foreach ( $matches as $match ) {
// Replace each unique merge tag only once.
if( strpos( $text, $match[0] ) === false ) {
continue;
}
$modifiers = rgar( $match, 1 );
$options = compact( 'url_encode', 'esc_html', 'nl2br', 'format' );
$content = $this->parse_template( 'all-fields', $modifiers, $form, $entry, $options );
if( $content !== false ) {
$text = str_replace( $match[0], $content, $text );
}
}
return $text;
}
public function parse_template( $template, $modifiers, $form, $entry, $options = array() ) {
$_modifiers = $modifiers;
$modifiers = $this->parse_modifiers( $modifiers );
if( in_array( 'notemplate', $modifiers ) ) {
return false;
}
$use_value = in_array( 'value', $modifiers );
$display_empty = in_array( 'empty', $modifiers );
$use_admin_label = in_array( 'admin', $modifiers );
$suffixes = array( $form['id'] );
if( array_key_exists( 'template', $modifiers ) ) {
array_unshift( $suffixes, $modifiers['template'] );
}
$items = rgar( $options, 'items' );
if( empty( $items ) ) {
$items = $this->get_items( $form, $entry, $display_empty, ! $use_value, $options['format'], $use_admin_label, 'all_fields', $_modifiers );
}
$output = $this->load_template( $template, null, array(
'form' => $form,
'entry' => $entry,
'items' => $items
), $suffixes );
if( $output === false && rgar( $options, 'fallback' ) ) {
if( is_callable( $options['fallback'] ) ) {
$output = call_user_func( $options['fallback'], $items );
}
}
return $output;
}
public function replace_nested_forms_all_fields( $value, $field, $nested_form, $entry, $modifiers ) {
$output = $this->parse_template( $modifiers, $nested_form, $entry, array( 'format' => 'html' ) );
if( $output ) {
$value = $output;
}
return $value;
}
public function parse_modifiers( $modifiers_str ) {
preg_match_all( '/([a-z]+)(?:(?:\[(.+?)\])|,?)/i', $modifiers_str, $modifiers, PREG_SET_ORDER );
$parsed = array();
foreach( $modifiers as $modifier ) {
list( $match, $modifier, $value ) = array_pad( $modifier, 3, null );
if( $value === null ) {
$value = $modifier;
}
// Split '1,2,3' into array( 1, 2, 3 ).
if( strpos( $value, ',' ) !== false ) {
$value = array_map( 'trim', explode( ',', $value ) );
}
$parsed[ $modifier ] = $value;
}
return $parsed;
}
public function get_items( $form, $lead, $display_empty = false, $use_text = false, $format = 'html', $use_admin_label = false, $merge_tag = '', $modifiers = '' ) {
return $this->get_submitted_fields( $form, $lead, $display_empty, $use_text, $format, $use_admin_label, $merge_tag, $modifiers );
}
public function get_submitted_fields( $form, $lead, $display_empty = false, $use_text = false, $format = 'html', $use_admin_label = false, $merge_tag = '', $modifiers = '' ) {
$items = array();
//$field_data = '';
$modifiers_array = explode( ',', $modifiers );
$no_admin = in_array( 'noadmin', $modifiers_array );
$no_hidden = in_array( 'nohidden', $modifiers_array );
$display_product_summary = false;
foreach ( $form['fields'] as $field ) {
$field_value = '';
$field_label = $use_admin_label && ! empty( $field->adminLabel ) ? $field->adminLabel : esc_html( GFCommon::get_label( $field, 0, false, $use_admin_label ) );
switch ( $field->type ) {
case 'captcha' :
break;
case 'section' :
$field_value = false;
if ( GFFormsModel::is_field_hidden( $form, $field, array(), $lead ) ){
continue;
}
if ( ( ! GFCommon::is_section_empty( $field, $form, $lead ) || $display_empty ) && ! $field->adminOnly ) {
switch ( $format ) {
case 'text' :
$field_value = "--------------------------------\n{$field_label}\n\n";
break;
default:
$field_value = '';
break;
}
}
$field_value = apply_filters( 'gform_merge_tag_filter', $field_value, $merge_tag, $modifiers, $field, $field_label );
//$field_data .= $field_value;
if( $field_value !== false ) {
$item = array(
'label' => $field_label,
'value' => $field_value,
'field' => $field
);
}
break;
case 'password' :
//ignore password fields
break;
default :
if ( GFCommon::is_product_field( $field->type ) ) {
// ignore product fields as they will be grouped together at the end of the grid
$display_product_summary = apply_filters( 'gform_display_product_summary', true, $field, $form, $lead );
if ( $display_product_summary ) {
continue;
}
} else if ( GFFormsModel::is_field_hidden( $form, $field, array(), $lead ) ) {
// ignore fields hidden by conditional logic
continue;
}
$raw_field_value = RGFormsModel::get_lead_field_value( $lead, $field );
$field_value = GFCommon::get_lead_field_display( $field, $raw_field_value, rgar( $lead, 'currency' ), $use_text, $format, 'email' );
$display_field = true;
//depending on parameters, don't display adminOnly or hidden fields
if ( $no_admin && $field->adminOnly ) {
$display_field = false;
} else if ( $no_hidden && RGFormsModel::get_input_type( $field ) == 'hidden' ) {
$display_field = false;
}
//if field is not supposed to be displayed, pass false to filter. otherwise, pass field's value
if ( ! $display_field ) {
$field_value = false;
}
$field_value = apply_filters( 'gform_merge_tag_filter', $field_value, $merge_tag, $modifiers, $field, $raw_field_value );
if ( $field_value === false ) {
continue;
}
if ( ! empty( $field_value ) || strlen( $field_value ) > 0 || $display_empty ) {
switch ( $format ) {
case 'text' :
//$field_data .= "{$field_label}: {$field_value}\n\n";
break;
default:
// $field_data .= sprintf(
// '<tr bgcolor="%3$s">
// <td colspan="2">
// <font style="font-family: sans-serif; font-size:12px;"><strong>%1$s</strong></font>
// </td>
// </tr>
// <tr bgcolor="%4$s">
// <td width="20">&nbsp;</td>
// <td>
// <font style="font-family: sans-serif; font-size:12px;">%2$s</font>
// </td>
// </tr>
// ', $field_label, empty( $field_value ) && strlen( $field_value ) == 0 ? '&nbsp;' : $field_value, apply_filters( 'gform_email_background_color_label', '#EAF2FA', $field, $lead ), apply_filters( 'gform_email_background_color_data', '#FFFFFF', $field, $lead )
// );
break;
}
$item = array(
'label' => $field_label,
'value' => $field_value,
'field' => $field
);
}
}
if( isset( $item ) ) {
$items[] = $item;
unset( $item );
}
}
if ( $display_product_summary ) {
$value = $this->all_fields_extra_options( GFCommon::get_submitted_pricing_fields( $form, $lead, $format, $use_text, $use_admin_label ), $merge_tag, $modifiers, 'order_summary', null );
if( $value !== false ) {
$items[] = array(
'label' => 'Order Summary',
'value' => $value,
);
}
}
return $items;
}
public function get_all_fields_field_value( $field, $value ) {
switch ( $field->type ) {
case 'html' :
$value = $field->content;
break;
// Sections are included by default; including them manually will append their description.
case 'section' :
$value .= sprintf( '<tr bgcolor="#FFFFFF">
<td width="20">&nbsp;</td>
<td>
<font style="font-family: sans-serif; font-size:12px;">%s</font>
</td>
</tr>
', $field->description );
break;
case 'signature' :
$url = is_callable( 'gf_signature' ) ? gf_signature()->get_signature_url( $value ) : $value;
$value = "<img alt='signature' src='{$url}' />";
break;
}
return $value;
}
public function log( $message ) {
GFCommon::log_debug( $message );
}
// ### TEMPLATE SYSTEM (compliments of EDD) ###
public function load_template( $slug, $name = null, $data = array(), $suffixes = array() ) {
ob_start();
extract( $data );
$template = $this->get_template_part( $slug, $name, false, $suffixes );
if( ! empty( $template ) ) {
include( $template );
}
$content = ob_get_clean();
return ! $template ? false : $content;
}
public function get_template_part( $slug, $name = null, $load = true, $suffixes = array() ) {
// Execute code for this part
do_action( 'get_template_part_' . $slug, $slug, $name, $suffixes );
// Setup possible parts
$templates = array();
if( isset( $name ) ) {
$suffixes[] = $name;
}
foreach( $suffixes as $suffix ) {
$templates[] = $slug . '-' . $suffix . '.php';
}
$templates[] = $slug . '.php';
// Return the part that is found
return $this->locate_template( $templates, $load, false );
}
public function locate_template( $template_names, $load = false, $require_once = true ) {
// No file found yet
$located = false;
// Try to find a template file
foreach ( (array) $template_names as $template_name ) {
// Continue if template is empty
if ( empty( $template_name ) )
continue;
// Trim off any slashes from the template name
$template_name = ltrim( $template_name, '/' );
// try locating this template file by looping through the template paths
foreach( $this->get_theme_template_paths() as $template_path ) {
if( file_exists( $template_path . $template_name ) ) {
$located = $template_path . $template_name;
break;
}
}
if( $located ) {
break;
}
}
if ( ( true == $load ) && ! empty( $located ) )
load_template( $located, $require_once );
return $located;
}
public function get_theme_template_paths() {
$template_dir = $this->get_theme_template_dir_name();
$file_paths = array(
1 => trailingslashit( get_stylesheet_directory() ) . $template_dir,
10 => trailingslashit( get_template_directory() ) . $template_dir
);
// sort the file paths based on priority
ksort( $file_paths, SORT_NUMERIC );
return array_map( 'trailingslashit', $file_paths );
}
public function get_theme_template_dir_name() {
return trailingslashit( 'gravity-forms' );
}
}
function gw_all_fields_template() {
return GW_All_Fields_Template::get_instance();
}
gw_all_fields_template();
view raw gw-gravity-forms-all-fields-template.php hosted with ❤ by GitHub

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 TagTemplate
{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 TagTemplate
{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 TagTemplate
{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 TagTemplate
{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.

Please note: you only need the plugin installed to use these modifiers. You do not need to install the template files in your theme.

Merge TagDescription
{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 TagDescription
{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:

<ul>
<?php foreach( $items as $item ): ?>
<li>
<strong><?php echo $item['label']; ?><strong><br>
<?php echo $item['value']; ?>
</li>
<?php endforeach; ?>
</ul>

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.

Did this resource help you do something awesome with Gravity Forms? Then you'll absolutely love Gravity Perks; a suite of 29+ essential add-ons for Gravity Forms with support you can count on.

Comments

  1. This could be a very valuable addition to the Gravity Forms toolkit, especially considering how conspicuously undeveloped this area of GForms seems to be.

    My initial obstacle in getting the modifications I need concerns display of “all fields.” In short, we have a complex field that combines multiple sub-fields to produce a total price. The default Order Summary does not display the prices of individual items, and the $items array used by your template doesn’t seem to contain any information about these fields whatsoever. However, when I do a var_dump of $items, the info that’s printed in the email is lacking in a number of ways, so I wonder whether some other logic is acting on the variable here.

    Which brings me to the second limitation: The only obvious way to get a preview of the notification is to re-submit it, then find the output in an email (or email log).

    The third initial issue is that, when I enable your plugin, one of two notifications – the one lacking the “all fields” tag – fails to send at all.

    So, I’m struggling here…

    Reply

    • Hi CK, this solution is pretty simple and provided as-is. Gravity Forms doesn’t provide a great way to replace the {all_fields} markup and provides even less support for replacing the order summary markup which is part of the {all_fields} markup. We’re certainly interested in improving this solution but it is, admittedly, a low priority.

      We don’t have a solution for previewing the notification either. That could be a big help. There are no known issues with this plugin interfering with emails being sent.

  2. Hi this looks exactly what I need, I can view the php and all I want to do is put a line break in for each section (it currently posts fine just <Strong> text for headers but no line or paragraph formatting. I’d just like the strong header and then the input then a line break for each section. Would this be difficult?

    Reply

  3. Hi David. As always, great stuff. Thank you.

    With this plugin, is there any way to show HTML fields if, within the form itself, they only show conditionally? In other words, is it possible to show them in them in the output only if they show in the form when completed by the user (whether they show depends on answers to prior questions)?

    Thanks Richard

    Reply

    • Hey Richard, this would require additional customization; it’s probably the desired default functionality and definitely a feature we would consider for a future version.

    • Thanks for the quick reply David. It’d be great if GF could do this in some shape or form. GravityPDF does it beautifully out of the box, and we can achieve a similar HTML output with GravityView. With GravityView, though, one needs to spend a lot of time configuring custom content outputs with conditional tags. The larger the form and conditional HTML fields, the larger this job becomes, and the more difficult it can get to keep the PDF and HTML outputs in sync. It would be awesome if GF could simply emulate what GravityPDF can do. We could then quickly show, through the all fields merge tag, only those form fields that have inputs (empty fields being ignored) and any HTML fields which show based on satisfaction with prior conditions. I can see many use cases for this. Anyway, perhaps wishful thinking for now, unless perhaps I have someone write a plugin for it. Do you think that would be a big job? Thanks.

    • You could feasibly use the conditional shortcode and multiple instances of a filtered {all_fields} merge tag. Sounds similar to what you’re doing with GravityView. Certainly wouldn’t be pretty…

      With that said, it wouldn’t be hard for someone to extend the All Fields Template plugin to support this.

    • David, I believe I’m in a similar boat to Richard here & wanted your thoughts. I have a pretty large multi-step form that has a lot of conditional formatting. Could I use this plugin with the conditional shortcode to build just 1 email notification that utilizes a custom template along with the all_fields merge tag to get my desired outcome? I don’t want to be maintaining different email notifications that are sent if a specific option is checked. I would prefer that they are all maintained within 1 notification.

      Thanks!

    • The short answer is yes. This gives you complete control over the output of the {all_fields} merge tag. As long as you comfortable working with basic PHP, you should be good to go. 🙂

  4. Thanks for your plugin! However, when I’m trying to change the wrapper of the table output..it’s doing nothing. Like want to remove the Form output border line or change its color to white. and want to move table to the left align with other text.

    Please advise.

    Reply

  5. Hello, We have a complex form with many HTML blocks that need to be seen or hidden conditionally in Notifications and Confirmations. The plugin is working to show the HTML fields in Notifications, however the template is not being applied. The notification just looks like a normal Gravity Forms notification with tables instead of UL/LI that is in the template. I tried putting it up in both the root of the child theme folder and in child-theme/gravity-forms/template/ . The plugin is not working at all for confirmations, no HTML fields, no template.

    Here’s the merge tag:

    {all_fields:include[88,105,106,107,109,110,111,115,136,160,161,162,165,166,167,168,169,170,171,172,173,174,175,177,178,179,180,182,184,185,186,187,188,190,191,192,193,195,197,198,209,210,211,212]}

    Do you have any thoughts on why this would happen?

    Thanks

    Reply

    • Hi Aaron, my local testing of this functionality is working as expected. I’m working with one user via support who is experiencing a similar issue as you. If I find out anything valuable while debugging, I’ll let you know.

    • Thank you, I tried disabling all other plugins and it still doesn’t work. I also tried using specific gravity forms merge tags combined with the filter option and disabling auto-formatting.

      Like this:

    • {:142:label}: {Is the outer surface peeling, flaking or cracking?:142}
      • {all_fields:filter[105,106]}

      The gravity forms specific merge tags obey the disable auto formatting option, but all_fields does not and gets formatted with the default values from gravity forms, not from the All Fields plugin template.

      I am on WordPress: 5.1.1 Genesis Framework 2.9.1 Child Theme Php Ver: 7.1.27 Mysql: 5.6.23-cll-lve

  6. Hi used the plugin works great, thank you as always though one thing the Address field moves the top line over to the right but the following lines of the address are indented to the left same with the ordersummary you can view a screen shot here https://pasteboard.co/HXWm95u.jpg.

    Not sure what to edit to change this cannot do it with css as there are just unamed spans any help appreciated REgards Alistair

    Reply

  7. What pet do you have? 1. Dog 2. Cat 3. Parrot 4. Other

    At the moment the email will just say: What pet do you have?: ‘3.Parrot’

    I need it to show: What pet do you have?: 1. Dog 2. Cat 3. Parrot (Selected) 4. Other

    Reply

    • Hi Fakhar, each $item has a field key which would have all of the choices: $item['field']->choices. You could loop through each choice and output the choice label and the “(Selected)” designator for the choice whose value matches the $item['value'].

  8. Hello,

    Thanks for providing this code. I have a rather specific scenario that I am dealing with which I wonder if you could help point me in the right direction.

    The form we are creating has a few HTML blocks in it which are making use of merge tags to fill in text from the users input. i.e. Dear Mr {Name:2.2}, we would like to inform you … etc.

    We are making use of https://gravitywiz.com/better-pre-submission-confirmation/ for this functionality.

    In the summary for {all_fields} we are including these HTML blocks so that the user can see what they have agreed to / filled in before submitting. The merge tags in this preview are not replaced with the form values.

    My question is, is there a way to convert the merge tags in this all_fields summary page? Is it then possible to submit these HTML blocks to the entry with the merge tags replaced with form values?

    Thanks very much

    Reply

    • Hi David. I thought that would be the case. Sleeping on it seems to have helped. Having returned to the problem to see if I could attack from a different angle, it now all just works™.

      So Good Job everyone! 👍

  9. Hi! I just downloaded the plug-in, but since I am not a programmer, I don´t understand the customization. I have created a form and the notification that the filler will get is too complicated. I would like to do it more simplier. Unfortunately I don´t understand tags and customizing the template at all.

    I have done the steps one and two. But now, I don’t have a clue, where I will do the customization. I don’t need to make the form different, I just want to have the form that will be send to the form filler in the notification. I can find the Styles and Layouts for the Gravity Forms, but I don’t have a clue, what I need to change to effect to the notification email. There is no that option.

    Reply

  10. Maybe I can use this plugin to solve my issue with the {all_fileds} merge tag? I have a form with various checkbox elements with various labels. Each label is set to the same value of “1”, but when I use the {all_fields} merge tag to preview the form or include the {all_fields} in a notification, because all the values are set to “1”, the output displays the first option label regardless of whether that is the option selected. Yes, I could set the value equal to the label, however I am summing the values to ensure that a minimum number of options are selected, hence them all having a value of 1. Is there a way around this where we can have the {all_fields} merge tag actually output the option label of the specific option and not the first one in the form field that has that (same) value?

    Reply

    • Hi Tyler, Gravity Forms uses the value to uniquely identify the choice. You will run into other issues like this if your choices do not have unique values.

  11. Your snippet here works really well, but a few pointers: – The template that you have made looks nice on the majority of email clients, but when it’s rendered in outlook for windows it’s getting butchered, doesn’t look right at all. – Email clients have come on a long way over the last couple of years, and now it’s pretty safe to use a style tag and classes throughout the document to style all elements, just avoid having multiple classes on elements as then outlook will ignore the extra classes.

    Reply

  12. Great tutorial David! Thanks!

    I was wondering if there’s a way to display specific items outside the loop. So let’s say I have made this simple template like you can see below. Is that something that’s possible?

    And is it possible to then loop through the nested forms data and do something you can see a bit further down? So looping through it with a ready made template?

    Cheers!

    Reply

    • Hi Peter, the short answer is yes, you can modify the template and output markup outside the loop. I’m not sure I understood the rest of your question?

  13. Hi David, thanks for this plug in. I have a form that all I want to do is wrap the phone number in an A tag with a tel: link to make the phone number clickable straight from the email. I’m a bit confused as to where this would be inputted in the all-fields.php file or if this is possible to do.

    Thanks! Chris

    Reply

  14. Hi. Thank you for the great tutorial. In my form I have created several steps. How can I display the fields by step and display the page name before the fields in each page? I would greatly appreciate any lead to improve the template.

    Reply

    • The fields are already in order of their pages and the pages are each represented by a field on the form. You’ll need to loop through and output special markup to wrap the fields by their respective pages.

  15. Thank you, David, for this excellent plugin and documentation.

    FYI, in case it helps anyone else, if all you want to do is exclude or include certain fields in the {all_fields} merge tag, just install the plugin. You don’t need to mess around with steps 2 or 3 in the above tutorial — i.e., no need to create the folder and upload the PHP file to your theme’s directory. I may be dense but it wasn’t obvious to me, and I messed around with it for a while before realizing that it was possible to simplify. :)

    Reply

  17. I would like to use this merge tag with the Nested Forms plugin in the manner described in the docs there. It is unclear from the documentation where I use as similar merge tag to the example {Players:1:filter[1]}. Also, it’s unclear what is specifically referenced by “Players.” Is this the title of the nested form?

    Reply

    • Hi Peter, “Players” refers to the field label of the Nested Form field that is on the parent form. The {Players:1:filter[1]}-style merge tag can be used anywhere that merge tags are supported in the scope of the parent form (notifications, confirmations, etc). Happy to answer any other questions you have via support. :)

  18. I do not know how to create a template, so I am just using from out of the box. Do I go to the editor and create a template there – any step-by-step instructions I’d appreciate particulary with screenshots! Sorry I’m not that saavy with coding…

    Reply

  19. Hello. I’ve used CSS to style my gravity form fields into 3 columns, BUT when I get a copy of the submitted form notification, it does not show the 3 columns (as it does online). Gravity Forms recommended that I reach out to you for help on this. I have downloaded your plugin, but I need more guidance on how to do this. Thanks.

    Reply

    • Hi Kat, I assume that you’re using a custom all fields template? If so, you’ll need to include your styles in the style attribute for each element. Most email clients will ignore a linked stylesheet or an inline style block.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.