Thank you, Chris. That helped.
I can see xdebug profiling statements in DokuWiki code and I do use xdebug. What I needed to figure out were internal DokuWiki interactions/workflow. Using session_start() helps.
DokuWiki closes the session after its initialisation. You can reopen the session, or comment out the session closing code. Do you need to use a session variable for this?
I use xdebug, every warning/notice/error, including ones I trigger myself, is reported with a function nesting sequence (name, file, line number) to arrive at the point of the error.
Cheers,
Chris
-- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist