Web Story is invalid

Hi there @rodrigodellarovere , thanks for reaching out. We’ll be happy to check on this for you. Can you please share the story URL for us to investigate?

Good night Luckyna, how are you?

The error started to appear in all urls, but I’ll pass one for you to see https://danidrops.com.br/web-stories/corte-de-cabelo-pixiecut/

I can see a few plugins that could potentially be causing a conflict here so could you try disabling the following plugins one by one checking your story each time you disable a plugin to see if this is causing the validation errors:

These errors are usually caused by plugin conflicts and I noticed a plugin that could cause a few of the errors. Could you please try deactivating the Ezoic plugin and retesting your story URL for any remaining validation errors?

Next, continue to disable plugins one by one then check your story each time to identify which could be the possible culprit.

If the validation errors persist, could you please provide your Site Health information, or you can share privately if you prefer via this form? This will help us troubleshoot the issue further.

As we haven’t received a response, I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist. Thank you!

Don’t you just love the way this topic was closed only 6 days later as resolved? It is most definitely not resolved. I am also having a similar problem and deactivated the Ezoic plugin. In talks with Ezoic, they have said they are trying to work with Google’s web story team to resolve the issue. So, yeah, it’s not resolved.

You know what? Instead of marking something resolved, when others have described the issue, why not find out what might be wrong on your end, Google? Marking something resolved doesn’t do anything but artificially increase your solve numbers.

This would be the same thing as a doctor putting in a faulty heart valve and finding out the patient was sick afterward. Sure, the doctor can remove the heart valve, mark it resolved and go home. However, other doctors and patients wouldn’t be aware not to use that heart valve and people could die – and doctors and hospitals would get sued. Isn’t it better for the manufacturer to repair the faulty units?

Thankfully, no one is going to die from this Google web stories plugin being incompatible with the Ezoic plugin, but that doesn’t mean the issue should be marked resolved – fix it!

@arbpen Thanks for getting in touch!

To clarify, it’s our standard practice to mark topics as “resolved” if we do not receive a reply from the requester within one week. The original requester is always welcome to reopen a topic if they still have questions. As such, I’m going to re-mark this topic as resolved.

As you’ve noted, marking a topic as resolved doesn’t necessarily indicate that the issue that they’ve reported has been fixed. We track broader issues that need to be addressed by our team in our GitHub repository.

Conflicts between Web Stories and other plugins are best addressed by the conflicting plugin with assistance and support from our Web Stories team as needed. Since plugin teams best understand their own codebase, they can often identify and address the issue much more quickly than the Web Stories team.

In this case, we are aware of the conflict between the Web Stories and Ezoic plugins. You and other Web Stories users have reported this to the Ezoic team and we are awaiting next steps from them, and we’ll continue to monitor the situation and answer any questions that the Ezoic team may have as they work to identify a cause and solution.

Bethany