Latest Update (6.3.5) breaks AMP

  • Resolved Dave_S

    (@dave_s)


    7 years, 8 months ago

    Hi,

    I just got a warning from Google Search Console that my AMP (Accelerated Mobile Pages) no longer validate.

    I deactivated Wordfence 6.3.5 and now all AMP pages validate fine again. AMP also works fine with version 6.3.4.

    Update:

    I did just dig a bit deeper into the issue and discovered that this seems to be a problem in conjunction with Yoast 4.5:

    Yoast 4.5 + Wordfence (no matter which version): AMP errors
    Yoast 4.4 + Wordfence (no matter which version): no AMP errors
    Yoast 4.5 alone: no AMP errors

    So not sure what Yoast 4.5 introduced that lets Wordfence corrupt the AMP code.

    Cheers,

    David

    • This topic was modified 7 years, 8 months ago by Dave_S.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfphil

    (@wfphil)

    Hello David,

    Sorry to hear that you are having this trouble.

    I see that you have opened a support topic with Yoast as well.

    Can you open a browser console to look for any errors. There are two links below. One is our guide for opening a browser console, and the other is an AMP browser console validation guide:

    https://docs.wordfence.com/en/Open_the_JavaScript_console_for_troubleshooting_plugins

    https://www.ampproject.org/docs/guides/debug/validate

    Please let us know of any errors that you find.

    Also if you could go to the Diagnostics tab on the Tools page and scroll down to the Log Files section near the bottom you can download your log files that may also provide insights into what is happening. If you aren’t comfortable looking at the log files then please let me know and I can provide an email address you can send them to.

    Thread Starter Dave_S

    (@dave_s)

    Hi Phil,

    Thanks for your fast response. I investigated a bit further and apparently neither Yoast nor Wordfence are the culprit but W3 Total Cache.

    Apparently W3TC suddenly started to throw random php warnings when database caching is enabled. As these only appear randomly and not on all AMP pages it looked like the problem was Yoast together with Wordfence (as it randomly worked fine when switching back to Yoast 4.4).

    So I mark that as resolved so far. Thanks!

    Plugin Support wfphil

    (@wfphil)

    Hello Dave,

    You’re welcome. Glad that you found a solution. It would be helpful to me how you discovered that it was W3 Total Cache database caching that was causing the issue. If you are too busy then don’t worry. Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Latest Update (6.3.5) breaks AMP’ is closed to new replies.

Tags