Updating WordPress is essential to keeping your site functional and secure, but updates can interfere with customizations or even break your site.
That’s why, in this post, we cover the five considerations you should bear in mind when it comes to installing WordPress updates. Follow these and you’ll be able to update every time without harming your site’s functionality!
1. Back Up Your Site Regularly (and Before Updating Anything)
To avoid any worry of an update harming your site, make sure to back up your site before you install any updates. You’re spoilt for choice with options on this front.
If you’re looking for perhaps the quickest and easiest solution, our first recommendation would be VaultPress. Developed by none other than the folks at Automattic, it’s a slick and full-featured premium remote backup solution that’s a cinch to setup and use.
Speaking of remote backup solutions, that’s the only type we recommend. There’s little point in backing up to your server if some kind of fatal error destroys both your site and its backup(s). If you’re a Dropbox fan, check out our recommended compatible backup solutions.
There are plenty of other solutions – both free and premium – and we’ve featured the most popular here. And in the interests of completeness, if you feel the need to carry out a manual backup at any time, the WordPress Codex has you covered.
2. Use WP Safe Updates to Test Plugin Updates
Because of the myriad combinations of developers, version compatibilities, and quality control, plugins are often the source of update conflicts.
Fortunately, developer Antti Kuosmanen has created a new plugin called WP Safe Updates that lets you test plugin updates in a ‘sandbox’ environment. This enables you to spot potential update conflicts before they have the chance to be an issue on your live site.
According to the plugin’s WordPress.org description:
The sandbox works similarly to how WordPress multisite works. We tell WordPress to temporarily use a different database prefix and a different plugins directory while in the alternative heap (sandbox).
In practice, WP Safe Updates adds a new Test Update button that appears when a plugin update is available. Clicking this button lets you preview any changes the plugin makes before committing to them. WP Safe Updates will show exactly how the updates will behave on your actual site when you do things like creating new posts or changing settings.
Please note that installing WP Safe Updates requires editing a small amount of your site’s code – instructions for which are available in the Installation section of the plugin’s WordPress.org Plugin Directory page.
While WP Safe Updates is a promising solution to a common WordPress updates frustration, you should be aware that the plugin is still in its alpha version. As such, it may not be entirely reliable in its functionality. That being said, we do recommend WordPress Safe Updates to anyone concerned about plugin updates interfering with their site’s functionality.
3. Use a Child Theme
Arguably WordPress’ biggest selling point is its customizability via themes and plugins. However, with great power comes great responsibility, and when making tweaks to your site’s design, you must ensure that you do so responsibly.
It’s tempting to make customizations by editing your theme’s PHP or CSS files directly, but you should refrain from doing so for two reasons:
- There’s a danger of getting the dreaded “white screen of death” due to one misplaced bracket or semicolon.
- Changes you make to the original theme files are impermanent (i.e. updating your site’s theme will overwrite them).
To avoid both these problems, you should always use a child theme to customize any of your site’s code. Child themes are easy to create, and they enable you to experiment to your heart’s content.
4. Review Theme, Plugin, and Core Update Changelogs for Conflicts
Before you install any update, we advise that you read its changelog for potential conflicts. Keeping up to speed with what’s new in the latest version of any given theme, plugin, or core update is useful in and of itself, but beyond that, you’re looking for any changes that might interfere with your unique setup and customizations.
For instance, if you’re using custom CSS to modify the appearance of a plugin-generated contact form, you should make sure the update doesn’t change any of the CSS IDs or classes that your custom code uses.
Where to find the changelog will depend on what you’re updating.
For plugins downloaded from WordPress.org, the changelog is one of the available tabs on the plugin’s WordPress.org Plugin Directory page.
For themes, you should consult the theme developer’s website. For example, default WordPress themes such as Twenty Sixteen have their changelog available within the WordPress Codex. All quality themes – free or paid – should include a changelog.
For updates to WordPress core, a complete changelog of every version to date is available in the Codex.
Reviewing the changelog for potential conflicts is key to making sure that any WordPress updates go smoothly.
5. Never Test Updates on a Live Site
To ensure the user experience isn’t interrupted by an update gone wrong, you should never test updates on a live site. Following this simple rule will save you an awful lot of headaches over time.
There are several options for testing WordPress updates outside of your live site. The one you pick will depend on your hosting solution, your technical ability, and the magnitude of the update. Options include:
- Create a WordPress staging site through your web host. The exact details will depend on your hosting provider, but managed hosting solutions such as WP Engine, FlyWheel, and Pressable all make this possible.
- Test updates with a plugin such as WP Staging. A great option for those on shared hosting plans, WP Staging “creates a file clone of your website into a subfolder of your current WordPress installation with an entire copy of your database.” You can then use this clone to test any updates. If an update breaks the test site, your live site will remain unharmed.
- Test updates in a local development environment containing a carbon copy of your site. For more details, check out our guides to creating a local development environment on a Mac and in Windows.
Using any of the above options will enable you to test updates and iron out the kinks before going live. A staging site is my personal choice; for more information, check out our guide to creating a WordPress staging site.
It’s one thing understanding how important updating WordPress is, but having the confidence to install updates without the fear of potential conflicts arising is something else altogether. Fortunately, with this article, you have the solution.
Follow the simple rules below to ensure that WordPress updates on your live site(s) successfully every time:
- Back up your site regularly (and before updating).
- Test plugin updates with WP Safe Updates.
- Make all theme customizations in a child theme.
- Review update changelogs before applying them.
- Never test updates on a live site.
What advice do you have for applying WordPress updates safely? We’d love you to subscribe and share them in the comments section below!
Article thumbnail image created with elements by phoelixDE and notbad / shutterstock.com