Add ability to disable unbounce plugin's debug logging? You're flooding the log!
-
Good day. I’d like to request a reconsideration of your debug logging mechanism. It’s common practice to have WP_DEBUG and WP_DEBUG_LOG permanently ON both in development and production, because it’s the only way to catch issues. During the last decade of working with WP, I’ve yet to see any other plugin completely flood debug.log like the Unbounce plugin does, which leads me to believe the developers here have misunderstood a few aspects about WordPress debug logging.
This is way too harsh:
UBConfig.php:
public static function debug_loggging_enabled() { return WP_DEBUG || WP_DEBUG_LOG || UBConfig::remote_debug_logging_enabled(); }
Could this be altered with an
apply_filters()
call for the result, so I could filter it always OFF with an mu-plugin but still keep the rest of my debug.log?
- The topic ‘Add ability to disable unbounce plugin's debug logging? You're flooding the log!’ is closed to new replies.