Blog

You have 3 choices for resolving your conflicts:

  Merge your code from one conflicting file into another and switch off the rewrite config.xml in one.

  Switch off the rewrite in one config.xml and then make the conflicting extension PHP file extend the other extension.

  Use the <depends> capability to make one extension depend on another. They will then rewrite in that order.

Which one you choose really does depend on how far you need to go. More often than not even though a class may conflict the actual methods within may not. In this scenario I’d go for option 3. If you have conflicting methods within classes then option 1 or 2 are applicable.

EXAMPLE OF OPTION 2

So originally where you may have had something like below:

  class Class1_Extension_Model_Type_Onepage extends Mage_Checkout_Model_Type_Onepage

You would change it to:

  class Class1_Extension_Model_Type_Onepage extends Class2_Extension_Model_Type_Onepage

Once you have done this you need to change extension Class2 config.xml file commenting out the conflicting “<rewrite>” blocks that are now inheriting from Class1.

EXAMPLE OF OPTION 3

Let’s say you have 2 extensions Briskbraintech_A and Briskbraintech_B. In the module for file Briskbraintech_B (under app/etc/modules) you would add the following:

  <depends Briskbraintech_A />

Now Magento will load the extensions in this order. So in effect the Briskbraintech_B class will be loaded first, then Briskbraintech_A, then base Magento.

We are providing Magento development services in affordable rate and fixing critical issue like conflicts, Magento Migration, Speed optimization, module development and customization on existing functionality.

Thank you!