Basic techniques on debugging WordPress that can assist you on first hand.
There are some basic techniques on debugging WordPress. The details can be found in WP Support Guide, but the basics are listed below:
- Enable Debugging - Edit your
define('WP_DEBUG', true);, so that any error can be seen
- Delete and Disable Cacheing - if any cacheing plugin is active, delete cached data, then disable cacheing.
- Deactivate all the Plugins - Disable all the plugins so that we can say, the problem is not from any plugin.
If you cannot enter into the admin panel (
/wp-admin), using FTP or cPanel, simply move all the plugins from
wp-content/plugins/directory a level up, to
wp-content/, or make a compressed file (eg.
pluginsdirectory [as a backup], and delete all the plugins from the plugins directory. Doing so would disable 'em forcefully.
- Switch to Default Theme - Switch to a default theme (like TwentyTwenty), so that we can say, the problem is not from any third party theme.
- Clear the browser cache - Clear the browser cache (cached images and resources) so that we can have latest view.
Following the above, we can easily get back to a default WordPress installation. If there is any error visible at this moment, it's coming from WordPress - we are sure now. To fix WordPress, follow the 2 simple steps:
- Backup: Take a complete backup of your WordPress directories and database
- Re-install WordPress: Get to the Dashboard » Updates (
/wp-admin/update-core.php) and Click on the Re-install Now button, so that the WordPress can reinstall itself
Hope any WordPress-specific issues will be solved at this instance. But there can be issues regarding WordPress if it doesn't meet the minimum requirements.
Please be aware that, any server-specific issue can cause error, if so, let not blame WordPress, you should contact to the Server Administrator.
When the WordPress is clear, finding the buggy add-on is simple. Just activate one-by-one, one at a single time, and check which one is causing the issue. If found, delete the buggy add-on, and find out a good alternative. Else, try to solve it, or report it to the respective author/developer, or contact any forum (being in their rules and regulations).
On questioning, include:
- the debugging process, and/or
- the error message, and/or
- the pointed-out error-prone code-block, and/or
- your process taken to resolving the issue.
Be descriptive but try to be brief. Hope WordPress won't be so buggy again. :)