First WebStory AMP Issues

@jhardin01 To confirm, what happened when you switched to a default theme like Twenty Twenty One? Did these issues persist?

-Tag amp-story is not allowed to have any sibling tags. (‘body’ should only have 1 child)
-Tag found outside the document head which is only allowed as a direct child of the document head
-Only amp-boilerplate and amp-custom ‘style’ tags are allowed, and only in the document head

Same errors, yes

https://search.google.com/test/amp/result?id=hTjYrkAD7d36WOgF_qexZA

i am on the 2021 theme now

Hi, just checking on an update! I do appreciate the help

@jhardin01 Hi there, it looks like the offending code is <script type="text/javascript" src="https://jordibhealthandfitness.com/sitespeed-js/d41d8cd98f00b204e9800998ecf8427e.js"></script><script type="text/javascript">

I’m curious if this may be coming from Grow Social Pro by Mediavine optimization. Could you test this by disabling the plugin and retesting your Story URL?

Yes, let me try that one again. I’ll keep it off for several minutes and rerun a few times.

Yes, errors are still there

@jhardin01 Thanks for sticking with it. Let’s try disabling all other plugins except Web Stories for just a moment to test.

1. Temporarily disable all plugins
2. Enable only Web Stories
3. Activate GeneratePress theme
4. Test your Story URL in AMP test tool

Please let me know once you’ve done this and I can check in test tool as well.

All plugins except webstories deactivated with Generate Press as theme.

I still get the errors.

I will keep these setting until you tell me to change them!

@jhardin01 Thanks so much! Now, keep all the plugins disabled and please try:

1. Deactivate GeneratePress theme
2. Activate default theme like Twenty Twenty One
3. Retest story URL

I am on 2021 now. Currently testing

Only javascript

I just reran it again and got all 4 errors

@jhardin01 Thank you. Please leave everything disabled/deactivated for just a few minutes while I check.

thank you!

@jhardin01 With all plugins disabled and using a default theme these issues still persist. It could be an issue from the site/hosting level. Could you contact your web developer or hosting provider to access the PHP error/ WP DEBUG logs? Temporarily setting define( ‘WP_DEBUG’, true ); and define( ‘WP_DEBUG_DISPLAY’, true ); in your wp-config.php file should show you an additional error message that can help us track down the issue.