Any plugin that adds custom scripts would be incompatible. Any plugin that adds markup which is not valid AMP would be incompatible. As for why it is saying AMP is incompatible, it may be due to CSS for your theme and plugins pushing out the CSS added by the AMP plugin.
Are you using the Native or Paired modes? If so, please try rechecking the AMP validity of the most recently-published post (via the revalidate link in the admin bar).
Otherwise, if you are using Classic mode, then that warning is somewhat misleading as I believe it doesn’t apply for you, at least in regards to AMP.
@westonruter Thanks for the prompt reply, I am using the paired mode and I needed to accept the errors generated by Amp due to the plugins I mentioned. From what I can see and I might be wrong, once the errors are accepted then any other errors (same)generated from those plugins will not be shown in subsequent pages or posts.
@drnick2 That is correct. Once you accept the sanitization (removal) of invalid markup that causes a validation error, you won’t get warnings about that same validation error anymore. (If the invalid markup has variable content you’ll have to do a bit more to make sure that happens.)
Would you please share a screenshot of the validation errors for a URL (e.g. the validated URL screen for the homepage)? I want to see why AMP is being flagged as not being compatible.
-
This reply was modified 7 years, 2 months ago by
Weston Ruter.
Below is a link for a couple of screenshots.
https://photos.app.goo.gl/94rFApUsQgZsF9X59
The top screenshot is when I activate a plugin and the second screenshot shows the accepted errors with the plugins listed that are causing the warning. Please edit out the link after you view the screenshots, thanks.
@westonruter Sorry did not direct the message to you.
Below is a link for a couple of screenshots.
https://photos.app.goo.gl/94rFApUsQgZsF9X59
The top screenshot is when I activate a plugin and the second screenshot shows the accepted errors with the plugins listed that are causing the warning. Please edit out the link and delete the previous message if possible after you view the screenshots, thanks.
@drnick2 thanks, but I need you to navigate into the validation URLs for that one specific URL (manuka-honey). That will then detail what the specific errors are for each plugin.
Note also that I cannot edit the forum posts to remove content.
@westonruter Thanks for explaining further what you needed. I had to split it into two photos, below is the link.
https://photos.app.goo.gl/7jtRFpptz5xxRJEaA
Thanks again:)
@drnick2 thanks. Ok, it is not expected that “Invalid element: script” happens in the AMP plugin. Please expand the details for one of those validation errors to reveal what the attributes are which are causing it to be invalid.
If you have a plugin that is replacing “https://” with “//” then that could be the problem. AMP requires the full URL to be present.
@westonruter No plugins used like that. Since it would take a lot of screenshots and there are essentially three errors related to Amp, I will list them below, if you need something more let me know.
Invalid_Element :Script
Invalid markup:
<script … >
code
invalid_element
node_attributes
type: text/javascript
node_name
script
parent_name
div
text
(function() { var po = document.createElement(‘script’); po.type = ‘text/javascript’; po.async = true; po.src = ‘https://apis.google.com/js/platform.js’; var s = document.getElementsByTagName(‘script’)[0]; s.parentNode.insertBefore(po, s); })();
type
js_error
sources
Invalid markup:
<script … >
code
invalid_element
node_attributes
async
src: //pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
node_name
script
parent_name
div
type
js_error
sources
Invalid markup:
<script>
code
invalid_element
node_attributes
node_name
script
parent_name
div
text
(adsbygoogle = window.adsbygoogle || []).push({});
type
js_error
sources
@drnick2 Those errors are not coming from the AMP plugin.
In your screenshots, the last 5 validation errors are for script elements said to be coming from the AMP plugin.
For all of those 5 errors, please share screenshots of the details for each expanded, ideally with the Sources also expanded.
It could be the detection is faulty for attributing the error to the AMP plugin.
@westonruter The previous message is for AMP and lists the error details, below is a link for a screenshot for the last detail on the list. The other four are also Amp and the details are in the previous message.
https://photos.app.goo.gl/awVpiqbBtCzyo8Vy6
@drnick2 please expand the sources as well, and add a screenshot of each of the 5 validation errors with the details and sources expanded.
Screenshot is better than copying the text since the text is hard to read. Also, the sources is important.
@drnick2 Any update on this?
No new updates, the plugin still has incompatibility issues but as I am sure you noticed you can accept these warnings/issues via a dropdown selection and the warnings are no longer visible.
@drnick2 By any chance, do you you have force_balance_tags() enabled for your content?
Otherwise, sharing full screenshots of the validation errors and their sources will still be helpful.
And yes, for expected validation errors, by accepting them you mark them as being acceptable, and thus the warnings no longer appear.
