“WordPress 6.5 is now available” — and every time the same dilemma. Update and you risk a plugin conflict that turns the whole site into a white screen. Skip the update and someone will find a vulnerability in a month and hack the site. I’ve worked out how to update WordPress, plugins, the theme, and PHP without getting a 500 error or losing a weekend to repairs. Here’s a step-by-step checklist, WP-CLI commands, and instructions for non-technical site owners.
Why update WordPress — and why putting it off is risky
Updates aren’t just developer whims. They close real vulnerabilities that thousands of sites around the world get hit with every day. On the other hand, updating without preparation is a great way to break a working site yourself. The middle ground is simple: you have to update, but you have to do it properly.
What breaks when you DON’T update
The most common problem is a hack. Vulnerabilities in older versions of the core and plugins are public knowledge, ready-made exploits exist, and botnets constantly scan the internet for vulnerable sites. My site on WordPress got hacked — what to do is a separate article, but the simplest preventive step against this scenario is to keep everything up to date.
Besides security, old versions stop working with modern hosting. WordPress 5.x won’t run on PHP 8.2, which is now standard at most hosts. Old plugins stop supporting new core versions — a year later you’ll find that half your critical plugins no longer receive updates and show “not tested with your version of WordPress.”
What breaks when you update WITHOUT preparation
The other extreme is clicking “update everything” and going to make coffee. Five minutes later the site shows a white screen, a 500 error, or the “Briefly unavailable for scheduled maintenance” message. I’ll cover the exact causes in the troubleshooting section, but here are the usual suspects:
- One plugin updated for the new core, but another plugin hasn’t caught up yet — conflict
- The theme uses a function that’s deprecated in the new version — fatal error
- The update changed an API and custom code in functions.php stopped working
- A PHP extension required by the new plugin isn’t installed on the server
The solution isn’t choosing between “update” and “don’t update.” It’s following the right process: backup, staging site, one change at a time, with a check after each step.
What to Check BEFORE Updating — 7-Point Checklist
Most update failures aren’t surprises — they’re the result of skipping this checklist. All seven checks take about 30 minutes and greatly reduce the chance of ending up with a broken site.
PHP Version on Your Hosting — Is It Compatible with the New Core?
WordPress 6.x officially supports PHP 7.4 and higher, but recommends PHP 8.2 or 8.3. If your hosting is still running PHP 7.0 or 7.2, the core update may succeed, but plugins can start throwing errors. Check your current version in your hosting control panel or through WordPress Site Health.
Requirements and compatibility:
- PHP 7.4 — minimum, but outdated and gradually losing plugin support
- PHP 8.0–8.1 — solid option; most plugins support it
- PHP 8.2 — current standard, recommended for all new sites
- PHP 8.3 — latest version, but not all plugins are fully compatible yet
If your hosting won’t let you update to PHP 8.2+, it’s a sign you should move to a modern host. Most quality providers support the latest PHP versions out of the box.
Plugin and Theme Compatibility — Where to Look for “Tested up to”
In the WordPress plugin directory (wordpress.org/plugins/), every plugin page shows a “Tested up to: X.X” line. This is the latest core version the plugin has been officially tested with. If a plugin says “Tested up to: 6.2” and you’re updating the core to 6.5, you risk conflicts.
The easiest way to check everything at once is with the WP Compatibility Checker plugin or the built-in “Plugin and theme auto-updates” indicator in Site Health. Both flag each plugin’s compatibility and highlight potential problems.
Child Theme — Or Did You Edit functions.php Directly?
If you or a previous developer edited functions.php in the main theme instead of a child theme, updating the theme will overwrite those changes. Check it quickly:
# via SSH
diff -q wp-content/themes/your-theme/functions.php /tmp/original-functions.php
# or just check the file size — if it was modified, it will differ from the original
If changes exist in the main theme, do NOT update the theme yet. Move the edits to a child theme first. Otherwise you’ll lose everything after the update. I cover how to do this in the theme update section below.
Site Health — WordPress’s Built-in Diagnostic Tool
In wp-admin → Tools → Site Health, WordPress lists potential issues: outdated plugins, REST API problems, and suboptimal settings. Before updating, go through the red warnings and fix the critical ones.
Error Logs — Are There Existing Problems?
Open wp-content/debug.log (if WP_DEBUG_LOG is enabled) or your hosting error log. If PHP errors or warnings are already appearing, fix them first. Otherwise new errors after the update will mix with old ones and make troubleshooting harder.
Free Disk Space and Database Space
WordPress updates need temporary space for archives and backups. Allow at least 100 MB free. Check via SSH:
df -h ~
du -sh ~/public_html
Time for Rollback — Do You Have Hours to Fix Issues?
Golden rule: don’t update on Friday evening or right before a sale. If something breaks, you’ll be fixing it over the weekend. The best time is Monday or Tuesday morning when you have the whole day ahead. Ideally update early in the day when traffic is lowest.
I handle this as part of my monthly WordPress maintenance: scheduled backups, core/plugin/theme updates, error monitoring, and quick fixes. Care plan is $99/month.
Step 1 — Backup Before Updating
A backup isn’t optional — it’s mandatory. If something breaks during the update, the backup lets you restore the site to a working state in 5 minutes. Without a backup, you’ll either spend hours digging through someone else’s code or pay for urgent recovery.
What a Full Backup Includes
A complete WordPress backup has three parts:
- Core files, plugins, and theme — the
wp-content/folder and root PHP files (index.php,wp-load.php,wp-config.php, etc.) - MySQL database — all
wp_*tables with content, settings, and users - Configuration —
wp-config.phpwith database credentials and.htaccesswith server rules
Backing up only files or only the database isn’t enough. If a plugin update breaks a table structure, a files-only backup won’t help. If theme files change, you can’t roll back without them.
How to Back Up with UpdraftPlus in 5 Minutes
UpdraftPlus is the most popular backup plugin for WordPress. The free version is enough for most sites. Steps:
- Install the plugin:
Plugins → Add New → UpdraftPlus → Install → Activate - Open settings:
Settings → UpdraftPlus Backups - Go to the “Settings” tab and choose cloud storage (Google Drive, Dropbox, or another provider)
- Authorize the chosen cloud storage
- Return to the “Current Status” tab and click “Backup Now”
- In the dialog, select all three checkboxes: Database, Files, Send to remote storage
- Click “Backup Now” and wait 2–5 minutes
You’ll end up with four files in the cloud: backup_*-db.gz (database) and three backup_*-others/plugins/themes/uploads.zip files. Download them locally as well — one copy in the cloud and another on your own drive is safer.
Hosting Provider Backups
Most reputable hosting providers create automatic backups. Check your hosting control panel for a “Backups” section. For a critical update, create a manual backup through the panel right before updating — it will contain the freshest state.
Backup via WP-CLI
For those working through SSH:
# files
cd ~/public_html
tar -czf ~/backup-$(date +%Y%m%d).tar.gz wp-content wp-config.php .htaccess
# database
wp db export ~/db-$(date +%Y%m%d).sql --add-drop-table
Two-command backup. Copy both files locally or to the cloud with scp.
| Method | Free | Level | When to Choose |
|---|---|---|---|
| UpdraftPlus | Yes (basic) | Beginner | Standard backup from the dashboard — one click and done |
| WP Staging | Yes (Free) | Intermediate | When you need both a backup and a test copy for the update |
| Hosting provider backup | Often yes | Beginner | Regular automatic backups without using the dashboard |
| WP-CLI / SSH | Yes | Advanced | Scriptable backups for large sites and cron jobs |
Step 2 — Staging: Test the Update on a Copy First
A staging site is a full copy of your live site where you can update safely. If something breaks, recreate the staging copy from a fresh backup and continue testing. It’s the next level of insurance after a backup.
Creating a Staging Site with WP Staging
The WP Staging plugin creates a copy in a subfolder (for example, your-site.com/staging-001/) with one click. Steps:
- Install the WP Staging plugin from the repository
- Open
WP Staging → Sites/Startin the dashboard menu - Enter a site name (for example,
test-update) - Choose which folders and tables to clone (everything by default)
- Click “Start Cloning” — it takes 1–10 minutes depending on site size
The staging site is available at your-site.com/test-update/. Use the same login and password as the live site. Now you can update WordPress, plugins, or the theme — whatever happens, the live site stays safe.
Hosting Provider Staging
Some hosting providers include a built-in staging feature. If your host offers one, use it — it’s usually more reliable than a plugin (isolated database, separate user).
What to Test After Updating on Staging
Don’t assume “the site loads, so it works.” Go through this checklist:
- Home page — all blocks in place, images loading
- Internal pages (categories, services, contact)
- Product catalog and single product pages (for stores)
- Cart: add, remove, proceed to checkout
- Checkout and payment (test order with your host’s card)
- Contact form: submits and arrives in email
- Account area, registration, login (if present)
- REST API:
/wp-json/wp/v2/postsreturns JSON - Dashboard: create a post, edit settings, media library
If anything breaks on staging, do NOT update the live site. Fix the issue first.
Step 3 — Updating the WordPress Core
Once the backup is ready and the staging site shows everything works, you can update the core. WordPress offers three methods — choose based on your comfort level.
Updating from the admin dashboard — one click
The simplest route. In wp-admin → Dashboard → Updates you’ll see the button “Update to version X.X.X”. Click it, wait 1–2 minutes, and you’re done. WordPress automatically:
- Enables maintenance mode (creates a
.maintenancefile) - Downloads the new version from
downloads.wordpress.org - Unpacks and replaces the core files
- Updates the database schema if needed
- Removes
.maintenanceand brings the site back online
If the process is interrupted, the .maintenance file may remain and the site will show “Briefly unavailable for scheduled maintenance”. Fix: connect via FTP and delete the .maintenance file in the root folder.
Manual update via FTP/SFTP — when the dashboard is unavailable
If the dashboard is down after a failed update, do it manually:
- Download the latest WordPress from
wordpress.org/download/ - Unzip the archive locally
- Connect to the server with FileZilla (or via SFTP)
- Go to the site root (
public_html) - Upload all files and folders from the unzipped archive EXCEPT
wp-contentandwp-config.php— this replaces the core while keeping your content and settings - Do not touch
wp-config.php— it stays yours
Afterward, visit your-site.com/wp-admin/ — WordPress will prompt you to update the database; click the button. Done.
Updating via WP-CLI: wp core update
The fastest method for technical users. Via SSH:
# update core to the latest version
wp core update
# update with version check (you can specify a version)
wp core update --version=6.5
# update the database structure after the core
wp core update-db
# verify checksums
wp core verify-checksums
The command wp core update does exactly what the dashboard button does, just without the UI. Handy for cron scripts and bulk updates across multiple sites.
Step 4 — Updating Plugins Without Conflicts
Plugins are the main source of problems during updates. In my experience, most WordPress breakages happen at this stage, not with the core. Approach: one at a time, with checks, in priority order.
One at a time, not all at once — why it matters
If you update 30 plugins at once and the site breaks, how do you know which one caused it? You don’t. You’ll have to disable everything and re-enable them one by one until you find the culprit — hours of work. Updating one by one with a check after each update catches the problem immediately.
Via WP-CLI:
# list plugins that need updating
wp plugin list --update=available --fields=name,version,update_version
# update one specific plugin
wp plugin update yoast-seo
# update all with one command (NOT recommended without staging)
wp plugin update --all
Which to update first, which to wait a week on
Plugin update priority:
- Security plugins first — Wordfence, Solid Security. They patch security holes and are usually stable
- Technical plugins — caching (WP Rocket, LiteSpeed), optimization (Autoptimize). Also usually stable
- SEO and analytics — Yoast, Rank Math. Stable, but not critical
- Custom plugins with heavy functionality — WooCommerce, Elementor. Their updates often break something; better on staging first
- Rarely used plugins with major updates — wait a week and check reviews. Sometimes the first major version has bugs; a fix usually appears within a week
Automatic plugin updates — when to enable, when not
WordPress 5.5+ has built-in automatic plugin updates. They are off by default. Enable them in the plugin list by clicking “Enable auto-updates” next to each plugin.
When to enable: for security plugins (they close vulnerabilities — every day of delay equals risk) and for small, stable plugins with minor updates.
When NOT to enable: for critical plugins with heavy functionality (WooCommerce, Elementor, payment plugins), for premium plugins that require license activation after update, or on commercial sites during peak season.
If your site has 20+ plugins, manual updates with checks take 3–4 hours a month. Hand maintenance over to me — I follow a clear schedule, check every plugin, and roll back immediately if anything goes wrong. Care plan is $99/month, cancel anytime.
Step 5 — Updating the theme without losing changes
The theme is a special case. If you made edits to its files, a regular update will overwrite them. So before updating, always check exactly how the theme is being used.
Why you need a child theme and how it protects your customizations
A child theme inherits all styles and functions from the parent theme but lets you add your own on top. When the parent theme updates, the child theme stays untouched. All your edits are preserved.
Creating a child theme in 3 steps:
- Create the folder
wp-content/themes/your-theme-child/ - Create a
style.cssfile inside it with this header:
/*
Theme Name: Your Theme Child
Template: your-theme
Version: 1.0
*/
- Create a
functions.phpfile that loads the parent styles:
<?php
add_action('wp_enqueue_scripts', function() {
wp_enqueue_style('parent-style',
get_template_directory_uri() . '/style.css'
);
});
Now activate the child theme under Appearance → Themes. Make all edits only in the child theme files. You can update the parent theme without worry.
How to update the theme if edits are in the parent — step-by-step migration
If you (or a previous developer) edited the parent theme, first move those edits to a child theme:
- Make a full backup
- Create a child theme following the steps above
- Find all your edits in the parent theme (especially
functions.php,style.css, and template files) - Copy the edited files into the child theme — for example,
wp-content/themes/your-theme/header.phpintowp-content/themes/your-theme-child/header.php - Activate the child theme
- Check the site — make sure everything is in place and looks the same
- Only then update the parent theme
It sounds like a lot of work, but you only do it once and it solves the theme update problem for good.
Step 6 — What to do right after the update
Once the update finishes, stay online and verify that everything still works. WordPress has built-in diagnostic tools, plus you can follow this checklist.
Site Health and loopback request
In Tools → Site Health WordPress shows the results of its internal checks. Pay special attention to:
- REST API — it should return a response. If it shows red, something is blocking the API (a security plugin, .htaccess rules)
- Loopback request — the site should be able to “call itself.” If it shows red, cron jobs and automatic updates may stop working
- HTTPS — all resources should load over https. If it shows yellow, you have mixed content that needs fixing
- PHP extensions — all required modules are installed
Post-update checklist
Click through the main user flows on the site (same checklist you used on staging):
- Home page — appearance, images, fonts
- Internal pages — everything in place
- Catalog and filters (for a store)
- Test order placed end-to-end through the site
- Forms — submit and arrive in email
- Admin area — create a post, media library works
- Logs — no new PHP errors in
wp-content/debug.log
After the update the site may feel slower because caches and opcache were cleared. This is normal for the first day. If speed is still poor after a week, consider running a speed optimization and rebuilding the caches. After updates it is also a good time to optimize the database — clean up revisions, transients, and autoload options.
What to do if the site breaks after the update
It happens. Even with perfect preparation. The main thing is not to panic and follow the diagnostic steps.
White Screen of Death (WSOD) — enable WP_DEBUG in wp-config.php
You open the site and see a blank white page with no text. This is the “White Screen of Death.” The cause is a fatal PHP error that WordPress hides by default. Enable debugging via FTP in wp-config.php:
// find the WP_DEBUG line and update it:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
// add the line above /* That's all, stop editing! */
Reload the page. All errors are now written to wp-content/debug.log. Open the file and look for the latest FATAL ERROR — it will show the exact cause and which plugin or file is responsible.
The most common causes of WSOD after an update are plugin incompatibility with the new core, use of deprecated functions, or exceeding the memory limit (increase WP_MEMORY_LIMIT to 256M).
500 error after the update — step-by-step troubleshooting
The site shows “500 Internal Server Error.” Check in order of likelihood:
- .htaccess — rename the file to
.htaccess.bakvia FTP. If the site loads, the problem is in that file. Go toSettings → Permalinksand click “Save Changes” — WordPress will regenerate.htaccess. - PHP version — after a plugin update, a newer PHP version may be required. Switch to PHP 8.2 or 8.3 in your hosting panel.
- Memory limit — add this line to
wp-config.php:define('WP_MEMORY_LIMIT', '256M'); - Plugins — rename the
wp-content/pluginsfolder toplugins-off. If the site loads, one of the plugins is at fault. Rename the folder back and disable plugins one by one from the admin area. - Theme — in the database via phpMyAdmin, change the
templateandstylesheetoptions to the default twentytwentyfour theme. If the site loads, the theme is the problem.
Roll back WordPress to the previous version
If the core update causes critical errors, roll back:
# via WP-CLI to a specific version
wp core update --version=6.4.3 --force
# or manual rollback
# 1. Download the older version from https://wordpress.org/download/releases/
# 2. Unzip it
# 3. Upload via FTP, replacing all files except wp-content and wp-config.php
# 4. Log into the admin area — it may ask to update the database; decline
An alternative is the WP Downgrade plugin. Install it, choose the desired version from the list, and click “Update.” Convenient for non-technical users.
Roll back a plugin to an older version
If a specific plugin is the culprit, the WP Rollback plugin lets you roll it back with one click. Install it, then a “Rollback” link appears next to each plugin in the list. Choose the needed version and the plugin restores it.
Another option is to restore the plugin from a backup: unzip the archive, locate the plugin folder in wp-content/plugins/, and replace it on the server. After that, disable automatic updates for that plugin to prevent recurrence.
I’ll restore WordPress for $249 flat within 24 hours. I’ll find the cause of the issue, get the site back to working condition, and restore data if needed.
Updating PHP for WordPress — when and how to move to 8.2 / 8.3
PHP is the engine that runs WordPress. An old PHP version means a slow site and accumulating security issues. The current standard is PHP 8.2.
WordPress minimum PHP requirements
| PHP version | PHP support | WordPress compatible? | Recommendation |
|---|---|---|---|
| 7.0 / 7.1 | Ended | WP runs but shouldn’t | Update hosting immediately |
| 7.2 / 7.3 | Ended | WP runs | Update within the next month |
| 7.4 | Ended 2022 | Minimum for WP 6.x | Acceptable but better to update |
| 8.0 / 8.1 | Active / Security | Full | Working option |
| 8.2 | Active | Full | Recommended |
| 8.3 | Latest | Full | If plugins support it |
How to update PHP in the hosting panel without taking the site down
Universal steps in most hosting panels:
- Make a full backup (if you haven’t recently)
- Before switching, check all plugins for compatibility with the new PHP version in Site Health. Wordfence, for example, sometimes needs an update for PHP 8.3
- Go to the hosting panel → “PHP” or “PHP Version” section
- Select the new version (8.2 or 8.3)
- Save the settings
- Check the site right away: homepage, admin area, forms
- If something breaks, switch PHP back in the same panel and troubleshoot
Switching PHP is reversible. If the new version doesn’t work, you can return to the old one in two minutes. It’s less risky than updating the WordPress core.
If your host doesn’t support PHP 8.2+, the platform is outdated — it’s time to move to a modern host. On current hosts, PHP 8.2 is the default.
WordPress Maintenance Checklist — What to Do and How Often
Updating is part of regular maintenance, not a one-time task. Here’s the schedule I follow myself and recommend to clients.
Daily / Weekly / Monthly — Maintenance Schedule Table
| What to do | How often | Time |
|---|---|---|
| Backup files and database to the cloud | Daily (automatic) | 0 minutes (cron) |
| Check that the site is working | Daily | 5 minutes |
| Review security notifications | Daily | 2 minutes |
| Update security plugins | As released (auto-update) | 0 minutes |
| Minor core updates | Within a week of release | 15 minutes |
| Update plugins and theme | Once a week | 30–60 minutes |
| Major WordPress core updates | Once a month via staging | 2–3 hours |
| Database cleanup (revisions, transients) | Once a month | 20 minutes |
| Audit installed plugins | Quarterly | 1 hour |
| Full security audit | Semiannually | 2–4 hours |
Total: about 10–15 hours a month for full site maintenance. For one site that’s a 2–3 hour weekly load on a developer.
When to hand maintenance to a contractor and what it costs
Regular maintenance takes 10–15 hours a month. I offer two subscription plans: Care at $99/month or Care+ at $199/month. Both include daily backups, updates (core, plugins, theme, PHP), 24/7 uptime monitoring, fast incident response, security checks, and database optimization. Cancel anytime.
An update with backup and testing takes 2–3 hours. Done monthly that’s a recurring cost. Care at $99/month or Care+ at $199/month covers updates, backups, monitoring, and recovery if something breaks.
Frequently asked questions
wordpress.org/download/ and unzip it locally. Connect to the server with an FTP client (FileZilla) and upload every file from the unzipped archive into the site root EXCEPT the wp-content folder and the wp-config.php file. This replaces the core with a fresh copy while keeping your content and settings. Then go to your-site.com/wp-admin/ — WordPress will offer to update the database structure; click the button.- Daily file and database backups to the cloud, 30-day history
- Core, plugin, theme, and PHP updates on schedule
- 24/7 uptime monitoring — you’ll know about issues before your visitors do
- Recovery SLA — response within 2 hours
- Monthly security checks and database optimization
Or message me on Telegram @demento174 or WhatsApp +995 555 18 41 06 — I reply within a couple of hours and the consultation is free.