This article was published on WordPress.org
SCRIPT_DEBUG
SCRIPT_DEBUG is a related constant that will force WordPress to use the “dev” versions of core CSS and JavaScript files rather than the minified versions that are normally loaded.
This is useful when you are testing modifications to any built-in .js or .css files. Default is false.
define( 'SCRIPT_DEBUG', true );
SAVEQUERIES
The SAVEQUERIES definition saves the database queries to an array and that array can be displayed to help analyze those queries.
The constant defined as true causes each query to be saved, how long that query took to execute, and what function called it.
define( 'SAVEQUERIES', true );
The array is stored in the global $wpdb->queries.
This will have a performance impact on your site, so make sure to turn this off when you aren’t debugging.
Example wp-config.php for Debugging
The following code, inserted in your wp-config.php file, will log all errors, notices, and warnings to a file called debug.log in the wp-content directory.
It will also hide the errors so they do not interrupt page generation.
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );
NOTE: You must insert this BEFORE /* That’s all, stop editing! Happy blogging. */ in the wp-config.php file.
