I hope you’re enjoying the Dispatch/Router series we’re in the middle of. The last few articles are coming along, and it looks like we’ll be able to get through the
Default router objects, as well as cover the URL rewriting system, in two or three more posts.
Easier MVC Tracking
I’m getting a lot of feedback from people whose main takeaway is
Magento routing is hugely complicated and impossible to track
While Industry Custom™ dictates we discard the word impossible, I tend to agree. Keeping track of all the routing rules in your head at one time is, if not impossible, an impractical distraction. That’s why the first bit of code I ever wrote for Commerce Bug was the Controller/Request tab
This tab quickly shows you which controller file was used for a request, the inferred module, controller, and action names, as well as the final path information from the request object. More than anything else, what Commerce Bug does it take the tedium out of Magento development, allowing you to free your mind and concentrate on the task at hand.
After a lot of hand wringing and internal debate, I’ve decided to actively solicit donations for my writing here. These articles take time to research, time to edit, and time to test. While they’re a great promotion vehicle for Pulse Storm’s products , anytime I spend on a new series inevitably becomes a future sunk cost.
If you’ve found any of my Magento articles useful, and there’s nothing on the shelf you’re interested in buying, you can use the donation button to below to send a few bucks my way.
No NPR style pledge drive/hostage negotiations here. Getting some financial compensation for writing will certainly help my motivation, but it’s not going to make or break things. If you like what I do here and have the means, I encourage you to donate. If you don’t, continue to read guilt free.
That’s it for now. Thanks again for reading, and for any and all support you’ve provided in the past few years. Stay tuned in via the feed for more Magento demystifying.