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.
My name is Mariusz Szatkowski and I work from Gdynia, Poland. I have no office in London. I maintain and support WordPress sites for London businesses remotely, by email and shared documents, and 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 follow the same last-Sunday clock changes. A message you send at 9:00 London time lands at 10:00 with me.
I have had a wordpress.org account since 2006, contributed to WordPress core for versions 7.0 and 7.1, maintain 30 plugins on wordpress.org, organise and speak at WordCamps, and have attended every WordCamp Europe from 2017 to 2026.
A site that nobody touches for six months is not stable, it is unpatched. Maintenance means a named person keeps WordPress core, plugins, theme and PHP current, and can say what changed.
The report is the part clients tell me they never had from an earlier provider. It also answers the question an auditor or a board member asks: who changed the site, and when.
Care plans and their prices sit on the WordPress maintenance cost page. The general service description is on WordPress website maintenance.
Yes, and this is the most common start. An agency finishes a build, the retainer lapses, and the site drifts. I ask for admin access and hosting access, then write down the WordPress and PHP versions, the plugin list with last release dates, whether the backups restore, and which plugins nobody maintains any more.
You get that as a document before any change is made. Where a plugin is abandoned I name a replacement or a way to remove it, and you decide. I do not touch hosting contracts or DNS without your written approval.
The Cyber Security Breaches Survey 2025, published by the UK government on 10 April 2025 from fieldwork between August and December 2024, found that 43% of businesses had identified a cyber security 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 is UK wide and has no London-only figure in what I read.
For WordPress, the 14-day figure is a useful internal target: a security release of a plugin gets tested on staging and shipped inside that window, faster when the flaw is already exploited.
If you are working towards Cyber Essentials, the National Cyber Security Centre lists security update management as one of its controls, aimed at stopping attackers using known software vulnerabilities as an entry point (NCSC Cyber Essentials overview). Tell me at the start. I keep a dated log of every update, which your assessor can use as evidence. What is in the scope of your certificate is for you and your assessor to decide.
Article 32 of the UK GDPR requires technical and organisational measures suited to the risk, including a process for regularly testing, assessing and evaluating how effective they are (Article 32). A scheduled update cycle with a report is one such process for a WordPress site that stores form entries, orders or user accounts.
Article 33 gives a controller 72 hours from becoming aware of a personal data breach to notify the regulator, unless the breach is unlikely to result in a risk to people (Article 33). Whether you must report is a decision for you and your adviser. My part is to make the facts quick to find: the update log, the backup history and who had admin access.
Maintenance work brings me close to personal data in the admin area. Before I start we agree in writing who has access, how it is shared and when it is removed. Whether I count as your processor is a legal question I leave to you and your adviser.
Cookies follow the Privacy and Electronic Communications Regulations. Section 112 of the Data (Use and Access) Act 2025 replaced regulation 6 and added Schedule A1 with exceptions to the consent rule (section 112), and the remaining provisions came into force on 5 February 2026 (S.I. 2026/82). A plugin update can change what a consent tool or analytics script loads. So after each cycle I check what loads before and after consent on staging.
Graphic design, UX, mockups and wireframes are outside what I offer. If you want a new look for the site, you or your designer provide the design as a Figma file or a wireframe, and I build it as a working, fast, accessible WordPress site. That is a separate piece of work with its own written scope.
I do not run hosting, and I am not a legal adviser. I work with the host you already use and I leave legal bases and contracts to you and your lawyer.
I do not offer calls or meetings. Decisions, quotes and handover notes are documents you can forward to a colleague or keep in your records.
If the problem is a security incident on a hacked site, start with a WordPress security audit. Stores run on WooCommerce have their own page, WooCommerce developer in London, and new builds are covered under WordPress developer in London. For the wider UK and Ireland scope see software, AI and WordPress development for UK and Irish businesses.
No. I work from Gdynia, Poland, as a sole proprietorship. Communication is email and shared documents, with a reply within 48 hours.
Yes. I start with an inventory of plugins, theme, PHP version and backups, then send a written scope. Code that has no owner or no updates is listed in the first report.
No. I work with the host you already use. If the host is the weak point, I say so in the report and describe what to ask them for.
No. Graphic design, UX and mockups are outside what I offer. If you or your designer provide a Figma file or a wireframe, I build it as a working, fast, accessible WordPress site, quoted as a separate piece of work.
Write through the contact form with the site address, the problem or the date a previous provider stopped, and who approves work on your side. I read it and reply in writing within 48 hours.
Examples of my work.
led-lumina.pl is a professional online store that presents a comprehensive range of innovative LED solutions for both individual and business customers. The ...
like2slide.com is a website for the ski, snowboard, and wakeboard community, built for inspiration, publishing, and stable operation.
marcoaldany.pl is a WordPress website built to present personalised services to show how this system can support companies offering personalised services or...
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.