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

@jhunter622 I’ve noticed that my issue is back as well. Unfortunately, it is not interesting neither practical such a commitment to fix the problem as often as it seems to be necessary. ??

Thanks, @awhig. Did you do anything in addition to canceling to remove Sitelock? I also canceled Sitelock and everything was great … at first. Today, I got another editor error. ??

Update: Upon troubleshooting a separate issue with Sucuri, I discovered that I had forgotten to remove the server IP from my “hosts” file. After I did this, the problem was resolved.

@awhig So, I found a really strange solution to the .js file not fully loading.

So, I pulled up the file through the URL and found that it was printed entirely on 1 line. Scrolling to the very end, I noticed that the script was cut off at a seemingly random position. Not at the end of a command, just a random character in the script. Refreshing the page showed that it still cut off at the same position.

I inspected the file via the plugin editor and found that it was also written entirely on 1 line. I had the thought that maybe the browser could only load so many characters on a single line, so I edited the file so that the script was split between multiple lines.

It worked. I no longer receive the error.

At first, I still got the error on other computers and other browsers, but waiting 24 hours solved that issue as well.

I’m not sure how this works, but maybe it’ll help out everyone here.

• This reply was modified 3 years, 6 months ago by mg31.

This is the same situation I am in still. I am on bluehost and using sitelock. Done the purge several times and still got the error. Yoast would randomly work and it was working when I updated the plugin yesterday but it went back to the broken state.

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

Also, when I disabled gutenberg through WPBakery I got this error instead.

TypeError: r is not a function
    at https://www.newheightseducation.org/wp-includes/js/dist/components.min.js?ver=05cdf30cf2623cd4539a5c19832b0114:1:310660
    at Bh (https://www.newheightseducation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:9:8089)
    at Dj (https://www.newheightseducation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:11:3529)
    at unstable_runWithPriority (https://www.newheightseducation.org/wp-includes/js/dist/vendor/react.min.js?ver=16.13.1:2:7938)
    at Da (https://www.newheightseducation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:7:824)
    at xb (https://www.newheightseducation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:11:3284)
    at mk.Events.current (https://www.newheightseducation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:13:25865)
    at Ei (https://www.newheightseducation.org/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:3:7199)

So we’re back to square 1. I’m now getting the same error. Even worse, when I try to inspect “search-metadata-previews-####.js”, it doesn’t appear in the sources tab. This is infuriating. The entire file doesn’t seem to be loading.

• This reply was modified 3 years, 6 months ago by mg31.

@mg31 To reiterate, the only permanent solution we found was to get rid of the Imperva cache, which was implemeneted through Sitelock on our website. Turning off the Sitelock CDN via the control panel did not even work. I believe something is wrong with that. We had to get rid of Sitelock completely off of the account. At least we got a refund.

Rich