• Resolved John

    (@dsl225)


    Thanks for this great addon!
    Definitely useful.
    But what happens once installed and WP 5.0 is updated?
    Do we need to still keep the plugin after that or will it be safe to uninstall it?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Pieter Bos

    (@senlin)

    Hi John,

    Thanks for your question.

    One of the functions of the Classic Editor Addon, and the one mostly emphasised in the recent article on WP Tavern, is that it surpresses the nag screen to try out Gutenberg, slated to arrive with the release of WP 4.9.8.

    But it actually does a few other things than that.

    The Classic Editor does not replace Gutenberg, but instead comes with a Settings screen where the user needs to go and untick a checkbox to make the classic editor become the default again.

    This Classic Editor Addon plugin changes that and automatically sets it to replace Gutenberg with the classic editor. This way it becomes a lot easier to make Gutenberg go away for people managing sites for others.

    The Classic Editor Addon also removes the settings of the Classic Editor plugin (on the Settings > Writing screen) and removes the link to the settings from the main Plugin page.

    If Gutenberg indeed is rolled into Core with WP 5.0, and you want to keep the current Editor experience, then you will still need both the Classic Editor plugin and our Classic Editor Addon.

    If you on the other hand want to experience Gutenberg, then you will indeed need to deactivate (and uninstall) both plugins.

    Does that answer your question?

    • This reply was modified 6 years, 8 months ago by Pieter Bos. Reason: link name
    • This reply was modified 6 years, 8 months ago by Pieter Bos. Reason: explaining all that the Classic Editor Addon does
    Thread Starter John

    (@dsl225)

    Yes, thanks.
    I indeed don’t want to hear about Gutenberg EVER!
    It’s a bit frustrating that, for doing so, I’ll need to have always 2 more plugins up and running…

    Would have been better to have a plugin that simply blocks this thing out of sites and just keeps the editor as is.I don’t well understand why we would need this plugin “classic editor” but I’m probably too old for that.

    Plugin Author Pieter Bos

    (@senlin)

    It’s a bit frustrating that, for doing so, I’ll need to have always 2 more plugins up and running…

    We agree and it is ridiculous that the Classic Editor plugin (by WP core) does not what it says it does.

    Hence our addon ??

    Thread Starter John

    (@dsl225)

    Thanks, well noted.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘What happens after WP 5.0?’ is closed to new replies.