I notice there’s a HUGE number of people, here and on dozens of webmaster forums, who are currently adding define(‘SCRIPT_DEBUG’, true); to their wp-config.php file after they updated to wordpress 3.5.
Of course a fix will come sooner or later, we can trust the wordpresss devs, but until them, seems many webmasters are eager to get a properly working editor again 😉
I wanted to ask, just in case, is there any potential problem with the addition of define(‘SCRIPT_DEBUG’, true); to our wp-config file ?
I have read https://codex.wordpress.org/Debugging_in_WordPress carefully, and apparently, ‘SCRIPT_DEBUG’, true only comes as a first step before adding actual logging to file triggers.
I come to ask a confirmation : this is it, I am not mistaken ? We can keep it to “true” on a production website with big traffic, there won’t be any after effects, or server performance issues ?
Sorry to be paranoid, and thanks a lot if someone can respond 🙂
- The topic ‘So, it isn't bad to keep SCRIPT_DEBUG', true in a "production" blog, right ?’ is closed to new replies.