Logic bug in Classic Editor 1.0

@azaozz Would suggest to fix this logic bug very soon, so finally the plugin really works as expected and as promised.

People are getting really upset in various forums, chats and social media platforms, wild conspiracy theories about behind-the-scenes influence of Automattic and money coming up and being discussed. Further delays and/or other features or notices which still point to Block editor after installing this plugin won’t really help here, all this gives the voluntary supporters and developers already a bad name now. ??

Everyone needs to realize that the author of this plugin is part of the core WordPress dev team. That team wants to encourage everyone to move to Gutenberg, come hell or high-water. I understand everyone, like myself, that installed this plugin wants the classic editor by default once it’s activated, and we don’t want to fiddle around with it once it’s activated. That’s not what Matt nor the core team wants. They really want to push people towards Gutenberg in a big big way. The push-back from the community against Gutenberg has been more pronounced than they (and I, for that matter) expected. In the last 24hrs GB proponents are quashing voices and moderating out discussions on facebook groups that are legitimate grievances or sound ‘too negative’ on Gutenberg. It’s very shocking to see this happen.

Default was changed in the dev. version. It also disables Gutenberg together with the Block Editor. Could you test? Can be downloaded at the bottom here: https://www.ads-software.com/plugins/classic-editor/advanced/.

Default for “Allow users to switch editors” seems to work as expected now with Classic Editor 1.2.

The message “The Classic Editor plugin prevents use of the new Block Editor. …” in “About WordPress“ still shows regardless off any setting.

Thanks Andrew, the dev version and now version 1.2 have much saner (for developers) defaults. I really appreciate you listening on this one.

The message “The Classic Editor plugin prevents use of the new Block Editor. …” in “About WordPress“ still shows regardless off any setting.

Right. Fixed that on GH, will be in the next version.

I believe this thread is (mostly) resolved in 1.2? ??

@azaozz When updating a few WordPress 4.9.8 sites from 0.5 to 1.2 today, the “Try Gutenberg” panel re-appeared in WordPress dashboard. It was hidden before and should stay hidden. Is that a known issue?

I noticed the “Try Gutenberg” panel too. My thoughts are that if we have explicitly chosen to turn off Gutenberg then this panel probably should not show either. Does this need a new support topic?

Hmm, can’t see it here (just checked again). What version of Gutenberg do you have? Tested here with 4.5 and 4.6.

In my case I am on WordPress 4.9.8 on all sites and I don’t have the Gutenberg plugin installed

• This reply was modified 5 years, 11 months ago by davemac.

Uh, I see the problem… (that’s what happens when fixing stuff at 2am). Will push 1.3 with a fix shortly.

@azaozz “Try Gutenberg” panel showed up in same context as described by @davemac, seems to be fixed with Classic Editor 1.3, thanks for fast response.

Thanks for confirming ??

I like that the option to switch editor appears. I think users have to know that it exists and slowly start to start using the new editor.

In version 1.3, on activation it appears to set the option ‘Allow users to switch editors’ to NO so this does not show up unless changed. In my view, this should be set to YES by default.

I do agree that on activation that it sets ‘Default editor for all users’ to Classic by default – that is the basic point of installing this plugin in the first place.