Unexpected error found when trying to post – YOAST is causing it!

  • Resolved amiltondeazevedo

    (@amiltondeazevedo)


    3 years, 10 months ago

    Hello, I’m experiencing the same errors as some other users, but since none of the answers helped me, here I am!

    Out of nowhere, while trying to create a new post, I’ve started to get the following unexpected error:

    
TypeError: Cannot read property 'SnippetEditor' of undefined
    at https://ruinaacesa.com.br/wp-content/plugins/wordpress-seo/js/dist/block-editor-1611.js:1:141386
    at zj (https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:13:24396)
    at Th (https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:10:10413)
    at tj (https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:10:10342)
    at Te (https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:10:7238)
    at https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:7:1114
    at unstable_runWithPriority (https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react.min.js?ver=16.13.1:2:7938)
    at Da (https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:7:824)
    at Pg (https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:7:1060)
    at ha (https://ruinaacesa.com.br/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:7:995)

    I’ve already checked the versions – both WordPress (5.7.1) and Yoast SEO (16.1.1) are updated and I’ve already installed the Health Check & Troubleshooting application, and it was throughout the troubleshooting mode is that I ensured that the problem was in the Yoast SEO indeed (with all plugins turned off, I could post normally; turning Yoast on would give me the error message). What can I do other than – I’d like not to – stop using the plugin? Thanks in advance.

    • This topic was modified 3 years, 10 months ago by James Huff.
    • This topic was modified 3 years, 10 months ago by Yui. Reason: please use CODE button for code formatting

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

Viewing 15 replies - 31 through 45 (of 52 total)
  • Plugin Support Michael Ti?a

    (@mikes41720)

    Hi @anacybele

    Can you also check and confirm if you are using the Imperva CDN?

    What we’ve noticed is that the issue here for some users is that the Yoast JS file is getting cut off by the Imperva CDN Cache. Some users have confirmed this and after clearing the cache, it resolved the issue, the JS error was no longer appearing.

    Can you please try clearing the Imperva CDN cache and check if the problem resolves?

    I didn’t know about the CDN stuff so I run a test on cdnplanet.com and it showed my URL is in Imperva. So I ended up in this address https://docs.imperva.com/bundle/cloud-application-security/page/settings/caching-settings.htm#Purge

    But to be honest, I don’t know what to do with these instructions at all. I don’t even have an Imperva account as it mentions before following the steps.

    What can I do next?

    Plugin Support devnihil

    (@devnihil)

    @anacybele Thanks for your reply and we’re sorry to hear you aren’t sure how to proceed with fix for this issue.

    If you can see that your site is using the Imperva cache when you test the URL, but aren’t sure how to clear the Javascript file from your site’s cache, we would recommend contacting your hosting provider for assistance. Even if the hosting service that they provide you doesn’t offer you direct access to clear the cache from Imperva, the hosting administrators will be able to upon request from you.

    @devnihil Yes, I tried that as well for testing. The same behavior occurs. The first hit, the full file is served. Every hit after that, the truncated file is served.

    I believe the Sitelock/Imperva CDN is screwing something up.

    Rich

    @anacybele Please check if you are using Sitelock on your hosting Account. If you are, then I believe Imperva is the CDN branded by Sitelock. You should be able to get to a Sitelock dashboard, and can clear the Trueshield cache. Though clearing the cache for me does not permanently fix the issue. It returns after 1 or 2 hits.

    Rich

    Thread Starter amiltondeazevedo

    (@amiltondeazevedo)

    Hello.

    Updating my situation: I followed the instructions regarding clearing CDN Cache (my site is also using Sitelock) and posting started to work normally. So maybe that settles – the problem is a conflict between Imperva CDN and Yoast, is that it?

    Apart from continuously clearing the cache, what could I do? Report the issue to Sitelock, perhaps?

    Also, thanks for all the attention and explanations, fellow users – and specially the plugin support.

    • This reply was modified 3 years, 10 months ago by amiltondeazevedo. Reason: correcting the english, lol

    I contacted the hosting administrator and he told me to install WP Super Cache and check some of the advanced options but it didn’t work. It was supposed to clear the cache. Maybe I’ll give up on Yoast, it is so frustrating not to know how to deal with such advanced settings. I’m not familiar with these things…

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi @anacybele

    Were you able to ask the hosting administrator regarding the Imperva cache specifically? We understand your frustration regarding the plugin not functioning as expected. To be clear, the full file is served on the host side, but something on their end is altering the output of our JS file, which is causing issues when it arrives on the client’s browser. We are contacting Imperva regarding this concern.

    Hey guys, thank you all! I found another hosting staff member to help me. She guided me on how to access the SIteLock settings and this time it worked. Thanks a lot, you really made my day!

    @anacybele
    Can you share what you found out? I have not been able to fix the issue permanently.

    Rich

    • This reply was modified 3 years, 10 months ago by awhig.

    @awhig sure! I had to access my hosting panel, and inside it I reached sitelock dashboard > trueshield settings> clean cache.
    I hope it can be useful for you too. Let me know if there is something missing.

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    @anacybele Thanks for your confirmation on this. We have forwarded the relevant information to our development team as well to see if we can figure it on our end as well.

    Have a fantastic rest of your week!

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

    I am having the same issue and, as others have noted, the problem is only temporarily fixed after clearing the cache under Trueshield settings. It continues to come back. Has anyone found a permanent solution?

    I never found a permanent solution. We ended up cancelling SiteLock to get rid of the Trueshield cache that was causing the issue.

    Weird thing is that, even with turning off Trueshield using the controls, it still didn’t actually turn off Trueshield. If that worked, maybe we would have kept Sitelock.

    Problem solved!

    Rich

Viewing 15 replies - 31 through 45 (of 52 total)
  • The topic ‘Unexpected error found when trying to post – YOAST is causing it!’ is closed to new replies.