It was the same issue!
Maybe, maybe not. This is why it helps to start your own threads, so that others can more easily find your question and perhaps answer them for you.
In your case, I can see that your site is running behind an nginx Proxy doing request caching, so the likely explanation for your problem is simply that you didn’t clear that particular cache, and that it is probably configured to ignore query strings.
This means that while your site is indeed updated, the requests to get the javascript code from your site are still getting the old javascript. Old javascript comes from the proxy cache and thus, voila, the javascript based editors are partially broken.
I can tell these things because your site is returning these strings in the response header:
x-cache-enabled:True
x-proxy-cache:HIT
If the problem magically clears itself up in a week or so, because the cache expires, then you’ll know that was the problem. Alternatively, you could look into your configuration, and possibly ask your host about it. They may want to adjust the proxy_cache_key
setting to include the $args for the query string, because WordPress uses query strings on JS files as a cache-buster. So, the caches should not ignore query strings, really.