Support » Plugin: Gutenberg » Version 5.2.2 review update

  • Pádraig Ó Beirn


    Final Update [5.2.2]
    Ok, I’ve given this enough time, listened to the feedback from my site editors and decided to switch my sites to a WordPress fork. Why? In a sentence – Gutenberg is more cumbersome. I, along with my users, prefer the simple classic editor. We don’t want to rely on a time-limited plugin for easy editing so, after 13 years, it’s sadly time to say goodbye to WordPress. Thanks to everyone involved with WordPress for all your work.

    Update [version 5.0.1]
    I don’t know if anyone reads updated reviews but I’d like to add some feedback which I hope is constructive. To that end I would like to bring it to the attention of @designsimply as she has replied in a considerate and helpful manner to concerns in the reviews and github. Likewise with @karmatosed who responded to my original review. Hopefully you both find the following feedback helpful…

    I like to type my text in the editor. I still hate that every paragraph or even a sentence is trapped in a block. I can see why it was done from a designer point of view but a writer/blogger would have gone for a multi-paragraph model. It’s simply easier to manipulate text as you want in the Classic editor. For example, in my last test I had two sentences that I wanted to format in Gutenberg but couldn’t do it as easily as the Classic editor because they were in two separate blocks and apparently they cannot be formatted.

    I tried using the Classic Editor block which is fine for typing and multi-paragraph formatting but not when it comes to inserting and aligning images. I press the + button above the classic editor block and align the image which is fine but it means I can just use one image per classic editor block. I like to place my images alongside the appropriate paragraph in the text. If I have 10 paragraphs and 5 images I can’t use the classic editor block and add aligned images to each paragraph.

    Regarding the alignment of images, once aligned they can’t be moved up or down. I don’t know if this is a bug but it’s easy to do this in the Classic editor and I’m really surprised it can’t be done in Gutenberg.

    I tried the media + text block to see if this would be a work-around. When you click on a standard image in Gutenberg you can set the size and link settings in the sidebar which is great. The Alt text can also be set and it would be nice if the caption but be added there too. Unfortunately none of this is available when you click on an image in the Media + text block.

    The end result of all this for me is any blog post I’ve attempted has ended up as a mish-mash of clutter in the Gutenberg editor. The Classic editor is simpler. I have seen it written by some that the use of page-builders such as Beaver, Divi etc. is a sign that the Classic Editor is problematic and needs to be replaced. Following that logic the rise of the Classic Editor plugin and it’s 1,000,000+ downloads is a sign that Gutenberg is problematic and needs to be replaced. My recommendation, for what it’s worth is to revert to a multi-paragraph model for text. Text and images are the basis for any blog/cms – get those right first as a priority and everything else should follow.

    Update [version 2.80]
    I have tried every iteration since 1.7 and engaged with github as best I could. Unfortunately, I still don’t like it for the simple reason that the classic editor is simpler and easier to use. Gutenberg gets in the way of my writing. Here are some examples of what I would consider basic issues that are still not resolved:

    1. You can’t select more than one paragraph to format (this should be a basic feature of any text editor which is why I can’t understand the 5-star reviews).

    2. You can’t link a thumbnail image to its full-size version with the image block. You can do this with the gallery block but not the image block.

    3. After inserting an image you can’t use Ctrl+X to cut and paste it somewhere else in the post.

    In comparison to Gutenberg as it stands (2.8) the classic editor is much cleaner and simpler for me to work with.

    Version 1.7 review:
    I tried this on a development site and it’s a step backwards in every way (in my opinion). I absolutely hate the blocks. The current post editor is clean and simple. It works. I just don’t get the point of Gutenberg. Leave it as a plugin and please don’t oppress it on the whole WordPress community as part of core. The version I tested is 1.7 and I can’t see any future for it only as an optional plugin.

    Those blocks are terrible! “The goal of the block editor is to make adding rich content to WordPress simple and enjoyable.” The editor is already simple and enjoyable!!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Tammie Lister


    I am sorry you are experiencing issues @padraigbeirne with the idea of blocks. It’s very right that for some users the editor right now works. It does not for every user though, that’s important. We need to look beyond our own use cases and experience and make a WordPress that allows everyone to participate. That’s one of the motivations of Gutenberg.

    Pádraig Ó Beirn


    @b-07 I realise it’s beta software but my initial shock was that it’s planned for integration in WP 5.0. I think it’s very early beta and despite the great work of the team I can’t see it being ready for commit to core by version 5 next year.

    I don’t know what you mean that I shouldn’t be using it on a mirror development site. That’s how I test everything.
    Thanks for your reply @karmatosed to my review and those of others. It’s great that both the positive and negative feedback is being listened to. My initial fear about Gutenberg being merged into version 5.0 core has been allayed by comments I’ve seen from Matt and yourself that there will be an option to continue to use the classic editor. That’s a great relief.

    Here are two examples to give you an idea of where I’m coming from as a long-time WordPress user.

    Example 1
    To embed a tweet in the current TinyMCE editor:
    Copy and paste the link in the location you want. Done.

    To embed a tweet in Gutenberg (1.7):
    Click the + button.
    Click the Embeds tab.
    Click the Twitter icon.
    Click Embed after pasting the link.

    Even with the Twitter icon appearing in the Recent tab (when repeating the process) embedding links is much easier in the classic editor than in Gutenberg.

    Example 2
    To add an uploaded image in the middle of a post/page using the current theTinyMCE editor:
    Click where you want to insert the image.
    Click Add Media.
    Click on image.
    Click Insert into Post.

    To add an uploaded image in Gutenberg (1.7)
    Click the + button on the block in the middle of the post/page where you want to insert the image.
    Click the Image icon.
    Click ‘Insert from media Library’.
    Click on image.
    Click Select.

    I could give more examples but I just don’t see how Gutenberg makes these two common tasks any “simpler and more enjoyable” than the current editor for any user, not just me. Maybe that will change as it evolves, and best of luck with its further development, but please continue to keep the classic editor as an option in version 5.

    Pádraig Ó Beirn


    In Gutenberg Oembed supported urls work by pasting as well which is great. Hope accessibility continues to improve as well.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Version 5.2.2 review update’ is closed to new replies.