Wouldn't it be lovely if we could control where it gets dumped? In a little hover over popup bug or something for eaxmple. It would also be nice to be able to edit the 'view' used to display this debug table, and allow us to do things like display it as a JSON object. That would be particularly helpful for debugging ajax endpoints, since the sql could be browsed in firebug for example.
Worth an RFE? Worth the dev time? You decide... Simon http://www.simonellistonball.com/ On Apr 4, 1:15 pm, grigri <[EMAIL PROTECTED]> wrote: > The SQL log is generated and output independently of the $cakeDebug > variable, which contains the controller dump for debug level 3. > > To get rid of the dump you need to be in debug level 0 or 1. There > might be another switch to turn it off specifically, but I don't know > it (especially not for 1.1) > > On Apr 4, 12:48 pm, aka <[EMAIL PROTECTED]> wrote: > > > Hi! > > > I'm using the latest stable release (1.1.19.6305). > > > I don't know if this is intended or not, nut when I make a following > > layout: > > > <html> > > <head> > > </head> > > <body> > > <?php echo $content_for_layout; ?> > > </body> > > </html> > > > The SQL-debug still shows on my page like i would have placed <?php > > echo $cakeDebug; ?> inside my layout. > > > This really puzzles my mind :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
