Classic as default does not work

  • Resolved burnuser

    (@burnuser)


    7 years, 4 months ago

    I have upgraded to WP 5.0 (Thank God only on staging site!) and afterwards Classic Editor (Option setting “Replace Gutenberg with Classic”) was upgraded to 1.1
    The existing Gutenberg setting was converted to “default = Classic”; “Allow user change editor = Yes”
    My user profile (admin) also shows “default = Classic”
    But editing a page … opens always Gutenberg!
    Only if I set “Allow user change editor = No”, the “default = Classic” setting works!

    3 Problems:
    1.) When upgrading with active “default = Classic” setting Gutenberg appears instead of Classic!
    2.) “Allow user change editor = No” as prerequisite for “default = Classic” is totally illogical and extremely misleading!
    3.) “Allow user change editor = No” as prerequisite for “default = Classic” makes it impossible to try Gutenberg even on single posts!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Andrew Ozz

    (@azaozz)

    7 years, 3 months ago

    Changed the default in the dev. version, Can you test (uninstall the current plugin then install from the zip)? Can be downloaded at the bottom here: https://wordpress.org/plugins/classic-editor/advanced/.

    Thread Starter burnuser

    (@burnuser)

    7 years, 3 months ago

    Tested 1.1 and 1.2 on 2 different installations (one with all other plugins inactive) but always the same result:
    “Allow user change editor = No” is the trigger for a working “default = Classic”

    Plugin Author Andrew Ozz

    (@azaozz)

    7 years, 3 months ago

    @burnuser did you “uninstall” the plugin before testing 1.2? That’s needed to delete the options/reset the defaults.

    There the “allow users: no” should be the default.

    • This reply was modified 7 years, 3 months ago by Andrew Ozz.
    • This reply was modified 7 years, 3 months ago by Andrew Ozz.
    Thread Starter burnuser

    (@burnuser)

    7 years, 3 months ago

    Yes, I have uninstalled it – and now a second time.
    With the same result at first sight.
    But …
    I made my test with same pages as before … and discovered a little trick at second sight!
    The visited pages of first test was marked as “Block Editor” in pages overview – without any changes or even saving them!
    And a click on “Change to Block /Classic” in editor view changes instantly – always without saving! – the marking on pages overview too.

    This behaviour in mind: Yes, Classic Editor as default works now in 1.2

    Plugin Author Andrew Ozz

    (@azaozz)

    7 years, 3 months ago

    Yes, Classic Editor as default works now in 1.2

    Great! Thanks for testing 🙂

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Classic as default does not work’ is closed to new replies.