{"id":10186,"date":"2019-07-06T12:08:11","date_gmt":"2019-07-06T12:08:11","guid":{"rendered":"https:\/\/wpproonline.com\/?p=171"},"modified":"2026-02-26T10:49:26","modified_gmt":"2026-02-26T10:49:26","slug":"debugging-tips-for-wordpress-common-errors-and-how-to-fix-them","status":"publish","type":"post","link":"https:\/\/www.digitalhubz.com\/blog\/debugging-tips-for-wordpress-common-errors-and-how-to-fix-them\/","title":{"rendered":"Debugging Tips for WordPress: Common Errors and How to Fix Them"},"content":{"rendered":"\n
The most disreputable issue to travel wrong with WordPress is that the White Screen Of Death. This is when you load your website and there\u2019s nothing but a white screen. No code, no errors; nothing. It\u2019s a disheartening thing to see. In this post, we\u2019ll say a way to create WordPress speak to you in addition as a way to resolve most problems.<\/p>\n\n
<\/p>\n\n
Making WordPress Communicate<\/h2>\n\n
It\u2019s very common for themes and plugins to have code that is slightly outdated but still perfectly functional. When this happens, PHP issues a warning. By default, PHP warnings are sent to the browser, and appearance considerably like your website is de facto broken, when it\u2019s not. For this reason, WordPress turns off that kind of reporting. On your production server, this is how things should be done. On a staging or development server, you want reporting turned on, so that you can see potential problems.<\/p>\n\n
In production, one of the side effects of turning off all reporting is that when something really goes wrong, it doesn\u2019t get reported in the browser, it simply renders a plain white screen. In WordPress, this is known as The White Screen Of Death. When this happens, ideally you\u2019ll copy your production site to a development server and work there. In a pinch, you can turn on reporting in production and see the errors right there.<\/p>\n\n
Let\u2019s take a glance at a way to activate PHP Error reportage in WordPress.<\/p>\n\n
Turning on PHP Error Reporting in WordPress<\/h2>\n\n
You\u2019ll need to edit your wp-config.php file. You can either pull it down with FTP, edit, and push back, or use a cPanel editor, or even SSH to your server and edit in real time. Any of these methods will work.<\/p>\n\n
Once you’ve got wp-config.php open, seek for this line:<\/p>\n\n
That turns off all error reporting. Replace that one line with these lines:<\/p>\n\n
\/\/ Enable PHP reporting\ndefine( \u2018WP_DEBUG\u2019, true );\n\/\/ Send error messages to the PHP log file\ndefine( \u2018WP_DEBUG_LOG\u2019, true );\n\/\/ Send error messages to the browser\ndefine( \u2018WP_DEBUG_DISPLAY\u2019, true );\n\/\/ Turn on the PHP config directive to send errors to the browser\n@ini_set( \u2018display_errors\u2019, 1 );<\/code><\/pre>\n\n
Then load your browser and you should see something like this:<\/p>\n\n<\/figure>\n\n
\n
NOTE: Savvy readers will notice that this is from Siteground\u2019s Optimizer. There\u2019s nothing wrong with their plugin, I stony-broke it by design for this demonstration.<\/em><\/p>\n<\/blockquote>\n\n
Reading PHP Messages<\/h2>\n\n
PHP reporting messages always have 4 parts:<\/p>\n\n
\n
The type of error. Below we have a syntax error, which would be like a grammar or spelling error in English.<\/li>\n
The actual error. Below we have some unexpected text, \u201cSiteground_Optimizer\u2019<\/li>\n
The file in which the problem exists<\/li>\n
The line number inside that file where you can find the problem.<\/li>\n<\/ol>\n\n<\/figure>\n\n
The four most common types of messages are<\/p>\n\n
\n
Fatal Error<\/li>\n
Parse Error<\/li>\n
Notice<\/li>\n
Warning<\/li>\n<\/ol>\n\n
Notices and Warnings will not stop your site from working and could be hidden by turning off WP_DEBUG. You should try to fix them if you can though, someday they may come back to haunt you.<\/p>\n\n
Fatal Errors and Parse Errors mean something is really broken, and they prevent your site from functioning.<\/p>\n\n
How To Recover<\/h2>\n\n
Deactivate<\/h4>\n\n
Your first step should always be to try to log into the backend of WordPress. Often the errors are in code that only runs on the front of the site, and you can log into the backend. If this is the case then you can simply deactivate the plugin or theme that\u2019s causing the problem. This doesn\u2019t truly fix the problem, but your site will come back, and that\u2019s a big step.<\/p>\n\n
In the WordPress admin, go to the Plugins folder, find the plugin that\u2019s causing a problem and click the Deactivate link. Here\u2019s an example:<\/p>\n\n<\/figure>\n\n
Ask For Help<\/h4>\n\n
Many managed WordPress hosts will work to simply take care of this issue for you. Check with your host to see what your available support options are. They may not be able to actually fix the problem, but they\u2019ll get your site front-end live again and help you understand the real problem so that you can move forward.<\/p>\n\n
Remove with FTP<\/h4>\n\n
If you can\u2019t log into the WordPress admin, you can log into your server with FTP. Follow the trail given within the error message and take away the plugin or theme inflicting the matter. I recommend downloading a copy first. The screenshot below uses the CyberDuck FTP client, and it\u2019s pointing at the Jetpack plugin. From there, you could download that folder and then delete it.<\/p>\n\n<\/figure>\n\n
Fixing the Real Problem<\/h4>\n\n
Once you\u2019ve determined the error that broke your site and removed the problem code, you\u2019ll probably want to find out why it broke, fix it, and put it back. You probably had that code for a reason.<\/p>\n\n
If you did NOT have a good reason for having that code, then you should simply discard it move on.<\/p>\n\n
Common reasons why code fails.<\/h2>\n\n
There was an update for the plugin or theme that introduced a bug.<\/h4>\n\n
Check to see what the latest version of the code is, and compare it to what you have. If it came out just yesterday then there very well could be a bug. You should contact the developer and explain the issue.<\/p>\n\n
There was a network interruption during a regular update.<\/h4>\n\n
The internet being what it is sometimes updated simply break in the middle. Try downloading the plugin or theme and uploading it with FTP. If it fixes the problem then an interruption was almost certainly the problem.<\/p>\n\n
Another plugin updated and introduced incompatible code.<\/h4>\n\n
This might also be indicated in the error message, but sometimes not. The plugin reporting the error might be perfectly fine, but some other plugin has introduced new code that collides with your good plugin. Perhaps you end up with two different functions named the same thing for example. In that case, you\u2019ll want to look at the update times for all of your plugins, and check the newest ones.<\/p>\n\n
In the case of a code collision, it\u2019s not really a bug in either plugin, but most times plugin developers want to be compatible with each other, so you should make both authors aware of the issue. Then it\u2019s a race to see who fixes it first.<\/p>\n\n
You can\u2019t tell<\/h4>\n\n
Sometimes you simply can\u2019t figure it out, especially if you\u2019re not a developer. It\u2019s perfectly fine to contact support or the developer through whatever means they offer and explain the problem. Often they\u2019ll be able to see the issue right away.<\/p>\n\n
Staying on top of things<\/h2>\n\n
You can\u2019t always know ahead of time when changes will be made, but if you have a detailed record of all changes then it goes a long way toward fixing things quickly. I recommend a plugin called WP Stream. It\u2019s a free plugin that tracks every action in WordPress. Every login, every content update, every code update, everything. And it tells who did it, and when.<\/p>\n\n
Summary<\/h2>\n\n
One of the most important things is getting good communication from WordPress. If you can read the log file, or make WordPress tell you the error, fixing the actual problem is almost always easy.<\/p>\n\n
I recommend getting a local development environment like Local by Flywheel or DesktopServer and practice breaking things and making the server tell you what\u2019s wrong. Once you get comfortable with broken sites, fixing them becomes a lot less scary.<\/p>\n\n
![\"\"](\"https:\/\/i2.wp.com\/wpproonline.com\/wp-content\/uploads\/2019\/07\/0_8vCK591uiWBHSkmG.png?fit=1024%2C77&ssl=1\")
<\/figure>\n\n![\"\"](\"https:\/\/i0.wp.com\/wpproonline.com\/wp-content\/uploads\/2019\/07\/0_L-X6ziSufhiclY6O.png?fit=1024%2C263&ssl=1\")
<\/figure>\n\n![\"\"](\"https:\/\/i1.wp.com\/wpproonline.com\/wp-content\/uploads\/2019\/07\/0_hdz4YoE_ucsQbrJu.png?fit=1024%2C437&ssl=1\")
<\/figure>\n\n![\"\"](\"https:\/\/i0.wp.com\/wpproonline.com\/wp-content\/uploads\/2019\/07\/0_7nnw2U349pRw5Dm6.png?fit=1024%2C906&ssl=1\")
<\/figure>\n\n