Tarun Gupta

Migrating to WordPress 5.0? Key Things to Remember

Tarun Gupta December 17th, 2018 Web Development no comments.

WordPress is here with its latest version, WordPress 5.0. Like previous updates, WordPress has left no stone unturned to make the migration seamless and smooth. However, there have been issues raised by users citing glitches and errors while migrating to the latest version. If you haven’t yet updated to the WordPress 5.0, go through the following to have a smooth migration.


WordPress 5. Update Essentials

Update Your PHP Version:

WordPress runs using PHP programming language. It’s important that all the WordPress themes, plugins and associated third party tools should be compatible with the latest PHP version. Using an outdated PHP version may lead to compatibility issues and bad user experience. The last word- since WordPress 5.0 is made to run with latest version of PHP, update to the same without delay.

Update WordPress Themes and Plugins:

Before migrating to WordPress 5.0, update your outdated plugins to their latest versions. This is a requirement now. Most plugin authors have already started doing this. Incompatible plugins may create functional issues and could invite hacking or malware threats.

If New Editor Sucks, Revert to the Classic One:

WordPress 5.0 comes with latest Gutenberg editor that’s designed to offer awesome editing experience. If you think that it’s not worth checking, better to stick with the classic editor. There have been multiple reports suggesting ambiguities in the Gutenberg Editor. So, if the new editor is troubling you, you can switch back to the classic editor any time.

Create Website Backup:

If you own a WordPress website, it’s a good practice to back up your website on a regular basis. If you’re not attentive to this point, start doing it right now. Now, as you’re heading to WordPress 5.0, creating a backup is mandatory. It’s handy in case some errors occur during the migration and website starts behaving strangely.

  Node.js And io.js Merged Under The Name Node Foundation

Use Caching Plugins:

There are occasions when file instances rested in cache create havoc. Sometimes after upgrading to the new editor, some problems remain persistent. This happens due to caching problems. If switching to classic editor yields no fruit, emptying cache and minifying JavaScript files is the best option.

Stage the Website on Test Server:

Don’t run the WordPress 5.0 update on your live website. The ideal solution would be to stage site on any other server. This is to ensure that changes made on the copy will not slow down your website. To note, stage websites are hidden and not visible to search engines are their crawlers. All the change made to the websites would be reflected on the staged site only, instead of real website.


Upgrading to the next level is always a great choice. The only thing to keep in mind is a note of caution. Go to the upgrade with a plan and basic know how of caching related issues. You should also check out a guide showing the way to switch between classic and Gutenberg editors.


I hope this brief guide will help you having WordPress 5.0 update a fair and smooth ride. Have suggestions / comments? Please write through the comment box below.


(Featured Image Credit: Siteground)


Comments are closed.