Comments on: Debugging Magento using Krumo http://activecodeline.com/debugging-magento-using-krumo Blog site of Branko Ajzele, web application developer. Tue, 07 Sep 2010 11:26:00 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: branko http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-3881 branko Sat, 23 May 2009 15:37:27 +0000 http://activecodeline.com/?p=141#comment-3881 People, people, people... I'm closing the comments for this post. I wrote it when I was first starting out with Magento. I use completely diferent and far more better debugging mechanisms for Magento. I really appreciate the feedback, but this post is old stuff. People, people, people… I’m closing the comments for this post. I wrote it when I was first starting out with Magento. I use completely diferent and far more better debugging mechanisms for Magento.

I really appreciate the feedback, but this post is old stuff.

]]> By: branko http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-5061 branko Sat, 23 May 2009 15:37:00 +0000 http://activecodeline.com/?p=141#comment-5061 People, people, people... I'm closing the comments for this post. I wrote it when I was first starting out with Magento. I use completely diferent and far more better debugging mechanisms for Magento. I really appreciate the feedback, but this post is old stuff. People, people, people… I’m closing the comments for this post. I wrote it when I was first starting out with Magento. I use completely diferent and far more better debugging mechanisms for Magento.

I really appreciate the feedback, but this post is old stuff.

]]> By: Michael http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-3880 Michael Sat, 23 May 2009 15:33:08 +0000 http://activecodeline.com/?p=141#comment-3880 Why don't you simply use ? There is also an option in System -> Configuration -> Developer -> Debug -> Template Path Hints and ...... -> Add Block Names To Hints Just make sure to select a website or a store view in the Configuration Scope dropdown in left column, as these options are not displayed on "Default Config" level. Why don’t you simply use ?

There is also an option in System -> Configuration -> Developer -> Debug -> Template Path Hints and …… -> Add Block Names To Hints

Just make sure to select a website or a store view in the Configuration Scope dropdown in left column, as these options are not displayed on “Default Config” level.

]]> By: Michael http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-5060 Michael Sat, 23 May 2009 15:33:00 +0000 http://activecodeline.com/?p=141#comment-5060 Why don't you simply use ? There is also an option in System -> Configuration -> Developer -> Debug -> Template Path Hints and ...... -> Add Block Names To Hints Just make sure to select a website or a store view in the Configuration Scope dropdown in left column, as these options are not displayed on "Default Config" level. Why don’t you simply use ?

There is also an option in System -> Configuration -> Developer -> Debug -> Template Path Hints and …… -> Add Block Names To Hints

Just make sure to select a website or a store view in the Configuration Scope dropdown in left column, as these options are not displayed on “Default Config” level.

]]> By: Sean http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-3871 Sean Thu, 21 May 2009 00:22:24 +0000 http://activecodeline.com/?p=141#comment-3871 I like Java, too. Every time I try debugging something in PHP I like Java a little more :) But Java web development, that's a whole other story... I like Java, too. Every time I try debugging something in PHP I like Java a little more :) But Java web development, that’s a whole other story…

]]> By: Anonymous http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-5059 Anonymous Thu, 21 May 2009 00:22:00 +0000 http://activecodeline.com/?p=141#comment-5059 I like Java, too. Every time I try debugging something in PHP I like Java a little more :) But Java web development, that's a whole other story... I like Java, too. Every time I try debugging something in PHP I like Java a little more :) But Java web development, that’s a whole other story…

]]> By: Marco http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-3775 Marco Tue, 28 Apr 2009 09:28:00 +0000 http://activecodeline.com/?p=141#comment-3775 Hi Gustavo, by saying there is no Java framework for ecommerce you are wrong. Check out apache ofbiz: http://ofbiz.apache.org/ but I think magento is the mightier one. best regards, Marco Hi Gustavo,

by saying there is no Java framework for ecommerce you are wrong. Check out apache ofbiz: http://ofbiz.apache.org/

but I think magento is the mightier one.

best regards, Marco

]]> By: Marco http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-5058 Marco Tue, 28 Apr 2009 09:28:00 +0000 http://activecodeline.com/?p=141#comment-5058 Hi Gustavo, by saying there is no Java framework for ecommerce you are wrong. Check out apache ofbiz: http://ofbiz.apache.org/ but I think magento is the mightier one. best regards, Marco Hi Gustavo,

