My pleasure.
However…
While I understand the ‘turn everything off, go default’ scenario, it rarely fixes things IMO, and sometimes sounds like a standard response to all errors, of all plugins.
This is nonsense (with all due respect). Imagine cars. You go to the dealer and buy a Toyota. Then, you go to Auto Zone and get a bunch of aftermarket products… one of them being a modified exhaust pipe. Well, when your exhaust fails… how are you going to know if it is coming from Toyota; or the aftermarket part? Well, you take off the aftermarket part, and see if you still have the issue.
WordPress is much the same way. If you used WordPress with NO addons/plugins/extra themes… then you would have no trouble updating. You would always be using the ‘barebones’ vanilla installation of WordPress. The same thing countless developers use when they test new versions.
Now, when you begin adding plugins and themes (especially those not hosted on WP.org).. you are adding a BUNCH of code to WP that may not necessarily be written to the best standards. I mean, it’s not hard at all to get a WP plugin ‘out there’.
When you add all this 3rd party code… it opens the possibility that there may be conflicts. The ONLY way to determine what plugin/theme is causing the conflict is to perform the steps.
Yes, it sucks. Yes, it’s a pain. Yes, your customers are going to see a broken site for 2 minutes.
But, what is your alternative? Using older, less secure, outdated, more error prone versions of the software? Not me!
This is another reason I strongly urge people to set up a local installation of WP on their computer using XAMPP or WAMP. Make a duplicate of your live site.. and do your testing there.
I chose the shorter and easier path, and simply downgraded to 5.2 without changing any other thing, and the editor is working again.
Maybe shorter and easier… but in the long run… you will have regrets, and it will be more difficult at that time to make an upgrade. But, some of the best lessons in life are only learned through experience ??