Upcoming Fix for AMP Mustache Warning in Search Console?
By Ed Radetic on Saturday, 28 July 2018
Posted in Technical Issues
Likes 0
Views 1.3K
Votes 0
Google Search Console is throwing a warning for our amp pages, they all have <script async custom-template="amp-mustache" src="https://cdn.ampproject.org/v0/amp-mustache-0.1.js"></script> and the mustache documentation here, https://www.ampproject.org/docs/reference/components/amp-mustache is showing that version 0.2 is available. Will this be updated in a release in the near future before more pages are indexed with the incorrect js?

Thank you in advance
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

It seems like I was unable to access you site, this is what i hitting now : 



403: Access Forbidden

Your location (MY) has been blacklisted.


By the way, this is my current IP address : 175.142.24.57
Arlex Wong
·
Saturday, 28 July 2018 08:59
·
0 Likes
·
0 Votes
·
0 Comments
·
I'm seeing the same issue from Google Webmasters. I think the ability to access our site is irrelevant - you are either using mustache 0.1 or you aren't. I'm seeing this warning across the majority of my pages so I'm guessing this version is being used. Is this something you are aware of?
Brandon Scivolette
·
Saturday, 04 August 2018 05:35
·
0 Likes
·
0 Votes
·
0 Comments
·
That was known issue, because we received number of user complain about this error.

Can you try download my attached file and replace into this file location and see how it goes. JoomlaFolder/components/com_easyblog/themes/wireframe/blogs/entry/amp.php
Arlex Wong
·
Saturday, 04 August 2018 11:57
·
0 Likes
·
0 Votes
·
0 Comments
·
The new file appears to pass the amp validation. Waiting for the official results, but in my test analysis it seemed fine.

Thank you.
Brandon Scivolette
·
Sunday, 05 August 2018 02:37
·
0 Likes
·
0 Votes
·
0 Comments
·
You're most welcome.

Keep us update if the issue still persists.
Arlex Wong
·
Sunday, 05 August 2018 11:54
·
0 Likes
·
0 Votes
·
0 Comments
·
That worked. Google validation for the fix passed.
Brandon Scivolette
·
Monday, 06 August 2018 08:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for getting back to us your issue resolved.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding
Arlex Wong
·
Monday, 06 August 2018 10:27
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post