This blog is made using WordPress.
And yes, it is (mostly) fantastic.
Earlier this year, WordPress promised a new version 5.0 – codenamed WordPress Gutenberg.
And today is the day that Gutenberg becomes available.
So, do I recommend updating to Gutenberg 5.0?
Sorry. I mean HELL no.
Instead, I rushed to upgrade all my blogs to the latest version of WordPress 4.9.8.
And to make sure it does not auto install on my sites, I disabled automatic updates by adding this line of code in my wp-config.php file:
define( 'WP_AUTO_UPDATE_CORE', true );
Note: This turns off all automatic installs – including less risky minor updates…
Using this code automatically blocks major updates… but allows automatic installs of minor updates:
define( 'WP_AUTO_UPDATE_CORE', 'minor' );
If your site has Gutenberg installed (and want to downgrade to version 4.9.8), watch this video tutorial:
Here are all the WordPress release archives on one page.
Here is the problem:
WordPress promised to make Gutenberg version 5.0 available “sometime in 2018”. And now that 2018 is coming to a close, it seems like they are rushing it out to meet some self-imposed deadline.
The reviews of beta WordPress Gutenberg 5.0 are TERRIBLE. Those who have been testing it out have rated it a 2.8 out of 5.0. Those testing it out in this discussion forum are reporting lots of problems. There are a whopping 251 unresolved bugs and issues showing right now!
Most people testing Gutenberg report the editor is “laggy” and slow.
The other issue is 3rd-party plugin developers were not given much notice about this pending major update. So their plugins might conflict with this new WordPress update – rendering our blogs invisible.
Clearly, WordPress update Gutenberg 5.0 is not ready for prime time. And I can see hundreds of thousands of bloggers complaining about this over the coming weeks.
Like any major software update, I plan to wait until version x.1. So in this case, I will take a look at WordPress Gutenberg when it reaches version 5.1.