hiroprot

The exact same thing happened again on another site. I’m so glad I posted my solution four weeks ago.

For SEO, here are the error messages I got this time:

• TypeError: ResizeObserver.unobserve: Argument 1 is not an object. in react-dom.min.js
• Uncaught TypeError: ResizeObserver.unobserve: Argument 1 is not an object. in vendor.js

I had exactly the same issue with the pro version of the plugin. As it turned out the auto-update didn’t work and the plugin was stuck on version 6.2.4. Once I manually downloaded the current version 6.4.2 from the vendor site and updated the plugin through FTP the issue was gone.

I am happy to confirm that version 2.6 fixes the issue. The number of errors in the Apache log went down from nearly 1,000 to 60 per week, and those remaining 60 have nothing to do with this awesome plugin.

Thanks, Jeff!

Thanks, a workaround is certainly helpful!

Awesome, thank you so much! This should get my Apache server errors down from ~1000 per week to less than ten (I hope).

I’ll let you know if I notice anything after upgrading.

Thanks for the information. It would be great to be able to choose which roles have access to that dashboard ??

@tigroumeow: did you see this question?

• This reply was modified 4 years, 1 month ago by hiroprot.

Any news regarding version 15.0?

@mikes41720 Could you elaborate on the status of this issue?

1. Is a fix being worked on by Yoast?
2. If yes, is it only for a specific plugin like bbPress, or a generic solution?
3. If yes, can you share a link to an issue tracker (or similar), so we can follow status, comments, etc.?

I am asking because we have a custom plugin that was developed specifically for us and I am not sure whether this needs to be fixed by the plugin authors or by Yoast.

@fpcsjames Thanks for your earlier answer.

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

@fpcsjames

Where exactly do you configure public = true for the custom post type?

In my case, the affected pages are a custom post type Documents (vldocs_document) that is managed by a plugin.

The corresponding settings in Yoast’s Search Appearance > Content Types are as follows:

• Show documents in search results: yes
• Show SEO settings for documents: show
• SEO title: [Title] [Page] [Separator] [Site title] documentation
• Meta description: [empty]
• Default page type: Web page (default)

Looking at the JSON I also noticed that the URLs for the affected entries are incorrect. Example:

• URL in JSON: https://uberagent.com/blog/vldocs_document/metrics/microsoft-office/
• Correct URL: https://uberagent.com/docs/uberagent/latest/metrics/microsoft-office/

Many thanks for the super-quick response. I’m looking forward to version 2.6 ??

Hi there,
I have the exact same issue as the original poster ("@type":["WebPage",null]). I was made aware of it through an email I got from the Google Search Console Team.

The issue only seems to affect pages with a certain custom post type we use for product documentation.

To answer the two questions:

1. Yes, Knowledge Graph and Schema sections are filled out in WordPress > SEO > Search Appearance
2. I cleared the cache of our caching plugin (W3 Total Cache), but that did not help.

One of the affected URLs:

• https://uberagent.com/docs/uberagent/latest/metrics/microsoft-office/

Awesome, happy to hear this.

Thank you!

Here are some resources that might be useful:

1. Working with Array values
2. ACF loop Repeater values with get_field