Updates fix security holes and bugs, but they can also break a live website. A plugin conflict can disable a checkout page, a theme update can shift a layout and a new PHP version can expose old code that no longer works. Skipping updates is not the answer, because unpatched software is a common way in for attackers. The answer is a repeatable process that lets you update with confidence. This guide walks through that process in the order a careful developer would follow, and it fits alongside our article on the non-negotiables of maintenance.
Before You Touch Anything
Start by taking a fresh, complete backup of both files and database, and confirm you can access it; see backup and disaster recovery. Read the release notes for each update to learn what changes and what is removed. Check that your theme, plugins and custom code are compatible with the new version, and note the PHP version currently in use, because PHP branches reach end of support on fixed dates. Choose a quiet time of day rather than a sales peak, and tell your team that an update is planned. For a business-critical site, write down the exact steps and keep them with the change log, so that a colleague could repeat them if you are unavailable. If you run a shop, pause promotions that depend on the site working perfectly that hour.
Test on Staging First
A staging site is a private copy of your website where changes can fail safely. Our guide to the staging environment explains how to set one up. Make sure staging cannot send real customer emails or take real payments, and block search engines from indexing it. Then update in a sensible order: core CMS first, then plugins and themes, then any PHP version change, ideally one item or a small group at a time. Changing everything at once makes it almost impossible to tell which update caused a fault. Turn on error monitoring so problems are recorded rather than guessed at.
What to Test
Work through the pages and functions that make money or protect trust. Check the homepage, main landing pages, navigation menus and site search. Submit every form and confirm the notification email arrives. Log in and out of member areas, and run a full test purchase in payment test mode. If your website has English and Chinese versions, switch languages on several pages. Look for visual changes on a phone as well as a desktop, since emulators are not enough. Check tracking too: confirm that analytics and conversion tags still fire, because a broken tag can quietly erase your marketing data. Finally, open the browser console and server log for new warnings, which can reveal deprecated code long before it fails.
Go Live and Keep Watching
When staging passes, repeat the same steps on the live site, again taking a backup first. Repeat your key tests immediately, then watch uptime alerts and logs closely for the next day or two. Some faults appear only under real traffic or when a scheduled task runs overnight. Keep a short change log with the date, versions and who did the work, so that any later problem can be traced quickly. Our team describes a disciplined approach to fixes in from bug to breakthrough.
Rolling Back and Hard Cases
Decide in advance what counts as a failure and who can approve a rollback. A rollback usually means restoring the backup taken before the update, or reinstalling the previous version of the affected plugin. Practise it so that it takes minutes, not hours. The harder case is an abandoned plugin or theme that will not work with a newer version. Replace it, rebuild the feature or move to custom code rather than leaving it in place, a risk explained in why modern websites age poorly. Custom code written years ago may also need small changes to run on a current PHP version, and a developer can review it before the old branch loses support. After a successful update, schedule the next one rather than waiting for a security notice to force your hand, because regular small updates are far easier to test than one large jump across several versions.
Safe updates are a core part of what ANGLIA does for clients, from staging copies to monitored releases. If your site is overdue for updates and you are nervous about touching it, our contact page is the quickest way to ask for help, and our system development team can also review custom code.






