Please consider removing the warning if Gutenberg is not active

  • Resolved Bill Erickson

    (@billerickson)


    6 years, 11 months ago

    If you install Classic Editor without having Gutenberg active, you get the following warning: https://cl.ly/2f3j1P2Q0G3z

    Why? If Gutenberg is not available the Classic Editor is already being used, which is what the installer of this plugin intends.

    The plugin should check if Gutenberg is available (either in plugin or merged into core), and if not it should return early.

    My use case for this plugin is to prevent clients from breaking their sites by upgrading to WordPress 5.0. I’d like to install and activate this plugin so at some unknown time in the future, when they update to WordPress 5.0, certain pages on their site don’t break and they frantically call me.

    This is only for sites that I know will break due to Gutenberg. For instance, where we’ve hidden the main editor and used a metabox for constructing the page content. The long term solution will be to rebuild these themes to use Gutenberg instead of a metabox for page content, but in the short term we need to keep the site editable without refactoring code.

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

    (@azaozz)

    Currently this plugin is (only) for testing with the Gutenberg plugin. Of course Classic Editor will be updated when Gutenberg is merged in core. I expect it will need changes and/or fixes then.

    I can understand the desire to have an “insurance” that some users won’t break their sites when Gutenberg is merged. Can remove the warning and self-deactivation in the next update to Classic Editor.

    • This reply was modified 6 years, 11 months ago by Andrew Ozz.
    Plugin Author Andrew Ozz

    (@azaozz)

    Done in 0.2.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Please consider removing the warning if Gutenberg is not active’ is closed to new replies.