The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: up1512001 <[email protected]>
Co-authored-by: Mamaduka <[email protected]>
Co-authored-by: david-binda <[email protected]>

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

Thanks for contributing, @up1512001!

Can you share a code snippet for get_the_term_list to return a WP_Error?

The issue mentions filtering the get_the_terms, in which case an error should be caught early, and code execution shouldn't reach get_the_term_list.

cc @david-binda

@Mamaduka sorry for the confusion on my end. The thing is that the get_the_term_list can return a WP_Error even in case the get_the_terms does not.

It would be the case when the get_term_link called from the get_the_term_list would return an instance of WP_Error.

As I have mentioned in the related issue, checking the return value of the get_the_term_list is what WordPress also does.

In order to reproduce the issue I've noticed in production logs, we could filter the get_the_terms in following fashion:

add_filter( 'get_the_terms', function( $terms, $post_id, $taxonomy ) {
    if ( array_key_exists( 0, $terms ) ) {
        $terms[0] = null;
    }
    return $terms;
}, 10, 3 );