7 Reasons to Not Switch to the Gutenberg WordPress Editor

Update: After many years, I’ve changed my opinion about Gutenberg. Automattic has fixed many of the annoyances I’ve outlined and others I’ve gotten used to. On the flip side, I’ve come to embrace the ability of Gutenberg to transform a page from just text + HTML to one crafted with various components. Webpages are very different from how they used to be, and a good page now needs many more custom elements, CTAs, and code blocks. Gutenberg enables that.

I’ve been using WordPress since 2010. Ten years of blogging on my personal blog and hundreds upon hundreds of freelance articles on dozens of others. I’ve been doing this for a long time. So when I heard that the new Gutenberg WordPress editor was close to completion, I was itching to try it out. I love new software and get a kick out of shaking things up. So I was hoping to be blown away.

I wasn’t. Oh boy, I wasn’t!

I know that beta versions of plugins are buggy, so I’ve already cut a lot of slack. I wrote a full-blown post of 1500 words on Gutenberg yesterday, complete with screenshots and everything else. I was stunned that WordPress could release something like this to the unsuspecting public.

Before I get into the problems, I have to briefly describe the significant paradigm change that Gutenberg brings.

No Single Text – Everything is a “Block”

You think you’re writing a single document. Let’s just say that Gutenberg believes otherwise. The new editor doesn’t treat your post as a single entity. It splits everything into blocks. Paragraphs, images. Even headings get their own block!

Here’s what I mean. In the screenshot below, the heading is a separate section from the paragraph above. Note the popup menu and trash icon to the side of the heading, which has my mouse over it:

Blocks in the WordPress Gutenberg Editor
Blocks in the WordPress Gutenberg Editor

And it takes this concept to the extreme, creating problems. So here’s a list of 10 things that bug me about WordPress’s revamped Gutenberg editor.

Problem 1: Shortcuts Function Only Inside the Block

Experienced writers use navigation shortcuts to move quickly from one part of the document to the other. It’s so common that I don’t even remember those shortcuts – it’s all muscle memory. Need to go to the beginning of the document? I watch as my fingers type in Ctrl+Home.

Except…in Gutenberg, that doesn’t happen. Other shortcuts that apply to the entire document don’t work either. For example:

Pressing Ctrl+Home

Expectation: Cursor goes to the top of the page
Reality: Cursor goes to the top of the current block! (Paragraph, image, etc.)

Pressing Ctrl+A

Expectation: The entire article is selected
Reality: Only the contents of the current block are selected!

See what I mean? This is ridiculous. This is all the same article. Not fifteen different ones!

Update: Ctrl+A now selects all the blocks instead of just one. It looks a bit weird, but at least it works. Other shortcuts like Ctrl+Home still don’t function.

Problem 2: Shortcuts for Headings and Paragraphs Don’t Work

