[wp-trac] [WordPress Trac] #18391: Expand WP_DEBUG_LOG and make WP_DEBUG_DISPLAY work as expected

[WordPress Trac]

#18391: Expand WP_DEBUG_LOG and make WP_DEBUG_DISPLAY work as expected
-------------------------+-----------------
 Reporter:  nacin        |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  3.3
Component:  General      |    Version:
 Severity:  normal       |   Keywords:
-------------------------+-----------------
 == WP_DEBUG_LOG ==

 WP_DEBUG_LOG currently creates wp-content/error.log. We should expand this
 to allow a path.

 To do this, if WP_DEBUG_LOG is !== true, != 1, != 'true', (anything else?)
 and 0 === validate_file(), we should treat it as a path.

 == WP_DEBUG_DISPLAY ==

 Setting WP_DEBUG_DISPLAY to false does not set display_errors to false.
 Instead, it prevents display_errors from being set to on. This forces a
 call to ini_set to turn off display_errors, assuming your php.ini is set
 to On, as expected for a development environment configuration.

 Instead, setting WP_DEBUG_DISPLAY to false should set display_errors to
 false. I've been thinking about this for months now, and the only
 situation I can come up with that this would be a compatibility issue
 would be when you deliberately have a production php.ini on production and
 a development php.ini in development. In this situation, WP_DEBUG_DISPLAY
 = false would screw up your development environment only -- the only
 breakage would be showing less errors, rather than more.

 WP_DEBUG_DISPLAY === null can remain a passthrough.

 Patch forthcoming.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18391>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software