Gravity Perks – Nested Forms - V1.1.46
Categories
Changelog
Support
Blog
Membership
Login/Register
![]()
Checkout
({{ cartItems }})
Cart
{{ product.name }}
USD {{ product.price }}
Language
Overview
- Updated how we ensure `GFFormDisplay` is loaded when printing entries to also prevent the error when printing with Gravity Flow and other add-ons.- Fixed issue where "Honeypot validation" enabled for nested child forms could cause the child form submission to fail in certain cases.
Improved reliability of skipping initialization of Nested Form fields on pages that are hidden in forms with conditional logic.
Updated CSS styles for Row Actions on small screen sizes.
- Added German translations. Credit: Florian Rinnhofer of sportunion.at- Fixed issue where the Knockout instance would not be properly re-used on AJAX forms.
- Fixed `{Parent:id}` merge tag not working in places such as notifications.- Added `$entry` argument to `gpnf_get_nested_form` filter hook to improve compatibility with GP Populate Anything.
- Fixed an issue where the session cookie could become oversized on complex multi-page forms and result in a server error.- Added new [`gpnf_calc_entries`](https://gravitywiz.com/gpnf_calc_entries) and [`gpnf_calc_replacement_value`](https://gravitywiz.com/gpnf_calc_replacement_value) filter hooks.
Fixed issue with :sum and :total merge tag modifiers where they would not calculate very small float values due to them being converted to scientific notation.
Fixed issue where the "Row ID" field would show in `{all_fields}` and the merge tag output for Nested Forms.
Fixed PHP error that could occur for some forms.
Improved support for `{Parent}` merge tags referencing the parent entry details such as `{Parent:entry_id}` when set to a field's default value and sent in notifications.
Added `:set` merge tag modifier for calculations which allows you to reutrn a list of values for use Advanced Calculation functions like `min()` and `max()`.
Added support for filtering the Save & Continue token that will be used to populate child entries into a Nested Form field.
Fixed `@media` query for Nested Form table layouts to resolve an inconsistency between `760px` and `768px`.
Improved compatibility with Gravity Flow User Input steps by bringing back compatibility layer.
Fixed potential PHP warning if using Gravity Flow by reverting the addition of a new compatibility layer. It will be re-added soon!
Fixed potential PHP error that could occur on the Entry Details page if GravityView is activated.
Fixed issue where the count template would always be used if GravityView is activated.
- Fixed issue where the Count templates were not being used in GravityView if the view is embedded using a shortcode.- Fixed potential PHP error introduced in 1.0.15.- Fixed an issue where the event handler in Nested Forms would not properly handle Chained Selects thus causing the placeholder to be incorrect on subsequent openings of the nested form.
Fixed conflict with eComerce Fields that was caused by Nested Forms unsetting child entry ID to null to ensure a fresh total was generated.
Fixed error that could occur when deleting both parent and child entries in the same request.
Fixed regression where a change in the form container element caused form change events not to fire.
Fixed regression where entries wouldn't be saved in certain circumstances if a Nested Form field is conditionally displayed by a calculated field.
- Added [gpnf_export_parent_entry_row](https://gravitywiz.com/documentation/gpnf_export_parent_entry_row/) filter to allow disabling the output of parent entry rows alongside their child entry rows.- Added [gpnf_export_parent_entry_data_on_child_entry_rows](https://gravitywiz.com/documentation/gpnf_export_parent_entry_data_on_child_entry_rows/) to allow exporting parent entry data on child entry rows.
Fixed inconsistent behavior of :total, :sum, and :count modifiers between the frontend and the backend if the Nested Form field is hidden. The correct behavior is to return `0` if the Nested Form field is hidden.
- Added new `.destroy()` method to `window.GPNestedForms` to allow for more integrations.- Fixed issue where the {Parent} merge tag wouldn't work with wpDataTables.- Added new [`gpnf_submitted_entry_ids`](https://gravitywiz.com/documentation/gpnf_submitted_entry_ids) filter.- Improved compatibility with Gravity Flow Discussion fields when editing child entries.- Improved how Nested Forms populates File Upload fields when editing child entries to improve compatibility with File Upload Pro's sorting and cropping functionality.
Improved Nested Form exporting by running field values through `gform_export_field_value`.
- Added support for populating Paragraph fields with the Rich Text Editor enabled using `{Parent}` merge tags.- Improved compatibility with Gravity Flow User Input Step. The min/max number of child entries is now validated.- Improved compatibility with GP Read Only when using `{Parent}` merge tags.
Fixed regression with multiple datepickers not behaving correctly in Nested Forms if focus trap is enabled.
Fixed regression where datepicker selects could not be interacted with in Firefox due to Focus Trap.
- Fixed PHP notice on parent form submission. - Added "Update URI" to plugin header to improve security.
Added [gpnf_should_delete](https://gravitywiz.com/documentation/gpnf_should_delete) JavaScript filter.
Added [gpnf_child_entries_separator](https://gravitywiz.com/documentation/gpnf_child_entries_separator/) filter to allow modifying the separator between child entries in the All Entries view.
- Fixed potential JavaScript errors when submitting/editing entries for some use-cases. - Added `enableFocusTrap` to [`gpnf_init_script_args`](https://gravitywiz.com/documentation/gpnf_init_script_args).
Fixed issue where jQuery UI modal was not updated to work with our new build flow.
Fixed issue where (Parent) merge tags would not be parsed if used in fields conditionally shown by a Section Field.
- Improved support for checkboxes pulled into child forms using the {Parent} merge tag. When more than one checkbox is selected, the values/labels will be comma delimited.- Added `:label` modifier to `{parent}` GPNF merge tags.
- Added [gpnf_modal_button_css_classes](https://gravitywiz.com/documentation/gpnf_modal_button_css_classes) JavaScript filter.- Added [gpnf_should_trash_entries_on_delete](https://gravitywiz.com/documentation/gpnf_should_trash_entries_on_delete) filter.- Fixed issue where child entry notifications would not be sent when using a Nested Form field with the WooCommerce GF Product Add-ons extension.
- Improved user experience of how Summary Fields are managed. They're now listed out vertically and sortable.- Added French translation. Thank you, [Cyrille Sanson](https://100son.net)!- Fixed typo in :sum modifier merge tag default value.
- Updated custom template names to have precedence before all standard template names.- Updated docblock with variables in `nested-entries-all.php`.- Added new `GP_Nested_Forms::get_template_names()` method and updated instances where we specified template names manually to use this new helper method.
- Fixed an issue where {Parent} merge tags were not processed correctly in nested form's notification.
Please purchare this item you can see note for Buyer !
- Please check the version we provided before purchasing. Because it may not be the latest version of the author.
- Before making a purchase, please read the Terms and Conditions & Refund Policy.
- If you have any questions, please first read the FAQ.
- If you haven’t found the answer to your question, please contact us, we will response asap.
- You can download the product after purchase by a direct link on your Downloads sections.
- Please note that any digital products presented on the website do not contain malicious code, viruses or advertising. We buy the original files from the developers.
- We offer frequent updates for one year from the date of purchase, but that doesn't mean we will have updates every version because not every developer release we have right away. After this period, you have to purchase the item again to receive further updates.
- We regularly update products as soon as we are notified about an update, we go and download it from the author and update it on our site, but In case the current version of the product is not the latest, You can request an update for the product by contact form.
- We send regular emails advising when products have been updated so please be sure to provide an active email address when you sign up.
- Our support team is available 24/7, if you have any question or need help in installing or configuring digital products purchased on the website, please don’t hesitate to contact us.
- Please note that we are not developers of the provided products, so our technical support capabilities are limited. We do not change product functionality and do not fix developer bugs.
- For more information please read FAQ & About Us.
