From a0960f9b04cf22ce2a26bf628bb441235edb086d Mon Sep 17 00:00:00 2001 From: Tim Otten <totten@civicrm.org> Date: Thu, 9 Aug 2018 15:13:25 -0700 Subject: [PATCH] Update debugging.md Fix comma splice. Make clearer reference to later section. --- docs/tools/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tools/debugging.md b/docs/tools/debugging.md index 99428bdf..f8ba1a39 100644 --- a/docs/tools/debugging.md +++ b/docs/tools/debugging.md @@ -32,7 +32,7 @@ After enabling debugging, append any of the following name-value pairs to the UR ### Displaying a backtrace -The backtrace can be enabled independently of debugging. If this option is selected, a backtrace will be displayed even if debugging is disabled. **A backtrace is normally displayed only when an error is encountered, to manually trigger a backtrace in your custom code see further down this readme.** +The backtrace can be enabled independently of debugging. If this option is selected, a backtrace will be displayed even if debugging is disabled. **A backtrace is normally displayed only when an error is encountered.** To manually trigger a backtrace in your custom code, see "Changing source code" (below). A backtrace is a list of all the functions that were run in the execution of the page, and the PHP files that contain these functions. It can be really useful in understanding the path that was taken through code, what gets executed where, etc. -- GitLab