Logic bug in Classic Editor 1.0

  • Resolved herbie888

    (@herbie888)


    5 years, 11 months ago

    Step 1.

    WordPress 4.9.8
    Classic Editor 0.5
    -> Classic editor settings [x] Replace the Block editor with the Classic editor.

    That’s the setup a few 100.000 users had until today to prepare, as they have been told by @matt in https://make.www.ads-software.com/core/2018/12/04/new-5-0-target-date/

    No problem, install the Classic Editor plugin and 5.0 will be indistinguishable from 4.9.8 for your posting and editing experience, …

    Step 2.

    Update to WordPress 5.0

    With Classic Editor 0.5 all is “indistinguishable from 4.9.8”, fine.

    Step 3.

    Classic Editor gets updated to 1.0, now:

    Posts list hover menu shows:
    “Block Editor | Classic Editor | Quick Edit | Trash | Preview”

    Edit post screen shows extra metabox “Editor” with Link “Switch to Block Editor”

    That’s clearly not “indistinguishable from 4.9.8”, bad.

    The bug:

    The new setting “Allow users to switch editors” defaults to “Yes” where it should default to “No” if Classic Editor had been installed before and explicitly had been configured to “replace Block Editor”.

Viewing 31 replies (of 31 total)

  • 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.

    This breaks backwards compatibility – before 5.0 went out, we were instructed to install Classic Editor plugin in order to maintain pre-Gutenberg editing experience. Back then it was only about getting rid of “Try Gutenberg” call-out, but the promise was (at least as I understood it) that with Classic Editor plugin installed there’s going to be no change when 5.0 rolls out. Giving users an option to switch to Gutenberg is certainly a change in behavior, so to have this option on by default breaks the backwards compatibility.

    While I don’t mind that Classic Editor does not just disable Gutenberg completely, but offers these additional “transition” options, I certainly expect them to be off by default and I’m glad that Andrew listened to the feedback in this thread.

Viewing 31 replies (of 31 total)
  • The topic ‘Logic bug in Classic Editor 1.0’ is closed to new replies.

Tags