How to Restore WordPress After a Failed Update
Comprehensive guide to safely restoring WordPress after failed updates. Learn backup strategies, manual recovery via FTP/phpMyAdmin, plugin-based restoration, and prevention techniques.
I am Mariusz Szatkowski, a sole proprietor working from Gdynia, Poland. I have no office in Bristol. I fix bugs on existing WordPress sites and move them to a new host, a new domain or a newer PHP version, remotely, by email and shared documents. I reply within 48 hours. My business address is ul. Starowiejska 16/2, 81-356 Gdynia.
Poland is one hour ahead of the UK all year, because both change their clocks on the same Sundays. A message you send at 9:00 in Bristol arrives at 10:00 with me.
My credentials are public. I joined wordpress.org in 2006 and contributed to core in WordPress 7.0 and 7.1. I look after 30 plugins in the wordpress.org directory, organise and speak at WordCamps, and have been to every WordCamp Europe from 2017 to 2026.
Typical requests: a contact form that stopped sending mail, a white screen after an update, a checkout that fails on one payment method, a menu broken on phones, a plugin conflict that appeared with a new PHP version, a login loop, a 500 error after a host change.
A bug in a plugin I did not write is reported to its author with a reproduction, and I give you a workaround meanwhile. Code that nobody maintains any more goes into the note, so you can decide whether to replace it.
Migration here means moving a site that already exists. It is one of three jobs, and each fails in a different place.
| Job | What I check first | Where it usually breaks |
|---|---|---|
| New host | PHP and database versions on both sides, file size, cron jobs, mail sending | Serialized data in the database, hard-coded paths, outgoing mail |
| New domain | Every internal URL, redirects from the old address, canonical tags, sitemap | Mixed content, lost redirects, forms that post to the old domain |
| PHP upgrade | Plugin and theme compatibility on staging, deprecation notices in the log | An unmaintained plugin that stops the whole upgrade |
Before the move I take a full backup and restore it on staging to prove it works. DNS is switched only after you approve the staging copy in writing. The old host stays untouched until the new site has run cleanly for an agreed period, so there is a way back.
PHP 8.2 receives security fixes until 31 December 2026, 8.3 until 31 December 2027 and 8.4 until 31 December 2028, according to the table on php.net. PHP 8.1 no longer appears in the list of supported branches. WordPress itself recommends PHP 8.3 or greater, with MariaDB 10.11 or MySQL 8.0 or newer and HTTPS.
If your Bristol host still runs 8.1 or older, the upgrade is a bug-fixing job in disguise: old plugins throw warnings on newer PHP, and each one is a small fault to fix or replace. On a site running 8.2, the date above is seven weeks away at the time of writing.
A hosting company stores your form entries, orders and user accounts, so for UK GDPR it normally acts as your processor. Article 28 says a controller must use only processors providing sufficient guarantees, that processing is governed by a written contract, and that a processor may not engage another processor without the controller’s written authorisation (Article 28, legislation.gov.uk).
In practice, a host move means a new contract. I ask for the new host’s data processing terms before the migration starts and pass them to you. Whether those terms are enough is a decision for you and your adviser. Where the staging copy lives and who has access to it during the move go into the migration note.
I handle personal data in your admin area during this work. We agree in writing who gives me access, how, and when it is removed.
The Cyber Security Breaches Survey 2025 found that 43% of UK businesses had identified a breach or attack in the previous 12 months, and that 32% had a policy to apply software security updates within 14 days (Cyber Security Breaches Survey 2025). The survey covers the whole UK and gives no Bristol figure.
A bug fix often exposes an outdated component. If I find a plugin with a known vulnerability while chasing your fault, it goes at the top of the note, ahead of the fix you asked for.
I do not do graphic design, UX, mockups or wireframes. If the migration is the moment you want a new look, you or your designer bring the design as a Figma file or a wireframe. I then build it as a fast, accessible WordPress site, scoped and agreed separately from the move.
I do not run hosting and I am not a legal adviser. I work with the host you choose.
I do not offer calls or meetings. Decisions and handover notes are documents.
For ongoing care after the fix, see WordPress website maintenance and WordPress update service. A site that was hacked needs WordPress malware removal first. Slow pages are covered on speed up WordPress, and new builds under WordPress developer in Bristol. Stores are on WooCommerce developer in Bristol. How contracts, invoicing and VAT work for UK and Irish clients is on software development for the UK and Ireland.
Yes. I start from the error log and a staging copy, and the first note lists the plugins and code with no owner.
The live site keeps running on the old host until the new copy is approved. DNS is switched after that, and a short overlap while records propagate is normal. I do not promise zero seconds of difference.
No. I work with the host and registrar you already use, or the ones you choose.
No. I do not do graphic design, UX or mockups. A Figma file or a wireframe from you or your designer is the starting point, and I build it.
Email the site address, what is broken or where it is moving from and to, the PHP version if you know it, and what changed last. I reply within 48 hours with a written next step.
Examples of my work.
In the eastern part of Mielno, an exclusive apartment complex by the Baltic Sea, DUNE Resort, is being developed. This exceptional investment evokes the lu...
Instytut-csr.net is one of the valuable projects in my WordPress developer portfolio, realised as an educational and informational platform dedicated to Corp...
Neolight.pl is an advanced project in my portfolio as a WordPress developer, realised as an advertising portal supporting LED screen campaigns in Poland. Aro...
Describe your project by e-mail. I reply within 48 hours.
Describe your projectComprehensive guide to safely restoring WordPress after failed updates. Learn backup strategies, manual recovery via FTP/phpMyAdmin, plugin-based restoration, and prevention techniques.
WordPress.org has cut the mandatory update cooldown from 24 hours to six, with work underway to skip it entirely when the Gandalf AI review finds no issues. What changed, and what agencies maintaining B2B sites should do about it.
Update crashed your site? Don't panic. See 3 proven ways to rollback WordPress core, plugins, or themes to a previous version.
CrUX field-data audit with per-template LCP, INP, CLS attribution.
Core Web Vitals, caching, and faster delivery.
A free check of your site's public version, results on screen.
Stability, updates, and post-launch support.
Updates checked before release, with a report.
Migration to Astro, Next.js, and headless WordPress.
Audit, hardening, and incident risk reduction.

How to optimize Interaction to Next Paint (INP) on WordPress sites. Practical fixes for the newest Core Web Vital metric that directly impacts Google rankings.

Field versus lab, LCP, INP and CLS for WordPress in 2026. Google's green LCP is still 2.5 s in CrUX. 100/100 in Lighthouse is a lab target. Edge HTML, consent banners, checkout widgets.

How we took a slow WooCommerce site from score 45 to 100. A technical deep dive into Speculation Rules, AVIF, and Critical CSS in 2026.