Join us Today at 2 pm ET / 11 am PT / 19:00 UTC on YouTube. I am thrilled to be talking to Hendrik Luehrsen, about contributing to WordPress Gutenberg and building blocks for new websites.


Gutenberg, the new visual editor for WordPress will be merged into  Core as the default editor later this year, when WordPress 5.0 will be released.

In August  a “Try Gutenberg” call out was released with WordPress 4.9.8 with a button to to install the Gutenberg plugin for post and pages or install official Classic Editor. If you install the Classic Editor, you will be able to keep using the current editor beyond the merge of Gutenberg into Core.

Beyond this global opt-out method,  developers, consultants and site admins can make more nuanced decisions on how Gutenberg is implemented on their sites. Here is a list. If you find one missing, feel free to post a link in the comments and we’ll update the post.

Caveat: Use at your own risk. We did not test the latest versions of mentioned plugins.

Built-in Methods and Plugins maintained by Core Contributors

Gary Pendergast, summarized built-in Methods that will be available when Gutenberg is merged into Core.

Note: There is not a single method. It’s all depends on context.

The Classic Editor plugin is the option for reverting to the classic editor across an entire site. It’s being advertised prominently in the upcoming WordPress 4.9.8 release as an option to install now, in preparation for WordPress 5.0. If you’re a site builder who wishes to opt your clients out of the block editor, installing the Classic Editor plugin (and contributing with bug reports or fixes) is the best long term solution to ensure the classic editor will continue to be available.

For metaboxes, it’s already possible to opt-out of the block editor, this API will be merged into Core.

For CPTs, the gutenberg_can_edit_post_type filter will be renamed when it’s merged (probably to block_editor_can_edit_post_type, or something of that nature), but will also be available as a code-based option.

Methods to avoid Gutenberg nag or modify it.

Built into Core with with 4.9.8 

For site – owners,  the easiest way is to just use the “Dismiss” link on the right side. Once you dismiss the prompt it won’t show up again. Wow, that was easy:-)

Via code in a plugin or in a file stored in /mu-plugins folder

add_action( 'init', function() {
    remove_action( 'try_gutenberg_panel', 'wp_try_gutenberg_panel' );  
});

The is also a new filter  try_gutenberg_learn_more_link  “that allows hosts or site owners to change the link, to provide extra information about Gutenberg, specific to their service or site. ” (Quoted from the trac ticket)

More details on both can be found on the Core Make blog

WP Buffs
Affiliate link

Plugins to disable the notice

There are a few plugins available that suppress the so called “Gutenberg Nag”.

Additional Plugins available on the WordPress Plugin Repository

Over the last four months, plugin developers also created various solutions to have a more granular control over Gutenberg editing experience.

  • Gutenberg Ramp – published by WordPress VIP team, allows you to enable Gutenberg on a post level basis for CTPs if they support the editor.
  • Jeff Starr’s plugin “Disable Gutenberg”  completely disables Gutenberg editor, and gives us the choice to do it by post type or user role.
  • Sara Gooding on WPTavern reviewed the Classic Editor Addon Plugin, that also implemented a feature to disable the 4.9.8 nag, but also needs the Classic Editor plugin installed.
  • Gutenberg Manager by the unCommons Team, also allows you to disable Gutenberg for selected Custom post types.
  • With Lee Rickler’s plugin GutenBeGone – you can disable individual Blocks that come with Gutenberg
  • LittleBizzy published yet another plugin: Disable Gutenberg

WordPress Fork Proposals

ClassicPress

A recent start-up, intending a fork of WordPress 4.9.8, probably one of the last versions without Gutenberg. At the time of this writing (8/27/28), it’s not ready for anyone to jump on board. Stay in the loop via the website.  “Forking is a features” Gary Pendergast, a WordPress Contributor blogged in August.

CalmPress

CalmPress is the name of another WordPress 4.9 fork. “to get a more stable and calm experience to all of its users” writes Mark Kaplun, the initiator of CalmPress. It’s not intended as a “one-man hobby”, but it’s what it looks like at this moment. You can follow along the progress via its blog

