After implementing the amp, in Webmaster Tools (search console) he gets errors. Below the message:
The “img” tag can not appear as a child of the “noscript” tag. Did you mean the tag “amp-img”?
Are the creator templates on the forum and refer to the error.
Hi,
We will reply as soon as possible, please check the support hours in the sidebar and top banner and also note that there was no support on Friday (banner was shown at top of forum).
Also please do not reply in your own topic after the initial post if possible, unless absolutely necessary. This will only renew the topic and delay the response, we answer from oldest to newest which is fair.
I could take a look at a post that has this problem, maybe I can see what exactly is the error referring to. Please provide a link to such a post.
Thanks
I am sending a link to the AMP error. Jst is just an example and the problem applies to all AMP posts.
https://profesjonalnyslub.pl/rocznice-slubu-i-ich-nazwy/amp/
Hi,
That AMP error is related to the image you use in the copyright field
– https://www.screencast.com/t/4Co3ZipYoL
AMP requires different image tags
– https://www.ampproject.org/docs/media/amp_replacements
If you would remove that image the post will be AMP validated.
I am asking for information on how to implement the changes so that it works on a standard template and amp. Should it not be possible to add footers for amp in the template panel?
Hi,
The img tags should be converted automatically to the amp-img tags, by the plugin. Like it happens for all the other images in the posts, seems images entered in the copyright field are not converted however. I have already added this on our list and the developer team will take a look as soon as possible. Sorry for the inconvenience. You could for the moment to manually replace the img tag, and use amp-img tags to have valid AMP pages.
Thanks
I am asking for information with an approximate date when you correct AMP. In that case, the module to turn off is not properly created.
I can’t provide a timeline in the matter unfortunately, it is on the list however and it will be examined by our team at some point. Sorry again for this.
