I’m having the same issue. For me, it looks the issue is I’m deferring the JS.
I used the testing tool at https://search.google.com/test/amp
If I plug your page in this tool, I also see the error about “defer” Line 31.
I’m not using the same AMP plugin you are, but I do have some plugins that defer scripts. I’m thinking that may be my issue.
Just a follow up. My staging site showed no errors so I figured it was a plugin setting.
I had a plugin called “Async JavaScript” that my host had installed. I changed is so the AMP scripts that were showing as “defer” were changed to “async”. That cleared the issue for me and the pages validate.
But the Google test page I referenced above seems to hold on to a cached version. I had to go back to Google Search Console, click into the page with issues and then click “TEST LIVE VERSION” at the bottom right. It’s on that Issue Detail panel.
Thread Starter
Scott
(@magius72)
I’m using a similar concatenation/minification plugin called Fast Velocity Minify.
I can input files to not minify in the plugin options — which I’m guessing would fix this issue — but not sure what files/paths to put there… (like, what file does this refer to: amp-mustache extension .js script ?)
-
This reply was modified 7 years, 1 month ago by
Scott.
On my Google Search Console, if I click through to a URL and the Issue Details panel, I can see a script reference in pink.
I’ve just grabbed those offending scripts and plugged in the whole URL. For example, on my plugin, there is a dedicated box to have a script run ASYNC. So, I entered the full path.
https://cdn.ampproject.org/v0.js
Your plugin probably has some settings and different pages use different AMP scripts. I’ve pulled out 4 for my site so far. I don’t think minification is the issue. It wasn’t for me.
If you’re not sure the setting, I would contact the Velocity plugin author or test on a staging site if you have one.
Try deactivating the velocity script and then test for AMP page validity using this
https://search.google.com/test/amp
Thread Starter
Scott
(@magius72)
UPDATE: added exceptions for the Javascripts:
https://cdn.ampproject.org/v0.js
https://cdn.ampproject.org/v0/amp-form-latest.js
https://cdn.ampproject.org/v0/amp-mustache-latest.js
to the Fast Velocity Minify plugin and that seems to do the trick! Thanks for the assistance.
-
This reply was modified 7 years, 1 month ago by Scott.
Hello @prodport
Can you please try the suggestion given by @magius72 and check if it works or not.
Hi,
Sorry if I wasnt’ clear in my earlier message, but I don’t use this plugin. And, I was able to get it to work when I stopped using “defer”
Hello @prodport
I can understand that you are facing issues while AMPforWP and defer.
Can you please contact me on team@magazine3.com so I will make sure your issue gets solved and you will use our plugin without any issues and problem?
Thread Starter
Scott
(@magius72)
UPDATE: actually, nothing got fixed — it just created more errors, on more pages! haha
Back to square one…
Hello @magius72
Can you please contact me on team@magazine3.com so I can troubleshoot your issue personally and will solve it for you?
Hello @magius72
Thank you for contacting will look into this issue there personally and will solve it for you.
