Any help will be appreciated.
@neeville Your site uses custom JavaScript, which isn’t permitted in AMP. The plugin informs you of the source of the errors, such as your theme, plugins or content. You will find information on validation errors here.
You can use AMP in reader mode to ensure AMP compatibility. It won’t use your active themes styling or layout but it will provide you with a AMP valid base template you can work with to add features.
If you want sure your AMP URLs look the same as your non AMP, and continue with transitional mode AMP you can use the validation tool to accept or reject any highlighted errors. Alternatively you can ask your theme provide if they plan for AMP compatibility also, or use an AMP compatible theme.
Thanks for your reply. My theme dev has no plans of making the plugin Amp compatible. So it’s up to me now. please give me a little direction and I will figure the rest. for example, the following code
<link rel='https://api.w.org/' href='https://spicegadget.com/wp-json/' />
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://spicegadget.com/xmlrpc.php?rsd" />
<link rel="wlwmanifest" type="application/wlwmanifest+xml" href="https://spicegadget.com/wp-includes/wlwmanifest.xml" />
<meta name="generator" content="WordPress 5.2.2" />
<style type="text/css">
Has this warning.
The mandatory attribute ‘amp-custom’ is missing in tag ‘style amp-custom’
please, how do I resolve this?
@neeville I don’t see any validation errors at present when checking your site. Most likely you had a plugin which is causing the error you reported.
It could also be a search console error, reporting on an error that no longer exists if you have just recently made any changes.
Search console is showing pass because it is showing old result of my site when I was using ampforwp. I switch because I like how this version integrates and show the main theme in amp. Please to see my site amp errors use this link.
The Amp Validator
@neeville Thanks for the update. You are performing an AMP test on a non AMP URL, which is why you see those errors.
You will need to do an AMP validator test on an AMP URL.
