• Resolved csc721

    (@csc721)


    After I published this web story, The checklist showed “Priority-Compatibility.”
    Then I ran a test on AMP test, it showed” The mandatory text inside tag ‘script amp-onerror’ is missing or incorrect.”

    I further ran AMP tests on all my previous successfully published web stories, they all showed exactly the same error message, which means they are all currently invalid…

    Please help…

    The page I need help with: [log in to see the link]

Viewing 15 replies - 16 through 30 (of 30 total)
  • Thread Starter csc721

    (@csc721)

    @adamdunnage I’ve tried to deactivate all my plugins one by one, and then ran AMP tests on each of them…My web stories are still invalid…

    The first is to contact my hosting company, now is something to do with my plugins…

    I feel like it’s a pure hassle now…

    This is the first WordPress plugin that is so troublesome I’ve encountered by far.

    @csc721 I appreciate the time you’ve spent troubleshooting this with us and understand your frustration. If you are willing to troubleshoot some more with us it would be great if you could provide the following.

    1. Do you see any browser console errors when in your Web Stories editor?
    2. When editing the affected story do you get any checklist errors or warnings?

    These could help us to detect what may be causing the AMP errors you are getting on your story.

    @csc721 Just to follow up once more on this and explain that the reason we are asking for all these checks with the hosting provider, plugins, console errors etc is because there are a number of components interacting with the Web Stories plugin.

    The initial checks with hosting provider was due to the fact that we noticed a CDN rewriting urls which you helpfully resolved with your host.

    Web Stories make use of the AMP framework which is why AMP validation is performed on them while in the editor and why it’s important that they pass validation. Plugin and theme conflicts are often the cause of these AMP validation errors which is why it’s good to rule this out.

    With these first two checks complete, it would be useful to see if you can see any console or checklist errors which may highlight something that could be contributing to the AMP error you are seeing on your stories.

    Again, I understand this is frustrating but it’s absolutely necessary to run through these checks so that we can narrow this down and get this resolved for you which will fix all your web stories with this error.

    Thread Starter csc721

    (@csc721)

    Hi @adamdunnage

    I’ve attached two screenshots as the links down below:

    https://prnt.sc/8AfUITt_pNiX

    https://prnt.sc/d0RiIP–Se2q

    Cheers.

    @csc721 Thank you I can see the first of your screenshots but not the second which I presume was the console errors? Would you be able to provide a new screenshot showing these if you can see any?

    Thread Starter csc721

    (@csc721)

    @adamdunnage The second screenshot is here https://prnt.sc/y5P6vE8W0PF0

    Thanks

    @csc721 Thanks for providing this. After looking at this in more depth I can see that something is injecting your site URL into the amp script onerror.

    Here is how it should look:
    <script amp-onerror="">document.querySelector("script[src*='/v0.js']").onerror=function(){document.querySelector('style[amp-boilerplate]').textContent=''}</script>

    Here is how yours currently looks:
    <script amp-onerror="">document.querySelector("script[src*='https://joyfuldumplings.com/v0.js']").onerror=function(){document.querySelector('style[amp-boilerplate]').textContent=''}</script>

    As you can see the src*= value is being changed by something to your site URL which is causing this AMP validation error. This could be a caching plugin that is trying to self host JavaScript. At this point I would suggest deactivating all plugins except for your Web Stories and check your stories once more to see if the error is gone. If it is then activate the plugins one by one checking your story between until you find the plugin causing this.

    It may be a setting in the plugin that you can change or switch off or you may need to contact the plugins support team but please let me know if you do find the cause.

    If you have any other questions about this then let me know.

    Thread Starter csc721

    (@csc721)

    @adamdunnage

    I use WP Fastest Cache and Perfmatters.
    In order to get my web stories valid, I need deactivated both plugins( I tried leave one another on, didn’t work)

    Can you recommend cache plugins that is compatible with Web Stores?

    Thanks

    @csc721 If you deactivate both plugins does this clear the AMP issue you are having on your stories? If yes then you will need to work out which one is causing the errors and could potentially reach out to that plugins support to see if they could address the issue or as you say switch to another plugin to do this.

    Unfortunately I am unable to recommend any other plugins for you to use.

    Thread Starter csc721

    (@csc721)

    @adamdunnage Yap…I need to deactivate both to clear AMP issue.
    Have you heard of other users who have the same problems with these two plugins?

    @csc721 This could be linked to a specific setting in one of the plugins so you could try to pinpoint that out by toggling specific options. Could I also ask if you have tried clearing all cache and delete cache and minified JS/CSS from WP Fastest Cache? If not does this help to clear the issue without deactivating the plugin?

    Thread Starter csc721

    (@csc721)

    @adamdunnage I did delete cache and minified JS/CSS from WP Fastest Cache, and the issues remain stays.

    @csc721 thanks for confirming. I am unable to currently recreate this on my side so I think at this point it would be worth contacting the plugins support teams who may be able to assist you further.

    Thread Starter csc721

    (@csc721)

    @adamdunnage Ok, thank you so much.

    @csc721 You’re very welcome and good luck with your stories.

Viewing 15 replies - 16 through 30 (of 30 total)
  • The topic ‘Compatibility issue’ is closed to new replies.