Gravity Wiz

Magically enhanced tutorials, snippets and plugins for Gravity Forms!

  • Gravity Perks
    • Gravity Perks
    • Tutorials & Snippets
    • About
  • Support
    • Documentation
    • Support
    • Account

Gravity Forms Nested Forms

A Gravity Forms Repeater Addon for simple or more complex forms. Create forms within forms for better management of complex data collection. Formception!

This plugin is part of Gravity Perks, a suite of 31+ essential Gravity Forms addons with support you can count on.

  • View All Perks
  • Buy Gravity Perks

What does it do?

This plugin adds a new Nested Form field type. This field allows you to select another form that will be used to collect “child” entries and attach them to the “parent” entry on submission. The child entries display in a clean, compact table on the parent form where they can be viewed, edited or deleted.

Can this be used as a Gravity Forms Repeater?

Yes, it sure can! While Nested Forms can perform much more complex functionality, it can be used as a simple Gravity Forms Repeater as well. A repeater allows you to dynamically add additional fields to a Gravity Form. GF Nested Forms differs only in that it allows you to submit the group of repeating fields via a modal.

Features

  • Simplify Complex Forms & Collect Repeatable Data
    Create forms that are easier for you to manage and easier for your users to complete.
  • Register Groups and Individuals on the Same Form
    Register a team and players or a company and employees or a make and models all on the same form.
  • Use Sum, Total and Count in Calculations
    Pull data from your nested forms into your parent form for powerful, dynamic calculations.
  • Control the Look & Feel
    Helpful UI, flexible templating, and handy hooks.
  • Process Feeds for Child Entries
    On child form submission – or – only when the parent form is submitted; allows you to do things like register a user for each child entry. Insane!
  • Powerful Developer Options
    Well-documented hooks and a flexible templating system make extending this plugin a breeze.
  • Automatic Updates
    Get updates and the latest features right in your dashboard.
  • Awesome Support
    We’re here to help! And we mean it.

Documentation

  1. How do I enable this functionality?
  2. Feature Details
    1. Nested Form Field
      1. Field Settings
        1. Nested Form
        2. Summary Fields
        3. Entry Labels
        4. Modal Header Color
        5. Entry Limits
        6. Feed Processing
      2. On the Frontend
      3. On the Backend
    2. Child Entries
    3. The {Parent} Merge Tag
      1. Populate Child Form Fields with Parent Form Data
      2. Display Parent Data in Child Form Notifications
    4. Feed Processing
    5. Calculations
    6. Templating
      1. Available Templates
      2. Templating Hooks
    7. Exporting
  3. FAQs
    1. What happens to child entries when the parent entry is never submitted?
    2. How do I dynamically populate a Nested Form field?
    3. How to set a Nested Form as required?
    4. How do I include Nested Entry totals in the Parent Form total?
    5. Why are my child entries not counting towards the parent form’s total?
    6. How do I show a single value from each child entry?
    7. Why my Nested Form modal window (popup) is not displaying?
    8. Am I able to add a conditional field within the nested section?
  4. Known Limitations
  5. Hooks
  6. Related Articles

How do I enable this functionality?

After installing and activating Gravity Forms Nested Forms, you’ll want to add a Nested Form field to your form. Let’s step through that process.

Create two forms; a parent form and a child form. The child form will be “nested” in the parent form via the Nested Form field.
Add a Nested Form field on your parent form and select your child form in the Nested Form field setting.
Select which fields from the child form should be displayed in the Nested Form field on the parent form.

Now that you have your first Nested Form field, let’s dig into the specifics of its settings and how it can be configured.


Feature Details

Nested Form Field

Field Settings
Nested Form

Select the form that should be used to create nested entries for current form.

Summary Fields

Select which fields from the nested entry should be displayed in the table on the parent form.​​

Notes:

  • This setting only impacts which fields from the nested form appear on the parent form. The modal will always show all fields that belong to the child form.
  • This setting was previously called “Display Fields”.
Entry Labels

Specify a singular and plural label with which entries submitted via this field will be labeled (i.e. “player”, “players”).

Modal Header Color

Select a color which will be used to set the background color of the nested form modal header.

Entry Limits

Specify the minimum and maximum number of entries that can be submitted for this field.

Feed Processing

Specify when feeds attached to the nested form should be processed. By default, feeds attached to the nested form will be processed when the parent form is submitted. See Feed Processing for more details on this feature.


On the Frontend

By default, child entries will be displayed in a clean, compact table. Click the “Add” button to add a new child entry.

Nested Forms Modal with Default Gravity Forms Styles

The Display Fields selected in the field settings will be displayed for each submitted child entry. Child entries can be edited by clicking the “Edit” link and deleted by clicking the “Delete” link.

Nested Forms Entries with Default Gravity Forms Styles
On the Backend

The backend will also display the configured Display Fields for each child entry. To view the full child entry click the “View Entry” button. To view the child entries in the Gravity Forms list view, click the “View Expanded {Item} List” link.


Child Entries

Child entries are entries that are submitted via a Nested Form field. For examples of how child entries are displayed on the frontend and on the backend, see the respective section.

