Common WordPress Errors and How to Fix Them

WordPress errors look alarming mostly because they replace your whole site with a blank page or a cryptic line of text, with no obvious next step attached. In practice, the overwhelming majority of them trace back to a small set of recurring causes: a plugin conflict, a resource limit, a bad file edit, or a mismatched setting. Here's how to recognize and fix the ones people run into most.

500 Internal Server Error

This is WordPress's catch-all for "something failed, and I can't tell you exactly what." It's most often caused by a corrupted .htaccess file, a plugin or theme conflict, or exhausted PHP resources. Start by renaming the .htaccess file in the site's root folder (WordPress regenerates a clean one automatically), then check if the error clears. If not, deactivate plugins one at a time, starting with any installed or updated recently, since a single incompatible plugin is the single most common cause.

"Allowed memory size exhausted"

This means a PHP process tried to use more memory than it was allowed, usually while running a resource-heavy plugin, a large import, or a poorly coded theme function. Raise the PHP memory limit as a first step, either through your hosting control panel or by adding define('WP_MEMORY_LIMIT', '256M'); to wp-config.php. But treat that as a temporary buffer, not a permanent fix: if one specific plugin or import is what's actually pushing memory that high, the underlying cause is still worth finding.

Syntax error after editing a file

If the site went white immediately after editing theme or plugin code, and the error message names a specific file and line number, this is almost always a missing semicolon, an unclosed bracket, or a stray character introduced during the edit. Connect over SFTP or your host's file manager, open the exact file and line named in the error, and compare it against a backup copy of the file from before the change. Restoring that one file is usually faster than trying to spot the typo by eye.

• Note the exact file path and line number from the error message
• Compare against a backup copy of that file made before the edit
• Restore the backup version if the fix isn't immediately obvious
• Make future code edits in a staging copy of the site, not directly on the live one

"There has been a critical error on this website"

This is WordPress's more recent, slightly friendlier replacement for a blank white screen, and it comes from the same underlying causes: a fatal PHP error triggered by a plugin, theme, or core conflict. WordPress usually emails the site administrator a more detailed version of the error when this happens, including the specific file involved. Enabling WP_DEBUG temporarily in wp-config.php surfaces that same detail directly on the page, which narrows down the cause much faster than guessing.

HTTP error when uploading images

This vague error during media uploads usually points to one of three things: the PHP memory limit being hit during image processing, a permissions problem on the uploads folder, or a conflict with an image-optimization plugin actively processing the file mid-upload. Try uploading a small, simple image first to see if the issue is image-size-specific, check that the wp-content/uploads folder has correct write permissions, and temporarily deactivate any image-optimization plugin to rule it out.

Mixed content warnings after adding SSL

After moving a site to HTTPS, a browser padlock warning about mixed content means some resources, usually images, scripts, or stylesheets, are still being loaded over plain HTTP. This almost always comes from hardcoded http:// links saved directly in old page content or theme settings, rather than from the SSL setup itself. A search-and-replace plugin that updates URLs across the database, followed by clearing any active cache, resolves most cases.

"Too many redirects"

This error means the browser is being bounced between two URLs in a loop, most often from a WordPress site URL setting that doesn't match how the domain is actually configured, or a conflict between a caching plugin and an SSL or redirect plugin both trying to force HTTPS. Check the Site Address and WordPress Address settings in Settings > General, confirm they match how the domain is actually served, and check for duplicate redirect rules across plugins and .htaccess.

Broken images or styling after a migration or restore

If a site was recently migrated or restored from a backup and images, stylesheets, or the layout suddenly look broken, the cause is almost always leftover references to the old domain or old file paths still sitting in the database. WordPress stores full URLs in many places rather than relative paths, so a domain change or a server move without an accompanying database search-and-replace leaves old links pointing nowhere. The fix mirrors the mixed content situation above: a search-and-replace tool run against the database, followed by clearing any active cache, updates those stale references in one pass rather than hunting for them page by page.

A general approach that works across most of these

• Note exactly when the error started, and what changed right before it
• Reproduce it in a private browser window to rule out a caching or login-session artifact
• Deactivate plugins one at a time rather than all at once, to identify the actual culprit
• Keep a recent backup before making any fix, in case a change makes things worse
• Contact hosting support with the exact error text and timing if server logs might hold the answer

Most WordPress errors aren't actually mysterious once you match the message to its usual cause. The pattern that repeats across nearly all of them is the same: something changed, WordPress can't recover from it gracefully, and it needs a specific piece of information, not a random guess, to get fixed.