Undefined property: WP_Error::$taxonomy

Hi,

Perhaps you can find what you are looking for in our developer portal — https://developer.yoast.com/#browse-technical-specifications

As mentioned also previously, we invite you to log and open a proper bug report for more assistance as well — https://github.com/Yoast/wordpress-seo/issues/new

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance, please create a new issue.

Again I think inactivity for several DAYS is no proper reason to Resolve a report!

Having said this I think I have found the proper additions to my tag reroute to circumvent these notices.
I will retest tomorrow and plan to report back.
However this can take some more days….. so please be patient! ??

@harm10 Thanks for your reply. Please let us know what the results of your testing are once completed.

I can report that I fixed my reroute script in such a way that the notices do no longer appear!
If you see the solution you would think that is obvious…… but most of the times fixes are like that!

Anyway I explained that I have a 404 reroute script in place. As some of my clients previously had either another CMS or used different permalinks getting a 404 does not have to mean that the content is not there.
For tags I also do a reroute if some 404 URL comes in that has tag in it.
I clean the URL, change the headers and the query and remove the 404 status.
The page with the new tag appears fine.

But Yoast gives these notices.
My first approach of trying to find why this happens within your script became harder and harder (also because I do not know your software that well).
So I began capturing query structure for a normal tag page and started comparing it to the query I reroute with.
There were small differences (which I also corrected) but one major one: the error situation. If you look at the notice it mentions WP_Error which should have pointed me in this way from the beginning!
I forgot to code this for the tag part in my script:

            unset( $query->query_vars['error'] );
            unset( $query->query['error'] );

and that did the trick!

I think the report can be resolved now………… ??

• This reply was modified 4 years, 3 months ago by Harm10.

@harm10 Thanks for confirming that you were able to correct it. We are going ahead and marking this issue as resolved, but please let us know if you require any further assistance.

Hello,
I have the same problem with indexable-term-archive-presentation.php and yoast-head-rest-field.php on line 122 with my 4 custom tax.
All plugins is update and my WordPress version too.

I have try lot of thinks like :
– Remove Yoast and tables in database then reinstall
– Use Yoast Test Helper for reset indexable
Result…I have always PHP errors.

But, if I create a new taxonomy in PHP with a new slug (and remove my 4 older taxonomies), the errors disappears.

I think we have create taxonomies with bad version of Yoast (maybe v14.0.1) and my taxonomies have problem in database.

How to resolve this ? Thanks

Hi,

I had this issue and worked out it was because one of my custom taxonomies was being registered as “theme”:

register_taxonomy( 'theme', array('product'), $args );

If I changed that to something like:

register_taxonomy( 'product-theme', array('product'), $args );

…the errors resolved.

B

• This reply was modified 4 years ago by pixelanddot.