Hi @csc721 thanks for reaching out. It looks like the issue here is that you are using a CDN which is rewriting many of your URLs in the source code of your site to use stackpathdns.com for example: https://730009-2439504-raikfcquaxqncofqfm.stackpathdns.com/.
This is causing the validation error because the URL is different what is being expected. You will need to address this to clear the AMP validation error you are seeing. This will need to be done via your CDN settings which falls out of the scope of Web Stories support.
Please do let us know if you you fix this and are still experiencing issues with your Web Stories and we can look further into this for you.
Thread Starter
csc721
(@csc721)
Hi @adamdunnage,
Can you give me the info regarding CDN settings? Thanks
@csc721 for assistance with your CDN settings you will need to reach out to the CDN providers support forum where they will be able to help you further with that.
Thread Starter
csc721
(@csc721)
@csc721 Running your story through AMP validation I can still see reference to the mentioned url above: https://validator.amp.dev/#url=https%3A%2F%2Fjoyfuldumplings.com%2Fweb-stories%2Fpassionfruit-overnight-oats-dairy-free%2F.
This will also need to be addressed to clear this error. You will need to continue to work with the CDN provider to resolve this.
Once this has been cleared please let me know if you are still seeing AMP validation errors on your stories.
Thread Starter
csc721
(@csc721)
@adamdunnage I can’t reach Cloudfare customer service…Can you share the info about the CDN settings. Thanks
@csc721 Unfortunately this is not part of our product so you will need to get assistance from Cloudflare. You may be able to find some help from the Cloudflare community, documentation etc by searching here.
Hope you can find a guide here to help with your issue. As mentioned before if you manage to find the solution and clear this message but still experience with your Web Stories then please let us know.
@csc721 We are going to mark your topic as resolved as we haven’t received a response. Please feel free to open a new support topic if you continue to experience any issues. Thank you!
Thread Starter
csc721
(@csc721)
@luckynasan
I’ve reached out to Cloudways technician, they replied me “could you please share if they have any logs regarding the issue related to Cloudways CDN as we could not find any problem related to it?”
Can I have any logs regarding the issue related to Cloudways CDN? Thanks
Hi @csc721 I have checked your Web Story once more and can no longer see reference to stackpathdns.com. I can still see an AMP validation error however which you can see here: https://search.google.com/test/amp/result?id=9B7vjfccXDGx3TJxwMwnOA.
I’d be happy to look into this further for you if you could provide your Site Health information or You can share privately if you prefer via this form.
@csc721 Checking in here! I’m still seeing the “The mandatory text inside tag script amp-onerror is missing or incorrect.” error on the test for your story. If you’d like some help with fixing this error, please provide your Site Health information via this private form and we’d be happy to help. Thanks!
Thread Starter
csc721
(@csc721)
@shetheliving I’ve submitted the Site Health Information via that private form. Please check, thanks.
@csc721 thanks for providing the Site Health Information. I can see you have several active plugins. There could be a plugin conflict causing this so if possible would you be able to manually deactivate plugins one by one and between each run your story through the AMP validator. For best results, use an incognito window when performing the AMP validation to avoid any cached results.
If at any point the story returns as valid then it means that the plugin previously deactivated is causing a conflict. Let me know how you get on with this and if you have any further questions.
Thread Starter
csc721
(@csc721)
@adamdunnage Can you suggest me a plugin for detecting plugin conflicts?
That will help me a lot. Thanks.
@csc721 Unfortunately I cannot recommend a plugin that will do this. The reason for this is that plugins with this functionality only replicate the plugins being deactivated on the backend and as a result the AMP results are not refreshed.
This means that you will have to manually deactivate these plugins for the AMP validation results to refresh when running them through the validation tool.
