13 Comments

  1. Daniel James

    It’s quite clear to see that version 5.0 has been an absolute mess from start to finish. Usually I’d be quite sympathetic but the sheer amount of problems people are having with it thus far and considering it’s supposed to released as ‘stable’ in a couple of weeks is beyond worrying.

    I used to be a ‘Gutenberg supporter’ but at this point it’s clear to see that the motive for rushing the release is because of Automattic/Matt here. There’s always been a large favouring towards WordPress.com but with Gutenberg’s imminent inclusion it’s even more obvious there’s an agenda at play here.

    I’m happy to see Gutenberg merged in. It’s going to happen anyway, but it can’t be merged in this quickly as it’s causing so many problems. I find it insulting that Gutenberg gets fast tracked yet Dark Mode, the feature plugin I made which adds a new CSS file to the dashboard get rejected because it didn’t follow and pass all merge proposal checks… at least it had a merge proposal written.

    The Gutenberg team straight up lied about having a public merge proposal done for it. It’s things like this that are driving high profile contributors away from the project (I’m definitely not one of them by any means, But Rian from the A11y team and John from the Core team are to name but two people).

    Matt, Gary; don’t forget about the community you helped build here. It’s not helping anyone.

    Report

    • David Decker

      Couldn’t agree more, Daniel!

      It is so frustrating over the last 12 months how engagement and feedback of the community gets ignored. Or that things get measured differently, for feature plugins like yours for example. I saw your proposal for Dark Mode and I can feel the frustration also as outside watcher – I did find that fair how you were threated – in comparison as how Gutenberg gets handled.

      It so saddens me.

      Report

  2. Nick

    Some things got fixed, but new huge bugs were also introduced with this beta 3. About two weeks to go, and time is running out, I almost feel sorry for the core devs as the pressure on them must be astronomic now…

    https://wordpress.org/support/topic/wordpress-5-0-beta3-does-not-save-acf-metabox-data/

    Also, still no custom buttons on the Classic Block, which is really important for shortcodes.

    Report

  3. Erick Danzer

    I’ve operated on the assumption that the Nov 19 deadline is like many Gutenberg projected release dates in the past: a target, and something that adds urgency for both the Gutenberg team and third party theme/plugin developers. But ultimately not realistic and bound to be deferred.

    To the powers that be: if you’re seriously considering a Nov 19, please, please do not.

    Gutenberg is no where near ready. There are bugs, even for obvious, vanilla use cases, not to mention edge cases. Theme and plugin developers are not caught up or ready. Even for plugin developers who are working hard to be ready, the api still changes and breaks things frequently in recent releases.

    Gutenberg is not a normal release – it profoundly alters the core UI on 30% of the internet, often in ways that are not backwards compatible. For a release of this magnitude, the product itself should be fully 100% ready, first (which it is not), and then it should site out there for 3-6 months while the ecosystem prepares for it.

    And the idea that it’s been widely tested is such a strange thing to say – because it’s the testing itself that still shows it’s not ready. Just being tested a long time is not the goal – the goal of testing to ensure it’s 100% stable, well-liked, and won’t break third party integrations. Testing to date still shows the opposite.

    I’m fond of Gutenberg. But a premature release would be a disaster of epic proportions for the entire WordPress ecosystem. And Nov 19 is clearly, definitely premature.

    Report

  4. Shaun

    If Gary, Matt and the rest of the team working on 5.0 think it’s nearly ready they are living in a fantasy land.

    It’s like WordPress is the Microsoft of the open source world, where it’s such a big player that buggy software can be shipped and people just have to deal with it.

    Report

  5. Peter

    Absolutely fantastic :-(
    WP will be quite instable for the near future due to GB.

    Report

  6. Morten Rand-Hendriksen

    “Over the past six months, there has been a release every two weeks,” Pendergast said. “We’ll plan to continue that over the first few WordPress 5.0.x releases, to ensure that bug fixes are available as quickly as possible. How soon should we expect WordPress 5.0.1? Approximately two weeks after WordPress 5.0, unless we see bug reports that indicate a need for a faster release.”

    This part concerns me. The Block Editor (nee “Gutenberg”) is a fundamental change to everything users know about WordPress, and for the majority of WordPress users, 5.0 will be their first introduction. Whatever the intent, the quote reads as “beta test in production” which is an uncomfortable notion considering the sheer scale of WordPress. Yes, software developers expect bugs at release, but this sounds more like the modern game developer ethos of releasing unfinished work and using real users as beta testers. It is a known issue in game development and not something we should be adopting. In my opinion.

    Report

    • Peter

      @Morten: Just read one of your tweets from today. Maybe i would wait till 18th with re-recording those videos. Otherwise chances are high, that you will have to re-re-re-record those sessions.

      Report

    • Miroslav Glavic

      Every time there is change, people will wine, they eventually learn the new changes and move on with their lives. I should sell the WP Community some cheese.

      Report

  7. Amir Helzer

    During the last months, we participated in testing Gutenberg with our plugins – WPML and Toolset. We found bugs in GB, created tickets and MRs, but they’re being overlooked. We are getting very slow and strict replies to our fix requests, while the project runs forward, ignoring many problems.

    Then, we’re going to get slapped on the hand because our plugins have “compatibility problems” with Gutenberg. That’s really great, encouraging, inclusive and democratic.

    Report

    • Stephen Vaughan

      It’s a grossly frustrating situation to be in and I for one sympathise with any developer that has to spend hours firefighting the mess that Gutenberg is when they good be putting their time to better use.

      Even on themes that purport to be built for Gutenberg, it doesn’t function properly

      Therefore I suggest that theme developers slap add_filter( ‘use_block_editor_for_post_type’, ‘__return_false’, 100 ); into the functions.php file to clobber Gutenberg as a form of protest till it conforms to a properly functioning piece of software.

      Report

    • Servitium

      Do you plan to support your plugins WPML & Toolset in ClassicPress?

      Report

  8. Samuel

    Pooh, that’s scary when you read all the developer comments. I hope Matt and co keep an eye on it and show consideration.

    I’ve reported an important bug so far and I’m getting answers. I hope the Gberg-guys don’t get tired….

    Report

Comments are closed.

%d bloggers like this: