[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:  SergeyBiryukov
     Type:  enhancement       |      Status:  reviewing
 Priority:  normal            |   Milestone:  5.0
Component:  Bootstrap/Load    |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+-----------------------------

Comment (by jabranr):

 IMHO, I don't see much of a point in checking if a developer's given file
 location exists or not. If developer is capable enough to specify a custom
 file location then file_write error should easily be understandable in
 case of a wrong file location. My take would be one of followings as
 already given in some of above patches:

 WP_DEBUG_LOG = true
 WP_DEBUG_LOG = 1
 WP_DEBUG_LOG = /tmp/wordpress.log

 My case is using docker image of WP where I can simple define this as part
 of the environment variables which would save me the hassle of sneaking in
 a line with "ini_set" to otherwise enable a custom location for logs.
 Example docker-compose:


 {{{
 ...

 services:
   wordpress:
     image: wordpress:latest
     environment:
       - WP_DEBUG=1
       - WP_DEBUG_LOG=/tmp/wordpress.log
 ...
 }}}


 PS could someone please post a link to the guidance on how to contribute
 to WP?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/18391#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform