Its a known problem with the WordPress core and plugins. If you don't suppress warnings and deprecated, you won't get output. That is a major catch-22/mess with WordPress development. How can you debug a web-app that doesn't output when you have warnings and errors? Answer: pipe them to a file. STDERR needs to go to a file. It requires programming (read 'a script'), and I have not fully researched/tested/debugged it yet. I know because I had to solve that problem before in WordPress and BBPress (their Forum/BBS startup), I use both on different sites.
The WP_DEBUG option, added in WordPress Version 2.3.1, controls the display of some errors and warnings. If this setting is absent from wp-config.php, then the value is assumed to be false.
NOTE: The true and false values in the example are not set in apostrophes (') because they are boolean values.
This will allow you to edit the scriptname.dev.js files in the wp-includes/js and wp-admin/js directories.
In Wordpress versions since 2.3.2, database errors are printed only if WP_DEBUG is set to true. In earlier versions, database errors were always printed. (Database errors are handled by the wpdb class and are not affected by PHP's error settings.)
In WordPress version 2.5, setting WP_DEBUG to true also raises the error reporting level to E_ALL and activates warnings when deprecated functions or files are used; otherwise, WordPress sets the error reporting level to E_ALL ^ E_NOTICE ^ E_USER_NOTICE.
Users browsing this forum: No registered users and 38 guests