WordPress 5.0 is here! If you’re a WordPress Content Manager with not that much of a technical background, this post is for you!
After several months of speculation, we finally know exactly what WP 5.0 looks like. We had tested, and reported on what we thought would happen, for sure, and even called our web hosts to see when they’d update their Managed WordPress core to WP 5.0.
We feel we’ve prepared better than any other agency that builds WordPress sites, mainly because we boast the value and speed related to a drag and drop theme based website, and we’re more than okay with admitting that.
Of course we write custom themes, and custom plug-ins, when needed, and when our clients have the budget for it, assuming it makes complete business sense for them.
But here’s the deal, our #1 superstar theme, Enfold, by Kriesi, had a huge patch needed in order to be compatible with Gutenberg.
The long story is described here.
But the real reason for this blog is to let you know that if you’re running the Enfold Theme on WordPress 5.0, you’ll need to do one of two things.
1. Upgrade to Enfold 4.5.1 (which you’ll need to do via FTP), because the ThemeForest / Envato API key doesn’t work anymore. You have to get a new key to upgrade from Enfold 4.5 to 4.5.1, and your old key won’t work to get you from any previous version up to 4.5 or 4.5.1. Sorry, and (enter sarcasm now), thanks ThemeForest/Envato Market.
2. OR, since #1 is a pain in the butt right now, install the “Disable Gutenberg” Plug-in.
I spent my entire night and morning today installing this plug-in into 66 websites. Why?
Because GoDaddy Managed WordPress, which I love, autoupdated the core of all of our clients’ websites to WP 5.0 overnight, making all Enfold sites’ Avia Layout Builder Editor look like this…
A Gutenberg / Block editor MESS!
So, after installing the Disable Gutenberg Plug-in, I was able to get the Avia Layout Builder reloaded properly and update content properly.
I highly recommend this solution as an immediate stop gap for any WordPress non-technical content manager using Enfold or any other drag and drop editor with WP 5.0.
I know it works with Enfold, and if you’re wondering what happens to a site on 4.9.8 that is about to be auto-updated to WP 5.0, I tested this and it works: install the Disable Gutenberg plug-in NOW and it will ensure your Enfold Avia Layout Builder pages stay compatible with WP 5.0 AFTER the upgrade, while not affecting your site prior to the upgrade.
This way, you get the best of all worlds. The new WP 5.0 Core Update, and the efficiency of your Enfold site.