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 (14)

  1. Vinai Kopp
    October 12, 2010 at 7:03 pm /

    You can influence the module load order by usind . in the files. This will override the alphabetical load order.

    Reply
  2. Graham
    October 12, 2010 at 9:19 pm /

    Good tip about the local vs. communitry.

    FYI I’m using this extension to resolve conflicts, it also suggests a resolution – its really quite good:

    http://www.magentocommerce.com/magento-connect/Maison+du+Logiciel/extension/2477/magento-conflict

    Reply
  3. Vinai Kopp
    October 13, 2010 at 8:00 am /

    The XML Tags where filtered out of my previous post – sorry about that!
    Here how the >depends< node can be used in the app/etc/modules/*.xml files:

    <Mage_Admin>
    <active>true</active>
    <codePool>core</codePool>
    <depends>
    <Mage_Core/>
    </depends>
    </Mage_Admin>

    This XML ensures the Mage_Core extension already is loaded when the Mage_Admin extension is loaded, even though it is behind it in alphabetical order.
    I sure hope this post doesn’t loose the XML again…
    Vinai

    Reply
  4. Robert
    October 13, 2010 at 5:36 pm /

    Nice tip Vinai, also, the <depends> tag forces the extension to check the dependencies so if you develop an extension that depends on a less used core extension which may have been disabled via the modules XML, this is very useful. Same goes, if your extension should depend on another installed third party extension.

    For example if you disable Mage_Wishlist in the modules XML, you will get an error report saying:
    Module "Mage_Rss" requires module "Mage_Wishlist. Since Mage_Rss depends on Mage_Wishlist,

    Reply
  5. Magento-Links der Woche KW41 | magelounge

    [...] Magento Extension Clashes – Winners and Loosers [...]

  6. Using A Backend Model To Customize Magento (A Tip From Magento Developers Paradise)

    [...] functionality in the save method. It works no matter how the object is saved, but is open to extension clash hell which is not appealing. (I’ve grouped these two together, because they’re mostly the [...]

  7. Kashif
    December 29, 2010 at 1:26 am /

    very helpful and informative article. keep up the good work

    Reply
  8. Faisal
    January 11, 2011 at 4:52 am /

    I liked this article a lot. I have a client that wants to load lots of extensions – the number is actually hovering around 50. Can magento extensions affect the magento performance?

    Reply
  9. Robert G
    Robert G
    January 13, 2011 at 4:28 am /

    I have multidomain site that is not working. Its a live site, so it very serious.

    The conflict manager shows 12 conflicts (4 of them with a Fooman extension and 2 of them with Netzarbeiter extension) Please take notice that Fooman and Netzarbejder extensions do not conflict with each other.

    The conflicts are mainly with extensions from Maison du logiciel (ERP), the originater of the above conflict manager. I find all this amusing since all the players are active or mentioned in the post.
    In terms winners and losers, I feel I am the loser.

    The other conflicts are with extension from:
    Amasty (order- and custumer attributes)
    Tiny Brick (True edit)
    Aitoc (advanced permissions).

    Actually I am very stressed and have had sleepless nights and find it very difficult to stay friends with magento.

    Will some sweet magento superhero please save me and my site?
    I am desperate to get my up and running again.

    I have 2 test sites running to resolve the issues. One where I have installed MDN extensions first and 1 where i have installed everything except MDN extensions.
    I have purchased alternative extensions from other suppliers in hope thay will not conflict.

    Here is my goal:
    Multi domain site (no problem)
    Advanced permissions pr domain (The Aitoc extension).
    Access control for B2B domain (site locked, no visible products) (Netzarbeiter ext.)
    registration before access with more details: Company, VAT nr, + addtional fields (Amasty ext.)
    Customized PDF invoices, shipping notes (Fooman extension)
    Point of sales for the brick and mortar shop (POS ext. from Maison du Logiciel).
    editable orders without destroying creditcard transaction (true edit from tiny brick).
    customer can add order nr. which will be on shipping note and invoice (not solved)
    one step checkout for all domains (fire checkout from templates master, looks like a winner)
    And most important: NO CONFLICTS
    If I get the above to work I can go from loser to winner also

    Please please please write to krp@atrading.dk if you can help

    Reply
  10. Magento dev notes: conflicting extensions

    [...] finally, here’s an excellent / slightly confounding exposé: http://magebase.com/magento-tutorials/magento-extension-clashes-winners-and-loosers/ This entry was posted in Uncategorized and tagged magento, php, programming, webdev. Bookmark the [...]

  11. Chris Campbell
    August 10, 2011 at 9:16 pm /

    Thanks Fooman You have just save me paying someone to sort out the problem. All I need to do was to change the load order and back in business. A simple “AA” did the trick.

    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>