Errors on Debug Tab After Viewing

I assume you are referring to https://birdzofafeather.ca/web-stories/pallet-shelves-diy/?

A couple of things I see at first glance:

1. The logo on the first page has an invalid link. This causes the INVALID_URL error. So you’d wanna fix that. We’ll look into better flagging this kinda error already in the editor.
2. The subtitles file for the video on the second page is referenced via HTTP instead of HTTPS, causing the subtitles not to show up. That causes the INVALID_URL_PROTOCOL error. (Aside: the file has some unicode issues)
   Try removing the subtitles and adding them again. Maybe you need a plugin or something else to convert the HTTP URLs to HTTPS in the database to fix this kind of mixed content issues in the future.

The other two issues could be related to a server configuration issue. If you could provide what information you can from your Site Health info privately through this form that would be great.

Thank you for your help; sorry for the delay; I have submitted the form.

Just an update: I’ve been working on your two suggestions since submitting the form:

1. I fixed the INVALID_URL error.

2. I also fixed the subtitles file and it now shows properly on the story. However, these two fixes only eliminated one error and there are still 4 issues showing in the Debug area as follows:

WRONG_PARENT_TAG?at?1:0

The parent tag of tag 'html' is '$root', but it can only be '!doctype'.

INVALID_URL_PROTOCOL?at?156:4140

Invalid URL protocol 'http:' for attribute 'src' in tag 'track'.

MISSING_REQUIRED_EXTENSION?at?158:10602

The tag 'amp-story-auto-analytics' requires including the 'amp-story-auto-analytics' extension JavaScript.

MANDATORY_TAG_MISSING?at?183:244

The mandatory tag 'html !doctype' is missing or incorrect.

Learn more

182| </amp-analytics>

183|<amp-story-social-share layout="nodisplay"><script type="application/json">{"shareProviders":[{"provider

MANDATORY_TAG_MISSING?at?183:244

The mandatory tag 'html !doctype' is missing or incorrect.

@sarator Thanks for sharing the information. When checking the information you kindly provided i can see you have a number of active plugins. A couple of these stand out as plugins we have seen conflicts with in the past. Could you please try and temporarily disable the following plugins on your site:

• Ezoic
• Jetpack

Once disabled, run your Story URL through the AMP validator once more and see if any more errors are cleared.

The INVALID_URL_PROTOCOL error is still there because the link on your first page is still incorrect.

The other issues are likely all because of the same root cause. As Adam mentioned, it’s likely because of a plugin conflict, but it could also be a server configuration issue (e.g. outdated PHP version).

Thank you @adamdunnage and @swissspidy! I disabled Ezoic first and that cleared ALL the remaining errors. However, Ezoic is our ad network and without that we won’t earn any income on our site so that defeats the purpose of having web stories. Do you know if there’s anything I can tell Ezoic if I open a ticket that they might be able to do on their end?

@sarator Glad we could find the cause of the conflict there. As the conflict is with the Ezoic plugin I would suggest reaching out to the team there as you have mentioned and explain the issue you are facing and they should be able to guide you on what could be causing this from their side.

Thank you for you help. Dealing with Ezoic is frustrating. They don’t understand the issue so want access to my site but I really don’t want them messing around in there.

I can’t be the only blog having a conflict with Ezoic’s plugin if it’s something you’re aware of and have seen conflicts with in the past. I may have to change ad networks if I want to publish web stories.

@sarator I understand your frustration but as the conflict is on the Ezoic side there is little we can do here as we are limited to support on the Web Stories plugin.