Summary

This PR fixes PHP warnings that flood the log file when saving a post 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:

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

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

// 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