You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are encountering frequent PHP warnings in our logs when using the gatsby-source-wordpress plugin. These warnings are cluttering the logs and raising concerns about potential underlying issues.
To Reproduce
Steps to reproduce the behavior:
Configure the gatsby-source-wordpress plugin.
Trigger a crawl/data fetch operation.
Observe multiple instances of the following PHP warning in the logs: PHP Warning: Attempt to read property "schema" on bool in /var/www/wordpress/wp-content/plugins/add-wpgraphql-seo/wp-graphql-yoast-seo.php on line 871
(Reference: wp-graphql-yoast-seo.php#L871)
Additional context
We are seeking clarification on whether this warning is expected behavior or indicative of a configuration error on our end. Furthermore, we'd like to know if this is something that should be addressed within the plugin to prevent such warnings.
Thank you for your attention to this matter and for your work on this plugin!
The text was updated successfully, but these errors were encountered:
We are encountering frequent PHP warnings in our logs when using the
gatsby-source-wordpress
plugin. These warnings are cluttering the logs and raising concerns about potential underlying issues.To Reproduce
Steps to reproduce the behavior:
gatsby-source-wordpress
plugin.PHP Warning: Attempt to read property "schema" on bool in /var/www/wordpress/wp-content/plugins/add-wpgraphql-seo/wp-graphql-yoast-seo.php on line 871
(Reference: wp-graphql-yoast-seo.php#L871)
Additional context
We are seeking clarification on whether this warning is expected behavior or indicative of a configuration error on our end. Furthermore, we'd like to know if this is something that should be addressed within the plugin to prevent such warnings.
Thank you for your attention to this matter and for your work on this plugin!
The text was updated successfully, but these errors were encountered: