Option to Disable Gutenberg

  • Cron

    (@cronuca)


    3 months ago

    Kindly considering adding an option to disable the gutenberg editor if a 3rd party page builder plugin or theme with it’s own editor is being used. This will drastically improve performance and make it more convenient to operate with other builders. I know there are plugins which do that, but having this option locally in the settings will be beneficial.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator t-p

    (@t-p)

    3 months ago

    To file a feature request, please follow https://core.trac.wordpress.org/newticket and choose “Feature request” as the report Type. For more see https://www.wpbeginner.com/beginners-guide/how-to-make-new-feature-suggestions-for-wordpress-beginners-guide-to-using-trac/

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    3 months ago

    3rd party editors have the capability of disabling the block editor themselves.

    Thread Starter Cron

    (@cronuca)

    3 months ago

    Unfortunately that is not the case! I didn’t find any 3rd party page builder having an option to disable gutenberg. Gutenberg still remains active.

    Yes although some dedicated plugins do have that option, but why have a plugin for such a simple thing!

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    3 months ago

    It absolutely is the case, but it’s a matter of choice. Most builders work fine with the block editor and have indeed adopted it.

    But if you choose, the classic editor plugin is available, and it is very simple, and low/no impact on your site.

    Thread Starter Cron

    (@cronuca)

    3 months ago

    I agree page builders work fine with Gutenberg without any conflicts, and i know about classic editor option too. Just that why have a separate plugin for a simple code block which can be coded on a toggle natively! Either way it was just a suggestion, guess no one like it!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.