Here we go then. I’m in the pub and have just updated to Wordpress 5.0.1.
I started writing this post on my iphone.
My own blocks didn’t seem to work properly. I investigated later. After I’d upgraded oik-blocks to the latest version, everything was fine on my laptop.
With Classic Editor v1.3 per post switching between editors can be done using the Default editor current user Meta Box.
Last updated:December 18, 2018
Well that was a fuck up!
I’ve heard reports that the Classic Editor plugin was updated just a few hours before WordPress 5.0 was released and now there’s a completely different user experience.
The ability to easily choose the editor to create your content has disappeared. For me, that was the whole reason for having the plugin. Some things don’t work in Gutenberg / 5.0 so I need the ability to use both.
I don’t think the use cases for the Classic Editor and Gutenberg and WordPress version combinations have been thought through. I know that I am going to continue to want to use both Gutenberg and the Classic editor under WordPress 5.0. And I need the ability to easily select my preferred editor. That’s how it was with 0.5. It’s how I tested my sites’ compatibility.
You don’t bugger about with something hours before a release. You give people a chance to test it.
Lessons need to be learned. WordPress 5.0 release should have been delayed until:
Fortunately, I haven’t yet upgraded anything yet. I will be testing Classic Editor v1.1 very carefully.
Last updated:December 7, 2018