Hey Rawhyder,
Thanks for the awesome feedback! It will help us create better plugin for you.
We’re two developers, we dedicate 2 days out of our week to the AMP plugin development. So, we will look into these over the next week, fix the issues and release an update soon as possible.
Regards,
Ahmed
Also, I totally forgot to mention, but if you could post the website url then it would really help us.
Regards,
Ahmed
Hi Ahmed, I sent you a website link via email, don’t really want to post it here. Thanks! 🙂
Sure Rawhyder, I can understand. Will look into this soon as possible.
Thanks, the target=”_blank” is the most crucial for me to work right now, since none of the links work. The console errors will all be fixed in time. 🙂
Sounds like you have a few issues with plugin compatibility to me, it seems that you have a few plugins that are adding their own code to AMP pages, which you shouldn’t be doing.
If you can, the best way for you to stop this is the disable amp pages from the settings of those plugins, some will have an option like “disable on these pages”, you can simply type something along the lines of ” */?amp ” and that will work if they support regular expressions.
Aside from that, you would need to individually disable the plugins you need in this plugin, or get the other plugin developers to stop their plugins loading on AMP pages.
Where would I add */?amp to, to disable that plugin from working on amp pages?
And this morning, I get a slew of new console errors:
The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
Missing structured data element
Invalid URL protocol ‘http:’ for attribute ‘src’ in tag ‘img’.
The attribute ‘ref’ may not appear in tag ‘a’.
Well if the plugin has an option to disable on certain pages, that’s where you would add that.
Currently, I think the best option would be to disable all of your plugins except for AMP and check if everything validates, it should.
Then enable your plugins one by one, re-validating after each activation and write down the ones where you see additional validation problems.
You can validate AMP pages by copying the URL into this page:
https://validator.ampproject.org/
A couple more errors: (Do you want these in separate posts? Or just continue adding them here?)
The attribute ‘border’ may not appear in tag ‘td’.
The attribute ‘size-full’ may not appear in tag ‘amp-img’.
Hey @rawhyder
Your username on the github is ‘Taig7’?
so that I can be sure that I am checking the right website url.
You may have sent me an email with URL, but I am not able to locate it.
Can you please send it to ahmed (at) magazine3.com so I can check it out and troubleshoot them.
Taig, not me. I sent you an email with all the errors and url. 🙂
A couple more Console Errors:
The attribute ‘border’ in tag ‘table’ is set to the invalid value ‘3’.
The attribute ‘cellpadding’ may not appear in tag ‘td’.
One more new one…
The attribute ‘color’ may not appear in tag ‘hr’.
@rawhyder,
Thank you for reporting the issue, we are going to release a big update in few days and I’m sure these issues will be fixed in the next update.
Our main focus is validation in this update.
Thank you once again for reporting the bugs.
Mohammed Kaludi
