1. John

    The “Dismiss Forever” button is missing.


  2. Nick

    The callout should appear on sites running on local servers and not on live sites. Some web designers are going to take advantage of the chaos Gutenberg will bring, as they will charge and arm and a leg just to install the Classic Editor plugin, just to bring sanity back to the site owners…


  3. Bob

    This is just yet again proof that the core team has no concept of what it takes to run an agency.

    We try to limit clients access to the admin as much as possible but this just opens it up for some client that doesn’t have a clue what they’re doing tearing a site up for no good reason. For what? So core can get feedback on a piece of garbage release that nobody wants?

    Simple solution: Stay the hell out of MY admin.


    • Devin Walker

      What if the prompt is only displayed to the “administer” role?


      • Bob

        Some of our clients insist on having Admin rights. We try to fight against that but at the end of the day it’s their site to do with what they please.

        Most stay away from it though as we tell them upfront that it’s $250/hour with a 2 hour minimum to fix anything they screw up due to poking around in the admin. ;-)

        This is just an addition potential headache for no good reason. We don’t owe WP anything in terms of trying out Gutenberg. If we wanted to try it, it sure as hell wouldn’t be on a live client site.


  4. Mike Cottam

    You can limit site users to specific areas of the WordPress dashboard so I don’t see that as an issue.

    The issue for me is that a vast number of users have no idea what Gutenberg is or how it can BENEFIT the way pages are created.

    More education needs to be provided before Gutenberg is shipped as part of WordPress core.


  5. bobbi

    Whew glad to hear that. Agree with above poster “Dismiss for ever button”.
    Why can Gutenberg just be a plugin for those who want to use it.
    After it rates very high for a long time with 100,000 users, then maybe think about adding to Core.
    And certainly fix all issues with plugins before even thinking about adding to Core.


    • Devin Walker

      Matt initially stated at WCEU next year he’d like to see at least 100l many sites running it prior to releasing it in core but I think this was just because it was in a QA answer. I totally understand things shift over time. However, at the time of this comment it looks like only 8k+ https://wordpress.org/plugins/gutenberg/

      I don’t think 100k is necessarily a number that has to be held to steadfast but at least more than 8k would be nice. :)


  6. Ty Cahill

    I really want to like Gutenberg. Every couple months I update the plugin and give it a try. With all the talk of prompting its installation with 4.9.5, I tried it out again over the weekend. It was a disaster with most of the pages in my dev site, so I had to deactivate it again.

    This can be a real mess when clients start turning it on and breaking things. And I really dislike how the current editor is gone. I have a number of pages that are better off without Gutenberg, and some are even best edited in text and NOT the visual editor. I think it’s really bad to force this new experiment on people. Give us the OPTION of using the Gutenberg editor alongside other editors, like how many page builder plugins do.

    Just my 2 cents.


  7. David Skarjune

    Reading the trac discussion is rather disappointing. The team skips over concerns about pushing such beta software onto production websites or the precedent of doing so or how it’s done, while the majority of the discussion is about tweaking the words, styling, and placement, primarily to make it more effective rather than clarifying risk and removal.

    Is this WordPress or Microsoft?


Comments are closed.

%d bloggers like this: