Not a valid AMP page

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

  • @staysnatched Hi there! Thanks for following up and reaching out with your topic. Sorry to hear there is still a validation error.

    According to the AMP specifications, the only “child” element in the body tag should be “amp-story” and if there are other child elements in <body> they are disallowed.

    It’s possible there is another plugin that may be conflicting or incompatible with the Web Stories plugin.

    Could you please install the Health Check & Troubleshooting plugin and through plugins one by one to find the one that may be conflicting?

    This allows you to enter “Troubleshooting mode”, which allows you to temporarily use your site with only Web Stories active, and no other plugin.

    Note: this does not affect other users or your site’s visitors. Troubleshooting will only be enabled for yourself.

    Thread Starter staysnatched

    (@staysnatched)

    Which plugins are required in order for it to work? I’m using AMP, Webstories, and Stackpath (which I need to clear my cache each time in order to test the changes) and even with just those 3 plug ins, I’m getting the same message.

    Is there a way for me to test it without having to clear my cache each time?

    @staysnatched Although Web Stories are powered by AMP, the official plugin is not required to be enabled for it to work. Web Stories does not require other plugins to work which is why we were curious if this issue occurs when only Web Stories was activated.

    You mentioned you are using Stackpath. We’ve previously had incompatibilities with Web Application Firewall (WAF) services before, but there was work to improve the compatibility in our latest release.

    If possible, could you try temporarily disabling the WAF for the /wp-json/web-stories/ route and tell us if the issue persists or not?

    Thread Starter staysnatched

    (@staysnatched)

    This ended up being an issue with AMP settings checked with Mediavine. It’s fixed now, so this can be closed. Thanks for your help!

    @staysnatched Thanks so much for following up. I was curious in your other topic opened if it could have been related to AMP settings in Mediavine. \

    Would you mind sharing what settings you updated?

    @staysnatched we’re going to close your topic now since we have not received a response. If you have any further information to add to the topic about your Mediavine settings we welcome it.

    Thread Starter staysnatched

    (@staysnatched)

    Sorry about that! I was away from my computer for the holiday. Mediavine has a GDPR AMP setting that I checked off that fixed it.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Not a valid AMP page’ is closed to new replies.