Title: AMP errors since updating plugin
Last modified: October 9, 2016

---

# AMP errors since updating plugin

 *  [lbrownie](https://wordpress.org/support/users/lbrownie/)
 * (@lbrownie)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/)
 * Hello,
    My AMP traffic has plummeted since updating the plugin yesterday. None
   of my stories are showing up in AMP, and a note says “your page has AMP implementation
   errors.” Prior to the update, all was good. Any idea what’s going on or what 
   I should do?
 * Thanks

Viewing 15 replies - 1 through 15 (of 21 total)

1 [2](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/page/2/?output_format=md)

 *  [npfamilyrecipes](https://wordpress.org/support/users/npfamilyrecipes/)
 * (@npfamilyrecipes)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8267930)
 * I ran into the same problem with the 0.4 update. Before the update, I had no 
   errors.
 * “Accelerated Mobile Pages > Invalid CSS stylesheet”
 * Details:
    The text (CDATA) inside tag ‘style amp-custom’ contains ‘CSS !important’,
   which is disallowed. AMP URL: [http://www.npfamilyrecipes.com/recipe/vegetarian-stir-fry-glass-noodle-mien-xao-chay/amp/](http://www.npfamilyrecipes.com/recipe/vegetarian-stir-fry-glass-noodle-mien-xao-chay/amp/)
   Canonical URL: [http://www.npfamilyrecipes.com/recipe/vegetarian-stir-fry-glass-noodle-mien-xao-chay/](http://www.npfamilyrecipes.com/recipe/vegetarian-stir-fry-glass-noodle-mien-xao-chay/)
   Last detected: 10/8/16
 * Thanks
 *  [gooma2](https://wordpress.org/support/users/gooma2/)
 * (@gooma2)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8268371)
 * We had the same with 0 errors and once we updated now at 177 errors mostly AMP
   related:
 * AMP markup missing or incorrect and invalid use of AMP tags
 *  [npfamilyrecipes](https://wordpress.org/support/users/npfamilyrecipes/)
 * (@npfamilyrecipes)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8268589)
 * I de-activate the plugin for now 🙁
 *  [Li-An](https://wordpress.org/support/users/li-an/)
 * (@li-an)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8270388)
 * Same here.
 *  [pako69](https://wordpress.org/support/users/pako69/)
 * (@pako69)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8270445)
 * !important is forbidden into AMP CSS…
 * A also uptdated to 0.4 without any errors with the AMP Validator [https://validator.ampproject.org/](https://validator.ampproject.org/)
 * As you have removed you Amp posts it’s difficult to have a look at the errors
   you get 🙂
    Are you using anoher AMP WordPress plugin? Yoast Glue, etc.?
 *  [Li-An](https://wordpress.org/support/users/li-an/)
 * (@li-an)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8270662)
 * [http://www.li-an.fr/blog/zolies-images/art-therapy-mickey-amis/amp](http://www.li-an.fr/blog/zolies-images/art-therapy-mickey-amis/amp)
   
   with this error:
 *  `itemscope
 *  itemtype=”[http://schema.org/Article&#8221](http://schema.org/Article&#8221);
 *  prefix=”og: [http://ogp.me/ns#&#8221](http://ogp.me/ns#&#8221); >
 * <head>
 *  <meta charset=”utf-8″>
 *  <meta name=”viewport” content=”width=device-width,initial-scale=1,minimum-scale
   =1,maximum-scale=1,user-scalable=no”>
 *  <title>Art Therapy avec Mickey et ses amis | Le blog de Li-An</title>
 *  <link rel=”canonical” href=”[http://www.li-an.fr/blog/zolies-images/art-therapy-mickey-amis/&#8221](http://www.li-an.fr/blog/zolies-images/art-therapy-mickey-amis/&#8221);/
   >
 *  <script src=”[https://cdn.ampproject.org/v0.js&#8221](https://cdn.ampproject.org/v0.js&#8221);
   async></script>`
    -  This reply was modified 9 years, 8 months ago by [Li-An](https://wordpress.org/support/users/li-an/).
 *  [pako69](https://wordpress.org/support/users/pako69/)
 * (@pako69)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8270811)
 * [@li-an](https://wordpress.org/support/users/li-an/)
    Your HTML tag is not what
   it should be if you are only using AMP 0.4. This Tag is defined is the single.
   php template of the plugin with that: `<html amp <?php language_attributes();?
   >>`
 * So you should have that:
    `<html amp lang="fr-FR">`
 * But you have that:
 *     ```
       <html amp lang="fr-FR"
       	itemscope 
       	itemtype="http://schema.org/Article" 
       	prefix="og: http://ogp.me/ns#" >
       ```
   
 * Wich is not correct and it’s the reason why you get this validating error : “
   The attribute ‘prefix’ may not appear in tag ‘html ⚡ for top-level html”
 * Are you using any other AMP plugin like Glue Yoast or others?
    Did you cleared
   you Comet Cache? Can you please disable Comet Cache for this posts?
 * The last error you get is: “The mandatory tag ‘html ⚡ for top-level html’ is
   missing or incorrect.”
    > I think this is an error that come from the first error
   you get…
 * PS: je suis aussi français 😉
 *  [Li-An](https://wordpress.org/support/users/li-an/)
 * (@li-an)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8271112)
 * OK, no problem with Comet Cache but I have one unique plugin which interferes
   with og microdata and it’s All in One SEO. After desactivating it, the test is
   fine. So you have to see what new changing interfers or All in One SEO have to
   adapt itself. I will open a thread about the incompatibility on All in One SEO
   forum.
 *  [pako69](https://wordpress.org/support/users/pako69/)
 * (@pako69)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8271686)
 * [@li-an](https://wordpress.org/support/users/li-an/)
 * Glad you found the bug!
 * Before upgrading a plugin I always test it within a fresh wordpress install without
   any other plugins installed, that way, you can say that the issue you have come,
   or not, from this plugin 😉
 *  [Li-An](https://wordpress.org/support/users/li-an/)
 * (@li-an)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8271753)
 * Yes, I know I should test like this – it’s what I say on wpfr forum to the people
   who meet problems – but “it worked” and now “it does not work”. It’s taking so
   much time to test 🙂
 *  [npfamilyrecipes](https://wordpress.org/support/users/npfamilyrecipes/)
 * (@npfamilyrecipes)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8273582)
 * hi pako69,
 * I have the plugin enabled.
 * Here’s the error from search console
 * The text (CDATA) inside tag ‘style amp-custom’ contains ‘CSS !important’, which
   is disallowed. AUTHOR_STYLESHEET_PROBLEM
    line 13, column 2
 * I don’t have any other AMP plugin installed beside this one.
 *  [pako69](https://wordpress.org/support/users/pako69/)
 * (@pako69)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8274416)
 * hi [@npfamilyrecipes](https://wordpress.org/support/users/npfamilyrecipes/)
 * I found why you have thoses errors, and they are made by your plugin **WP Ultimate
   Recipe** that has “!important” in CSS Rules wich is forbidden.
 * This AMP plugin retrieve thoses rules into this:
 *     ```
       .amp-wp-inline-acfc10591ad6724049dc5658039906b8 {
           color: #000000 !important;
           font-family: Open Sans, sans-serif !important;
           font-size: 14px !important;
           padding-bottom: 10px !important;
           padding-left: 10px !important;
           padding-right: 10px !important;
           padding-top: 10px !important;
           vertical-align: inherit !important;
       }
       ```
   
 * The team of AMP plugin is aware of that bug and a new version of AMP plugin should
   be released soon :
    [https://github.com/Automattic/amp-wp/pull/525](https://github.com/Automattic/amp-wp/pull/525)
 * And you are not the only one : [https://wordpress.org/support/topic/error-css-important-the-answer/](https://wordpress.org/support/topic/error-css-important-the-answer/)
 * PS:I also suggest you to add somme CSS rules to your Simple Share Buttons Adder
   plugin, which break the layout of you AMP posts.
 *  [npfamilyrecipes](https://wordpress.org/support/users/npfamilyrecipes/)
 * (@npfamilyrecipes)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8274439)
 * hi [@pako69](https://wordpress.org/support/users/pako69/),
 * Thank you for your help. Also thanks for your suggestion on the simple share 
   buttons adder.
 *  [pako69](https://wordpress.org/support/users/pako69/)
 * (@pako69)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8274446)
 * You are welcome [@npfamilyrecipes](https://wordpress.org/support/users/npfamilyrecipes/)
   🙂
 *  [npfamilyrecipes](https://wordpress.org/support/users/npfamilyrecipes/)
 * (@npfamilyrecipes)
 * [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/#post-8274571)
 * hi [@pako69](https://wordpress.org/support/users/pako69/)
 * Just updated to 0.4.1. Validated PASS. Thank you and anyone that involved in 
   the fix.

Viewing 15 replies - 1 through 15 (of 21 total)

1 [2](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/page/2/?output_format=md)

The topic ‘AMP errors since updating plugin’ is closed to new replies.

 * ![](https://ps.w.org/amp/assets/icon.svg?rev=2527602)
 * [AMP](https://wordpress.org/plugins/amp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/amp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/amp/)
 * [Active Topics](https://wordpress.org/support/plugin/amp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/amp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/amp/reviews/)

## Tags

 * [AMP Plugin](https://wordpress.org/support/topic-tag/amp-plugin/)
 * [Google AMP](https://wordpress.org/support/topic-tag/google-amp/)

 * 21 replies
 * 6 participants
 * Last reply from: [pako69](https://wordpress.org/support/users/pako69/)
 * Last activity: [9 years, 8 months ago](https://wordpress.org/support/topic/amp-errors-since-updating-plugin/page/2/#post-8274913)
 * Status: not resolved