When a parent entry is trashed, its child entries will be trashed as well.

In order to protect the user from accidental data loss, child entries will be repopulated into the Nested Form field if the parent form is reloaded.


The {Parent} Merge Tag

The special {Parent} merge tag allows you to 1) populate data entered into the parent form into the child form and 2) populate data submitted on the parent entry in child form notifications.

Populate Child Form Fields with Parent Form Data

Any field on the child form that supports a default value can be populated via the {Parent} merge tag. Currently, you must manually specify the field/input ID from the parent form that should be populated into the child form. In the following example, we’ll populate the value of field ID 3 from the parent form into field ID 1 on the child form.

To populate multi-input fields (like the Name field), you will need to specify the input ID (which includes the field ID and the input index).

Here is a quick reference guide for the input indexes of common field types. The input ID will always use the FIELDID.INPUTID format. For example, a field ID of 2 and an input index of 3 would give you an input ID of 2.3.

All examples assume a field ID of 1.

Input Name Index Example
Name Field
Prefix 2 {Parent:1.2}
First 3 {Parent:1.3}
Middle 4 {Parent:1.4}
Last 6 {Parent:1.6}
Suffix 8 {Parent:1.8}
Address Field
Street Address 1 {Parent:1.1}
Address Line 2 2 {Parent:1.2}
City 3 {Parent:1.3}
State / Province 4 {Parent:1.4}
Zip / Postal Code 5 {Parent:1.5}
Country 6 {Parent:1.6}
Display Parent Data in Child Form Notifications

The {Parent} merge tag can also be used to display data from the parent entry in the notification send for a child entry. The desired entry property must be manually specified. For example, if you want to fetch the parent entry ID, you would use {Parent:id}. If you want to fetch the parent entry creation date, you would use {Parent:date_created}.

All properties of the entry object are supported. For a full list, see Gravity Forms’ Entry object documentation.


Feed Processing

By default, GF Nested Forms will only process feeds attached to the nested form after the parent form is submitted.

A practical example of this would be a parent form that creates a team and a nested form that uses the User Registration to register players. In most cases, you wouldn’t want the user accounts created for the players until the team submission has been finalized. GF Nested Forms handles this for you automatically.

In some cases, you may want to trigger the nested form feed to be processed when the nested form is submitted (e.g. collecting emails for a mailing list via MailChimp). To do this, use this snippet to enable the advanced Feed Processing setting:

add_filter( 'gpnf_enable_feed_processing_setting', '__return_true' );

And then select, “nested form” in the select.

A child entry is always created from a child form submission. The Feed Processing setting does not impact this behavior.

For even more granular control over when nested feeds are processed, use the gpnf_should_process_feed filter.


Calculations

GF Nested Forms provides support for using Nested Form fields in your Gravity Forms calculations. To use a Nested Form field in your calculation formula, you will need to manually type the desired merge tag using the following template:

{FIELD_LABEL:FIELD_ID:MODIFIER}

To include your child entry totals in your parent form’s total, see our simple walkthrough.

The following examples are based on a field label of “Players” and a field ID of “1”.

  • count – Returns the total number of child entries attached to the Nested Form field. If there are two child entries submitted for a Nested Form field, this merge tag would return 2.

    {Players:1:count}

  • total – Returns the sum of all child entry totals. For example, if Child Entry #1 has a total of $10 and Child Entry #2 has a total of $25, this merge tag would return 35.

    {Players:1:total}

  • sum – Returns the sum of the specified target field’s value from each child entry. For example, you had a Quantity field with an ID of “2” on your nested form and Child Entry #1 had a quantity of 2 and Child Entry #2 had a quantity of 3, this merge tag would return 5.

    {Players:1:sum=2}


Templating

You can take complete control over the Nested Form field output via the templating system. To do so, you will need to copy the template files from the plugin to your theme.

In the plugin, they’re located in the templates directory:

<WordPress plugins>/gp-nested-forms/templates

In your theme, you will need to create a directory named gp-nested-forms and copy the template files there:

<WordPress themes>/your-theme/gp-nested-forms/

Now anytime GF Nested Forms attempts to load a template file, it will pull your version of the template file from your theme.

