< Basic Variables | Variables | Edit Variables >
$AbortFunctionAbort() function.
$EnableDiag
The following actions are available only if you set in your configuration file. They can be used for debugging and should not be set in a production environment.
$EnableDiag = 1;
markup() )
markup() )
?action=ruleset gives you, apply the Cookbook:MarkupRulesetDebugging recipe: it can also show the pattern and the replacement strings.
phpinfo() and exits. No page will be processed
$EnableMarkupDiag$EnableMarkupDiag to 1 will list files and line numbers of all patterns. Note, this needs to be set early in config.php before a Markup() call or before including a recipe.
$EnableIMSCaching$EnableStopWatch<!--function:StopWatchHTML 1--> in the wiki template.
$EnableStopWatch= 0; # No timings (the default). No HTML will be generated.$EnableStopWatch= 1; # Wall-clock timings only.$EnableStopWatch= 2; # Wall-clock and CPU usage timings. Won't work on Windows.
See also:
scripts/refcount.php is useful for debugging
Is it possible for someone with admin privileges to always have access to debugging tools, without letting everyone else access them?
You can easily & automatically allow debugging for anyone with admin privileges (meanwhile leaving it off for everyone else) by including this line in config.php - just be sure that 1) $EnableDiag is either null or set to 0, and 2) to include it near the end of config.php, AFTER declaring your passwords, and after any Auth User or other privilege settings:
if (Cond Auth?($pagename, 'admin')) $EnableDiag = 1; # allows admin to always call phpinfo, etc
< Basic Variables | Variables | Edit Variables >
This page may have a more recent version on pmwiki.org: PmWiki:DebugVariables, and a talk page: PmWiki:DebugVariables-Talk.