NEWS
28 Nov. 2011
LNCS proceedings is available online
25 August 2011
Pictures from the conference are now on the web.
15 August 2011
Online Registration is closed, but OnSite registration is possible.
26 July 2011
Updated info about venue, etc.
18 June 2011
Program published
13 June 2011
EXTENSION: Doctoral Symposium has the submission site open for 12 more hours (i.e., until midnight, Oslo time).
7 June 2011
Registration page for the main conference is open.
6 June 2011
Author notification: list of accepted papers available
03 June 2011
Submission site opened for the Doctoral Symposium.
04 Apr. 2011
Deadline Extension: submission deadline has been extended to 14 April (midnight Hawaii time)
29 Mar. 2011
Sponsorships are available for participants. See Registration page for details on eligibility criteria.
16 Feb. 2011
FCT 2011 is honored by the invited speakers:
11 Feb. 2011
One can use the FCT11 Posters for display with the purpose of advertising the FCT 2011 symposium.
31 Jan. 2011
A Doctoral Symposium event will be associated with the FCT 2011. See the specific CFP.
10 Jan. 2011
First call for workshops is out
15 Dec. 2010
First call for papers is out
14 Dec. 2010
Web Page is up
< Basic Variables | Variables | Edit Variables >
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;
- ?action=ruleset
- displays a list of all markups in 3 columns:
- column 1 = markup-name (1. parameter of markup() )
- column 2 = when will rule apply (2. parameter of markup() )
- column 3 = PmWiki's internal sort key (derived from #2)
?action=ruleset
gives you, apply the Cookbook:MarkupRulesetDebugging recipe: it can also show the pattern and the replacement strings.
- doesn't make use of PmWiki's authorization mechanisms.
- ?action=phpinfo
- displays the output of phpinfo() and exits. no page will be processed
- doesn't make use of PmWiki's authorization mechanisms.
- ?action=diag
- displays a dump of all global vars and exits. no page will be processed
- doesn't make use of PmWiki's authorization mechanisms.
$EnableIMSCaching
- A variable which, when set equal to 1, recognizes the "If-Modified-Since" header coming from browsers and allows browsers to use locally cached pages. Disabled by default to help the administrator customize its page without needing permanent reloading.
$EnableStopWatch
- This activates an internal stopwatch that shows how long it takes to render a page. (If you have a wiki that composes a HTML page from multiple pages, such as a normal layout with a sidebar, you'll get separate timings for each subpage and for the total page.)
- The timings can be displayed by adding
<!--function:StopWatchHTML 1-->
in the wiki template. - Valid values are:
$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 Stopwatch for more details.
See also:
- scripts/refcount.php is useful for debugging
Is it possible for someone with admin priviledges to always have access to debugging tools, without letting everyone else access them?
You can easily & automatically allow debugging for anyone with admin priviledges (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 AuthUser or other priviledge settings:
if (CondAuth($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.