Skip to main content

Case Study

Updating an Out-of-Date WordPress Site Without Breaking It

An illustrative composite of how we bring an out-of-date WordPress site onto supported versions, rehearsed on a private copy before the live site.

Alex

Alex

CEO

November 3, 2026
Industry Case Study
Focus Custom Development
Year 2026
Published November 3, 2026

At a glance

The problem
A WordPress site had fallen behind on its core software, plugins and PHP, and every update looked like a risk to the live site.
Systems touched
The live WordPress site with its theme and plugins, plus the domain's DNS and the email routed through it.
What we built
A rehearsed update on a private copy made safe first, with a before-and-after check of every page and code fixes for the newer PHP, then the same steps repeated on the live site.
What changed
The site runs on supported versions and visitors get the same pages as before, so the next update is a routine job.

An illustrative composite rather than one named client's results, so it carries no outcome figures.

This page is an illustrative composite. It draws on update and domain work we have done on real WordPress sites, with every client detail removed, so it shows how the work runs and carries no outcome figures.

The Challenge

The site worked, so it had been left alone. WordPress itself was a major version behind and the plugins screen had a long list of pending updates. One premium plugin couldn’t update at all, because its licence was no longer connected to the site. The theme had been written for an older version of PHP, the language WordPress runs on, and that version was heading towards the end of its support.

Some of the waiting updates were big ones. A forms plugin was a major version behind, and a jump like that can change how forms behave. Nobody could say for certain what else in the theme would object to a newer PHP version until it was tried.

Leaving it alone doesn’t make the problem smaller. Each update that’s put off makes the next one bigger, and the faults an update can cause are the ones nobody notices until a customer does: a form that stops sending, or a page that shows yesterday’s content.

The Approach

Nothing changed on the live site until the whole update had been rehearsed on a copy. We cloned the site to a private, password-protected address on the server and made the copy safe before doing anything else. Outgoing email was switched off, anything that takes payments was put into test mode, scheduled tasks were stopped and search engines were told to stay away.

Before the first update we recorded a baseline: every page address on the site with its response and its size, plus the warnings the code produces with debugging switched on. After each change we ran the same check and compared the two. A matching record meant the change was safe, and where something differed, the comparison showed which page to look at.

The changes went in one at a time. WordPress and the plugins were updated first, still on the old PHP version, and checked against the baseline. Then we took the baseline again, so the PHP change was measured on its own. The theme needed a handful of small code fixes for the newer PHP, mostly function calls the new version flags as deprecated. We fixed them by writing in the values the code was already using, so every page behaves as it did before. An update is the wrong moment to change how anything works.

Background jobs got their own check. Scheduled tasks set up through the hosting panel follow the site to the new PHP version. Ones added by hand on the server don’t, so each was found and pointed at the new version. After the switch we cleared the site’s page cache before the server’s cache, then checked the pages as a logged-out visitor sees them, including listing pages compared against a fresh copy.

When the update comes with a move to new hosting, the domain is the other place things go wrong. Every DNS record is exported and saved before anything is changed, and the email records are left exactly as they were, so mail keeps arriving. Before the domain is pointed somewhere new, the old DNS is made to match the new setup, because some internet providers keep the old answer for days. An old IPv6 address is a common trap: browsers that support it prefer it, and can keep reaching the old host after everyone else has moved.

Once the copy passed, the same steps ran on the live site in the same order, with a full backup of the files and database taken first.

What Was Delivered

  • A private, made-safe copy of the site where the full update was rehearsed before the live site was touched
  • WordPress and its plugins on current versions, with forms tested end to end after the major forms update
  • Theme code fixed for the newer PHP version without changing what any page does
  • A before-and-after comparison of every page address, run on the copy and again on the live site
  • Background jobs found and moved to the new PHP version, including any set up by hand on the server
  • DNS records saved before any domain change, with email records left in place
  • Full backups of the files and database kept from before the change

The Result

The site runs on supported versions of WordPress and PHP, and its plugins are current. Visitors get the same pages they got before: the before-and-after comparison is how that was checked, page by page, rather than assumed. Forms reach the inbox and email carried on arriving through the change.

The other change is for whoever looks after the site. With a baseline, a rehearsal copy and a known order of steps, the next update can happen while the gap is still small.

What Made This Work

Measuring the PHP change on its own. If WordPress, the plugins and PHP all change at once and a page breaks, there’s no way to tell which change caused it, and the quickest fix is usually to roll the lot back. Taking the baseline again after the plugin updates meant the PHP switch was compared against a site that already had them. Any difference after that could only have come from PHP, so there was one place to look for each.

Is Your WordPress Site Behind on Updates?

If your site is with another provider, switching website provider to us includes bringing it onto supported versions of WordPress and the server software, with a bigger update quoted before work starts. The £750 switching credit is one free day of our development, worth £750 +VAT. Ongoing updates sit under a support retainer, and our page on old WordPress systems covers the wider picture. Browse Case Studies for other builds, including the WordPress Growth Automation System, or get in touch to talk about your site.

Written by

Alex

CEO

I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.