Just full of bugs, not even beta

Hi there,

after years of development, the most basic and simple operations cause bugs.

Have you reproduced the bugs while having the plugin itself installed, or only using the native block editor?

Confirming as these are not the same and the Gutenberg plugin works mostly on experimental mode before it is added to core — it would be more reliable to use only the core version.

Another thought: more than half of the people who reviewed Gutenberg gave it only 1 star. Yet WordPress puts it out as the standard editor – why???

I believe there are different things here. After replying to a lot of reviews, I wouldn’t use it as a key metric to add it to core or not — especially as there are a lot of 5-star ratings as well.

• Some folks reviewed it a long time ago before improvements were added.
• Other people don’t like the way WordPress is going with the Site Editor and Block Editor, and add a rating to Gutenberg as a way to represent rejection (even it the plugin itself is not a problem for them).
• Also, there are several legit reviews (like yours with the copy/paste bugs) — these are mostly part of constant improvement for the plugin, and the idea is to keep working on the plugin to improve your experience.

Hi Felipe, thanks for your reply. I can image that is not easy having to cope with all these rants and complaints.

I don’t really know who made the decision at WordPress to use Gutenberg as the native editor. If there is another thread where one can voice concern about this, I’d be happy to re-post. But when you’re frustrated with the editor, that editor’s page is the first place that comes to mind to leave a comment.

I’m using the builtin block editor, not the plugin. Obviously because it’s the native editor – I would not have installed it myself, given the bad ratings. 800 5-stars is better than nothing, but compared to 2400 1-stars, I would not call that ?a lot“. Plugins with an average less than 3 most people wouldn’t even consider for fear of ruining your website. Even if many of Gutenberg’s 1-stars are older, just looking at the most recent page of reviews, the rate has not improved much.

As to the bugs, I wouldn’t call “moving through text with arrow keys” experimental – bugs like this simply should not happen, especially when a software is matured and the native editor. And those two I mentioned are not the only bugs. Gutenberg to me has always behaved buggy. You try to add a block, it doesn’t work, you try again, it works. You can’t see the advanced editor tools, you scroll up and down, or delete and re-add the block, then you see them. And so on. I don’t think I’ve ever felt “safe” with this editor in the sense that it will do what it’s supposed to do.

The sad thing is, I like the concept of Gutenberg, it looks much better than the old “classic” editor. But to work with an unstable thing like this is just awful. I have actually just removed it, after I kept trying for a year or so.

I really think Gutenberg should not be the native editor. People like me fall into the trap of trying it out and then getting frustrated and wasting their working hours as test subjects. That is simply not nice. If you want it as the native editor, make it stable first!

Hi @christianpothmann!

Thank you for sharing your feedback. ??

Regarding having Gutenberg on core, it is really not something in discussion anymore. This was an executive decision after having feedback across the whole project.

As to the bugs, I wouldn’t call “moving through text with arrow keys” experimental – bugs like this simply should not happen

Oh, yes, I was referring to the plugin, not the core Block Editor — the native editor is surely not experimental and indeed shouldn’t happen. ??

Would you be open to creating a topic for investigating the issues you’re facing? I understand if you are no longer using it and want to test that.

Generally, these cases where we find major issues on the core editor are often conflicts with plugins instead of problems with the core code.