See what order to do your updates to avoid issues with upgrading to WordPress 5.3.
NOTE: If you have a specilaty theme that has its own functions plugin, or you have other speciality integrations, check with your designer/developer first before you do the updates. Follow their directions if they differ from those given below.
If you have issues after updates, leave a comment to let us know. I do not support individual themes and plugins, but the whole BlogAid village will want to know about any conflicts and fixes that any of us find.
Reported Issues So Far
See the issues that I’ve heard about.
Some site owners have reported getting a white screen if their Gutenberg plugin was active during the update. I updated a test site under this condition and had no issues. But, now that the Gutenberg plugin has updated again, my advice is to delete it first, then update to WP 5.3.
Some site owners have reported getting a white screen when using the Classic Editor plugin that was set to allow you to chose either Classic or Gutenberg editing on a post/page.
The TinyMCE Advanced plugin had a notice in the plugins repository that it could not be installed on a site running WP 5.2.4 or lower. It has been updated to only function on WP 5.3 and higher at this point.
This is why the order below reflects updating WP first, then your plugins, as others may have this same condition.
Some updates froze and/or locked the site into maintenance mode.
- For freezing, you may get this message:
“The authenticity of wordpress-5.3-new-bundled.zip could not be verified as no signature was found.” You may need to unlock the update, as it cannot do another attempt while in that state. There are plugins to help with this, including the Fix Another Update in Progress plugin. I had this happen on one site and after unlocking, I tried the update again and got the same message, but the update completed.
- If it locks into maintenance mode, you’ll need to remove that maintenance file from the host side, using something like File Manager, if you have control panel access.
Some folks have reported that the captions under images and videos are no longer center aligned. Hopefully this will be fixed in WP 5.3.1.
See the order of operations I recommend.
Take a full backup
See this Backup Checklist to ensure your backup includes everything you may need.
If you are using that plugin, update it first.
You will need to log into each child site and update the MainWP Child plugin too.
Delete the Gutenberg Plugin
If you are using it, delete it first.
There are multiple code changes in the core that your plugins may be dependent on.
During the update, I saw the notice below.
You may or may not see it.
After clicking the Update WordPress Database, I saw this notice. If you didn’t see the notice above, you will not see this one.
After clicking the Continue button I was taken to the splash page for what’s new in WP 5.3.
Do Initial Site Check
Check your site after the update to ensure all is well.
To check your site:
- Poke around the front side (as a visitor would see the stie) while logged in.
- Try to create a new page – this will ensure your editor works.
- Open the site in a new browser and poke around the front side.
READ: this post on the new process to use when updating with the WP Rollback plugin installed.
Check your site by the methods above.
Check Gutenberg Posts
Check a post where you have a feature that makes use of the Gutenberg plugin.
Purge All Cache
Ensure you get your
- Local caching plugin
- Cloudflare or other CDN
Do Deep Checks
Open your site in a new incognito window.
Poke all over it and ensure all functions work.
Log into your site and try to create a page and/or other functions you do while logged in.
Check Again Tomorrow
It could take a full 10 hours for all cache to deeply purge.
Check your site again the next day to ensure all is well.
The next time you attempt to log in, you may also see a notice asking you to verify that your admin email address is correct.
If it is not, click that it is anyway, so you can finish logging in.
And then go to your admin User and update the email to the correct one.
WP will send an email to the old address asking for confirmation, so be on the lookout for that and follow the steps to confirm it.
Be sure you delete the new TwentyTwenty theme that was added along with the update. It’s just one more security hole you don’t need.