Conversation
supportThis plugin removed and replaced my debug if statements. ORIGINAL /*** — Turn on WP DEBUG Here — ***/ define( ‘WP_DEBUG’, false ); if (WP_DEBUG) { define( ‘WP_DEBUG_DISPLAY’, true ); // true OR false define( ‘SCRIPT_DEBUG’, true ); // true OR false, force WordPress to use the DEV versions of core CSS and JavaScript files rather than the minified versions define( ‘SAVEQUERIES’, true ); // true causes each query to be saved, how long that query took to execute, and what function called it. } define( ‘WP_DEBUG_LOG’, $sitepath . ‘.hold/wp-errors.log’ ); // Create a hidden folder named .hold After activating the plugin: /*** — Turn on WP DEBUG Here — ***/ if (WP_DEBUG) { // true OR false // true OR false, force WordPress to use the DEV versions of core CSS and JavaScript files rather than the minified versions define( ‘SAVEQUERIES’, true ); // true causes each query to be saved, how long that query took to execute, and what function called it. } // Create a hidden folder named .hold
@technoogies Debug Log Manager only directly modifies wp-config.php. It does not touch .htaccess. Perhaps you have something that is trying to sync wp-config.php with .htaccess?
You are correct! I miss stated the file name and it is wp-config.php.
@technoogies Debug Log Manager does not expect an if statement to be present. Can you remove all the debug-related lines in wp-config.php first? Then try to disable then re-enable debug loggin in Debug Log Manager’s dashboard.
All of my sites are set this way. The plugin works regardless of the if statement. Would it pass over it if the entire if statement was commented out? I’ll just need to remember to remove them if not, when activating the plugin. Maybe add a check for if statements in a future release and comment it out automatically, then remove the commented if when disabled?
@technoogies I thought debug logging was broken / not working. If it works, then that’s OK I guess. It’s just that toggling debugging on / off in Debug Log Manager will probably not restore your wp-config.php as it was with the if statement. I will probably not make any change in Debug Log Manager to compensate for an edge case like yours. Fiddling with wp-config.php programmatically is rather tricky. It’s been working fine as is for 5,000+ installs so far, so, I’ll leave it as is for now if you don’t mind. Thanks again for reporting the issue in details.
@technoogies Debug Log Manager only directly modifies wp-config.php. It does not touch .htaccess. Perhaps you have something that is trying to sync wp-config.php with .htaccess?
You are correct! I miss stated the file name and it is wp-config.php.
@technoogies Debug Log Manager does not expect an if statement to be present. Can you remove all the debug-related lines in wp-config.php first? Then try to disable then re-enable debug loggin in Debug Log Manager’s dashboard.
All of my sites are set this way. The plugin works regardless of the if statement. Would it pass over it if the entire if statement was commented out? I’ll just need to remember to remove them if not, when activating the plugin. Maybe add a check for if statements in a future release and comment it out automatically, then remove the commented if when disabled?
@technoogies I thought debug logging was broken / not working. If it works, then that’s OK I guess. It’s just that toggling debugging on / off in Debug Log Manager will probably not restore your wp-config.php as it was with the if statement. I will probably not make any change in Debug Log Manager to compensate for an edge case like yours. Fiddling with wp-config.php programmatically is rather tricky. It’s been working fine as is for 5,000+ installs so far, so, I’ll leave it as is for now if you don’t mind. Thanks again for reporting the issue in details.