Troubleshooting
How to Disable WordPress Plugins Without Admin Access
Disable one broken plugin by renaming its folder, deactivate all plugins through WP-CLI, or reset the plugins directory safely without deleting settings.
Tag
Finding the actual cause when WordPress breaks.
Troubleshooting
Disable one broken plugin by renaming its folder, deactivate all plugins through WP-CLI, or reset the plugins directory safely without deleting settings.
Troubleshooting
Fix wp-admin returning to the login form by clearing site cookies, matching WordPress URLs and HTTPS, bypassing cache, and isolating authentication plugins.
Troubleshooting
Raise WordPress memory in wp-config.php, verify the effective PHP limit, and use the fatal error log to find the plugin, query or import that exhausted it.
Troubleshooting
If the error appears during a theme or plugin upload, check PHP upload limits. If it appears after an admin action, refresh the nonce and investigate caching, cookies or time drift.
Troubleshooting
Fix the right layer: resave rewrite rules when all pretty permalinks fail, repair one page’s slug or status when only one URL fails, and add redirects for moved content.
Troubleshooting
Remove the temporary .maintenance file only after confirming the update process has stopped, then complete or roll back the interrupted update and verify the site.
Troubleshooting
Check whether the database server is available, verify wp-config.php credentials, test the connection and repair tables only when corruption is actually reported.
Troubleshooting
A WordPress 500 error is a server-side failure. Find its log entry first, then test plugins, the active theme, rewrite rules, PHP limits and core files in a safe order.
Troubleshooting
Recover a blank WordPress site by checking Recovery Mode and error logs first, then isolating plugins, the active theme, memory exhaustion and damaged core files.