[wp-trac] [WordPress Trac] #18512: Add backtrace details to _doing_it_wrong output

[WordPress Trac]

#18512: Add backtrace details to _doing_it_wrong output
-------------------------------------+------------------------
 Reporter:  chrisbliss18             |       Owner:
     Type:  enhancement              |      Status:  closed
 Priority:  normal                   |   Milestone:
Component:  Warnings/Notices         |     Version:
 Severity:  normal                   |  Resolution:  duplicate
 Keywords:  has-patch needs-testing  |
-------------------------------------+------------------------

Comment (by chrisbliss18):

 Definitely a duplicate. Thanks for that. I'm always terrible at finding
 related tickets. One day, I might figure out the magic to find such
 things.

 Beyond that, I must say that your response is why I frequently hate
 submitting patches.

 I saw a notice that someone (at least Nacin as he coded it) felt added
 value to core. However, I found this notice to be lacking as it
 essentially amounted to "some code is misbehaving, but I'm not going to
 tell you what code is at fault."

 I thought, "I can quickly add a backtrace output to make the notice more
 valuable and immediately usable," and began working on a patch.

 Your response of being able to add a backtrace to anything doesn't help
 anybody. I know that I can get a backtrace of anything I want, I did so
 when I made this patch. Clearly I don't need to be educated on this. I
 made this patch not for me but for other developers that may not know the
 tricks you or I do. Being able to provide them relevant feedback for
 possible problems rather than "something went wrong, I hope you know
 enough to figure out what and where" is the least we can do.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18512#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software