WordPress 5.0 Upgrade – What You Should Know Before Upgrading

 

We have tried the WordPress 5.0 update against a scope of sites presently facilitated with Big Head, both more seasoned and fresher. In the wake of updating the product and ensuring the module for the "Exemplary" editorial manager is introduced, the sites proceeded true to form without any progressions required. 

On the off chance that your site is facilitated with Big Head and your facilitating bundle incorporates updates to the product to be performed by Big Head, kindly realize that we will continue forward with that update instantly. Our overall approach with such an update is to give the freshest variant a couple of days just in the event that any potential bugs are distinguished with the bigger delivery, and afterward playing out the overhauls as we go. 

In the event that you are wanting to do the update yourself, here are a couple of things you should know: 

1. Continuously play out a reinforcement of the site records and information base prior to playing out any updates to your site. While the update cycle has worked impeccably 99% of the time, this will give you simple protection against that 1% of the time there might be an issue. 
   
   
2. On the off chance that you are updating from WordPress 4.9.8, you may have seen a notice on the Dashboard about the new editorial manager coming, and been allowed a chance to add the Classic Editor. on the off chance that you have just done that, you will just need a couple little settings changes going ahead (see thing #5 in this rundown.) 
   
   
3. In the event that you have WooCommerce introduced on your site, note that the WooCommerce engineers have recommended unequivocally to refresh WooCommerce before moving up to WordPress 5.0 – it appears to be this request may forestall a potential information base clash. We played out our test update with WooCommerce first, and afterward WordPress, and things came easily, so you ought to be fine to follow that approach. 
   
   
4. When you are prepared to refresh to 5.0, and you have a reinforcement of your site, feel free to continue. When the update is finished, you will get an invite screen revealing to you about the new update. At the highest point of the page, there will be a notification to permit you to keep the Classic Editor on the off chance that you don't as of now have it introduced. We do recommend adding this for a consistent encounter and until you can decide whether there is any contention with your site's customizing and the new manager. 
   
   
5. With the Classic Editor introduced and enacted, you will be able to change to and fro on any post thing on the site. This can be valuable for testing; in any case, in the event that you might want to cripple this choice and simply hold the Classic Editor, you can roll out an improvement inside the site Settings, under Writing. You can set the default proofreader, and handicap the capacity for clients to switch the editorial manager. 
   
   
6. When done, return and test your site to guarantee everything is running true to form.