Fix WordPress errors

Symptom: A blank page with exactly this message; usually WordPress also sends an email with a recovery link.

Cause: A PHP fatal error – almost always a plugin/theme conflict, an incompatible update or too little memory.

Fix:

1. Open the recovery-mode email from WordPress – the link leads to a protected backend.
2. Deactivate the last activated or updated plugin (rename the plugin folder via FTP if no backend is reachable).
3. Increase the PHP memory limit (WP_MEMORY_LIMIT in wp-config.php).
4. Enable WP_DEBUG and read the exact file/line from debug.log.

Symptom: A completely blank white page – with no error message at all.

Cause: A PHP error or a reached memory limit while error display is switched off.

Fix:

1. Turn on WP_DEBUG in wp-config.php so the message becomes visible.
2. Deactivate all plugins (rename /wp-content/plugins via FTP).
3. Switch to a default theme.
4. Increase the memory limit and clear the server/object cache.

Symptom: "403 Forbidden – You don't have permission to access…" instead of your page.

Cause: Wrong file permissions, a broken or blocking .htaccess, a security plugin or firewall (mod_security) – or an accidental IP block.

Fix:

1. Check file permissions: folders 755, files 644.
2. Back up and regenerate .htaccess (just save under Settings → Permalinks in WordPress).
3. Temporarily deactivate the security plugin or firewall.
4. Ask your host to check mod_security/WAF rules and make sure your own IP isn't blocked.

Symptom: Broken layout, missing features or errors right after a core, plugin or theme update.

Cause: An incompatibility between the update and another plugin, the theme or the PHP version.

Fix:

1. Clear all caches (server, plugin, CDN, browser).
2. Roll the offending plugin/theme back to the previous version.
3. Check and align the PHP version.
4. For future updates: use a staging environment and take a backup first.

Symptom: "Error establishing a database connection" instead of the website.

Cause: Wrong database credentials, an overloaded or down DB server, or corrupted tables.

Fix:

1. Check the DB credentials in wp-config.php (DB_NAME, DB_USER, DB_PASSWORD, DB_HOST).
2. Check with your host whether the database server is running and not at its connection limit.
3. Repair the database (define('WP_ALLOW_REPAIR', true) and open /wp-admin/maint/repair.php).

It's a PHP fatal error, usually from a plugin or theme update. Use the WordPress recovery-mode email, deactivate the last changed plugin (via FTP if needed), raise the PHP memory limit, and read the exact cause from debug.log with WP_DEBUG enabled.

Enable WP_DEBUG in wp-config.php to reveal the hidden error message. Then deactivate all plugins via FTP, switch to a default theme and raise the memory limit. In most cases a single plugin or the theme is the cause.

Check file permissions (folders 755, files 644), regenerate .htaccess via Settings → Permalinks, temporarily deactivate security plugins, and have your host check mod_security/firewall rules. Often an overly strict security rule blocks access.

Clear all caches first. If the error persists, roll the offending plugin or theme back to the previous version and check the PHP version. For future updates a staging environment plus backup ensures a faulty update never hits the live site.

When the error message is unclear, several causes combine, it's a store with revenue on the line, or you're not comfortable editing code/database. We fix WordPress errors at a fixed price and prevent them with ongoing maintenance.

In wp-config.php set define('WP_DEBUG', true); plus define('WP_DEBUG_LOG', true); — WordPress then writes all errors with file and line to wp-content/debug.log. That reveals the exact cause. On live sites suppress the display (WP_DEBUG_DISPLAY false) and turn debug mode off again afterwards.

Via FTP or the host's file manager: rename the plugins folder (deactivates all plugins at once), reset the active theme to a default theme, or set a new password directly in the database (phpMyAdmin). Usually a plugin or theme conflict is blocking the login.

Via FTP, rename wp-content/plugins to e.g. plugins_off — WordPress then deactivates all plugins. Once you're back in, rename it back and reactivate one by one until the error returns: that's the culprit. The fastest way to isolate a plugin conflict.

An error is usually a technical problem: after an update, a plugin conflict, too little memory. A hack shows up through foreign content, unknown redirects, spam pages or a Google warning. If anything points to an attack, it's not about repairing but cleaning — then our WordPress emergency help is the right call.

In wp-config.php with define('WP_MEMORY_LIMIT', '256M'); — alternatively in php.ini or .htaccess. This fixes the »Allowed memory size exhausted« message. On shared hosting a hard server limit often applies; then the host has to raise it.

Always test bigger changes (code, database, risky updates) on a staging copy and only then push live. For quick fixes, maintenance mode plus a current, tested backup is enough — so a failed attempt never damages the live site.