PHP warning in filter_graph when post is not in Yoast index #1125
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a post type is excluded from the Yoast SEO index using the
wpseo_indexable_excluded_post_typesfilter, the post may not have a proper indexable object or ID when passed into Yoast’sfilter_graphhook (using the$contextargument). Co-Authors Plus currently assumes that a validpostobject within the$contextand therefore theIDwill be available within this filter, which can trigger warnings.The problematic function is here:
Co-Authors-Plus/php/integrations/yoast.php
Lines 149 to 223 in 14725a6
This issue was observed with a custom post type that is excluded via:
The
filter_graphfilter still runs for this post type, even though it is not Yoast-indexable. However, Co-Authors tries to accessget_coauthors( $context->post->ID ), which can result in an error if$context->postis missing due to the post not being indexed.Proposed Solution
I propose adding a check to ensure the
postand thepost->IDexist within the$contextthat is passed to the filter, before trying to attach co-authors to it.