Leave WordPress – Community and Ecosystem

There are plenty of options to leave the WordPress eco sytem, depending on your needs and goals. W3Tech covers approximately 300+  Content Management Systems. There are the commercial walled-garden options: Shopify, SquareSpace, Wix or the proprietary software Adobe Experience Manager. Below, you find three examples of modern CMS to check out as developer. 

Ghost 2.0

Founded by John O’Nolan, a former WordPress Core contributor, and Hannah Wolfe, Ghost’s 1st version was released in 2013. It’s a blogging platform entirely written in server-side JavaScript based on nodejs. The open-source software is available for self-hosters as well as a hosted solution, maintained by the Ghost Foundation.

Drupal

Drupal, is the other major PHP-based open-source content management system with a large community. Lately, it made headlines, for efforts to integrated Gutenberg in its own code base.

Craft CMS

Craft is another PHP/MySQL based Content Management System, just released in it 3rd version. Back in April, the Craft Plugin Store was opened, integrated with GitHub and annual updates for residual income for the developers.

Photo by Jamie Street on Unsplash

Published by Birgit Pauli-Haack

web + mobile strategist & coder 4 nonprofits. #nptech #WordPress @wpswfl @nptechdata @wp4good #podcast - Day job @paulisystems Cu at #WCUS and #19ntc

Join the Conversation

21 Comments

  1. Hi Brigit,

    Thanks for the heads up on the name change to block_editor_can_edit_post_type

    1. Further heads up… Seems like they went with a slightly filter different name (as of WordPress 5 beta) use_block_editor_for_post_type – and in addition now, use_block_editor_for_post also.

  2. You are welcome! Thanks for stopping by and leaving a comment! Happy August!

    1. Hi Birgit,

      Any updates on the final replacement for the filter that can be placed in functions.php file.

      Currently add_filter(‘gutenberg_can_edit_post_type’, ‘__return_false’); works but I havn’t seen this or its replacement mentioned in this post?

      1. Hi Stephen,

        I posted your question in the Slack channel #core-editor this morning and learned the following:
        You will not see _gutenberg_ prefix in 5.0. Gary Pendergast is leading the effort to get rid of these code name in one task, and maybe even with a plugin release before the merge.

        1. Thanks for the quick reply. We will have to wait a bit longer to see what options are available in terms of a simple filter in the functions file.

  3. Hi Birgit,

    Just getting back to you. I’ve been testing WP 5 the over the last few days and digging around in Classic Editor plugin I found the following:

    add_filter( ‘use_block_editor_for_post_type’, ‘__return_false’, 100 );

    Adding this to the functions.php file ( preferably a child theme ) disables Gutenberg in WordPress 5, no need for a plugin.

    You can pre-populate this filter into current 4.9.8 versions so they are ready when WP is officially launched.

    Caveats: the above filter won’t disable the plugin version of Gutenberg and we could see another name change to the filter.

    1. Thanks for the link to Gary’s filters. They will be useful.

      Starting to warm to many aspects of Gutenberg…hell froze over! There are still many niggles but the one big hurdle is locating all the blocks with hover. From testing this issue is accentuated where third party plugins start nesting blocks within blocks, its gets really frustrating. The vendors are doing some great work with these blocks so it would serve us all well if the Gutenberg devs could crack the nutshell of finding stuff in the UI.

  4. Hi Birgit, just wanted to let you know I’ve recently released yet another plugin for selectively enabling or disabling Gutenberg given different conditions. Or rather, setting which editor will be used by default according to cascading settings checks, and also providing buttons to easily change between them. I did this because I believe there needs to be more flexibility for a combination of both using and not-using Gutenberg on a site, to help more smoothly transition to it being available in core soon.
    Even though there are programmatic solutions available for this, they are not easy for end users to implement, and are somewhat more complex when there are a number of conditions to take into consideration. So having these all coded and tested in one place to provide a user interface like this seems to be a better way forward, rather than just a the limiting choice between “on” or “off”. https://wordpress.org/plugins/guten-free-options/

Leave a comment

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: