WordPress 5.0 with Gutenberg Editor was finally released on December 6th, 2018. We’re not going to judge if the new editor is the right move for WordPress and its users – site owners will soon make that judgment call – but we are going to discuss how Olibro, as an agency, dealt with the upgrade.
Some suggest it is too early to make the change and one should wait for a more stable version such as 5.1 and beyond. But we like to keep our websites current with the latest versions of all software modules if they don’t break the site.
For site editors, however, there is a learning curve with Gutenberg as opposed to the classic editor. For this reason, we installed WordPress’ Classic Editor plugin and activated it so that those who update their site’s content can use the familiar interface until they feel comfortable switching to the new editor.
We devised a process the upgrade our websites as follows:
- Copy the site over to a staging site and upgrade the WordPress and all plugins.
- If there are no errors, upgrade the production site and test. If there are errors and fixes are simple, fix the code, test, and upgrade the production site.
- If there are errors and fixes are more substantial, provide clients with an estimate of what it takes before making any changes to the site.
An upgrade is a part of our Managed WordPress plans. But fixing major issues need clients’ approval before we can start. Step #3 will ensure there will be no surprises.