Yes, I am facing the same after updating the AMP Plugin just now. It is a bug from developer end.
@satheeshrajv The AMP plugin does not add the HTML5 microdata attributes which you have in your site. They may be getting added by Yoast. You may need to connect with Yoast support: https://yoast.com/help/support/
But this issue is happening only after updating the amp plugin. Issue is getting resolved if I revert back to old version.
Humm, ok. Can you please try 1.5.1 with the Optimizer disabled? You can disable the Optimizer by installing and activating this plugin: https://gist.github.com/westonruter/8d52c0b807e6dfbbdf2219622d0f4a7e
If that fixes the problem, then it will narrow down the problem to being a bug in the Optimizer.
I’ve captured the HTML output of that page with the Optimizer enabled: https://gist.github.com/westonruter/ed5ded1dbafc1d87f6960780dd16b0eb
Please disable the Optimizer via the above plugin and then I’ll capture the output of the page to compare in order to determine if there is a bug in the Optimizer.
I have installed the Optimizer disabled plugin. But still the issue is there.
OK, thank you. I’ve captured the unoptimized and optimized output from v1.5.1: https://gist.github.com/westonruter/ed5ded1dbafc1d87f6960780dd16b0eb
Please roll-back to v1.4.4 and let me know when so I can grab the output so we can compare with the old version as well.
@satheeshrajv Additionally, are you using the Newspaper theme’s AMP mobile theme for your site? I am able to replicate the same errors when using their mobile theme and version 1.5.1, but the errors go away with a default theme and/or the previous version 1.4.4 of the plugin. For testing, I’m using the Structured Data Testing Tool.
When I rollback to 1.4.4 error gone.
@reneesoffice Yes I’m using Newspaper mobile theme. But that theme to work I need to install amp plugin. Yes the error goes away after the rollback of plugin to 1.4.4
-
This reply was modified 5 years, 12 months ago by
satheeshrajv.
Thanks very much. I’ve captured the output from 1.4.4 and added it to: https://gist.github.com/westonruter/ed5ded1dbafc1d87f6960780dd16b0eb
By comparing 1.4.4 and 1.5.1 I have identified the cause of the problem: the new meta sanitizer is 1.5.x is moving all meta tags to the head and this is breaking the Schema.org meta.
We’ll fix this promptly and give you a build to test.
Thanks for the quick response. One more doubt. Last time I got some Json error and You asked me to install “AMP JSON Validation Error Workaround” plugin. Do I still need this plugin or can I uninstall it?
That is no longer necessary, no.
We have just merged the fix for this, and there is a plugin build available for testing if you can: https://github.com/ampproject/amp-wp/pull/4505#issuecomment-607924311
The 1.5.2 release should be published on WordPress.org later today, but if you can test sooner that would add confidence.