by saying there is no Java framework for ecommerce you are wrong. Check out apache ofbiz: http://ofbiz.apache.org/

but I think magento is the mightier one.

best regards, Marco

]]> By: branko http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-3722 branko Sun, 19 Apr 2009 05:48:25 +0000 http://activecodeline.com/?p=141#comment-3722 @Gustavo Java, as well as C# (which I know a bit :)) are THE kick ass programming languages. When it comes to debugging requirements PHP cannot measure with those two. Main difference (in my opinion) is that PHP is not strongly typed, therefore debuggers broke and broke and broke.... God knows I tried XDebug and bunch of other debugging solutions... NONE of them will work on complex systems like Magento. I've read tens of so called Debugging HowTO's, but they all seem to be based on "Here's my index.php and my sample.php file. No let me include one in another and run the debugging." Yea, good luck with that approach. Anyhow, I ended using my custom class that I extended from Exception class (PHP built one) and ended using something like "<?php new acl($someVariable, "Some description, if any") ?>" where "acl" is the name of my custom class. Inside the class I made it to to various things, one of which is output to FireBug (FirePHP). Why inherit from Exception? -This enabled me to get name and line of file where I called it. Hope this helps. @Gustavo

Java, as well as C# (which I know a bit :) ) are THE kick ass programming languages. When it comes to debugging requirements PHP cannot measure with those two. Main difference (in my opinion) is that PHP is not strongly typed, therefore debuggers broke and broke and broke…. God knows I tried XDebug and bunch of other debugging solutions… NONE of them will work on complex systems like Magento. I’ve read tens of so called Debugging HowTO’s, but they all seem to be based on “Here’s my index.php and my sample.php file. No let me include one in another and run the debugging.” Yea, good luck with that approach. Anyhow, I ended using my custom class that I extended from Exception class (PHP built one) and ended using something like “< ?php new acl($someVariable, "Some description, if any") ?>” where “acl” is the name of my custom class. Inside the class I made it to to various things, one of which is output to FireBug (FirePHP). Why inherit from Exception? -This enabled me to get name and line of file where I called it. Hope this helps.

]]> By: branko http://activecodeline.com/debugging-magento-using-krumo/comment-page-1#comment-5057 branko Sun, 19 Apr 2009 05:48:00 +0000 http://activecodeline.com/?p=141#comment-5057 @Gustavo Java, as well as C# (which I know a bit :)) are THE kick ass programming languages. When it comes to debugging requirements PHP cannot measure with those two. Main difference (in my opinion) is that PHP is not strongly typed, therefore debuggers broke and broke and broke.... God knows I tried XDebug and bunch of other debugging solutions... NONE of them will work on complex systems like Magento. I've read tens of so called Debugging HowTO's, but they all seem to be based on "Here's my index.php and my sample.php file. No let me include one in another and run the debugging." Yea, good luck with that approach. Anyhow, I ended using my custom class that I extended from Exception class (PHP built one) and ended using something like "" where "acl" is the name of my custom class. Inside the class I made it to to various things, one of which is output to FireBug (FirePHP). Why inherit from Exception? -This enabled me to get name and line of file where I called it. Hope this helps. @Gustavo

Java, as well as C# (which I know a bit :) ) are THE kick ass programming languages. When it comes to debugging requirements PHP cannot measure with those two. Main difference (in my opinion) is that PHP is not strongly typed, therefore debuggers broke and broke and broke…. God knows I tried XDebug and bunch of other debugging solutions… NONE of them will work on complex systems like Magento. I’ve read tens of so called Debugging HowTO’s, but they all seem to be based on “Here’s my index.php and my sample.php file. No let me include one in another and run the debugging.” Yea, good luck with that approach. Anyhow, I ended using my custom class that I extended from Exception class (PHP built one) and ended using something like “” where “acl” is the name of my custom class. Inside the class I made it to to various things, one of which is output to FireBug (FirePHP). Why inherit from Exception? -This enabled me to get name and line of file where I called it. Hope this helps.

]]>