Title: mg31's Replies | WordPress.org --- # mg31 [ ](https://wordpress.org/support/users/mg31/) * [Profile](https://wordpress.org/support/users/mg31/) * [Topics Started](https://wordpress.org/support/users/mg31/topics/) * [Replies Created](https://wordpress.org/support/users/mg31/replies/) * [Reviews Written](https://wordpress.org/support/users/mg31/reviews/) * [Topics Replied To](https://wordpress.org/support/users/mg31/replied-to/) * [Engagements](https://wordpress.org/support/users/mg31/engagements/) * [Favorites](https://wordpress.org/support/users/mg31/favorites/) Search replies: ## Forum Replies Created Viewing 2 replies - 1 through 2 (of 2 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Unexpected error found when trying to post – YOAST is causing it!](https://wordpress.org/support/topic/unexpected-error-found-when-trying-to-post-yoast-is-causing-it/) * [mg31](https://wordpress.org/support/users/mg31/) * (@mg31) * [5 years, 4 months ago](https://wordpress.org/support/topic/unexpected-error-found-when-trying-to-post-yoast-is-causing-it/page/4/#post-14495289) * 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 5 years, 4 months ago by [mg31](https://wordpress.org/support/users/mg31/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Unexpected error found when trying to post – YOAST is causing it!](https://wordpress.org/support/topic/unexpected-error-found-when-trying-to-post-yoast-is-causing-it/) * [mg31](https://wordpress.org/support/users/mg31/) * (@mg31) * [5 years, 4 months ago](https://wordpress.org/support/topic/unexpected-error-found-when-trying-to-post-yoast-is-causing-it/page/4/#post-14482555) * [@awhig](https://wordpress.org/support/users/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 5 years, 4 months ago by [mg31](https://wordpress.org/support/users/mg31/). Viewing 2 replies - 1 through 2 (of 2 total)