Classic Editor plugin encourages using Block Editor – why?

Hi,

I just installed the 1.1 update, I went to the posts screen and the first option that I see when I hover the page title is “Block Editor”.

If someone installs the Classic Editor plugin, it means that they don’t want to use the block editor. The option to switch between editors (Allow users to switch editors) should be disabled by default if one chooses to use the Classic Editor plugin.

In the past several weeks, we’ve been instructing our users to install the Classic Editor plugin because with the current state of Gutenberg, there is no way to safely convert our elements to blocks. We had the peace of mind that the Classic Editor will help us keep the things in the way everything used to work.

We’ve been relying on the Classic Editor plugin and now, all the Classic Editor plugin does, is encourage using the block editor as first option. The truth is that not every user is aware of the difference between Classic Editor and Block Editor and this option to switch between the editors can be confusing to many.

If we, as developers, have decided to enable the Classic Editor plugin, it means that we don’t want our users to use the block editor as it is currently not ready and it could break their sites. What is the point to use the Classic Editor plugin if it by default encourages using the block editor? Are we now supposed to ask them to do the extra step and go and update their options to disable the editor switching?

Please make the option to switch between editors disabled by default or at least make the classic_editor_plugin_settings filter work in themes. The classic_editor_plugin_settings filter runs upon the plugins_loaded action, which is before the theme is loaded and therefore, we cannot control this option from our themes.

• This topic was modified 5 years, 11 months ago by Deni.