WP debug mode [RELEASED]

Mark

User feature
I think a great feature for the WordPres toolkit will be the option to debug applications.
I guess everyone who has to deal with WP, knows what this is all about. In the wp-config.php file, you need to add the appropriate directives to have errors displayed in the application for development or debugging work. Very usefull.

define('WP_DEBUG',true);
define('WP_DEBUG_DISPLAY',true);
define('WP_DEBUG_LOG',true);

https://wordpress.org/documentation/article/debugging-in-wordpress/
https://make.wordpress.org/cli/handbook/references/internal-api/wp-cli-debug/

AdamM

Mason

If implemented, should have a separate setting for "WP_DEBUG" and "WP_DEBUG_DISPLAY" - in case you want to only log errors.

Adrien

+1 a must-have feature.

Adam

We can implement this, I'll add it as a feature request.

ss88us

Great idea! Could you please split these toggles out? For sensitive applications, I would never show errors to the browser.

Adrien

This is what spinupwp does:

wp-debug.log turned on and relocated to a folder not publicly accessible

Aliysa_Enhance

This has now been scheduled for April https://enhance.com/support/product-roadmap

digitalexpanse

but as if you'd want
define('WP_DEBUG_DISPLAY',true);

Aliysa_Enhance

The ability to quickly activate WP debug mode is now available in our latest update 9.2.0: https://enhance.com/support/release-notes

standtech

Trying to troubleshoot a plugin, but after adding the following lines don't see any debug messages at all. Already restarted the PHP container. Dont think this has anything to do with Enhance either. Any clue why this may not work ?

wp-config.php:>

/* Add any custom values between this line and the "stop editing" line. */
define( 'SCRIPT_DEBUG', true );
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );

Omar

standtech

If you use server-level caching (OPcache, Redis, etc.), restart it.
WP_DEBUG_DISPLAY is set to false, so errors will not be displayed on screen, but they should still be logged since WP_DEBUG_LOG is set to true. Look in wp-content/debug.log.
If there is a syntax error in wp-config.php, it could prevent the debug directives from being applied. Try adding the lines just before /* That's all, stop editing! Happy publishing. */.
Check the php.ini or use ini_get(‘display_errors’) to see if the server configuration is overriding WordPress.

Are you sure the plugin code is generating errors? If the plugin handles errors well, it may not be generating any. Try forcing a temporary error in the plugin code (e.g., echo $non-existent_variable;)

standtech

Omar WP_DEBUG_DISPLAY is set to false, so errors will not be displayed on screen, but they should still be logged since WP_DEBUG_LOG is set to true. Look in wp-content/debug.log.

Thanks . No new log ,

Omar If there is a syntax error in wp-config.php, it could prevent the debug directives from being applied. Try adding the lines just before /* That's all, stop editing! Happy publishing. */.

Yes did this as well , no logs yet

Omar Check the php.ini or use ini_get(‘display_errors’) to see if the server configuration is overriding WordPress.

As per the php info . file is located as "Loaded Configuration File /usr/local/lib/php.ini " but is empty.
.

Omar

standtech Did you change WP_DEBUG_DISPLAY totrue? And nothing showed up on the screen?

Did you try forcing a temporary error in the plugin code (e.g., echo $non-existent_variable;)?

Is there an @ silencing errors? If the plugin uses @function_that_fails(), errors could be silenced.

Could you share the name of the plugin? It might be useful.

Create a temporary file called info.php with <?php phpinfo(); ?> and check the display_errors and error_reporting settings.

If after reviewing all of this you still cannot see the messages, you can try temporarily adding this to the beginning of wp-config.php to force error output:

ini_set('display_errors', '1');
ini_set('error_reporting', E_ALL);

standtech

Omar Hello Omar , Thanks for your replies and help . Issue is resolved.

Seems plugin didnt log outputs to the log file for some reason, and when those debug flags were set before /* That's all, stop editing! Happy publishing. */ , it was giving us below error

PHP Warning: Constant WP_DEBUG already defined in /var/www/39c2f96b-e0bc-4bae-9d9f-d7bf43da1be7/public_html/wp-config.php on line 95

Which was resolved after adding those debug settings immediately after /* Add any custom values between this line and the "stop editing" line. */