15 Comments

  1. Richard Ginn

    At version 2.4 of Gutenberg it is soooooo much better than 1.0, BUTTT still not ready for prime time.

    Report

  2. Gary

    Change of plans, this won’t be happening in the 4.9.5 release: there are still a few issues we’d like to fix up the callout happens, they won’t be done in time for the 4.9.5 release.

    I expect there’ll be a smaller 4.9.6 release that contains this callout, and any bugfixes that happen to be ready. 🙂

    Report

  3. Adam Ainsworth

    That’s a very Microsoft way of doing it – put an enticing button advertising a new feature which may cause problems or be undesirable to the user, but not really indicating as such.

    Report

    • Steven Gliebe

      Not sure I like this approach. It’s getting a bit ahead of plugin and theme authors. We were told 5.0, now it’s going to be pressed on users ahead of 5.0. Many will have a bad experience because their theme or plugin author isn’t ready and they’ll be hesitant going forward with 5.0.

      I’m for Gutenberg but not for jumping the gun like this.

      Report

  4. Peter

    Wow… just wow again…
    My only question is: what if the user can install plugins or edit posts BUT they do not want ever activate Gutenberg? Will they always get slammed by those buttons in the face? Did anyone think about this scenario at all?!

    Report

    • Cavalary

      The person who created the plugin to hide it did :) Fortunately…

      Report

    • Gary

      As with every widget on the Dashboard, clicking the “Dismiss” button on the top right closes it permanently, you won’t see it again.

      If you need to bring it back for any reason, you can re-enable it in the Screen Options dropdown on your Dashboard. 🙂

      Report

  5. Marcus Tibesar

    I’ve gone live with Gutenberg 2.4 on my personal site and have created a couple of Posts with no issues. That’s not say its ready nor others won’t have problems with it. Just a comment is all.

    Report

  6. Greg Schoppe

    Here’s how you can disable Gutenberg (including this nag panel), before the release of 4.9.5, to keep your clients safe from accidentally changing their workflow or breaking editor integrations or complex custom field interfaces. The best part? you can bulk install the plugins involved for all your clients, via MainWP, ManageWP or even Jetpack.

    https://gschoppe.com/wordpress/disable-gutenberg-now/

    Report

  7. Benjamin Intal

    I’ve got to say that this is a great method to leverage your audience to become beta testers for Gutenberg.

    Report

  8. Patrik

    Sounds like I’m gonna have to tell every admin on every site I have ever built, to not click that damn button. As if I didn’t have enough work.

    Thanks, Matt.

    And yes, end users are usually admins. No other role would be sufficient when handing off a site to the client.

    Report

  9. Paul

    I’ve stopped using WP for my new clients and am slowly moving the old ones away. Just too much autocratic nonsense to deal with.

    Report

  10. Ibad Rehman

    I had an experience with Gutenberg a few weeks ago. It was sweet n sour but I think that’s because I am not very prone to changes. :)

    Report

Comments are closed.

%d bloggers like this: