AMP Bug?

  • Resolved danescobar

    (@danescobar)


    8 years, 4 months ago

    Hi Team Automattic,

    Recently AMP validator tools have started to throw this error in all AMP pages since 11/19 making all AMP pages invalid:

    The attribute ‘src’ in tag ‘amp-anim extension .js script’ is set to the invalid value ‘https://cdn.ampproject.org/v0/amp-anim-0.1.js’ defer onload=”

    Is this caused by your plugin which may be outdated or an incompatibility with other? I’m only using Yoast Glue and AMP Woocommerce besides yours. I deactivated both and the problem persisted.

    Thanks for your attention.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Weston Ruter

    (@westonruter)

    8 years, 4 months ago

    I’m seeing the same at https://validator.ampproject.org/#url=https%3A%2F%2Ffindgoodhealth.org%2Fvitamins-for-hair-growth%2Famp%2F

    It looks like you may have a theme, plugin, or server module that tries to improve performance by adding defer to all scripts. This would probably be the reason for the problem.

    Thread Starter danescobar

    (@danescobar)

    8 years, 4 months ago

    Hmm I’m currently using Autoptimize but only activated optimize js code and no other option in that section. Other optimization plugins I’m using are WP Super Cache, WP-Optimize and WP-Disable. I have difficulties finding which plugin could be adding defer to all scripts. I’ll investigate further but would be appreciated for any help. Thanks for pointing me in the right direction Weston.

    Thread Starter danescobar

    (@danescobar)

    8 years, 4 months ago

    Finally found what was causing the defer onload bug. A code snippet I added several days ago from a “guide” to improve performance. It’s becoming increasingly hard to find reputable sources of information online offering reliable and tested advice, I’ll be more careful in the future.

    Thanks a lot for all the help.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘AMP Bug?’ is closed to new replies.