Plugin, Theme & Core File Updates

Updates that never break your website

Core, plugins, themes and PHP kept current by engineers who rehearse the whole thing on a staging copy first. You get the security and speed of an up to date site without ever gambling with the one that earns you money.

downtime in update windows
h
to patch a critical security flaw
%
rehearsed in staging first
PHP 8.3 ready
Visual QA Passed
Stacks we keep current
WordPressWooCommerceElementorDiviShopifyWebflowPHP 8.3Gravity FormsWordPressWooCommerceElementorDiviShopifyWebflowPHP 8.3Gravity FormsWordPressWooCommerceElementorDiviShopifyWebflowPHP 8.3Gravity Forms
Why site owners call us

The update notification nobody wants to click

Four things we hear from teams sitting on a pile of pending versions, and how a proper update routine settles each one for good.

Wide Open Doors

We are months behind and it keeps us up at night.

Fixed: vulnerabilities patched on a visible schedule.

Fear Of Pressing Update

Last time we updated, the layout fell apart.

Fixed: every version rehearsed on a clone first.

Things Failing Quietly

Our form stopped sending and a customer told us.

Fixed: checkout, forms and logins tested by hand.

A Backlog And No Time

Ninety updates pending and nobody wants to click.

Fixed: backlog cleared, then held at zero monthly.
How we handle it

Treated like an engineering job, never a gamble

Most sites get updated by pressing the blue button and hoping. We map compatibility, rehearse the release on a clone, prove it works, and keep a restore point ready the whole time.

Staging First, Always

Nothing reaches your visitors until it has proven itself.

The pain

Every update on the live site feels like tossing a coin.

How we fix it: A synced clone of your site takes the update first, so every surprise happens somewhere harmless and gets solved before deployment.

Compatibility Mapping

Core, PHP and plugin versions checked against each other.

The pain

Nobody warned us the new PHP version would take the whole site down.

How we fix it: We map how core, PHP and every extension depend on one another, then sequence the updates so nothing lands out of order.

Rollback Ready

A restore point sitting behind every single change.

The pain

The automatic update broke us and the newest backup was three weeks old.

How we fix it: A full file and database snapshot is taken before every window, so returning to the last known good version is a two minute job.

What we look after

From core files to the last page builder widget

Six areas of your stack, all covered by the same team, so a core release, a plugin patch and a theme upgrade never fight each other again.

CMS Core Updates

WordPress, Shopify and Webflow app cores brought current, with major and minor releases planned rather than pounced on.

Major releasesMinor patchesRelease planning

PHP & Server Compatibility

PHP upgrades, server side adjustments, database schema updates and the deprecated code that trips them all up.

PHP upgradesSchema updatesDeprecated code

Plugin & Extension Updates

Third party plugins and extensions updated in a safe order, with conflicts debugged and dead weight removed as we go.

Extension updatesConflict debuggingPlugin cleanup

Licence & Vulnerability Audits

Premium licences tracked and renewed on time, plus regular sweeps for abandoned plugins and published security advisories.

Licence trackingAbandoned pluginsSecurity advisories

Theme & Builder Care

Parent and child themes, plus Elementor, Divi and other builder frameworks, updated without losing your custom template work.

Child themesBuilder frameworksTemplate checks

Layout & Responsive Fixes

Custom CSS verified, mobile behaviour rechecked and any typography or interface regression repaired before you ever see it.

Custom CSSMobile checksRegression repair
The safe path to live

Three gates every version has to pass

A snapshot before anything moves, a full rehearsal on a clone, then a quiet deployment with someone watching. Your visitors only ever meet software that has already been proven.

GATE 01 / BEFORE ANYTHING MOVES

Snapshot and clone

A full copy of files and database is taken, then your live site is mirrored into a private staging environment nobody else can reach.

  • Full site and database backup
  • Staging environment deployment
GATE 02 / INSIDE THE SANDBOX

Update, then prove it

Core, plugins and themes are applied on the clone and put through visual and functional testing until the whole thing behaves.

  • Visual regression testing
  • Critical path QA on checkout and forms
GATE 03 / ON THE LIVE SITE

Deploy quietly, verify loudly

Approved changes go out in your calmest hour, caches are cleared, and a person walks the real site before we call it finished.

  • Scheduled low traffic deployment
  • Live QA and speed verification
Testing, QA & safety systems

The safety net under every release

Confidence comes from having somewhere to fall. Snapshots, sandboxes and hands on testing are what let us move quickly on patches without ever betting your revenue on them.

Snapshots & Restore

Files and database captured before a single version changes, held off site, and restorable in minutes if a release misbehaves.

Full site snapshotDatabase dumpRestore in minutes

Sandbox Rehearsal

A private clone of your site takes every update first, so the messy part of any release happens where it cannot cost you a customer.

Synced cloneSandbox runsApproval before live

Regression & Path Testing

Screens compared before and after, then the paths that actually make money walked by hand across phones, tablets and desktops.

Visual regressionCheckout and formsDevices and browsers
downtime in update windows
h
to patch a critical security flaw
min
to restore if anything slips
%
rehearsed in staging first
How we work together

Your first window, then a rhythm you can forget about

Steps 1 to 5 clear the backlog. Step 6 keeps it at zero.
1
Access & audit

Credentials handed over, then a full read of site health, PHP and every pending version.

2
Snapshot & clone

Complete file and database backup, then a synced copy of your site spun up.

3
Update the clone

Core, plugins and themes applied in a safe order, conflicts solved as they appear.

4
Prove it works

Visual checks across devices plus hands on QA on checkout, forms and logins.

5
Quiet deployment

Approved changes pushed during your calmest hours, caches cleared, speed verified.

6
Log & repeat

Version log, health note and your slot in next month booked before we leave.

Reporting & the monthly queue

A site that quietly stays current

Every month your site joins a booked update window. You get the version log, the QA result and a short health note, so you always know what changed and why nothing broke.

See what a maintenance retainer covers
Update Log · This Month
All current
Versions applied
27
Pending
0
A monthly window booked in advance
A version log of everything that changed
Speed and health checked after each deploy
A named engineer who actually replies
Selected work

Backlogs cleared, nothing else touched

Three sites that were badly behind, and what happened once someone took the updates seriously.

WordPress core update work for Marlow & FinchWordPress core
Marlow & Finch

Two years of skipped versions cleared in one weekend

Challenge: An unsupported PHP version, ninety two pending updates and a team that had stopped opening the dashboard.

versions brought current
minutes of downtime
s
faster page load
WooCommerce update work for Hartley SupplyWooCommerce
Hartley Supply

A checkout that now survives every release

Challenge: A payment plugin had silently stopped working twice after routine updates, and customers were the ones who noticed.

%
orders protected since
h
patch turnaround
silent failures
Page builder upgrade for Studio NinefoldPage builder
Studio Ninefold

A builder upgrade with not one layout wobble

Challenge: A theme framework release had previously wrecked custom CSS across forty landing pages, so nobody dared upgrade again.

pages verified by hand
layout regressions
h
total update window
FAQs

Frequently Asked Questions

That is exactly what the staging copy is for. Every version lands on a clone of your site first, gets checked page by page, and only reaches your visitors once it has behaved itself. If something does go sideways on the clone, we solve it there while your live site carries on earning.

Find out exactly how far behind you are

Send us access and we will send back a plain list of every pending core, plugin and theme version, which ones are risky, which are abandoned, and what we would update first. No pitch, no jargon.

Response within one business day · No obligation