To fix a WordPress site, start with what changed most recently: an update, a new plugin, a theme switch, or a change at your host. Most common failures, such as a white screen, the “critical error” message, or a site that broke after an update, come from a plugin, a theme, or the PHP version, and the error log usually names the culprit without you touching any content. Take a full backup before any step that touches files or the database.
Someone on your team opens the homepage before a campaign goes out and gets a blank page with one line about a critical error. Yesterday evening everything worked. Did someone click “Update all”? Did the host upgrade something overnight? Clicking around at random is how one broken thing becomes three. Here is the order to work in.
What should you do in the first few minutes?
Work out what is broken and what changed before you fix anything. Check whether the whole site is down or just one page, whether wp-admin loads, and whether the site looks the same in a private window and on another network. A site that looks fine to you and broken to a customer is usually a cache issue, not a code issue.
Then pin down the last change. Plugin updates, a newly installed plugin, a hosting setting, a PHP version switch: that is almost always where to start. If you can reach your hosting control panel, look for any notice from the host too. Sometimes the fault is theirs.
Before you touch anything: back up the files and the database, even with the site broken. If your host offers staging (a test copy of the site), try the steps marked risky below there first. A backup of a broken site still keeps your latest content and orders safe if the fix goes wrong.
White screen or “critical error”: how do you find the cause?
Start with the Recovery Mode email; if there isn’t one, turn on the debug log. When a plugin or theme triggers a fatal error, WordPress shows a “There has been a critical error on this website” message and usually emails the site admin address a special link. That link logs you into recovery mode, where the faulty component is paused so you can deactivate or update it. The link expires, so check the admin inbox, spam folder included, quickly.
No email? In wp-config.php, above the line that says to stop editing, set WP_DEBUG and WP_DEBUG_LOG to true and WP_DEBUG_DISPLAY to false. Errors then go to wp-content/debug.log instead of appearing to visitors. The last lines usually include a file path, and the path tells you at once whether it is a plugin (wp-content/plugins/…) or a theme (wp-content/themes/…).
Careful (risky step): one missing character in wp-config.php can take the site down. Keep a copy of the original file, and switch debugging off when you are done. A debug.log left in place can expose paths and technical details to anyone who finds it.
If the log shows “allowed memory size exhausted”, the site needs more memory than it has. You can raise WP_MEMORY_LIMIT in wp-config.php, but your host sets the ceiling. If more memory doesn’t help, the real problem is usually a heavy plugin, not the number.
Site broken after an update? Undo what changed
When a WordPress site breaks after an update, roll back the most recent change: deactivate the plugin that updated, switch the theme temporarily, or return to the previous PHP version. If wp-admin loads, do it from the Plugins screen, one plugin at a time, checking the site after each.
If wp-admin won’t load, go to the files over SFTP or your host’s file manager. Rename the suspect plugin’s folder inside wp-content/plugins (add “-off” to the name, for example) and WordPress deactivates it because it can no longer find it. Not sure which plugin? Rename the whole plugins folder and every plugin is deactivated at once. Then restore the original name and reactivate plugins one by one until the site breaks again. That one is your culprit. The same trick works for the active theme folder in wp-content/themes; WordPress falls back to a default theme if one is installed.
Careful (risky step): deactivating a plugin usually keeps its settings, but on a store it can stop payments, shipping or invoicing while customers are mid-checkout. On a site taking live orders, test on staging or at least pick a quiet hour. Don’t delete plugins while troubleshooting: unlike deactivation, deletion can remove data.
Sometimes the update is fine and the PHP version your host just switched to is the real trigger. If the errors started right after such a change, you can temporarily return to the previous version in the hosting panel while you find the component that isn’t compatible. And if nothing works, restoring a backup taken before the update is the fastest route back to a working site. Remember that a full restore also rolls back the database, so orders, form entries and comments added since then will be gone.
500 error or “Error establishing a database connection”: what’s the difference?
A 500 error means the server failed to run the site; a database connection error means WordPress can’t reach its own data. They are different failures with different checks.
For a 500 error, start with the server error log in your hosting panel and the debug log above. On Apache or LiteSpeed servers, check the .htaccess file in the site root: rename it temporarily, and if the site comes back, generate a fresh one under Settings → Permalinks → Save. If not, go back to the plugin and memory checks.
For a database connection error, first compare the connection details in wp-config.php (database name, user, password and host) with what your hosting account shows. If nobody changed them, the database server may be down, which is a question for your host. If the host confirms the server is fine, tables may be corrupted. WordPress has a built-in repair tool: add WP_ALLOW_REPAIR to wp-config.php, then visit /wp-admin/maint/repair.php.
Careful (risky step): back up the database before any database work. The repair page is open to anyone while that setting is on, so remove it the moment you finish.
Slow or half-broken admin: where do you start?
A slow dashboard, or buttons and the editor not responding, usually points to a plugin conflict or a script loading where it shouldn’t. Start with Tools → Site Health, which flags known problems such as an outdated PHP version, failing scheduled tasks, or blocked connections.
Then test for conflicts without breaking the site for visitors. The Health Check & Troubleshooting plugin from the WordPress.org directory has a troubleshooting mode that disables plugins and switches the theme for your session only, while visitors still see the normal site. Turn plugins back on one at a time until the problem returns. If the block editor won’t load, open your browser’s developer tools (F12) and look for a JavaScript error in the Console tab; it usually names the plugin.
One more check that saves time: clear the cache in your caching plugin, at the host, and in the CDN if you use one. Caching and minification plugins that combine JavaScript files are a frequent cause of pages and admin screens that are only partly broken.
Forms or emails not sending: why does it happen?
Usually the form works and the email never leaves, or lands in spam. WordPress sends mail through the server’s own mail function, which many hosts restrict or send without authentication, and mailbox providers treat that mail with suspicion.
The standard fix is sending over SMTP: an SMTP plugin that connects to a real mailbox on your domain or to a sending service, with a username and password. Also check that your domain’s DNS has SPF and DKIM records for whatever service sends on your behalf. After setup, send a test from the plugin and a real form submission to an address outside your organisation.
If you run a store, test the WooCommerce order emails as well. A customer who never got an order confirmation will call, and you’ll learn about the fault from the phone instead of from your own test.
When should you stop and call a professional?
Stop when you have no recent backup, no access to the files or hosting, or when every extra step puts orders and customer data at risk. If the store is live, if the error is in the database, if the fix means editing code you don’t know, the right move is not to try one more thing. A site that is broken but stable for an hour beats a broken site someone keeps changing.
If you see signs of a hack, such as unknown admin users, redirects to strange sites or files you never uploaded, that is a different problem. Use the hacked WordPress site guide instead.
Arriving prepared saves time on both sides. Have admin access to the site and hosting ready, a note of what changed and when, a screenshot of the error, and your latest backup. Websight is a team with 15+ years of experience in design, development and website care. Per the plans page, Websight’s care plans include daily off-site backups and emergency downtime support, with production bugs and breakages fixed as part of the plan. For a one-off problem, describe what happened on the contact page.
One last step worth doing today, while the site works: confirm you have a backup you can actually restore, and that you know where your hosting and SFTP logins are. On the day the white screen appears, those two things are the difference between a quiet fix and a frantic password hunt.
שאלות נפוצות
Why does WordPress say "There has been a critical error on this website"?
Because code in a plugin, a theme or the site itself hit an error that stops the page from loading. WordPress replaces the blank screen with that message and usually emails the site admin a link to recovery mode. If the email never arrives, turn on the debug log and it will show which file caused the error.
How do you fix the WordPress white screen of death without admin access?
Go in through SFTP or your host's file manager. Rename the suspect plugin's folder, or the whole plugins folder, so WordPress deactivates the plugins. If the site comes back, restore the names and reactivate plugins one by one until you find the culprit. Take a backup first.
Does deactivating a plugin delete its settings?
Usually not. Deactivation stops the code and leaves the settings in the database, so the plugin picks up where it left off when reactivated. Deleting is different: some plugins remove their data on deletion. That is why you deactivate, not delete, while troubleshooting.
My WordPress site broke after an update. Can I go back to the previous version?
Yes, and the safe way is restoring a backup taken before the update. A full restore also rolls back the database, so orders and form entries added since then may be lost. Often the real cause is a plugin that isn't compatible with the new version, and deactivating or updating that plugin is enough.
How do you tell whether the problem is your site or your host?
Check whether other sites on the same hosting account are down, whether the control panel shows an incident, and what the server error log says. A database connection error or 500 error that hits several sites at once usually points to the server. In that case, open a ticket with your host before changing anything on the site.