Comment out the top line there, and add the rest to your wp-config.php file to get more detailed error reporting from your WordPress site. Definitely don’t do this live, do it for local development and testing.
// define('WP_DEBUG', false);
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
Nice one Chris. Thanks.
for a live website I would recommend:
don’t forget to drop a phperrors.log file inside your remote directory with write permissions
What does make you code any different then:
?
Thanks @geopaL!
I have the same question as @Willem-Siebe Spoelstra does.
Why do you recommend that code instead of using the WordPress constants WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY? I know they are meant for local testing and staging installs but…what are the advantages of the code you have provided? Is it for performance reasons?
The only thing that comes into my mind is the fact that Enabling WP_DEBUG will consume extra system resources trying to detect deprecated WordPress functions and arguments that are being used.
Thanks!
Not sure where the errors get reported to with this turned on.. is there a log file somewhere?
Answered my own question on the codex.
/**
* This will log all errors notices and warnings to a file called debug.log in
* wp-content (if Apache does not have write permission, you may need to create
* the file first and set the appropriate permissions (i.e. use 666) )
*/
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);
@ini_set(‘display_errors’,0);
I need your help when I log in my dashboard is a blank page. I tried to rename my file via FTP using Filezilla but nothing is coming up. Do you have any advices for me. Thanks you.
Hi,
you may try plugin https://wordpress.org/plugins/debug/ to Debug all issues in WordPress site. and you not need to edit php code in wp-config file.
SoniNow: Your “debug” plugin seems like the ideal solution to my own need, but I’ve not been able to get it to work. Initially it made it impossible to access my test site at all, but restoring config.php from the backup copy solved that and I discovered that the 0600 permission with which it wrote the changed config.php file prevented my server (on localhost) from accessing it at all. This might be what caused Alice’s situation. Changing the permission to 0664 eliminated the login problem but the plugin still failed under WordPress 4.3…
Hi, I don’t understand the advice:
Definitely don’t do this live, do it for local development and testing.
I understand you don’t want to ‘show’ the errors to public and for that you define WP_DEBUG_DISPLAY to false. But why is it bad practice to ‘log’ the errors to a log file?
Kind regards,
Willem