Nevermind...
 
I didn't realize but my logToResults var was set to True!
 
Changing it back to False fixed the issue.  Sorry for the bother.
 

Jim Kass
Web Developer

--
Forestweb: The Source for Industry Intelligence
Best Content -- Most Relevant -- Best Delivery
http://www.forestweb.com
(310) 553 - 0008

-----Original Message-----
From: Jim Kass [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 11, 2003 12:14 PM
To: [EMAIL PROTECTED] Com
Subject: Strange Behaivor...

Hey guys,
 
Anyone ever come across the following situation before?
 
The SYSTEM configuration variable LoggingLevel is actually printing the log results to the screen as if I were in debugmode=forceOn. 
 
No matter what debugmode I set, the logging at the bottom of the screen shows up, unless I set LoggingLevel to "NoLogging", in which case it shows nothing on the screen or the logs.
 
i.e.
If I put LoggingLevel to LogLevel1 - it shows the appfile name that I am accessing... if I put it to LogLevel3, it shows what I am used to seeing when debugMode is forceOn.
 
Anyone have any idea what this is about, or how to resolve it??  This is clearly not the behaivor that I am expecting - LoggingLevel should have nothing to do with debugMode, and when debugMode is set to forceOff - it SHOULD NOT SHOW ANYTHING, regardless of what LoggingLevel is set to.

Jim Kass
Web Developer

--
Forestweb: The Source for Industry Intelligence
Best Content -- Most Relevant -- Best Delivery
http://www.forestweb.com
(310) 553 - 0008

 
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

Reply via email to