We manage roughly 70 WP sites on behalf of our clients. A few of them maintain active staging accounts, and its within these accounts that I witnessed just how destructive Gutenberg can be. We make extensive use of Advanced Custom Fields, particularly the Flexible Content feature. Our least broken version of a broken site featured the Gutenberg editor and none of our custom fields. In the worst version, absolutely nothing loaded, not Gutenberg, not our layout editor (custom-built by us, but only using core ACF functionality), nothing – just the menu on the left and a blank screen on the right.
At best, this should be an optional plug-in you can use to replace the established TinyMCE editor. It should NOT be core, and should not be a forced download, whether as part of the core or plug-in. If I had it my way, it would simply be scrapped. I know neither of these things will happen, but unless there’s a major restructuring of Gutenberg or WP commits to supporting the original editor as part of core indefinitely, it’s going to be a LONG time before we upgrade any of our clients to 5.x. FYI, I tried installing the Classic Editor plug-in on top of Gutenberg, and it did not work. I had to deactivate Gutenberg entirely. I haven’t played with the beta, so I’m not sure if the Classic Editor plug-in will override Gutenberg properly when Gutenberg is part of the core build, but in the interest of ensuring the Classic Editor doesn’t get pulled out from under us in the future, we are freezing upgrades for the immediate/foreseeable future.
- The topic ‘Breaks every site’ is closed to new replies.