If your site went sideways right after updating to WordPress 7.0, you’re not alone and you’re not the only one searching for this at 11pm. Support forums have been filling up with the same handful of problems since the release on May 20: critical errors, plugins that stop working, updates that refuse to run at all. Almost none of it needs a full rebuild. Here’s what’s actually going on and what to do about each one.
First, figure out what kind of broken you’re dealing with
Before anything else, check whether the whole site is down or just wp-admin. Open your homepage in a private/incognito tab. If the front end still loads and only the dashboard is throwing an error, that’s almost always a plugin or theme conflict, not a fatal core problem, and it’s the easier fix. If both are down, it’s more likely a PHP compatibility issue, and the steps below still apply, just start with the PHP version check.
Getting a critical error? Here’s what’s actually causing it
The 7.0.2 point release in particular has generated a wave of “critical error, can’t log into admin” reports. In nearly every thread I’ve read, the cause is a plugin or theme that hasn’t been updated for WordPress 7.0’s new admin code, not a corrupted install.
The fastest way to confirm this: connect over FTP or your host’s file manager, go to wp-content/plugins, and rename the folder to something like plugins-off. WordPress treats every plugin as deactivated the moment it can’t find the folder. If the site comes back, rename it back and reactivate plugins one at a time, checking the site after each one, until you find the culprit. It’s tedious but it’s the only reliable way to isolate which plugin is actually fighting with core.
We’ve written a broader walkthrough of this exact troubleshooting pattern in our white screen of death guide if the error you’re seeing is a blank page instead of an explicit error message.
Your plugin stopped working after the update
Two separate things get lumped together under “plugin broke.” The first is plugins that fail to auto-update at all, usually a licensing/connection issue between the plugin and its update server, unrelated to WordPress 7.0 itself. The fix there is a manual update from the plugin developer’s site or a re-entered license key. Our manual plugin update guide covers that process.
The second, more interesting problem is plugins that update fine but then misbehave. WordPress 7.0 moved the block editor to run inside an iframe. Any plugin with custom JavaScript that reaches for the global document object, expecting to find the editor content directly on the page, will silently stop working because that content now lives one layer deeper. This mostly affects plugins built by smaller teams that haven’t caught up yet, particularly some page builder add-ons and custom block plugins. If a plugin’s editor button or panel just stopped appearing, this is the first thing to check with the plugin’s own support before assuming your site is broken.
Update won’t even start? Check your PHP version
This one catches people off guard because there’s no obvious error, just a missing update button. WordPress 7.0 raised its minimum PHP requirement to 7.4 and will not offer the update, auto or manual, to any site still running PHP 7.2 or 7.3. If you’re on shared hosting from a few years back, this is very likely your situation.
Most hosts let you change the PHP version from a control panel in under a minute. Bump it to at least 7.4, ideally 8.1 or newer since those versions are still receiving security support, then try the WordPress update again. If you’re comfortable on the command line, our PHP upgrade walkthrough covers the server side of this in more depth. One caution: jumping PHP versions can itself break older plugins, so do this on a staging copy first if you have one.
Images look stretched or squished
This is a smaller, purely cosmetic bug worth mentioning because it’s confusing when you spot it: a new CSS selector shipped in 7.0.1 that some themes weren’t written to account for, and it can stretch featured images vertically on affected pages. It’s a theme compatibility gap, not something wrong with your images. Updating the theme (or, if it’s abandoned, adding a short CSS override) resolves it. Don’t spend time re-uploading or re-cropping images, that’s not the actual problem.
Should you have updated yet at all?
Honestly, for most business sites, waiting 1-2 weeks after any major WordPress release is the right call, and that window has already passed for 7.0. The early instability has mostly settled. If you haven’t updated yet and you’re reading this out of caution rather than panic, the sane approach is: back up the site, update on staging first, test your specific plugin stack, then push to production. If you’ve already updated and hit one of the problems above, the fixes are usually quick, not a reason to panic-rollback.
When it’s worth just handing this off
Most of what’s above takes 15-30 minutes for someone who’s done it before. If you’ve tried the plugin-folder-rename test and the site’s still down, or you’re not confident poking around your server’s file system with a client-facing site on the line, that’s the point where it’s cheaper to get a second pair of eyes than to keep guessing. I fix exactly this kind of post-update breakage regularly, usually same day.
