[wp-trac] [WordPress Trac] #63554: Are we sensitive about direct accessed URL fatal errors?

[WordPress Trac]

#63554: Are we sensitive about direct accessed URL fatal errors?
--------------------------+-----------------------------
 Reporter:  SirLouen      |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Related to #62722

 Issuing this command within `wordpress-develop` (inside `src/`), reports a
 total of 450 files. Many of them are `includes`, but may others are actual
 maintained WP files.

 `(find . -path './wp-content' -prune -false -o -name '*.php' -print | sed
 's|^\./||' | sort -u | xargs -P 10 -I {} curl -s -o /dev/null
 "http://localhost:8889/{}"; grep "PHP Fatal error" wp-content/debug.log |
 grep -o '/[^ ]*.php' | sort -u)`

 What this command does is simple:

 First it gets all the PHP files within `src/` except the ones from `wp-
 content` and then it issues a curl against each. This should be reporting
 in `wp-content/debug.log` (I needed a little tweak in `tools/local-env
 /php-config.ini` adding `log_errors = On` because, for some reason, it was
 not displaying the on the `debug.log` but I'm not 100% sure if I messed
 something, so I'm just saying). Finally, it displays all the files that
 had a "PHP Fatal Error" string within the error in `debug.log`

 So I was wondering: Shall we be sensitive about this?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63554>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform