[wp-trac] [WordPress Trac] #63303: Direct access to wp-settings.php results in a fatal error due to undefined ABSPATH constant.

[WordPress Trac]

#63303: Direct access to wp-settings.php results in a fatal error due to undefined
ABSPATH constant.
----------------------------+------------------------------
 Reporter:  matinlk         |       Owner:  (none)
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Bootstrap/Load  |     Version:
 Severity:  critical        |  Resolution:  duplicate
 Keywords:  close           |     Focuses:
----------------------------+------------------------------
Changes (by SirLouen):

 * keywords:  has-patch dev-feedback has-testing-info => close
 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Replying to [comment:12 sabernhardt]:
 > Back to the topic of this ticket, I do not have an opinion about
 `exit`/`die()` or `wp_load.php`. Also, other files might need to block
 direct access just as much as `wp-settings.php` (it is one of the files
 included on #62722).

 Great catch.
 I advocate for triaging harder.

 > I do not commit code changes, so ultimately any time I edit the
 milestone it is no more than a recommendation.
 Even a good milestone recommendation will bring attention and prob get
 more useful commits into cycles. Zillions of good patches are being lost
 in the space.
 For example, if you can propose 6.8.2 to #62722, would  be great.

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