{"id":17729031,"date":"2024-05-02T15:55:39","date_gmt":"2024-05-02T15:55:39","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/back-trace\/"},"modified":"2024-05-02T15:55:39","modified_gmt":"2024-05-02T15:55:39","slug":"back-trace","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/back-trace\/","title":{"rendered":"Back trace?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">I would really love the ability to see a back trace of an error&#8217;s origin. Sometimes an error is thrown on a WordPress core function because some function up the chain was the culprit, but it&#8217;s currently impossible to know where that is. So adding the output of <strong><code>debug_backtrace<\/code><\/strong> to the database log, or even if you could simply add an action to the <code>Log_Handler-&gt;handle()<\/code> function so I could add a trace myself, that would be <em>super helpful.<\/em> Thanks for considering it and for providing such a useful plugin!<\/p>\n","protected":false},"template":"","class_list":["post-17729031","topic","type-topic","status-publish","hentry","topic-tag-feature-request"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/17729031","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/17729031\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=17729031"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}