Available Templates
  • nested-entries.php – Used to render the child entries in a Nested Form field on the frontend.
  • nested-entries-detail.php – Used to render the child entries on the entry detail page (in the Gravity Forms backend).
  • nested-entries-simple-list.php – Used to render a single value from each child entry in a simple list format when the Nested Form field merge tag (or {all_fields} merge tag) is filtered to a single field via the All Fields Template plugin (e.g., {Players:1:filtered[2]}).
  • nested-entry.php – Used to render a single child entry via the Nested Form field merge tag (e.g. {Players:1} – or – when a Nested Form field is rendered via the {all_fields} merge tag.
Templating Hooks

To make minor changes to verbiage or customize the data that will be used to render the Nested Form field, use the gpnf_template_args filter.


Exporting

Child entries can be exported together with their parent entry. Select the parent form on the Export Entries page and select the child fields you want to export alongside the parent entry. For more details, see our tutorial on Exporting with Nested Forms.


FAQs

What happens to child entries when the parent entry is never submitted?

Child entries with no parent entry are called orphaned entries. Orphaned entries are considered “expired” after a week. Expired entries are trashed daily. To modify how long orphaned entries should be preserved, use the gpnf_expiration_modifier filter.

If the user returns the form, their orphaned child entries will be repopulated into the Nested Form field.

How do I dynamically populate a Nested Form field?

Nested Form fields can be dynamically populated the same way as other Gravity Forms fields. Nested Form fields expect a comma-delimited list of entry IDs for the dynamic population value.

How to set a Nested Form as required?

To set a Nested Form as required, go to the Advanced tab of the field options window and set the Minimum field to “1” in the Entry Limits option.

How do I include Nested Entry totals in the Parent Form total?

We’ll need to include a Calculated Product field on the parent form to capture the entry totals for each nested entry and automatically apply those totals towards the Parent Forms total. Here’s how to set this up in three, quick steps.

Add a Product field to your parent form.
Set the “Field Type” setting to “Calculation” and check the “Disable quantity field” checkbox.
Manually enter the Nested Form field merge tag into the “Formula” setting and append the “:total” modifier.

The Nested Form field merge tag is not yet available in the merge tag list. Just add {:1:total} where “1” is the ID of your Nested Form field on your parent form.

All done! See the demo at top of this page to see this live.

Why are my child entries not counting towards the parent form’s total?

You must explicitly include child entry totals in your parent form via a Calculated Product field. See this walkthrough.

How do I show a single value from each child entry?

First, you’ll need to install our All Fields Template plugin. This provides the ability to filter which fields from the nested form are displayed in the Nested Form field’s merge tag (and {all_fields}).

Once installed, you can filter down to a specific field like so:

{Players:1:filter[1]}

Based on our demo form, this would display a simple list of the Player’s names.

Why my Nested Form modal window (popup) is not displaying?

An element with a larger z-index generally covers an element with a lower one. So if your theme has a larger z-index specified, it’ll cover the modal window from the Nested Forms field. The solution in this case is to specify a larger z-index number for the Nested Form modal window, like this: .gpnf-dialog.ui-dialog { z-index: 99999999 !important; }

Am I able to add a conditional field within the nested section?

Yup! A child form can use any of Gravity Forms core features, including conditional logic.


Known Limitations

  • You may not include a Nested Form field within a nested form.
  • You may not display a form independently if it is nested inside of a Nested Form field on the same page.
  • Mobile support is lacking; we are working on improvements for v1.0.
  • Payment feeds will not be processed on child forms.
  • By default, child notifications are sent regardless of the parent entry’s payment status. To delay child notifications until the parent entry has been paid, use this snippet.

Hooks

  • gpnf_bypass_entry_permissions
  • gpnf_can_user_edit_entry
  • gpnf_disable_export_fields
  • gpnf_display_value
  • gpnf_entry_url
  • gpnf_expiration_modifier
  • gpnf_export_child_field_header
  • gpnf_init_script_args
  • gpnf_item_labels
  • gpnf_jquery_ui_dependencies
  • gpnf_parent_merge_tag_value
  • gpnf_should_process_feed
  • gpnf_should_send_notification
  • gpnf_template_args
  • gpnf_use_jquery_ui

Related Articles

  • Register Multiple Users From a Single Form
  • Exporting with Nested Forms

Perk Deets

  • Version 1.0-beta-8.16
  • Updated November 19, 2019
  • Released December 25, 2017
  • View Changelog

Changelog

1.0-beta-8.16

  • Fixed issue where max entry limit message was not translatable.

1.0-beta-8.15

  • Updated GP_Nested_Forms::get_fields_by_ids() method to return the fields in order of the field IDs passed.

1.0-beta-8.14

  • Added support for Partial Entries add-on.

1.0-beta-8.13

  • Fixed issue where GF Encrypted Fields was removing child entry meta resulting in child entries that were not property connected with their parent.

1.0-beta-8.12

  • Fixed issue where using global namespace removed events from previously initialized instances of Nested Forms.

1.0-beta-8.11

  • Fixed various issues with AJAX-enabled forms. (#14)

1.0-beta-8.10

  • Fixed issue where Post Category fields would not be re-populated with the correct value when editing a child entry.

1.0-beta-8.9

  • Fixed issue where the GPNF session cookie wouldn't be properly reset after editing a form with Nested Form fields in a GravityView.
  • Fixed issue where child entries added when editing an entry with a GravityView view would not be assigned to the parent form.

1.0-beta-8.8

  • Fixed issue where {Parent} merge tag wouldn't work on certain multi-page forms.

1.0-beta-8.7

  • Fixed issue where some strings displayed in the child form modal were not localized.

1.0-beta-8.6

  • Fixed issue where AJAX-enabled parent forms caused modal to fail to close after submitting a child form.
  • Fixed issue where {Parent} merge tag wouldn't work in some cases.

1.0-beta-8.5

  • Fixed potential recursion with handle_nested_forms_markup filter.

1.0-beta-8.4

  • Fixed issue where deleting a child entry from from the modal's delete button failed to delete the child entry.

1.0-beta-8.3

  • Updated Nested Forms field value method to ignore entries with alphanumeric IDs.

1.1

  • Fixed issue where new method for retrieving Nested Form field value dynamically incorrectly returned all child entries for a parent entry rather than only the child entries for the current Nested Form field.

1.0

  • Added support for auto-resizing modal when window is resized.
  • Added responsive styling for Nested Form field.
  • Updated acceptance tests to work with tingle. Added export entries test.
  • Updated font size of modal header.
  • Fixed notice generated by undeclared $entry_ids variable in entry limit validation.
  • Fixed issue where modal content was hidden incorrectly when two of the same child form existed on the page.
  • Fixed UX issue where modal buttons were re-initialized on the modal confirmation page, creating a flicker on the submit button as the spinner was replaced with the submit button text.

1.0-beta-8.2

  • Fixed regression with {Parent} merge tag when using the new responsive UI.

1.0-beta-8.1

  • Fixed issue where new method for retrieving Nested Form field value dynamically incorrectly returned all child entries for a parent entry rather than only the child entries for the current Nested Form field.

1.0-beta-8

  • Added full integration with GravityView.
  • Added support for exporting child entries alongside their parent entry.
  • Added resopnsive styling and implemented a new modal experience.
  • Added 'gpnf_entry_limit_min' and 'gpnf_entry_limit_max' WordPress filters.
  • Added merge tag modifiers to merge tag selector for calculation-enabled fields.
  • Added message when max entry limit is reached.
  • Added security enhancement.
  • Added is_gravityview() helper method.
  • Added support for admins and users with the 'gravityforms_edit_entries' capability to edit nested entries on the front end created by other users
  • Added nested-entries-count.php template. This is a new template that can be used to display the count of child entries in a parent entries.
  • Added support for changing modal spinner via Gravity Forms' "gform_ajax_spinner_url" filter.
  • Added gpnf_disable_export_fields filter to allow disabling the addition of child form fields to the parent form export settings.
  • Updated Nested Form field value handling.
  • Updated GravityView integration to use the count template for views and the simple template on single entry pages.
  • Fixed issue where query parameters were not populated correctly when editing child entries.
  • Fixed issue where Delete and Cancel buttons would show in Nested Forms on GravityView edit views.
  • Fixed conflict with Preview Confirmation where psuedo-entry without a proper entry ID would return child entries that did not belong to the psuedo-entry.
  • Fixed issue where extra lines were being added to parent export when no child fields were selected.
  • Removed feed processing setting to alleviate confusion.

1.0-beta-7.28

  • Fixed issue where extra lines were being added to parent export when no child fields were selected.

1.0-beta-7.27

  • Fixed conflict with Preview Confirmation where psuedo-entry without a proper entry ID would return child entries that did not belong to the psuedo-entry.

1.0-beta-7.26

  • Added gpnf_disable_export_fields filter to allow disabling the addition of child form fields to the parent form export settings.

1.0-beta-7.25

  • Added support for changing modal spinner via Gravity Forms' "gform_ajax_spinner_url" filter.
  • Improved Nested Form Field value handling.

1.0-beta-7.24

  • Added security enhancement.
  • Added is_gravityview() helper method.
  • Updated GravityView integration to use the count template for views and the simple template on single entry pages.
  • Added nested-entries-count.php template. This is a new template that can be used to display the count of child entries in a parent entries.
  • Fixed issue where Delete and Cancel buttons would show in Nested Forms on GravityView edit views.
  • Added support for admins and users with the 'gravityforms_edit_entries' capability to edit nested entries on the front end created by other users

1.0-beta-7.23

  • Fixed issue where query parameters were not populated correctly when editing child entries.
  • Added 'gpnf_entry_limit_max' JS filter.
  • Added 'gpnf_entry_limit_min' and 'gpnf_entry_limit_max' WordPress filters.

1.0-beta-7.22

  • Added support for exporting child entries alongside their parent entry. (#11)
  • Added "gpnf_enable_feed_processing_setting" to re-enable.
  • Added support for exporting child entries along side their parent entry.

1.0-beta-7.21

  • Fixed issue when rendering child entries which contained sections with conditional logic.
  • Fixed issue where maximum entries met message would be shown in the form editor at all times.
  • Updated session script to be part of the GPNestedForms class.
  • Added message beside submit button if maximum number of entries is met.
  • Added count, total, and sum merge tags to merge tag selectors including the merge tag dropdown for calculations.
  • Added support for Nested Forms on GravityView edit pages.
  • Added count, total, and sum merge tags to merge tag selectors including the merge tag dropdown for calculations.
  • Added support for Nested Forms on GravityView edit pages.
  • Fixed issue where deleting parent entries would not result in the child entries being deleted.

1.0-beta-7.20

  • Updated {Parent} merge tag to be replaced with an empty string when loading a form outside of a Nested Form field.

1.0-beta-7.19

  • Added "gpnf_can_user_edit_entry" filter to better support overriding entry permissions when viewing, editing, and deleting entries in Nested Forms fields.

1.0-beta-7.18

  • Added support for using Nested Forms in WordPress admin.

1.0-beta-7.17

  • Fixed error generated when {Parent} merge tag was called in a context where parent entry was expected but did not exist (i.e. child form notifications).

1.0-beta-7.16

  • Fixed issue where child entry created_by property did not match that of its parent when a non-logged-in user registered via the parent form.

1.0-beta-7.15

  • Fixed issue with ACF where Limit Submission's version of select2 was loaded instead of its own.
  • Fixed notices generated when Nested Form field does not have a nested form selected.

1.0-beta-7.14

  • Added "gpnf_parent_merge_tag_value" filter to allow modify the value of the parent merge tag before it is replaced.

1.0-beta-7.13

  • Fixed issue where product cache was not refreshed correctly.

1.0-beta-7.12

  • Fixed issue where incorrect child from was refreshed after adding, editing or deleting an entry when multiple Nested Form fields existed on a parent form.

1.0-beta-7.11

  • Added two new filters: ‘gpnf_process_feeds_nested_entries’ and ‘gpnf_process_feeds_nested_form’
  • Added gp_nested_forms()->get_nested_form() helper method
  • Fixed issue where the raw value of some fields including fields with dynamic choices from GP Populate Anything would be used instead of the choice text/label.

1.0-beta-7.10

  • Fixed fatal error generated by trashing a parent entry after child entry has been permanently deleted.
  • Fixed issue where <hr> in All Fields markup were incorrectly visible in some mail clients.

1.0-beta-7.9

  • Fixed issue where close button was not styled property in Safari on mobile devices.

1.0-beta-7.8

  • Fixed issue where values of GPPA-populated choice-based fields were not correctly displayed in the Nested Form field on the entry detail view.

1.0-beta-7.7

  • Fixed issue where {Parent} merge tag did not correctly populate from Radio Button fields.
  • Updated plugin author.

1.0-beta-7.6

  • Added support for scrolling back to original page position after closing modal; impacts long child forms, particularly on mobile.
  • Added support for formatting {all_fields} value for text. Requires Gravity Forms 2.4.8.12 or greater.

1.0-beta-7.5

  • Updated how markup for Nested Form field merge tags (individually and in {all_fields}) is generated.
  • Added "nested-entries-all" template to allow overriding the the markup generated for Nested Form field merge tags (individually and in {all_fields}).
  • Updated Display Fields setting name to "Summary Fields" and improved description to alleviate customer confusion on its purpose.

1.0-beta-7.4

  • Updated check for WooCommerce to be more comprehensive.

1.0-beta-7.3

  • Updated Nested Forms markup to always be output in the footer; resolves an on-going issue with the WC GF Product Add-ons plugin.
  • Added a simplified Nested Entries Detail template; will be automatically used when a Nested Form field is displayed in a WooCommerce cart or on Gravity Forms' Print Entry view.

1.0-beta-7.2

  • Fixed JS error generated when Beaver Builder triggers document ready event without having reloaded the UI.

1.0-beta-7.1

  • Added support for handling change in Gravity Forms 2.4.7 which adds support for wrapping GF's inline scripts in DOMContentLoaded listener.
  • Updated minimum Gravity Forms version to 2.4.
  • Updated logging for cron events to be more helpful.
  • Fixed issue where modal was not visible when other elements on page had a higher z-index.
  • Fixed issue where datepicker inside modal was displayed behind modal due to z-index conflict.

1.0-beta-7

  • Added "gpnf_session_script_data" filter to allow modifying the data used to initialize the session script.
  • Added support for automatically populating fields from session cookie when refreshing the form markup.
  • Added logging around daily cron that cleans up orphaned entries.
  • Added basic responsive fix to prevent Nested Entries table from spilling outside container on mobile.
  • Added support for gpnf_bypass_entry_permissions filter to allow advanced users to determine if entry permissions should be bypassed when populating entries into a Nested Form field.
  • Updated child form feeds to be processed after parent form feeds when configured to be processed when the parent form is submitted.
  • Updated Nested Entries Detail template to no longer output "View Entry" or "View Expanded List" when in print view.
  • Updated parent entry processing to run child form through gform_pre_process filter to improve compatibility with 3rd party add-ons.
  • Updated "gpnf_append_nested_forms_to_footer" to default to true if "gform_init_scripts_footer" is set to true.
  • Updated priority of GP_Nested_Forms::output_nested_forms_markup() to 21 to ensure it is output after jQuery.
  • Updated session cookie with COOKIEPATH, COOKIE_DOMAIN, and secure flag.
  • Updated cookies to use COOKIE_DOMAIN constant for consistency with WordPress.
  • Updated gpnf_template_args docblock with addition of the "actions" property and removal of the "related_entries_link" property.
  • Fixed issue where close button does not appear when Bootstrap is loaded after jQuery UI.
  • Fixed notice when form mapped in Nested Form field no longer exists.
  • Fixed issue where child entries were not editable and failed to persist when navigating between pages after being populated via Save & Continue.
  • Fixed use of deprecated GFFormsModel::get_incomplete_submission_values() method.
  • Fixed issue where Print Entry view displayed "&nbsp".
  • Fixed issue where perk name was not output on Logging page.
  • Fixed issue where {Parent} merge tag was case sensitive.
  • Fixed issue where modal header color setting was not saved correctly.
  • Fixed issue where Nested Form fields on different forms loaded on the same page did not initialize correctly.
  • Fixed JS error when attempting to repopulate entries between AJAX-enabled page submissions.
  • Fixed issue where field ID was not respected when fetching submitted nested entries.
  • Fixed issue where :sum merge tag was not working correctly on AJAX-enabled forms with multiple Nested Form fields.
  • Fixed notice generated by attempting to access $form as an object.
  • Fixed security issue where arbitrary entry data could be viewed in a Nested Form field.
  • Fixed up {Parent} merge tag to work with paginated child forms
  • Fixed issue where saving Nested Form field without fields in the Form Editor would cause a PHP notice/error
  • Fixed issue where multiple "other" choices were added when including multiple instances of the same child form.
  • Fixed issue where the Multi-file Upload field's delete icon returned a 404 when displayed in a nested form.
  • Fixed issue where adding an image to a Multi-field Upload field on a nested form did not correctly save the image when editing a child entry.
  • Fixed issue where {Parent} did not reevaluate conditional logic when value changed.
  • Fixed issue where AJAX-enabled forms still broke Nested-Forms-based calculations.
  • Fixed issues with calculations and saving entries when AJAX was enabled on parent form.
  • Fixed issue where parent merge tag replacement broke routing in notifications.

1.0-beta-6.24

  • Fixed issue where close button does not appear when Bootstrap is loaded after jQuery UI.
  • Fixed notice when form mapped in Nested Form field no longer exists.

1.0-beta-6.23

  • Fixed issue where child entries were not editable and failed to persist when navigating between pages after being populated via Save & Continue.

1.0-beta-6.22

  • Updated Nested Entries Detail template to no longer output "View Entry" or "View Expanded List" when in print view.
  • Fixed use of deprecated GFFormsModel::get_incomplete_submission_values() method.
  • Fixed issue where Print Entry view displayed "&nbsp".

1.0-beta-6.21

  • Updated parent entry processing to run child form through gform_pre_process filter to improve compatibility with 3rd party add-ons.

1.0-beta-6.20

  • Fixed issue where perk name was not output on Logging page.

1.0-beta-6.19

  • Added logging around daily cron that cleans up orphaned entries.

1.0-beta-6.18

  • Fixed issue where {Parent} merge tag was case sensitive.

1.0-beta-6.17

  • Fixed issue where modal header color setting was not saved correctly.

1.0-beta-6.16

  • Added support for automatically populating fields from session cookie when refreshing the form markup.

1.0-beta-6.15

  • Fixed issue where Nested Form fields on different forms loaded on the same page did not initialize correctly.
  • Updated "gpnf_append_nested_forms_to_footer" to default to true if "gform_init_scripts_footer" is set to true.
  • Updated priority of GP_Nested_Forms::output_nested_forms_markup() to 21 to ensure it is output after jQuery.
  • Updated session cookie with COOKIEPATH, COOKIE_DOMAIN, and secure flag.

1.0-beta-6.14

  • Updated cookies to use COOKIE_DOMAIN constant for consistency with WordPress.

1.0-beta-6.13

  • Added "gpnf_session_script_data" filter to allow modifying the data used to initialize the session script.

1.0-beta-6.12

  • Added basic responsive fix to prevent Nested Entries table from spilling outside container on mobile.

1.0-beta-6.11

  • Fixed JS error when attempting to repopulate entries between AJAX-enabled page submissions.

1.0-beta-6.10

  • Fixed issue where field ID was not respected when fetching submitted nested entries.

1.0-beta-6.9

  • Fixed issue where :sum merge tag was not working correctly on AJAX-enabled forms with multiple Nested Form fields.
  • Fixed notice generated by attempting to access $form as an object.

1.0-beta-6.8

  • Fixed security issue where arbitrary entry data could be viewed in a Nested Form field.
  • Added support for gpnf_bypass_entry_permissions filter to allow advanced users to determine if entry permissions should be bypassed when populating entries into a Nested Form field.
  • Updated gpnf_template_args docblock with addition of the "actions" property and removal of the "related_entries_link" property.

1.0-beta-6.7

  • Fixed up {Parent:__} merge tag to work with paginated child forms
  • Fixed issue where saving Nested Form field without fields in the Form Editor would cause a PHP notice/error

1.0-beta-6.6

  • Fixed issue where multiple "other" choices were added when including multiple instances of the same child form.

1.0-beta-6.5

  • Fixed issue where the Multi-file Upload field's delete icon returned a 404 when displayed in a nested form.
  • Fixed issue where adding an image to a Multi-field Upload field on a nested form did not correctly save the image when editing a child entry.

1.0-beta-6.4

  • Fixed issue where {Parent:1} did not reevaluate conditional logic when value changed.

1.0-beta-6.3

  • Fixed issue where AJAX-enabled forms still broke Nested-Forms-based calculations.

1.0-beta-6.2

  • Fixed issues with calculations and saving entries when AJAX was enabled on parent form.
  • Fixed issue where parent merge tag replacement broke routing in notifications.

1.0-beta-6.1

  • Fixed issue where parent merge tag replacement broke routing in notifications.

1.0-beta-6

  • Added support for {Parent} merge tag which allows populating child form inputs with data from the parent form.

1.0-beta-5.17

  • Updated Zapier integration so child entry feeds are always processed after parent form feed.
  • Updated field container selector to target only by id rather than element + id.

1.0-beta-5.16

  • Fixed issue where child entries were not editable/deletable when making https AJAX request from http URL.

1.0-beta-5.15

  • Fixed issue where entry total was not updated when editing via Nested Form field.

1.0-beta-5.14

  • Fixed security issues.

1.0-beta-5.13

  • Updated feed processing to only filter feeds when an entry has been created; allows feed validation to still process.

1.0-beta-5.12

  • Updated session init script to be output very late in the footer to allow footer-enqueued jQuery to load first.

1.0-beta-5.11

  • Updated name of Gravity Forms filter included in 1.0-beta-5.10 to its updated version.

1.0-beta-5.10

  • Fixed issue where updating an entry would fail to save some values depending on how conditional logic was configured.

1.0-beta-5.9

  • Fixed issue where dynamically populated and Save & Continue child entries were incorrectly prevented from loading in a Nested Form field.

1.0-beta-5.8

  • Added support for script minification.
    • Fixed issue where false entry values were output as a string (i.e. "false") rather than empty in Nested Form field.

1.0-beta-5.7

  • Fixed issue with List field values containing commas being incorrectly split up when populating child form for editing.

1.0-beta-5.6

  • Added security enhancement to better protect viewing/editing/deleting child entries on the frontend.

1.0-beta-5.5

  • Fixed additional issues related to missing modal close button caused by other themes/plugins.
  • Added 'gpnf_jquery_ui_dependencies' filter to allow 3rd parties to add their own dependencies for jQuery UI.

1.0-beta-5.4

  • Fixed issue introduced by modal close button fix in 1.0-beta-5.2.

1.0-beta-5.3

  • Added support for label placement setting on Nested Form field.

1.0-beta-5.2

  • Fixed issue where modal close button is missing when Bootstrap is loaded after jQuery UI.
  • Added support for displaying additional entry actions in the Nested Form Detail view.
  • Updated notification processing to only surpress notifications of the "form_submission" event.

1.0-beta-5

  • Fixed major issue where unorphaned child entries were deleted during orphaned entry cleanup.

1.0-beta-4.26

  • Fixed JS error that appeared when parent form contained Nested Form field with an administrative visibility.

1.0-beta-4.25

  • Updated integration with All Fields Template (v0.9.2) to better support filtering child form fields within merge tags.

1.0-beta-4.24

  • Updated get_entry_display_values() to support returning all entry display values (rather than only the selected display fields).

1.0-beta-4.23

  • Fixed issue where No Duplicates validation was enforced when editing a child entry.

1.0-beta-4.22

  • Fixed issue where when refreshing the Nested Form markup, GF was ignoring the isSelected property of choices in favor of determining the selected status based on non-existant post values.

1.0-beta-4.21

  • Fixed fatal error when attempting to delete a parent entry.

1.0-beta-4.20

  • Fixed issue where Nested Form fields were not correctly populated via User Registration Update feeds.

1.0-beta-4.19

  • Fixed issue with :sum calc modifier where one or more child entries did not contain a value for the target field ID.

1.0-beta-4.18

  • Added support for GF Zapier.

1.0-beta-4.17

  • Updated to use minimum_requirements() method for declaring minimum requirements.

1.0-beta-4.16

  • Added 'gpnf_entry_url' filter to allow filtering the entry URL when linking to child entries.
  • Fixed issue with :sum calculation modifier when target field ID was not present in child entry.

1.0-beta-4.15

  • Added support for integrating with GF Preview Submission.

1.0-beta-4.14

  • Fixed issues with translation support.

1.0-beta-4.13

  • Fixed issue where :total, :count, and :sum calculation modifiers included child entries from ALL Nested Form fields.

1.0-beta-4.12

  • Added integration with GW All Field Template to allow filtering which fields display from the nested form when displaying the Nested Form field value.
  • Added support for displaying a simple list of nested entry values when filtered for a single field.
  • Added support for 'nested-entries-simple-list' and 'nested-entry' templates.

1.0-beta-4.11

  • Fixed issue where Feed Processing field setting did not have a default value so feeds were not sent in either context (child/parent).

1.0-beta-4.10

  • Changed child form notifications to not be sent until the parent form is submitted.
  • Added 'gpnf_should_send_notification' filter.
  • Added support for populating child entries in request data for GF Webhooks Add-on.

1.0-beta-4.9

  • Nested form is now refreshed after adding or deleting entries.

1.0-beta-4.8

  • Fixed JS error caused by session initialization when parent form was AJAX-enabled.

1.0-beta-4.7

  • Refactored event reprioritization; new method lovingly dubbed, "The Event Handler".

1.0-beta-4.6

  • Added support for displaying labels instead of values for choice-based fields (preserving the ability to use values in calculations).
  • Fixed issue where ":sum" calculations were not calculated correctly on submission.
  • Fixed issue where some 3rd party add-ons caused nested form markup to be output multiple times.

1.0-beta-4.5

  • Fixed issue where only the first Nested Form field on a page had markup; template was set to require once.

1.0-beta-4.4

  • Fixed issue where View Entry links displayed outside admin resulted in 404s.

1.0-beta-4.3

  • Updated minimum required version of Gravity Forms to 2.3-beta-1.
  • Fixed issue where Nested Form JS data was not always available depending on how 3rd party scripts bound to the gform_post_render JS event.
  • Fixed issue where repositioning modal when the modal height exceeded the window height would jump up to the modal header.

1.0-beta-4.2

  • Updated field to not show up in conditional logic for other fields.

1.0-beta-4.1

  • Rewrote the GP_Template class.

1.0.beta3.12

  • Updated modal responsiveness.

1.0.beta3.11

  • Updated modal styles to be enqueued (rather than hardcoded)

1.0.beta3.9

  • Fixed issue where child entries were not populated when resuming a saved entry (via GF's Save & Continue feature)

1.0.beta3.8

  • Updated modal size to dynamically adjust to be 40 pixels smaller than the document size; primarily benefits mobile usage

1.0.beta3.7

  • Fixed issue where if multiple nested form fields were using the same child form, the first field would be updated with entries submitted from any other nested form field mapped to the same child form.

1.0.beta3.6

  • Fixed issue where Nested Form field's "Add Entry" button was being triggered when pressing enter within another field

1.0.beta3.5

  • Added JS hook for modify the arguments used to initailize the nested form modal: gpnf_modal_args
  • Added PHP hook for modifying the display value of child entry values in the parent form: gpnf_display_value
  • Miscellaneous cleanup items.

1.0.beta3.4

  • Fixed issue where child forms with conditional logic did not display when editing a child entry

1.0.beta3.3

  • Added support for repop of List fields when editing a child entry

1.0.beta3.2

  • Fixed JS error on confirmation page for AJAX-enabled forms; caused by KO bindings being applied twice

1.0.beta3.1

  • Fixed issue where non-logged-in users could not edit their nested entries
  • Fixed issue where multi-input fields were not repopulated for editing

1.0.beta3.0

  • Added support for parent forms with AJAX-enabled
  • Added translation support
  • Fixed notices generated when no nested fields have been selected via the field settings

1.0.beta2.3

  • Fixed issue where navigating to the previous page in a multi-page nested form would break the nested form submission flow (and entry was not captured in parent form)

1.0.beta2.2

  • Fixed issue with usage of jQuery.clone(); replaced with jQuery.extend().

1.0.beta2.1

  • Fix for IE8 recursive loop issue

1.0.beta2.0

  • Updated jQuery UI stylesheet URL to be protocol-less to better work with secure sites
  • Fixed several notices
  • Fixed several coding standards violations

1.0beta.1.3

  • Updated frontend to support HTML values rather than simply TEXT (allows currency symbols to be shown)
  • Updated get_entry_display_values() method to get the display value
  • Fixed error on entry detail edit where input HTML function was not called correctly resulting in a "Method GFField::input_html() must be over-ridden in a sub-class." error.
  • Removed documentation link to Terms of Service perk (will replace once real documentation is written)

1.0.beta1.2

  • Fixed issue where "Total" field did not update when nested entry was edited

1.0.beta1.1

  • Added support for displaying all child entry values in {all_fields} merge tag (previously showed comma-delimited list of child entry IDs)

1.0.alpha3.3

  • Fixed issue where gformInitDatepicker was not found and generated error

All Perks

  • GF Auto Login
  • GF Better User Activation
  • GF Blacklist
  • GF Conditional Logic Dates
  • GF Conditional Pricing
  • GF Copy Cat
  • GF Date Time Calculator
  • GF Disable Entry Creation
  • GF Easy Passthrough
  • GF eCommerce Fields
  • GF Email Users
  • GF Expand Textareas
  • GF Limit Checkboxes
  • GF Limit Choices
  • GF Limit Dates
  • GF Limit Submissions
  • GF Live Preview
  • GF Media Library
  • GF Multi-Page Navigation
  • GF Nested Forms
  • GF Pay Per Word
  • GF PayPal One-time Fee
  • GF Placeholder
  • GF Populate Anything
  • GF Post Content Merge Tags
  • GF Preview Submission
  • GF Price Range
  • GF Read Only
  • GF Reload Form
  • GF Terms Of Service
  • GF Unique ID
  • GF Word Count

Copyright © 2019 · Powered by WordPress · Gravity Wiz LLC · Log out

  • Support
  • Affiliates
  • About
  • Sitemap
  • Gravity Perks
    ▼
    • Gravity Perks
    • Tutorials & Snippets
    • About
  • Support
    ▼
    • Documentation
    • Support
    • Account