Well you can't use classes that are not loaded, and Debugger is not loaded when you are not debugging. As for CakeLog it is also not loaded unless you load it first. Instead of using CakeLog::write() I would suggest you either App::import() CakeLog first or use $this->log (). However, it is normal for logging statements to not show up when debug = 0. There are even enhancement tickets on trac to that effect.
-Mark On Jul 8, 8:36 pm, brian <[email protected]> wrote: > I think you meant debug > 0 :-) > > I've seen something similar that I've meant to post about here. I had > some code that included some lines with Debugger::log($something) > that, when I had debug = 0 caused a fatal error. That doesn't seem > right at all. I'd assumed that it would either write to the log anyway > or not at all, but a fatal error seems like a bug. > > > > On Wed, Jul 8, 2009 at 3:25 PM, rb<[email protected]> wrote: > > > After searching the group, I'm seeing there are a few issues when > > debug = 0. > > > My issue is with Cakelog::write. Anytime I use it w/ debug < 0, > > everything renders just fine -- no errors. > > > Once I set debug = 0, the page will show up blank. > > > Is there something about cakephp classes while debug = 0 that I'm not > > aware of? Or has anyone seen this issue before? > > > Thanks.. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
