On Mon, 3 Oct 2005, Alex McLintock wrote:
Can anyone give me an example of how to switch on debugging in Alzabo - in
particular with the Apprentice MasonBook example application running on
Apache 1.3x?
From the docs I basically have to set the environment variable ALZABO_DEBUG
to 'SQL|TRACE' or 'ALL' or something else. I'm doing that in my apache
startup script but nothing seems to be going to the error_log. Is there
another way of doing it?
If you set ALZABO_DEBUG to SQL you'll get all the SQL Alzabo generated.
TRACE is for getting stacktraces out of Alzabo at various points, and is
probably not what you want.
Is Mason trapping the debugging? I can write "print STDERR debugging info" in
mason templates and they seem to come out fine.
Debugging info just goes directly to STDERR all by itself, you can't trap
it (at least for now).
So for a mod_perl app, you can just add this to your Apache config:
PerlSetEnv ALZABO_DEBUG TRACE
Make sure this is set _before_ you load Alzabo.
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
|
