ATK Debugging: Difference between revisions

Revision as of 16:25, 12 February 2010

Debugging is enabled using the following configuration variable:

  $config_debug = 1;

The $config_debug setting can have various values:

1 - general debugging output is appended to every screen
2 - like 1, but with the addition that redirects are paused so you can see what happens right before the page would normally redirect
3 - like 2, but adds stack trace information and detailed query debugging to every statement. Has a significant performance impact so use only when necessary
0 - Turn off debugging. Debugging information is still collected under the hood, to be able to use it in case of errors.
-1 - Like 0, but now no debugging information is collected at all. Performs the best, but is the hardest to find problems.

Jeroen an Sluijs created a firefox plugin that allows ATK application developers to easily turn on/off debugging from within the browser. See the Debughelper Firefox Add-on page for details.

@@ Line 1: / Line 1: @@
-Todo: documentation about debugging
+Debugging is enabled using the following configuration variable:
+<syntaxhighlight lang="php">
+  $config_debug = 1;
+</syntaxhighlight>
+The $config_debug setting can have various values:
+* 1 - general debugging output is appended to every screen
+* 2 - like 1, but with the addition that redirects are paused so you can see what happens right before the page would normally redirect
+* 3 - like 2, but adds stack trace information and detailed query debugging to every statement. Has a significant performance impact so use only when necessary
+* 0 - Turn off debugging. Debugging information is still collected under the hood, to be able to use it in case of errors.
+* -1 - Like 0, but now no debugging information is collected at all. Performs the best, but is the hardest to find problems.
 == Related Howto's ==