On Jul 11, 2:21 pm, brian <[email protected]> wrote:
> On Sat, Jul 11, 2009 at 1:16 AM, mark_story<[email protected]> wrote:
>
> > 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.
>
> The way I see it, if debug = 0, any calls to Debugger::log() should
> simply be ignored, rather than kill the app. I think I'll have a look
> at Trac to see if anything's been posted along these lines. If not,
> I'll post something and make my case.
Your case for loading the Debugger class even in production, even
though it's not needed and just incase someone left a call to
Debugger::foo() in their code?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
