There are several drop down fields. Each subsequent one is filled from the parent by Term_ID using populate anything. In the feed settings, when using this code, you can not specify in which categories the product will be recorded.

Context

⛑️ Ticket(s): https://secure.helpscout.net/link/to/conversation

📓 Notion: https://notion.so/link/to/card

💬 Slack: https://slack.com/link/to/thread-or-message

Summary

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2049282106/40053?folderId=14965

Summary

The Gravity Forms Chained Selects field requires you to manually select a value in each Drop Down even if there is only a single option available in that Drop Down. This snippet will automatically selected an option when it is the only option available.

HS#29155

User wanted to conditionally edit the entry. This filter will allow him to do this with the following sample code:

add_filter( 'gpepee_edit_entry_id_123', function( $update_entry_id, $form_id ) {
	// Update "4" to the field ID you want to check the value of.
	if ( rgpost( 'input_1' ) === 'Add New' ) {
		$update_entry_id = false;
	}
	return $update_entry_id;
}, 10, 2 );

One sneaky but significant change I made in this PR (unrelated to the filter) is changing from which form the edit entry ID is fetched when fetching from the session. For some reason, it was setup to pull from the target form's session rather than the source form's session.

This doesn't make sense as the entire point of the snippet is to edit the same entry that has been populated into the form. I suspect most users are using the token or logged-in user's last entry option which were functioning correctly.

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2011825626/38759/

Summary

• Refactors gpnf-auto-attach-child-files into a class.
• Moves configuration logic to constructor args so that users can easily create multiple, unique configurations.
• Adds child_form_upload_field_ids config option to limit which child form upload fields are included in a notification.

Chrome seems to have changed their mind again about which autocomplete keywords they'll honor and ignore. Looks like "off" is working again.

This PR imports the GPNF Delay Child Notifications for Parent Payment snippet.

It also fixes an issue where notifications were sent twice by filtering on gform_entry_post_save and specific parent form IDs.

#23899 / DWC.

Good afternoon. This code works well, but the changed path (/wp-content/uploads/images/id91e8cc636fab491e8cd/file.png ) of the photos is displayed only in the frontend. In the administrative part of the site, in the product card, photos still have paths like /wp-content/uploads/2022/11/file.png

I added an additional code, now in the administrative part in the product card the path to the photos is the same as in the frontend.

Context

⛑️ Ticket(s): https://secure.helpscout.net/link/to/conversation

📓 Notion: https://notion.so/link/to/card

💬 Slack: https://slack.com/link/to/thread-or-message

Summary

This PR migrates the gp-nested-forms-auto-attach-child-files snippet to the library.

It also fixes a configuration issue where uploaded files were not attached to the parent form due to a notification ID check. By removing this check, once the snippet is enabled, any form that contains a child form will have uploaded files attached when this snippet is enabled.

Source: https://gist.github.com/spivurno/89efb788d3dc54a35ac001ad13322a74 Ticket: #27868

HS#25575

This PR adds support for bypassing GP Limit Submissions feeds when editing an entry. It does some significant refactoring so we'll want to retest these three scenarios.

1. Default functionality — updating an entry.
2. Deleting a partial entry when Partial Entries is active and delete_partial parameter is true.
3. Limit Submission feeds are bypassed when editing an entry.

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2015154047/38861/

It is difficult to configure gpnf-override-parent-merge-tag-on-submission.php for multiple child forms. This enables users to more easily apply the logic to multiple child forms.

Summary

• Refactors the snippet to a class to match our preferred snippet style.
• Support instantiating one instance of GPNF_Override_Parent_Merge_Tags per child form a user wants to configure.
• Support instantiating a single instance of GPNF_Override_Parent_Merge_Tags with no arguments to apply this to all child forms.

HS#32379

Nested Forms wasn't playing nice with Cache Buster due to its init script being bound and called multiple times and the Nested Form field container not existing. The latter issue is addressed in this PR.

With the existing implementation, all init scripts were loaded and triggered in the footer on the initial page load and then were re-included and re-triggered in the AJAX request that fetches the form markup. I'm honestly surprised we haven't been running into more issues like this.

My solution is to:

• allow the default init scripts to be output to the footer
• suppress the default init script trigger (e.g. gform_post_render)
• suppress init scripts during the AJAX request so they are not re-included
• manually trigger init scripts (via gform_post_render) after we've included the fetched markup

An alternate approach would be to suppress both the init scripts and default init script trigger and allow both to be included/executed as part including the markup from the AJAX request in the page but there have been some ambiguous issues with this approach in the past. Nested Forms itself deliberately moved away from that flow and seems to be much more stable now.

My only lingering concern is that since the default init scripts are output to the footer on page load, they will be cached. This may be an issue for plugins like Populate Anything that output dynamic data. I couldn't recreate a specific issue though so let me know if you can.

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2099104029/41936?folderId=3808239

Summary

When resuming a Save & Continue session, GPPA-populated fields correctly honor the Save & Continue value. This snippet would force GPPA to repopulate the field, ignoring the Save & Continue value.

The snippet in Action: https://www.loom.com/share/6ccde3a615234810b086a41f3c029f2d

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2103452211/42095/

Summary

• Relies on a new, unreleased filter in GPFR called gpfr_sanitize_file_name_chars.
• Removes commas from the list of dissallowed characters when renaming files with GPFR.

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2096156781/41821?folderId=3808239

Summary

Strip slashes from GPPA populated value. Possible enhancements to look at could include running over all fields and detecting the existence of specific patterns of values which need to be decoded/strip slashes from.

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2079000554/41152/

Summary

Customer wanted a way to provide a hint of the field's value while masking most of it for privacy.

Added the :mask modifier which will show the first and last letter and replace the rest of the output with asterisks. For email values, it splits the username and domain and masks them separately.

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2075899506/40995?folderId=3808239

Summary

Check for Gravity Forms before initializing to prevent fatal errors, if Gravity Forms is not enabled.

Context

⛑️ Ticket(s): https://secure.helpscout.net/conversation/2070005018/40733?folderId=3808239

Summary

If the source date is selected, a change in modifier value (in the field with GPPA Field Value Objects) does not update the target date.