awhig

@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

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

@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, 7 months ago by awhig.

@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

@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

In my case, I think I’ve finally narrowed down the issue to the Sitelock CDN which uses Imperva CDN. It is not serving the full JS file. If I clear the CDN cache, the full file is served once. After that, the truncated JS file is served. Please see my comments at https://www.ads-software.com/support/topic/unexpected-error-found-when-trying-to-post-yoast-is-causing-it/page/2/#post-14357813

Ok. Now I’m mad. It worked for several hits, but then reverted back after I checked a few minutes later. Going to fully turn off sitelock now, and see if that does it.

I set it to “Temporarily Bypass Sitelock’s network” and that didn’t help. Same behavior. I purge the cache and it works for one hit. Then reverts to the truncated file. Interestingly, the x-cdn header still shows Imperva, even though I turned off Sitelock I thought.

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

Ok. I was able to permanently fix the issue by going to SiteLock, and under Settings, Traffic Routing, turn off “Use Trueshield for prevention”.

After clearing the Sitelock cache. It works once, and then reverts back to the truncated version.

Argh.

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

Ok. I figured it out. On our Bluehost account, we have
“Global Sitelock CDN/WAF Premium”. In the sitelock dashboard, under “Settings”, “Trueshield Settings”, there is a “Purge Cache” button. Clicking that, and going back to the JS file, the complete file was served.

Very maddening to find this. Bluehost tech support, did not know the connection between Sitelock CDN and Imperva. Even after I fixed the issue, he insisted Imperva was something else. My theory is that Sitelock CDN is outsourced to Imperva. Maybe someone knows for sure.

**** UPDATE. ***

The file gets served fully once or twice, then reverts back to the incomplete version. If I clear the Sitelock cache again, it works once or twice, then incomplete file gets served again. I have no idea what is going on.

*** END UPDATE ***

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

We are using Bluehost. I believe Imperva is implemented by them. There are some controls under the performance tab for the site. I tried clearing the cache. I also tried turning off the caching via their controls, but did not see any change. In fact, I could still see the Imperva tag in the response headers after turning caching off. Not sure how exactly to turn off Imperva. Will open a ticket with bluehost.

I believe I found the source of the issue. I have another WP installation that is working ok. The full JS file is being served.

The file that is throwing the error on my other server is truncated. I double checked that the file was complete by examining the JS file through the plugin editor, and it is ok. When I look at the file through the URL, served by the server, it is truncated. You can see it here:

https://collectededitions.com/wp-content/plugins/wordpress-seo/js/dist/yoast/search-metadata-previews-1611.js

The full file is 78K. This file is only 54K. So it must be an HTTP server setting that is limiting the full file from being served? This WP installation is on a shared server, so I’ll have to see what I can do from my end.

I’m also getting the error on Windows

Edition	Windows 10 Home
Version	20H2
Installed on	?12/?1/?2020
OS build	19042.928
Experience	Windows Feature Experience Pack 120.2212.551.0

Using Chrome Version 89.0.4389.128 (Official Build) (64-bit)

I updated to Version 90.0.4430.85 (Official Build) (64-bit) and still get the error.

jquery-migrate.min.js?ver=3.3.2:1 JQMIGRATE: Migrate is installed, version 3.3.2
search-metadata-previews-1611.js:1 Uncaught SyntaxError: Invalid or unexpected token
react-dom.min.js?ver=16.13.1:9 TypeError: Cannot read property 'SnippetEditor' of undefined

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

Unhappy to report that another user on our site is still not able to edit posts. He updated chrome to latest, cleared cache and cookies and this did not work. Is using Version 90.0.4430.85

He then installed Firefox and was still not able.

He is using Mac OS Mojave.

Rich

I do not have the SSO plugin or the Endurance Page Cache plugin.

My issue was resolved after updating my Chrome on MACOS
Version 89.0.4389.114 -> Version 90.0.4430.72 (Official Build) (x86_64)

No other plugins were enabled/disabled besides YOAST, when narrowing down the issue.

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