Re: request for debugging advice
For the record, here is my attempted import:
App::import('Vendor', 'krumo', array('file' => 'krumo/class.krumo.php'));
--
View this message in context:
http://www.nabble.com/request-for-debugging-advice-tp20033875p20063162.html
Sent from the CakePHP mailing list archive at Nabble.com.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" 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
-~--~~~~--~~--~--~---
Re: request for debugging advice
Is anyone able to get Krumo to work by following the Bakery article? http://bakery.cakephp.org/articles/view/nicer-print_r-with-krumo http://bakery.cakephp.org/articles/view/nicer-print_r-with-krumo RyOnLife wrote: > > Took less than 5 minutes for me to give it a crack, but the Bakery article > seems to be a bit outdated: I'm getting a fatal error because the krumo > class cannot be found. I changed from vendor() to App::import in the > helper, but couldn't find anything else. I'm thinking I'm missing another > change needed to make it 1.2 RC3 ready... > > > > grigri wrote: >> >> >> I think there's a bakery article on it... >> >> yep, here it is: >> http://bakery.cakephp.org/articles/view/nicer-print_r-with-krumo >> >> I couldn't get the skin images to work with that, but it was a long >> time ago - cake has got better since. >> >> Let us know how you get on, if it works well I might start using it >> again! >> >> On Oct 17, 4:02 pm, RyOnLife <[EMAIL PROTECTED]> wrote: >>> Having trouble getting it to work. I just dropped the class into my >>> include_path, required it, then tried both krumo($var) (call to >>> undefined >>> function) and krumo::krumo($var) (class not found) with no luck. What's >>> the >>> best way to make it work with Cake? Do I have to turn it into a helper? >>> >>> >>> >>> RyOnLife wrote: >>> >>> > Sweet! Just what I was looking for. Thanks. >>> >>> > grigri wrote: >>> >>> >> You could check out Krumo :http://krumo.sourceforge.net/ >>> >>> >> It's a php debugging solution; makes expandable variables and stuff. >>> >> I've used it in the past with good results. >>> >>> >> hth >>> >> grigri >>> >>> >> On Oct 17, 3:05 pm, RyOnLife <[EMAIL PROTECTED]> wrote: >>> >>> Just to clarify... What I really like about firecake.php and the >>> FireBug >>> >>> output is that the arrays are expandable/collapsible. That's the >>> >>> functionality I'd like to find in another debugging solution. >>> >>> >>> RyOnLife wrote: >>> >>> >>> > I've been using the firecake.php helper to aid in my debugging. I >>> >>> > primarily use it to drill into the values held in those big nested >>> >>> arrays >>> >>> > that result from running recursive find() on models. Was working >>> >>> great, >>> >>> > but now I'm getting unterminated string literal errors on the >>> >>> > fbout['Variables'] that gets passed to the header. >>> >>> >>> > After hours of trying to track the problem down, I'm ready to wave >>> the >>> >>> > white flag and try another solution. What's another good way to >>> drill >>> >>> into >>> >>> > the values in variables and arrays? I've been doing >>> print_r($array) >>> >>> and >>> >>> > due to the size of these arrays, it's just not cutting it. >>> >>> >>> > Thanks, >>> >>> > Ryan >>> >>> >>> -- >>> >>> View this message in >>> >>> >>> context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003397... >>> >>> Sent from the CakePHP mailing list archive at Nabble.com. >>> >>> -- >>> View this message in >>> context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003506... >>> Sent from the CakePHP mailing list archive at Nabble.com. >> >> >> >> > > -- View this message in context: http://www.nabble.com/request-for-debugging-advice-tp20033875p20062944.html Sent from the CakePHP mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~--~~~~--~~--~--~---
Re: request for debugging advice
Took less than 5 minutes for me to give it a crack, but the Bakery article seems to be a bit outdated: I'm getting a fatal error because the krumo class cannot be found. I changed from vendor() to App::import in the helper, but couldn't find anything else. I'm thinking I'm missing another change needed to make it 1.2 RC3 ready... grigri wrote: > > > I think there's a bakery article on it... > > yep, here it is: > http://bakery.cakephp.org/articles/view/nicer-print_r-with-krumo > > I couldn't get the skin images to work with that, but it was a long > time ago - cake has got better since. > > Let us know how you get on, if it works well I might start using it > again! > > On Oct 17, 4:02 pm, RyOnLife <[EMAIL PROTECTED]> wrote: >> Having trouble getting it to work. I just dropped the class into my >> include_path, required it, then tried both krumo($var) (call to undefined >> function) and krumo::krumo($var) (class not found) with no luck. What's >> the >> best way to make it work with Cake? Do I have to turn it into a helper? >> >> >> >> RyOnLife wrote: >> >> > Sweet! Just what I was looking for. Thanks. >> >> > grigri wrote: >> >> >> You could check out Krumo :http://krumo.sourceforge.net/ >> >> >> It's a php debugging solution; makes expandable variables and stuff. >> >> I've used it in the past with good results. >> >> >> hth >> >> grigri >> >> >> On Oct 17, 3:05 pm, RyOnLife <[EMAIL PROTECTED]> wrote: >> >>> Just to clarify... What I really like about firecake.php and the >> FireBug >> >>> output is that the arrays are expandable/collapsible. That's the >> >>> functionality I'd like to find in another debugging solution. >> >> >>> RyOnLife wrote: >> >> >>> > I've been using the firecake.php helper to aid in my debugging. I >> >>> > primarily use it to drill into the values held in those big nested >> >>> arrays >> >>> > that result from running recursive find() on models. Was working >> >>> great, >> >>> > but now I'm getting unterminated string literal errors on the >> >>> > fbout['Variables'] that gets passed to the header. >> >> >>> > After hours of trying to track the problem down, I'm ready to wave >> the >> >>> > white flag and try another solution. What's another good way to >> drill >> >>> into >> >>> > the values in variables and arrays? I've been doing print_r($array) >> >>> and >> >>> > due to the size of these arrays, it's just not cutting it. >> >> >>> > Thanks, >> >>> > Ryan >> >> >>> -- >> >>> View this message in >> >>> >> context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003397... >> >>> Sent from the CakePHP mailing list archive at Nabble.com. >> >> -- >> View this message in >> context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003506... >> Sent from the CakePHP mailing list archive at Nabble.com. > > > > -- View this message in context: http://www.nabble.com/request-for-debugging-advice-tp20033875p20035626.html Sent from the CakePHP mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~--~~~~--~~--~--~---
Re: request for debugging advice
Having trouble getting it to work. I just dropped the class into my include_path, required it, then tried both krumo($var) (call to undefined function) and krumo::krumo($var) (class not found) with no luck. What's the best way to make it work with Cake? Do I have to turn it into a helper? RyOnLife wrote: > > Sweet! Just what I was looking for. Thanks. > > > grigri wrote: >> >> >> You could check out Krumo : http://krumo.sourceforge.net/ >> >> It's a php debugging solution; makes expandable variables and stuff. >> I've used it in the past with good results. >> >> hth >> grigri >> >> On Oct 17, 3:05 pm, RyOnLife <[EMAIL PROTECTED]> wrote: >>> Just to clarify... What I really like about firecake.php and the FireBug >>> output is that the arrays are expandable/collapsible. That's the >>> functionality I'd like to find in another debugging solution. >>> >>> >>> >>> RyOnLife wrote: >>> >>> > I've been using the firecake.php helper to aid in my debugging. I >>> > primarily use it to drill into the values held in those big nested >>> arrays >>> > that result from running recursive find() on models. Was working >>> great, >>> > but now I'm getting unterminated string literal errors on the >>> > fbout['Variables'] that gets passed to the header. >>> >>> > After hours of trying to track the problem down, I'm ready to wave the >>> > white flag and try another solution. What's another good way to drill >>> into >>> > the values in variables and arrays? I've been doing print_r($array) >>> and >>> > due to the size of these arrays, it's just not cutting it. >>> >>> > Thanks, >>> > Ryan >>> >>> -- >>> View this message in >>> context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003397... >>> Sent from the CakePHP mailing list archive at Nabble.com. >> >> >> >> > > -- View this message in context: http://www.nabble.com/request-for-debugging-advice-tp20033875p20035064.html Sent from the CakePHP mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~--~~~~--~~--~--~---
Re: request for debugging advice
I think there's a bakery article on it... yep, here it is: http://bakery.cakephp.org/articles/view/nicer-print_r-with-krumo I couldn't get the skin images to work with that, but it was a long time ago - cake has got better since. Let us know how you get on, if it works well I might start using it again! On Oct 17, 4:02 pm, RyOnLife <[EMAIL PROTECTED]> wrote: > Having trouble getting it to work. I just dropped the class into my > include_path, required it, then tried both krumo($var) (call to undefined > function) and krumo::krumo($var) (class not found) with no luck. What's the > best way to make it work with Cake? Do I have to turn it into a helper? > > > > RyOnLife wrote: > > > Sweet! Just what I was looking for. Thanks. > > > grigri wrote: > > >> You could check out Krumo :http://krumo.sourceforge.net/ > > >> It's a php debugging solution; makes expandable variables and stuff. > >> I've used it in the past with good results. > > >> hth > >> grigri > > >> On Oct 17, 3:05 pm, RyOnLife <[EMAIL PROTECTED]> wrote: > >>> Just to clarify... What I really like about firecake.php and the FireBug > >>> output is that the arrays are expandable/collapsible. That's the > >>> functionality I'd like to find in another debugging solution. > > >>> RyOnLife wrote: > > >>> > I've been using the firecake.php helper to aid in my debugging. I > >>> > primarily use it to drill into the values held in those big nested > >>> arrays > >>> > that result from running recursive find() on models. Was working > >>> great, > >>> > but now I'm getting unterminated string literal errors on the > >>> > fbout['Variables'] that gets passed to the header. > > >>> > After hours of trying to track the problem down, I'm ready to wave the > >>> > white flag and try another solution. What's another good way to drill > >>> into > >>> > the values in variables and arrays? I've been doing print_r($array) > >>> and > >>> > due to the size of these arrays, it's just not cutting it. > > >>> > Thanks, > >>> > Ryan > > >>> -- > >>> View this message in > >>> context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003397... > >>> Sent from the CakePHP mailing list archive at Nabble.com. > > -- > View this message in > context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003506... > Sent from the CakePHP mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~--~~~~--~~--~--~---
Re: request for debugging advice
Sweet! Just what I was looking for. Thanks. grigri wrote: > > > You could check out Krumo : http://krumo.sourceforge.net/ > > It's a php debugging solution; makes expandable variables and stuff. > I've used it in the past with good results. > > hth > grigri > > On Oct 17, 3:05 pm, RyOnLife <[EMAIL PROTECTED]> wrote: >> Just to clarify... What I really like about firecake.php and the FireBug >> output is that the arrays are expandable/collapsible. That's the >> functionality I'd like to find in another debugging solution. >> >> >> >> RyOnLife wrote: >> >> > I've been using the firecake.php helper to aid in my debugging. I >> > primarily use it to drill into the values held in those big nested >> arrays >> > that result from running recursive find() on models. Was working great, >> > but now I'm getting unterminated string literal errors on the >> > fbout['Variables'] that gets passed to the header. >> >> > After hours of trying to track the problem down, I'm ready to wave the >> > white flag and try another solution. What's another good way to drill >> into >> > the values in variables and arrays? I've been doing print_r($array) and >> > due to the size of these arrays, it's just not cutting it. >> >> > Thanks, >> > Ryan >> >> -- >> View this message in >> context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003397... >> Sent from the CakePHP mailing list archive at Nabble.com. > > > > -- View this message in context: http://www.nabble.com/request-for-debugging-advice-tp20033875p20034773.html Sent from the CakePHP mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~--~~~~--~~--~--~---
Re: request for debugging advice
You could check out Krumo : http://krumo.sourceforge.net/ It's a php debugging solution; makes expandable variables and stuff. I've used it in the past with good results. hth grigri On Oct 17, 3:05 pm, RyOnLife <[EMAIL PROTECTED]> wrote: > Just to clarify... What I really like about firecake.php and the FireBug > output is that the arrays are expandable/collapsible. That's the > functionality I'd like to find in another debugging solution. > > > > RyOnLife wrote: > > > I've been using the firecake.php helper to aid in my debugging. I > > primarily use it to drill into the values held in those big nested arrays > > that result from running recursive find() on models. Was working great, > > but now I'm getting unterminated string literal errors on the > > fbout['Variables'] that gets passed to the header. > > > After hours of trying to track the problem down, I'm ready to wave the > > white flag and try another solution. What's another good way to drill into > > the values in variables and arrays? I've been doing print_r($array) and > > due to the size of these arrays, it's just not cutting it. > > > Thanks, > > Ryan > > -- > View this message in > context:http://www.nabble.com/request-for-debugging-advice-tp20033875p2003397... > Sent from the CakePHP mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~--~~~~--~~--~--~---
Re: request for debugging advice
Just to clarify... What I really like about firecake.php and the FireBug output is that the arrays are expandable/collapsible. That's the functionality I'd like to find in another debugging solution. RyOnLife wrote: > > I've been using the firecake.php helper to aid in my debugging. I > primarily use it to drill into the values held in those big nested arrays > that result from running recursive find() on models. Was working great, > but now I'm getting unterminated string literal errors on the > fbout['Variables'] that gets passed to the header. > > After hours of trying to track the problem down, I'm ready to wave the > white flag and try another solution. What's another good way to drill into > the values in variables and arrays? I've been doing print_r($array) and > due to the size of these arrays, it's just not cutting it. > > Thanks, > Ryan > -- View this message in context: http://www.nabble.com/request-for-debugging-advice-tp20033875p20033974.html Sent from the CakePHP mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~--~~~~--~~--~--~---
