Articles in this series

  • Anatomy of Magento's xml files

Author - Kristof Ringleff

Hi I'm Kristof the founder of Fooman. I will share some of my experiences gained from developing Magento extensions since version 1.0 here on MageBase.

You can see a list of all my open source and commercial extensions on Magento Connect.

More Info »

Reader Comments (5)

  1. Alan Storm
    May 28, 2010 at 2:33 am /

    All good advice, in particular the advice to avoid CamelCasing in class names. PHP has case insensitive classnames but the files Magento will be autoloading will most likely not being case insensitive. That one killed an hour or so.

    You might want to checkout Configlint. It’s an open source/free project that’s aimed at providing a set of rules to validate Magento’s config files

    http://github.com/astorm/Configlint

    Reply
  2. Alan
    May 30, 2010 at 6:49 am /

    Good tip, although there’s no way (that I know of) to override the autoloader without replacing the entire class the local hierarchy. That works well for local development, but I’d be wary of replacing that file in something that I was distributing.

    Reply
  3. Alan
    Alan
    June 1, 2010 at 8:28 am /

    You’re right, code is a lot better than words sometimes. I just pushed a branch with your ideas broken out into a new lint module. Anyone interested just drop by the link mentioned above.

    Reply

Add a Comment & Join the Discussion

Insert small snippets of code by using [code]{your_code_here}[/code]
For larger code blocks please use http://pastebin.com and paste your link.

You may also use the following HTML in your comment: <a href="" title=""> <abbr title="">
<acronym title=""> <blockquote cite=""> <cite> <em> <strike> <strong>