Update: There are new shortcuts for headings in Gutenberg. For an “H2” heading, start the line with two hashes (##) and press space. For an H3 heading, use three hashes (###) and so on.

Professional writers know to use keyboard shortcuts for creating headings and paragraphs. The classic WordPress editor has taught us that Alt+Shift+2 creates a new “H2” heading, and pressing “3” instead of “2” makes it H3. Little things like this save time and keep us in the flow—no need to move our hand to the mouse.

But Gutenberg breaks this and years upon years of muscle memory. Now pressing shortcuts like Alt+Shift+2 merely selects the line of text. It doesn’t convert into a heading. Is this a bug or intended behavior? I hope it’s not something WordPress wants to leave for later, thinking it’s a low priority. That’s Google’s strategy, not Automattic’s!

Problem 3: Horribly Distracting Popups Upon Mouseover

Update: Gutenberg now has a “Top toolbar” option in the settings menu which sticks all the block actions to the top of the page, so there are no more annoying popups. Here’s a screenshot:

Top Toolbar in Gutenberg
Top Toolbar in Gutenberg

Do you know the main use of my mouse pointer while editing? To place my cursor where I want to start typing. Either make a link there, or select some text with the keyboard for formatting, deleting an extra space, or correcting an error.

Do you know what I DON’T use my mouse pointer for? To move the paragraphs up and down! I also don’t use it to get a “menu”, a trash icon, and a whole bunch of other stuff. Gutenberg, however, obliges by filling my screen with trash whenever my mouse pointer happens to hover over a “block” (which is basically everything).

Here it’s helpfully asking me whether I want to move the current paragraph up or down:

Movement Icons for Blocks
Movement Icons for Blocks

Like, why would you do this? How often have you moved your mouse over a paragraph to displace the thing up or down? What is the use case here? Is this actually something that people want?

Forget about “distraction-free writing”. Gutenberg is “distraction-heavy” writing. It’s not just you and the words on the screen. It’s you, lines demarcating blocks, unhelpful icons everywhere that disappear and reappear as you move around the article.

Very zen. NOT!

Problem 4: Accidentally Creating Blocks

Let’s say I want to add another sentence to an existing paragraph. I click the end of the last line. Easy, right? Gutenberg often thinks I want to create a new block instead. Then I have to go and delete said block (Aha – so that’s the reason for the trash icon!)

The line between “placing your cursor” and creating a new block is thin. You better have pinpoint precision with that mouse.

Problem 5: Word Count is No Longer Automatically Visible

I often quickly peek at the bottom of the WordPress editor to get a quick idea of the number of words on the page. I do this without breaking my flow and without distractions. That functionality is chopped in Gutenberg.

Instead, we get a new “Information” icon at the top of the page which gives us the count when we click on it:

Information Button to Get Document Details
Information Button to Get Document Details

Along with other unhelpful stuff like the number of paragraphs and blocks. Seriously – in 10 years of writing, I have never once been curious about the number of paragraphs in my article (or blocks). Who needs this stuff? And while designing it, did anyone pause to consider whether it’s useful?

Problem 6: Some Boxes Below the Editor are Now Missing

Update: This issue has been fixed. You can now see all the boxes below the editor like before.

Some themes, like Genesis, have useful options below the WordPress editor. For example, you can change the layout of individual posts or pages. I don’t personally use it, but others might have gotten used to that functionality.

But the Gutenberg WordPress editor axes it. Again, I don’t know if it’s a bug or whether they expect us to find that option elsewhere. And if it happens with Genesis themes, I’m willing to bet that many of your other plugin boxes below the editor will disappear.

Adding on, basic stuff like custom fields is missing! Custom fields are a great way to specify individual parameters for posts or pages. Like, say, a special image URL for Facebook. Or a particular image apart from the featured image for the post. Earlier, you could hide or show these options using the “Screen Options” button at the top. That facility has been removed in the new Gutenberg WordPress editor.

I’m told there’s a separate plugin for custom fields. But yeah, that’s what we need—one more plugin to enable, by default, into WordPress.

Problem 7: HTML Code is All Messed Up

Update: This isn’t as big a problem as I once thought. If you copy the HTML and paste it into another WordPress Gutenberg editor, it preserves the formatting. The only hindrance is if you want to paste it into another HTML viewer – a use case I haven’t encountered thus far.

Along with blocks, Gutenberg seriously screws up the HTML code generated by the editor. On the top right, there’s a menu with the “Code Editor” option. But here’s the junk it produces:

HTML code is all messed up
HTML code is all messed up

Now you may say that these are just comments, and it doesn’t matter that they’re there. Except that it does bother me. I like to keep things as clean as possible. And if you want to transfer your Gutenberg code to another WordPress editor or HTML viewer, these junk comments will also follow. I just don’t like that.

Using the Classical Editor Instead

Update: Gutenberg is now the default editor, but you can install the Classic Editor plugin to continue using the older version. Currently, the plan is to continue supporting the classic editor until 2024 or for “as long as necessary”. So if you still can’t stand Gutenberg after all these years, you can continue using the older editor.

I don’t know how it’ll be in the final version, but now you can revert to the classical editor after installing the Gutenberg plugin. You can find the option in the list of posts from the WordPress admin as shown here:

Access the Classical Editor
Access the Classical Editor

Though I suspect this will go away soon once Gutenberg is fully integrated into WordPress.

Final Thoughts on the Gutenberg WordPress Editor

Some of you may say that these are just the problems of a beta plugin. I disagree. These look like deliberate design choices to me. Stuff like ditching global text shortcuts is a natural outgrowth of the “block” mentality. No one made an “accidental” decision to put a separate button for the word count. I’m sorry, but the new Gutenberg WordPress editor is just a lousy replacement for what we have now.

Yes, the current editor is a bit slow and outdated. But it’s been refined over the years to give us what we need, and Gutenberg chucks a lot of that learning out of the window and expects us to get used to it.

Sorry, but that’s not going to happen, and not unless they change it fundamentally. In the meantime, I will be composing my posts in Microsoft Word.

About Bhagwad Park

I've been writing about web hosting and WordPress tutorials since 2008. I also create tutorials on Linux server administration, and have a ton of experience with web hosting products. Contact me via e-mail!


  1. This is what I’ve been saying all along – roll Gutenberg into WordPress.com as the default editor and then have it as an option via Jetpack or a standalone plugin for self-hosted installs.


  2. Ah, this is honestly everything I feared that would happen.

    What I fail most to understand about Gutenberg’s purpose is my experience as a writer. When I’m typing something out, I don’t want to have to stop each time and focus on stupid blocks. If I wanted a site builder, I’d have installed one already.

    I installed the “Classic Editor” plugin. Literally cannot be bothered with Gutenberg, and I’m so miffed by the intrusiveness.


  3. this is BS..you may as well just send a virus to millions of people and let them figure out whats wrong with site now…forget the phone too..what asinine person thought this was a good idea to do to millions of people..DUMMIES


  4. I run many WP sites and one of them is a Meetup alternative. The majority of group admins struggle using the editor. They are not technically minded. They would get totally lost using a page builder – any page builder.

    Page builders for WP are nothing new and are a good option for those who want to use them. But the key word is “option”.

    The attraction of WP is its versatility. You can make your sites as simple or complicated as you see fit. If they make this hard-coded and block any plugin that tries to disable it, then they are going to lose a lot of long-term users.

    Meetup revamped their platform in December 2017, alienating the majority of its users. It seems companies are not interested in what their users think. If they think they have a good idea, they deploy it whether users think it’s good or not.

    Criticism is tolerated at first, then policed and finally blocked. Already the WP moderators are deleting posts that don’t support Gutenberg. Why companies deliberately shoot themselves in the foot is beyond me.


    • It’s as if someone thought “Let’s make it modern“, and to hell with usability 🙂


    • 100% agree. Currently I’m working on a project where Gutenberg will fit brilliantly. Taking the stress out of content creation for the editors who, may be great writers but, are mainly not particularly tech savvy.

      Then on other projects, Gutenberg just gets in the way, like this article suggests. In those projects, the writers just want to write and are well aware of how to add images, use pull quotes etc. For these I’m readying an email explaining how to dump in an HTML block as per usual.

      The problem is, you’re damned if you do, damned if you don’t.


  5. If they want to kill WordPress, this is one if the ways to do it. OMG!


  6. So to resume, y’all are suffering from neophobia.



    • You don’t believe these are valid criticisms? If not, why not?


    • Nope, I love new. I thrive on new. I need new in my life. I stagnate if I don’t get it. This on the other hand is garbage.


    • Gutenberg was non-functional on my site so none of this mattered. I could edit a page or post but not save it … at all. It would not update! After a half hour on the phone with my web host we decided to turn the classic editor plugin on and see what happened. All problems disappeared. So I will stay with the Classic editor on all sites I manage.


  7. It is a new thing, all my theme bought from themeforest not support this editor.
    I think it may take long time for plugins which base on default tinyMCE to cover to Gutenberg.


  8. Ok so when Gutenberg finally rolls out in 5.0, why don’t everyone not update to that newest version of wordpress. I do not like not updating, but I would make an exception here. Plus, install the classic editor plugin on top of that. This Gutenberg is not only going to affect the editing portion, but also how the front end is designed. Many of us web designers design custom themes on wordpress. This will dramatically increase my costs as it will lengthen development time. Bottom line. Do not switch to Gutenberg. Revert back to a previous version of WordPress that is not using Gutenberg.


    • Two-thirds of the writers I know use Classic Editor. But Automattic has no intention of supporting it forever. They thought they’d get rid of it in 2021, then 2022.

      The solution is to switch to ClassicPress.net which is a fork of WordPress just prior to Gutenberg. Anyone who wants to keep developing for or using Classic WP should consider switching sooner rather than later.

      Eventually, themes and plugins developed before Gutenberg are likely to drop support. One by one they’ll go by the wayside or you’ll have to keep switching as they quit working.

      Better to move over now so developers will focus on creating themes and plugins specifically for Classic Press. There already some; however, that most still work has slowed desire to do that.


  9. Exact. I agree perfectly with you. It is the impression I had when I found myself in front of him.
    The WordPress team is making a resounding mistake, implementing it by default.
    In my opinion if they really wanted it, they would have to offer it as an alternative to the classic editor, which can be set from the settings panel.
    Moreover, just yesterday, writing a post, and using the classic version on Gutemberg (it is possible as if it were a block), I realized the disappearance of the media button (!!!): it is not possible to insert in the “classic” block media like photo or videos or gallery.

    Ps. Sorry for my poor English!


  10. opensource says

    Also, that feel of a CMS update being so invasive with themes and plugins baffles me, it is WordPress still open source?


  11. I understand concerns about the new system of doing things – it takes time to get used to it.

    All I read here is based on personal taste and habits, and doesn’t provide any valid arguments against the new direction in WP.

    It posses more of a challenge to those of us that do coding – learnig React as essential part of the new core, than adding or editing content.

    Get used to it. It ain’t going away. And the more you prolong the switch, the less prepared you will be when it becomes unavoidable.


    • In order for the Block Editor to be usable, they need to fix some things. I think we should have the option of using a block the way we used to the Classic Editor and make design changes from within it. If that’s possible, it isn’t obvious. As we all know by now, they rolled this out with WordPress 5.0. From what I understand, the Classic Editor plugin isn’t going anywhere either. Some of the bigger sites I work on will be using the Classic Editor – I work with WordPress all day and with these larger websites, I need to be efficient. The Block Editor will stay on the smaller sites so that I can slowly get used to it.

      My initial response to the change was “yuck” but I think I’ll wait to have a firm opinion until I at least get more comfortable with the Block Editor. I’ll give it a chance, but I don’t think this is a good move on WordPress’s part.

      With some of the older posts, they transitioned into Block Editor in one block, with the subheadings and images all in that same block. So I suspect composing a post that way is possible, I just don’t know how to do it yet and it certainly isn’t obvious. I can learn from these posts, though.


  12. I tried Gutenberg, I liked some new options they offer, but switched again to the classic editor because I found problems they have to fix.
    For instance, image files could not be centered (although this option was chosen).
    I could not change the color of links.
    I tried many things but couldn’t fix both issues.
    I don’t have these issues with the classic editor.
    If they solve some problems, I will definitely use it, it’s almost identical to MailChimp’s editor.


  13. The whole custom made page attribute functionality of my website crashed, disappeared. And it all felt like demonetisation, you have something useful to do but can’t do it.


  14. You have described exactly what my experience and feelings have been. I moved rather recently (over the past two and half years) most of my sites to WordPress (about ten of them, I had only two WP sites earlier), confident that I had found the perfect, lasting solution for my heavily text-content oriented sites. Continuity was for me the keyword. It cost me many weeks of work, not mentioning expenses for paying a designer for doing some things I could not do by myself, but I saw that as a long-term time investment.

    When I started discovering Gutenberg a little less than a year ago, it depressed me. The entire logic of Gutenberg runs counter the way I am publishing my websites. If I had seen a CMS like that, I would never have switched to WP. I can probably use Gutenberg for two or three of my sites, but not for the other ones.

    For the time being, I will disable Gutenberg and stick to the Classic Editor. But it is clear that the WP management does not intend to keep the Classic Editor working for many years – a few years, certainly, but I am not sure that it will be there in ten or fifteen years. True, there might be other editors available by then that could be used as substitutes for Gutenberg. But there is no certainty.

    I am following with much interest the ClassicPress project. I am tempted by such a fork, while wondering if there is a promising future for it. I would be quite interested to read your comments about that.


    • In all honesty, I’ve simply started to type out all my posts in Word 2016, and then copy paste. Earlier, there used to be compatibility problems if you did that, but no more.


  15. I run a local club website. I have no HTML / CSS etc training. Basically, I type text in and add the odd image.
    I am finding no advantage to the new editor and several disadvantages, of which the principal one is simple unfamiliarity. It is frustrating to find I can’t do things I already learned how to do, so I must learn anew.

    I understand “Gutenberg” will eventually be the only editor available, other than the “Word” option suggested by Bhagwad Park , above. I may well follow his example.


  16. Douglas Randall Gross says

    It is not very practical if you are truly authoring something. If your website does not have any true writing on it and the text is not the same as standard reading, that is fine. Like a store or a bar or a restaurant, but if you are writing a real blog the new editor pretty much just brings it down to the level of Twitter. It is nothing but in the way for me, and I never do anything but paste my HTML into the TEXT tab anyway.


  17. I have already signed up for the fork of wordpress. It’s called ClassicPress and it was created by a developer who decided that Gutenberg is a “disaster” that would not happen to him, so he created a fork of WordPress and calls it ClassicPress.

    It’s in beta testing now and they are inviting all to participate. Once it’s ready to go live, I will be installing it on my server and saying goodbye to WordPress forever. I’m an author and illustrator and I don’ have the time nor desire to learn to work with a blockhead page builder that has already proven to be a disaster on too many people’s websites. It created nothing but frustration for me when I tested it multiple times.

    Check out the new fork of WordPress at classicpress.net


  18. Hey… a great article with great points but I am afraid you have missed a big one for me. Have you ever tried using Ctrl Z (undo) in a block? It’s a nightmare. It actually deletes much more than the last typo. When I tried to retrieve using Ctrl Y, the text disappears and is unretrievable with keyboard shortcuts. Thankfully, there’s hope if you use the undo-redo arrows on the taskbar above.


  19. The worst part for me: photo galleries. The classic editor lets me choose between several different styles of gallery, the new one has one and one only. And I hate it.


  20. You can also disable 100% all Gutenberg junk with no settings or database queries:


    (put in the mu-plugins folder and your clients will never even know the difference)


  21. How does one control the width of a sentence or column using Gutenberg? On a 27″ monitor the sentences are much too wide if one hides the right-hand side bar.


  22. So bad, this Gutenberg editor.
    I am happy there was a plugin available (classic editor) to start using the classic editor again.


  23. I have been trying Gutenberg, but i cannot get it to work properly. a red banner at the top saying “Updating failed”. I have no idea what that mean, or what I’m supposed to do about it, and I can’t seem to find an answer anywhere.

    When I try to upload an image to the post page from my computer, I get this error: “Error while uploading file 1.jpg to the media library.” The image is a small jpg, so size and file type are not the issue. Loading an image from media library work fine.

    I’ve contacted my theme support (Flexible Pro) in hopes that the problem is theme-based, and they can fix it.

    Thank god they haven’t taken away the Classic Editor.


    • I’ve been having the same problem. If I can’t create a page or post, exactly why should I be using this system?


    • I had a “Updating failed” problem. Contacted my very helpful hosting provider who said the Gutenberg update corrupted the mysql database! Fortunately, they could rebuild the database and my site was saved. Am starting to move away from WordPress now. I’l be blogging about it but I’m not sure if I can put a link here. If you are after a straight blogging platform, check out Publii. I’m also looking into Hugo. These static sites are lightning fast without need for caches, but there is a learning curve – more about un-learning WordPress!


  24. In 30 years of building software and websites I have never seen such a horrid disaster forced on users who trusted a system. We stalled on moving to WP for as long as possible, and our worst fears just came to fruition.

    Has anyone here ever taken a site out of a builder and back into the default editor? We deal with that all of the time and it is a horror. That code between paragraphs remains and has to be cleaned manually (or through a questionable plugin.) Moving between blocks to edit paragraphs is idiotic, and crushes the option to lift code into notepad for edits. There are so many things wrong with this, even if you don’t consider that blocks will also eventually run their course. Everything does.

    Why wouldn’t WP just offer 2 versions if they felt they had to do this? It surely looks like certain death of the platform. The logic supposedly was due to industry competition–but there’s no way this should have been a concern. The only thing accomplished is more end-users feeling they can manage their own site without assistance, and having larger problems and bigger fix-it bills to deal with as a result.

    WP: This opens the doors for some savvy developers who realize the beauty was in simplicity and build a new sleek CMS; and for unscrupulous developers (we all know there are some,) to charge clients exorbitant fees to fix sites that suffer the effects. It’s another big hit to small business, at best. With us, that means 100s, and over the years, 1000s, of clients are at risk; and those who don’t want to switch will not be applying upgrades (assuming that blocking Gutenberg will eventually be disallowed.) So much for internet security. I’ve already been asked to revert 3 sites that hated the new editor (we opted for a plugin for now, but that won’t last either.)

    It looks like it may be time to go back to the older CMS that have still held on to the belief that web developers should be building sites that earn a living for them, not end-users, and that we just need a framework–not micro-management. I’d happily pay to use a system that doesn’t upset itself like this. I don’t get it at all. Sad day in WPLand…


  25. OMG…. This morning I logged into one of my hosted websites and (stupidly) clicked the upgrade to 5.0 button (not knowing the full impact of that decision). I’m not a professional developer but have historically found WordPress to be a good semi-intuitive way for myself and non-technical users to be able to blog and add content to their websites.

    What in the Sam hell just happened? I’m scrambling, and will be spending HOURS/DAYS trying to figure out how to use this monstrously non-intuitive editor. My first challenge was to simply add a link to a PDF file. Before, it was easy….add media. I’m an hour-and-a-half in and I still can’t figure it out.

    Will this cluster of an upgrade auto-update on my other websites that are set to automatic updates? If so, when is that deadline?

    I don’t have time for this crap. I’m going to bet that in the upcoming weeks the community will find a torrent of people who host websites for others who are non-technical, all of which the users a) won’t have the slightest idea how to use this screwed up interface, and b) will ALL have to be retrained by said website hosting individuals, costing those individuals dozens and dozens of hours in labor, and cost to do so.

    [This was deleted on another site that has a supposed unbiased “article” on this change, but obviously are Gutenberg propagandists. Time will tell if this remains posted here.]


  26. AMEN!! I tried it for a week or so and have such frustration with glitches and ineffeciency… (I thought it was just because I’m old and it takes me longer… kind of thrilled to see you all are as frustrated as me! 😉 ) I am also so glad to see there’s a plugin to go back to classic editing. DONE!


  27. Maybe static html is the solution? (If you don’t need to blog)


    • I’ve got 5 sites myself that I am right now mirroring with HTTrack to take back to static HTML. I’ll do my own redesign shortly to clean them all up but this gets me away from WordPress sooner rather than later. I am not a fan of the new editor in any way, don’t like this direction they’re taking with WordPress, so out the door I go. I’ve been toying with the idea for a while, since the Dec update to 5.0. The block editor is a mess. My posts tend to be longish, written in the editor, and heavily edited before posting. The block editor is a disaster for this kind of writing, IMO.


  28. Im a WordPress Developer and when I update my wordpress projects to Version 5, all of my custom fields are having problems in backend. That’s why I downgraded my wordpress projects and back to Version 4.


  29. Problem 8 : cannot select and copy tags… might be a small thing, but when I saw that I couldn’t select and copy tags, which is an operation I do regularly, I just switched back to classic editor…
    Are they actually planning of making Gutenberg a good editor at all ?


  30. Great… WordPress already had one of the worst WYSISWYG editors out there (they way it didn’t actually generate HTML code, but instead added paragraph/linebreaks on output – also meaning that if you paste in HTML code written outside of the editor, you would have to manually remove the linebreaks or the braindead add f*&%ing BR tags for every linebreak in the code). And it sounds like they actually managed to find a way to make it even worse!

    Yet another addition to long, long list of “reasons I don’t use or recommend WordPress anymore.” ESPECIALLY now that the vastly superior CMS ExpressionEngine has gone open source.


  31. Is the phrase ditto familiar? Just back into a few WordPress installs, and I am like !@#-~!!. Thanks for the informative article.


  32. When I write a post using this Gutenberg editor, Yoast SEO suggestions also don’t appear below the post as it used to appear below the post in the previous editor. Is it just happening to me or with everybody? I don’t understand. Can you tell something about this?


  33. I believe the latest version of Yoast works with the Gutenberg editor. Did you check it out?


  34. After updating to the latest version I immediately installed Disable Gutenberg plugin to switch back to the classic editor. The whole concept of blocks seems to be a bit confusing. Should try out Gutenberg blocks in the local environment to get an idea of how it works before using in the live website.


  35. OMFG without a warning the Gutenberg crap was suddenly there. I was working on a site in the Classic one and after reopening the same page it was Gutenberg all over. Talking about Autosave, blocks and more ‘features’ I didn’t get in 15 minutes even using editors in Joomla and WordPress for years. This is just terrible.


  36. Yep, hate it. So relieved when I realised I could revert back to Classic Editor.


  37. Most users ABSOLUTELY don’t need Gutenberg!
    WordPress platform will be lost users!
    If somebody need Gutenberg – can be use plugin, BUT NOT FULL Integrated in WordPress.
    NO any good tutorials!
    Gutenberg will kill WordPress!
    Creating page not so easy, like it was before(copy and paste)!
    For customers most important just add any info(+media) on own blog in 2-3 minutes.
    And it’s all!
    I hate Gutenberg! Please remove Gutenberg in next WordPress versions or make 2 versions: with gutenberg and classic!


  38. I just tried using Gutenberg, which was pushed on all of us as a forced upgrade. I agree, it’s a disaster. All my existing content was pushed into blocks, and I can’t find anything beyond the first 16 lines of an existing blog post. I see a single block on the page, but can’t navigate or scroll in it and don’t know where the rest of my content went. It does look like there’s advertising or some kind of random junk surrounding the block.

    I installed the Classic Editor, but that’s buggy also, and I’m having trouble selecting text and moving my cursor around in it. Though it looks similar to the original WordPress interface….it just doesn’t act like it.

    Automattic/the WordPress team really ruined a good thing. It seems like Gutenberg was designed by people who’ve never created written content before — maybe they’re app developers, not web developers. Maybe it’s fine if you’re creating a website with just images, but not if you’re trying to write something that’s more than a couple of lines long.

    In terms of disaster, it ranks with “New Coke” and iPhones with no headphone jacks in them. Very bad decision, and it leaves thousands of us in the lurch. If they’re smart and paying attention — and now that they’re scattered in remote locations with no home office anymore, I’m not sure if they ARE paying attention — they’ll come out with an update that makes Gutenberg optional, not the default.


  39. Honestly, if WordPress don’t do something about this horrible Gutenberg editor, it will be the end of WordPress as the most popular platform for web developers. Thankfully, we can switch back to the classic editor using a plugin (for the time being). I am a professional web developer and I have used WordPress since about 2005. I’m now looking around for alternatives.


  40. Must say I have been looking for support on why Gutenberg is possibly the biggest hype and the largest fail I have seen from wordpress for a long time. The code behind that it produces is horrific. Comments and all sorts of superfluous junk. If you need a page builder spend the money and get a decent one. Siteorigin and WPbakery are usually my go to page editors. yes they cost money but with them comes performance and logic.


  41. I delayed updating to the new editor till just before Christmas. Since we did the update, I have virtually not been able to post – as I try to learn how to cope with this clunky new system.
    How dare they take away the “justify” text option – just because “they” think neat left text is better? That’s like a clothes shop saying they won’t stock blue jeans any longer because the buyer personally prefers black ones.
    The blocks are not just slower when it comes to preparing posts – I keep losing them. I used to post three articles an hour and now it’s more like one article every three hours, so thanks to this update my income is now 10% of what it was.
    Anyone know of any alternatives to WP? If not, you’ve all identified a gap in the market – please develop one!


    • Have you heard about the ClassicPress fork? This could be an alternative.
      I hate gutenberg and I will leave WordPress soon and switch all my client sites to another system, because I hate to be forced to use such a utter garbage…
      And I can’t understand that the WordPress developers don’t listen to their community which made WordPress what it is/has been.
      I think that a star rating below 2 stars and over 3 million active installations of classic editor plugin is a statement they should react on accordingly.


    • Install the disable Gutenberg plugin and carry on as normal, Hide SEO bloat, Lean WP are also two excellent plusings they clear out the shite Yoasts SEO plugin makes and WP.


  42. I have a theory the folks who built Gutenberg dont build websites or if they do theres defo no client involved/deadline/consideration of folks over the age of 14. I think this is what they are so bemused and the rest of us just went WTF! Its a joke the comments in code just makes my skin crawl, I am so sick of helping clients remov this bloat ware from WP. Its sucking the fun out of my job day by day. BrokenPress as it feels now. I install WP and 4 plugins to disable crap, pure and utter crap like the customizer etc. Would it kill them to add all this new shite from the past 5 years in a section in thr admin where it can be disabled. Anyways rant completed.


  43. Matthew Park says

    “I have a theory the folks who built Gutenberg dont build websites or if they do theres defo no client involved/deadline/consideration of folks over the age of 14.”

    No, I have to disagree.

    People behind Gutenberg want to infuriate and alienate WordPress users & developers so much that they abandon WordPress altogether.

    Gutenberg is total crap.


  44. Gutenberg is a disaster. I have installed “disable gutenberg” plugin on all my sites (130+).


  45. I’ve been designing websites since the internet was new.

    I just spent the last two hours trying to figure out how to keep WP from automatically deleting my and tags.

    Not a single fix worked.

    This is terrible.

    Dear WP guys: I’m a big boy. You can trust me with carriage returns. I promise.


  46. Their intentions could be good, but the result is a disaster for many users. When I first heard of Gutenberg, they made it sound like it was the 8th wonder of the world of web pages editing. It ended up being just another builder, a little bit clumsy, and changed several WP useful features, like the possibility to easily edit the permalink. Now the offer a useless button to fully change the permalinks scheme, and the edit option is hidden in the “quick edit” option for every post or page.

    They should have made Gutenberg optional. If want a builder, which I do, I do install a specialized one I like, cos there is not a normalization like there’s in text editors. Some WP themes include their own builders, and in several cases collide with the Gutenberg.


  47. I avoided to switch to Gutemberg as long as it was in its beta testing version. But unfortunately after the latest WordPress updates this editor became the default one.
    I tested it for a couple of posts, but that was the most time consuming and counter productive thing I’ve ever tried in my life.
    I’ve just installed the Classic Editor plugin and reloaded the posts that I have created with Gutenberg and at this point I realized that I had done to each of these posts more than 20 revisions!
    I’m considering seriously to switch my website to Classic Press. This Gutenberg crap is simply a nightmare. It seems that productivity and optimal performance is not in the vocabulary of WordPress developers.


  48. Interesting article. I’m no expert when it comes to WordPress. I avoid such things whenever possible but use them for the blogging portion of my websites because of the content management / search features. So take this comment for what it is.

    At least some of this criticism of Gutenberg seems to come down more to what veteran WP users are accustomed to than what’s actually optimal. I have to wonder if any fundamental change to WP would be greeted positively by the WP community.

    Take the Ctrl+A criticism as an example. What I would expect from an editor like Gutenberg is following behavior:
    1. If I’m in a block and hit Ctrl+A, I select all text from that block.
    2. If I click to the side or somewhere outside my blocks and click Ctrl+A, I select all the text from the article.
    And that’s exactly what happens. It’s maybe not what one expects if one is used to the old editor, but it’s a more logical and powerful behavior.

    As for mobile vs. desktop usability, there will always be downsides to optimizing a UI for mobile. But WP developers need to deal with a question that more and more bloggers will ask in the coming decade: Why should I need a PC to do something as simple as write a blog post?


  49. Totally agree. This is classic product updating without a real rationale. The beauty of WP has been its consistency. Now the (simple?) act of creating a post has become a mess. And managing media? Forget about it. There are dozens of products in the market or our memory that were improved to death . Example? VW Bug. Now WP has gone and shot itself in the foot. How long before it disappears, too? Thanks for your post. Captured my sentiments exactly..


  50. 2019 may.
    I paste article text to wordpress gutenberg editor. I got lots of blocks. Now I want copy back this content. I press ctrl + a / ctrl + c. Nothing happend. I must click “copy all content” inside top right menu. Ok. I click that. I got copierd content with lots of comment and overrall mess. Something simple like that not working.
    This is not expierient what I want.


  51. How about Mong9 Editor? It is lightweight and developer friendly.
    It is a content editor similar to Gutenberg, but has an intuitive UI.


  52. Completely agree.
    I have a photography website based in a WordPress theme and I was used to type my articles in the classic editor, either mixing text with images or several photos grouped as a gallery. But with the new block editor, it completely messes up my article even before I save it. A mix of text and images are suddently compiled into a malfunctioning html block, that I need to remove and start over again. And this is my FIRST time trying to make an article with this bogus editor.

    I’m going back to the classic view.



  53. After I updated to WordPress 5, the very first page (I don’t use posts) that I tried to edit in Gutenberg had its formatting COMPLETELY destroyed – I did nothing to cause this. I was devastated! I finally did some digging and discovered the Classic Editor plugin. I had to do a site restore from ManageWP, installed the Classic Editor plugin, and now I’m back to sanity. Before the next major WP revision, I will be looking carefully at what they are changing – I would like to avoid panics like this in the future!


  54. I’m on WordPress.com (not .org) and plugins are not available. I’ written over 1500 blogs over ten years and this morning when I went to write & post something, I got this white screen bullshit, some crappy block editor, and all the editing commands (italic) kept disappearing, and I couldn’t cut & paste two words farther down the sentence, and no colors available, and again the damn editing commands kept disappearing, and if I wanted to look something up in another post, the damned thing said “you haven’t saved, do you want to leave?” and NO I didn’t want to leave, I wanted to open another post on another tab, and who wrote this damned program anyway and foisted it onto long-time users. Probably the 14-year-old troll-in-training son of one of the WordPress owners. I want that SOB’s name so I can write them a nasty letter totally unlike this exceedingly gentle and mild-mannered message I am now writing.

    I can’t even find a decent non-BS tutorial without having to plow through some “Isn’t life wonderful now that you have the new, wonderful block editor, everything will now be sooooo much easier, tra la la” load of crap.

    Sorry, WordPress people. This Gutenberg thing sucks.


  55. WordPress 5.6 and Gutenberg is still there lol.
    When will they learn that nobody likes it?


  56. 2 years has past since your original post and I couldn’t agree more. I am old but I usually like to see new features with upgrades but this is not the case. The editor actually has improved in these 2 years and I must agree it has some good points but, as you said, the entire concept of “blocks” is wrong. For people writing long content it’s very difficult to use these editor, jumping from one block to another, leaving the keyboard because I need to use the mouse for something really odd.
    I manage about 100 wordpress sites and in all of them I see the Classic Editor plugin is installed and active.


  57. I’m late for the party, but after some time off (2 years) from WordPress developing I got a project from a friend and got back in the “business”. Oh boy have things de-evolved! Gutenberg has every annoying instance one does NOT ask for when writing a page. It has this very icky thing going on about trying to balance between a visual editor and backend content editor. A lot less makes sense now should one be developing PROPER templates with proper Custom Fields etc.

    At the same time the grid and block system is rather limited, so who is it for actually? I remember I used to use PageBuilder for stuff like that and it was actually quite a finalised product that was there should one need it.


  58. It sucks. I don’t have any idea what blocks can add to my work/life but even if I did, the layout is awful and it just seems wrong. It’s like my computer doesn’t “know” what to do with it. Not to mention that I use Safari and none of the settings are stored so I’m stuck with lots of features I don’t need, every time I log in. Who are the people responsible for this mess? Where can I find the reasons why they think this is a good idea for an editor?


  59. Dont fall for this, WP dev for 10+ years, if you use Gutenberg you are a crash test dummy. WP is trying to sell you back simple HTML editors with this idea that blocks will work. There was a CMS called osCommerce way back when that worked in blocks like this, thing was a nightmare. Use any of the paid professional builders or just learn some HTML. It is taking me longer to train Gutenberg than it would do basic HTML and CSS via div and span with a person, so what is the point. You could literally learn web dev in the time it will take you to learn this broken editor. The comments are a joke, the whole idea they replace shortcodes is just so silly.


  60. I have been b!tching about Gutenberg for years. The philosophy of wordpress’s user experience is gone down the tubes since they released it. There is no wonder why the classic editor has been the most popular plugin in the worpress community for how many years now. I was recently on a project that used an outdated headless version of wordpress with no ability to switch editor without upsetting the apple cart of angular developers. I took it upon myself to actually try and use Gutenberg, to do some very basic stuff. It was a absolute joke It’s such a poorly designed interface I landed up spending most of my time in html blocks hardcoding simle text and inline css, (which defeats the whole point of a block editor). Why wordpress persists in force feeding this to the community I dont understand.


  61. Jim Camomile says

    I Keep giving G’berg another chance and it keeps proving my original notion. It really does suck as a basic premise and adding features does nothing but add to the complexity and confusion. If it had a way to allow people with some dev skills to side-step all of it’s foolishness and get on with coding a simple and elegant page, making use of short-codes to add more complex blocks, then I would be able to complete my work on time and get on to more enjoyable pursuits. As it is, it takes much longer to do the basics and then I need to proceed to iron out the mess with additional css work.


  62. This will remove HTML comments:

    You can use it as a regex in most notepad or find replace plugins. It will remove the nasty nasty Gutenberg code. I have more. This is the real issue with Guts, if you convert a post its lost, the entire markup they generate is so nasty. HTML comments are just silly.


Speak Your Mind