The use the the DEBUG constant is going the way of the dodo in Cake
(or already has).
Yeah use Configure::write/read now.
On Sep 21, 3:04 pm, MattC <[EMAIL PROTECTED]> wrote:
> Hey Mike,
> You can use the same syntax to set the debug level as you saw in the
> Cake code. So after you include the phpBB files put:
> Configure::write('debug', '1');
> Or even better define your own debug, CAKE_DEBUG and use that instead:
> Configure::write('debug', CAKE_DEBUG);
>
> That should overwrite whatever values Cake got from phpBB. You may
> have to mess around to find the best place to put this in your code so
> that it has the desired effect. Your app_controller may be a good
> place.
>
> -Mattwww.pseudocoder.com
>
> On Sep 21, 3:53 pm, MikeK <[EMAIL PROTECTED]> wrote:
>
> > Just checking with the gurus on best practices. My CakePHP application
> > (1.2 based) is bridged to phpBB for Authentication, ACL and a number
> > of other features. WEBROOT/index.php has some code at the very top
> > that imports appropriate modules from phpBB to setup phpBB sessions
> > and vars that runs on every page I load -- no problem all works well.
>
> > The issue I have is the redefinition of DEBUG. Both CakePHP and phpBB
> > use DEBUG. Regardless of what I set DEBUG to in core.php, it gets
> > redefined to whatever it is set to in my phpBB installation (usually
> > 0) when those files are included by WEBROOT/index.php (ala the
> > ordering in index.php for Cake top level). For development I have been
> > running with phpBB in debug mode (1), but now as I deploy I really
> > want to run Cake in DEBUG=1 and phpBB at DEBUG=0. I have a significant
> > website that really needs to run phpBB with DEBUG=0 for performance
> > sake.
>
> > After grepping both source trees Cake has far fewer uses of the
> > constant, and appears to primarily use it to set the value of through
> > a Conf::write('debug', DEBUG). I am considering renameing DEBUG
> > throughout the Cake source tree to be CAKE_DEBUG so I can get
> > individual control of these constants and debugging for these bridged
> > packages.
>
> > Am I missing some better method of how to get this level of control of
> > debugging? I hate to hack up either distribution...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
