many of these errors can come from other plugins that haven’t updated. We had LiveFyre and Related Posts throwing syntax errors and had to have our developer figure those out.
With a change as big as this one, there’s so many variables that can cause problems it’s rather frustrating.
The JS issue would come as AMP was created to strip out all JS (javascript) to make load time much faster.
Ok – so as AMP is created – and the creation of AMP pages is coming from the automatic WP amp plugin – so maybe the plugin creating the amp pages is throwing the error. I guess should get with the developer of the plugin – automatic WP amp. Make sense?
and, thanks again for your comment and help
The biggest thing is trying to follow back to see what exactly is making the error occur. Many times (we found, at least) that one of our plugins was causing it.
It sounds daunting at first, but most times it’s pretty simple and logical backtracking. We were getting a lot of rel=Youtube errors so I was able to realize that the only plugin we had giving us outbound links to Youtube was our Related Posts so our developer was able to fix those….and so forth.
Hopefully that makes sense as many of the errors getting thrown aren’t coming from the AMP plugin, just repercussions of Google’s new AMP code which is very strict.
understood, but the plugin – I assume – would follow the AMP rules (put in place by the AMP project and that Google would draw from) to render the AMP pages.
I did just notice on another thread that PageFrog may have caused errors for another website – had that installed but pulled it off after the AMP pages stopped rendering even when you typed in /amp at the end of the AMP’d page site address
anyway – thanks again and will let some time pass to see if the amp pages are picked up by google and see if the errors go away.
and understand that all of this is relatively new and kinks show up and are eventually worked out
> understood, but the plugin – I assume – would follow the AMP rules (put in place by the AMP project and that Google would draw from) to render the AMP pages.
We’re trying! 🙂 There are a lot of rules so it’s not super easy to achieve 100% validation (it’s possible but it is a significant amount of work and there are many trade-offs we need to consider as well).
kudos to you… thanks again for the plugin – no thumbs down here just thumbs up. not sure where the Google rendered errors are coming from … just trying to break it down and taking from the ideas expressed in the thread…
on another note, do you think the error from google –
“Unknown syntax error
Review your page for errors. AMP pages that do not follow the AMP specifications may appear in Google search results without AMP-specific display features. Learn more”
“boilerplate (js enabled) required by boilerplate (no script)”
—
is coming from the AMP plugin or …?
Thanks again in advance for your help
Thanks in advance for any comments/help.
Not sure where this error might be coming from –
“Unknown syntax error
Review your page for errors. AMP pages that do not follow the AMP specifications may appear in Google search results without AMP-specific display features. Learn more”
“boilerplate (js enabled) required by boilerplate (no script)”
And, the search console from Google does show 2 indexed with 34 with errors. Strange b/c all pages use same page structure. Does anyone know how to view the pages that are exactly indexed? (it shows 2 indexed but does not show them – only shows the pages with errors)
Latest error from the console developer tool shows the following –
1. The attribute ‘type’ may not appear in tag ‘style amp-custom’. (see https://www.ampproject.org/docs/reference/spec.html#stylesheets)”
2. The tag ‘head > style : boilerplate’ is missing or incorrect, but required by ‘noscript > style : boilerplate’. (see https://www.ampproject.org/docs/reference/spec.html#required-markup)”
3. The mandatory tag ‘head > style : boilerplate’ is missing or incorrect. (see https://www.ampproject.org/docs/reference/spec.html#required-markup)”
The AMP plugin was deactivated and no amp pages show up
Used the following from as the format for the page we are testing:
The AMP HTML format
Sample document
<!doctype html>
<html ⚡>
<head>
<meta charset="utf-8">
<title>Sample document</title>
<link rel="canonical" href="./regular-html-version.html">
<meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1">
<style amp-custom>
h1 {color: red}
</style>
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "NewsArticle",
"headline": "Article headline",
"image": [
"thumbnail1.jpg"
],
"datePublished": "2015-02-05T08:00:00+08:00"
}
</script>
<script async custom-element="amp-carousel" src="https://cdn.ampproject.org/v0/amp-carousel-0.1.js"></script>
<style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
<script async src="https://cdn.ampproject.org/v0.js"></script>
</head>
<body>
<h1>Sample document</h1>
<p>
Some text
<amp-img src=sample.jpg width=300 height=300></amp-img>
</p>
<amp-ad width=300 height=250
type="a9"
data-aax_size="300x250"
data-aax_pubname="test123"
data-aax_src="302">
</amp-ad>
</body>
</html>
