Sample work · Websites
WordPress updates with backup: broken update detected and rolled back
Backed up files and database on a test page before each update, applied updates individually and checked them; a faulty plugin update was detected and restored from the backup.
Sample work (demo), not a client job. Built as a trial task with invented example data; the check figures below come from the automatic test run and are not polished.
What was built
- Before each update, a backup of files and database is created, the archive is checked for readability
- Updates applied individually, then important pages and the error log checked
- A broken update (critical error) is immediately rolled back from the backup, the site runs as before
- Report with versions before/after and reason per rollback; site and plugin are fictitious
How it was checked
Automatic test run on 2026-10-31, taken from the log (test data invented, figures measured):
- Local maintenance run: backup (wp-content + DB, ZIP healthy) before each update, update 1.0.0->1.1.0 kept, broken 1.2.0 (Fatal, HTTP 500) detected and automatically rolled back, output identical afterwards, DB rollback proven, monthly report
- 13/13 checks green
Limits
What this sample does not cover, so nobody expects more:
- local with SQLite and php -S; at the customer's site the same process runs via WP-CLI over SSH/hosting console or with their hosting backup - this requires their access; the database is handled there with 'wp db ...'
- Updates offline from ZIP files; core updates and updates from wordpress.org were not pulled live
- checked are HTTP status and fatal error in the log per page; a visual error without a fatal error (shifted layout) additionally requires the rendered check (wp_theme_anpassen)
- Premium plugins require the customer's license key; no malware removal, no repair after a hack
Something like this for your business?
Describe briefly what you need. You get a fixed price before I start; nothing happens without your yes.