Frustrated by Magento? Then you’ll love Commerce Bug, the must have debugging extension for anyone using Magento. Whether you’re just starting out or you’re a seasoned pro, Commerce Bug will save you and your team hours everyday. Grab a copy and start working with Magento instead of against it.

Updated for Magento 2! No Frills Magento Layout is the only Magento
front end book you'll ever need. Get your copy
today!

I’m taking a quick break from the Magento series as I plumb the depth of EAV and get through a crunch phase at The Day Job™. In the selfless interest of helping out the internet and the selfish interest of keeping my front page free of moldy content, I thought I’d pass on a simple Controller dispatch logging patch for Magento. This is mainly useful when you’re setting up a new Module and can’t figure out why Magento won’t see it, or if Magento keeps throwing the CMS 404 page in your face

A Few Caveats

These files are not a true Magento Module. While powerful, creating something like this with Magento’s override system would be an order of magnitude harder

Because of the above, I can’t make any promises about using this with a anything but Magento version 1.3.2.3

Standard caveats about production servers apply. Use at your own risk, no warranties, etc.

You’ll also see a message whenever Magento can’t make a Module, Controller, or Action Method match, which is useful when debugging 404 problems.

Like this article? Then you’ll love Commerce Bug, the must have debugging extension for anyone using Magento. Whether you’re just starting out or you’re a seasoned pro, Commerce Bug will save you and your team hours everyday. Grab a copy and start working with Magento instead of against it.