[wp-trac] [WordPress Trac] #59282: WordPress should register custom error and exception handlers

[WordPress Trac]

#59282: WordPress should register custom error and exception handlers
-------------------------------------------------+-------------------------
 Reporter:  bjorsch                              |       Owner:  (none)
     Type:  feature request                      |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Bootstrap/Load                       |     Version:  6.4
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback needs-test-   |     Focuses:
  info                                           |
-------------------------------------------------+-------------------------

Comment (by SirLouen):

 Replying to [comment:16 bjorsch]:
 > "Needs-testing-info" was added even longer ago, but without any comment
 as to what, if anything, was needed from me.
 True, you are right, `needs-test-info` was thrown at @anomiex, who created
 this patch. But since you commented in the dev-chat, I supposed that you
 could follow along with the patch easily (in the last couple of months
 I've seen that generally who write in `dev-chat` are people who reported +
 wrote the patch at the same time and are trying to make the whole point).

 > Instruction that you could arrange for warnings or errors (containing
 unescaped HTML) to be raised, with various configurations for PHP's
 display_errors and other ini settings, and see that HTML (if any) returned
 to the browser is properly escaped while log files don't have unnecessary
 escaping? Are you needing more detail than that? If so, please in turn be
 specific about what detail you need. 🙂

 Yes, throwing some code examples to see in action. It's a good starting
 point, specially because they help to put people on the mood without
 having to do a massive effort to read through all the code and having to
 understand it (specially, when there are like 1 zillion reports waiting in
 the backlog). For this massive patch, I think we should play around a lot
 with it to convince someone that its time to move it forward. We should
 build an entire Testing Case to prove it's totally consistent (apart from
 Unit Tests). As I say, a couple of code examples to replicate and see
 clear differences before and after, is the best starting point. I forgot
 [https://make.wordpress.org/test/2025/05/15/building-the-testing-use-
 case/#comment-3314 to link to this post] that maybe, could be helpful in
 this process.

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