Skip to content

Taxonomy: Discard terms that no longer resolve in WP_Term_Query::populate_terms() - #14843

Open
mpeshev wants to merge 2 commits into
WordPress:trunkfrom
mpeshev:59785-term-query-missing-term
Open

mpeshev wants to merge 2 commits into
WordPress:trunkfrom
mpeshev:59785-term-query-missing-term

Conversation

@mpeshev

@mpeshev mpeshev commented Oct 25, 2026

Copy link
Copy Markdown

In WP_Term_Query::populate_terms(), rows that carry an object_id or count are assigned to the result of get_term() before it is checked. When the term no longer resolves, for example because a persistent cache still lists a deleted term or a get_term filter returns null, this is a fatal error: Attempt to assign property "object_id" on null.

The function already discards anything that is not a WP_Term a few lines later, so this skips such terms before the assignments, the same guard [60661] added for child terms in #63877. One guard covers both the object_id and the count assignment.

Trac ticket: https://core.trac.wordpress.org/ticket/59785

Testing

  • vendor/bin/phpunit --filter test_unresolvable_term_with_object_id_should_be_discarded fails without the patch with Attempt to assign property "object_id" on null and passes with it.
  • vendor/bin/phpunit --group taxonomy (1122 tests) passes.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: reproducing the fatal in trunk, drafting the fix and test, and running them. I reviewed every line.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

🤖 Generated with Claude Code

…ulate_terms()`.

When a query returns term rows with an `object_id` or `count`, `populate_terms()` assigns those values to the result of `get_term()` before checking it. If the term no longer resolves, for example because a persistent cache still lists a deleted term or a `get_term` filter returns null, this is a fatal error: "Attempt to assign property "object_id" on null".

Skip such terms, as the function already does for the other branch and as [60661] did for child terms.

See #59785.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props nofearinc.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@github-actions

This comment has been minimized.

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

The guard in `WP_Term_Query::populate_terms()` narrows `$term` to `WP_Term`, so the baselined error about `WP_Error|WP_Term` no longer occurs there.

See #59785.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant