>
> \## Summary
>
> This PR fixes PHP warnings that flood the log file when saving a p…ost with a relationship field that has the "Sync associated taxonomy with this relationship" option enabled, but no bidirectional relationship (sister\_id) is configured.
>
> Fixes #7477
>
> \## The Problem
>
> When \`pick\_sync\_taxonomy\` is enabled but there is no bidirectional relationship set up:
> \- \`$related\_pod\` is \`null\`
> \- \`$related\_field\` is \`null\`
>
> The original code at line 1959-1967 had this condition:
>
> \`\`\`php
> if (
> (
> empty( $related\_field )
> || empty( $related\_pod )
> )
> && empty( $options\[static::$type . '\_sync\_taxonomy' \] )
> ) {
> return;
> }
> \`\`\`
>
> This means the function only returns early if BOTH conditions are true:
> 1. No bidirectional relationship exists, AND
> 2. No taxonomy sync is enabled
>
> So when taxonomy sync IS enabled (but no bidirectional relationship exists), the code continues past this check and then tries to access \`$related\_pod\['type'\]\` on line 1974, which triggers the PHP warning.
>
> \## The Solution
>
> Move the taxonomy sync logic to run first (it does not need \`$related\_pod\` or \`$related\_field\`), then add an early return if no bidirectional relationship exists.
>
> \### Before
>
> \`\`\`php
> if (
> (
> empty( $related\_field )
> || empty( $related\_pod )
> )
> && empty( $options\[static::$type . '\_sync\_taxonomy' \] )
> ) {
> return;
> }
>
> // Handle the bi-directional relationship updates.
>
> $no\_conflict = true;
>
> // Only check no conflict mode if this isn't the current pod type.
> if ( $related\_pod\['type'\] !== $pod\['type'\] ) { // \<-- PHP Warning here!
> $no\_conflict = pods\_no\_conflict\_check( $related\_pod\['type'\] );
> }
>
> // ... more bidirectional code ...
>
> // Handle syncing of taxonomy terms.
> if ( ! empty( $pod\['type'\] ) && 'post\_type' === $pod\['type'\] && ! empty( $options\[static::$type . '\_sync\_taxonomy' \] ) ) {
> // taxonomy sync code
> }
>
> if ( ! $no\_conflict ) {
> pods\_no\_conflict\_off( $related\_pod\['type'\] ); // \<-- PHP Warning here too!
> }
> \`\`\`
>
> \### After
>
> \`\`\`php
> // Handle syncing of taxonomy terms first (doesn't require bidirectional relationship).
> if ( ! empty( $pod\['type'\] ) && 'post\_type' === $pod\['type'\] && ! empty( $options\[static::$type . '\_sync\_taxonomy' \] ) ) {
> // taxonomy sync code - runs independently
> }
>
> // Exit early if no bidirectional relationship to handle.
> if ( empty( $related\_field ) || empty( $related\_pod ) ) {
> return;
> }
>
> // Handle the bi-directional relationship updates.
> // Now we are sure $related\_pod and $related\_field are not null
>
> $no\_conflict = true;
>
> if ( $related\_pod\['type'\] !== $pod\['type'\] ) {
> $no\_conflict = pods\_no\_conflict\_check( $related\_pod\['type'\] );
> }
>
> // ... rest of bidirectional code ...
>
> if ( ! $no\_conflict ) {
> pods\_no\_conflict\_off( $related\_pod\['type'\] );
> }
> \`\`\`
>
> \## Why This Works
>
> 1. Taxonomy sync does not need \`$related\_pod\` or \`$related\_field\` - it only uses \`$pod\`, \`$options\`, and \`$value\_ids\`
> 2. By moving it to the top, it runs first regardless of whether a bidirectional relationship exists
> 3. The early return after taxonomy sync prevents the bidirectional code from executing when \`$related\_pod\` is null
> 4. Bidirectional relationships still work exactly as before when properly configured
>
> \## Testing Done
>
> \- Tested with Pick field related to taxonomy with "Sync taxonomy" enabled
> \- No bidirectional relationship (sister\_id) configured
> \- Saved post with taxonomy terms selected
> \- Verified: No PHP warnings in debug.log
> \- Verified: Taxonomy terms sync correctly to the post
> \- Also tested with bidirectional relationship enabled to make sure that still works
>
> \## Files Changed
>
> \- \`classes/fields/pick.php\` - Reordered logic in the \`save()\` method
>
> \## Plugin zip
> \[pods-fix-7477.zip\](https://github.com/user-attachments/files/24968327/pods-fix-7477.zip)
---
### Author:  [@adamrice](https://community.gravityforms.com/u/adamrice)
#### Post date: [March 18, 2026, 5:10pm UTC](https://community.gravityforms.com/t/mapping-booleans-to-custom-user-profile-fields-using-user-registration-add-on/20157/3 "2026-03-18T17:10:30Z")
Faisal–
Thanks. I am appending a screenshot of the relevant Pods fields. The Gravity Forms export is a little too big to include here, so I’ve uploaded it [here](https://8stars.org/misc/gravityforms-export-2026-03-18.json).
Although Gravity Forms lets you place multiple checkboxes under a single title, for clarity I’ve created a separate title for each checkbox in the form.
Let me know if I can provide any more information.
---
### Author:  [@faisalahammad](https://community.gravityforms.com/u/faisalahammad)
#### Post date: [April 1, 2026, 8:51am UTC](https://community.gravityforms.com/t/mapping-booleans-to-custom-user-profile-fields-using-user-registration-add-on/20157/4 "2026-04-01T08:51:28Z")
Hi @adamrice
Sorry for the delay. I’ve already resolved the issue for the single checkbox item. Could you please share your all Pods by exporting so I can import on my end and give you a complete solution?
> **[WP All Import & Export - Free & Pro Versions - Pods Docs](https://docs.pods.io/plugins/wp-all-import-export/)**
>
> WP All Import & Export is an extremely powerful importer/exporter that makes it easy to import/export any XML or CSV file to WordPress.
Thank you
---
### Author:  [@faisalahammad](https://community.gravityforms.com/u/faisalahammad)
#### Post date: [April 1, 2026, 11:15am UTC](https://community.gravityforms.com/t/mapping-booleans-to-custom-user-profile-fields-using-user-registration-add-on/20157/5 "2026-04-01T11:15:03Z")
Hi again,
I’ve resolved the issue. Now you can select the Pods fields under **Gravity Forms \> Settings \> User Registration \> User Meta** , as shown in the screenshot below.
After a user is created or updated, the user meta will auto-sync and can be found under the user profile.
Please use the following code as an MU-Plugin for now. I plan to release a small plugin later for easier use in the future.
```php
load_pod( ['name' => 'user'], false );
if ( ! empty( $pod ) && ! empty( $pod['fields'] ) ) {
if ( ! is_array( $keys ) ) {
$keys = [];
}
foreach ( $pod['fields'] as $field ) {
$keys[] = [
'label' => '[Pods] ' . $field['label'],
'name' => $field['name'],
'value' => $field['name'],
'required' => false
];
}
}
return $keys;
}, 10, 1 );
// 2. Intercept boolean values to ensure they save as 1/0 for Pods
add_filter( 'gform_user_registration_meta_value', function( $value, $meta_key, $meta, $form, $entry ) {
if ( ! function_exists( 'pods_api' ) ) {
return $value;
}
$api = pods_api();
$pod = $api->load_pod( ['name' => 'user'], false );
if ( empty( $pod ) || empty( $pod['fields'] ) || empty( $pod['fields'][$meta_key] ) ) {
return $value; // Not a Pods field or not registered.
}
$field = $pod['fields'][$meta_key];
// Only apply processing to boolean fields
if ( 'boolean' === $field['type'] ) {
if ( is_array( $value ) ) {
$value = empty( $value ) ? 0 : 1;
} else {
// In Gravity Forms, an unchecked string is usually empty "".
// A explicitly false string could be "false" or "no".
// Valid labels are considered truthy.
$value = ( empty( $value ) || '0' === $value || false === filter_var( $value, FILTER_VALIDATE_BOOLEAN, FILTER_NULL_ON_FAILURE ) ) ? 0 : 1;
}
}
return $value;
}, 10, 5 );
```
You can also get the source code from here:
>
MU-Plugin guideline:
> **[Must Use Plugins – Advanced Administration Handbook | Developer.WordPress.org](https://developer.wordpress.org/advanced-administration/plugins/mu-plugins/)**
>
> Must-use plugins (a.k.a. mu-plugins) are plugins installed in a special directory inside the content folder and which are automatically…
Give it a try, and let me know how that goes! 😄
Best regards,
Faisal
---
### Author:  [@adamrice](https://community.gravityforms.com/u/adamrice)
#### Post date: [April 1, 2026, 12:07pm UTC](https://community.gravityforms.com/t/mapping-booleans-to-custom-user-profile-fields-using-user-registration-add-on/20157/6 "2026-04-01T12:07:08Z")
Thanks very much. I haven’t had a chance to try this out yet, but I appreciate your time and expertise.
---
### Author:  [@faisalahammad](https://community.gravityforms.com/u/faisalahammad)
#### Post date: [April 1, 2026, 12:34pm UTC](https://community.gravityforms.com/t/mapping-booleans-to-custom-user-profile-fields-using-user-registration-add-on/20157/7 "2026-04-01T12:34:49Z")
You’re welcome.
Please keep me posted about the outcome. 👍
---
### Author:  [@system](https://community.gravityforms.com/u/system)
#### Post date: [May 1, 2026, 12:35pm UTC](https://community.gravityforms.com/t/mapping-booleans-to-custom-user-profile-fields-using-user-registration-add-on/20157/8 "2026-05-01T12:35:10Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.