jf327

@codymckibb can you elaborate on how this broke your entire business? There’s no way the dev team can make fixes for the problems you seem to have had if you don’t list what they were.

I don’t wanna say I don’t believe you, but I have a hard time trusting reviewers when they only complain and don’t give justification beyond “it’s the worst thing ever”.

I’m curious what y’all are specifically having problems with. I manage around a dozen WP sites, and I’ve switched nearly all of them over to Gutenberg with no issues.

I developed a small plugin to make some minor tweaks and fix some early GB visual issues, but several of those have now been fixed, and it seems to be working better than ever. It’s still a work in progress in some regards, but it seems to be a fine piece of software at this point.

To the OP, what part of it makes it the “worst thing [you’ve] ever seen”?

Hello @courtneypk. Last I checked, all four of these issues are still present, and I actually built a simple plugin to fix the first two. I’ve been immensely busy the last few months, but I’ll do my best to make some bug reports on Github.

The editor as a whole has definitely improved since I wrote this review. For example, loading time is much quicker, and I like that.

@anevins

Yea, don’t do that. That’ll disable all core updates and will prevent your site from receiving automatic security patches.

I use that on around a dozen sites and none of them have had issues. I like having full control over when the sites update (to make sure there are no compatibility issues), even if it is for small security updates. Then again, I do routine maintenance on the sites so they never go too long without me updating the core.

In the OP’s case, I was merely suggesting that as one possible solution he could use for his dilemna. So, I guess a correction to my original reply would be, use at your own risk, and only if you regularly maintain your websites.

@leapdragon

The same thing just happened to me after updating wp-core and quickly testing out in a sandbox. Site loads? Pages load? Backend looks right? Okay, great, let’s get back to work.

Half a dozen page edits later, O WAIT, HTML that we didn’t touch is getting borked. Why?!

I’ve not had this happen when using either the Classic editor block, or the HTML block. Your HTML tags should not be affected. The only blocks that would remove them would be ones that are specifically meant to hold a single element, like a paragraph or heading block.

Both the Classic Editor plugin and Disable Gutenberg plugin are free to use, and they restore the classic editor.

I agree that this project was rushed, and that it should have been held back for several more months to fix some glaring bugs, but I think calling it “novice software from the 90s” is uncalled for. It has a very clean interface, and most options are easy to find. If you have any trouble finding things, I’d be happy to help you out.

This isn’t a very constructive review… all I can tell you is to try installing either the Classic Editor plugin or the Disable Gutenberg plugin.

Not to jump to WP’s defense, but you can easily disable automatic updates for the core using this line of code in your wp-config.php file (located in your site’s root directory):

define('WP_AUTO_UPDATE_CORE', false);

That way you won’t have to worry about your site getting messed up by future updates.

There’s also the Classic Editor and Disable Gutenberg plugins available that will completely remove the Gutenberg editor from your site.