Extension Conflicts

When one or more of your extensions are in conflict, they will not function as intended or will not function at all often producing just a blank page.

  • The easiest way to identify which extensions are in conflict is to use the extension conflict tool which can be found below

Once you have found out which extensions are conflicting you will need to change the conflicting file of one extension (lets call it A) to inherit from the other extension (lets call it B).

So originally where you may have had something like:

  • class A_Extension_Model_Type_Onepage extends Mage_Checkout_Model_Type_Onepage

You would change it to:

  • class A_Extension_Model_Type_Onepage extends B_Extension_Model_Type_Onepage

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

You will also need to identify any conflicting phtml files and merge the files into one phtml file incorporating all of the functionality of the multiple files. This means you will also have to edit any related layout xml files to point to the new merged phtml file.


Extension Conflict Tool

We have developed a version of MDNs extension conflict tool which is compatible with PHP5.3 / Magento Enterprise 1.8.

Please find it attached. The original version of this extension is available here

Note: We do offer a conflict resolution service which is charged at an hourly rate. It is not provided as a free service with any extension purchase.


MDM_Extension_Conflict_php5.3_0.2.zip 13k Download
0 votes

Leave a Reply

Featuring WPMU Bloglist Widget by YD WordPress Developer