How to fix 3rd party extension conflicts?

Amasty modules are efficient feature-rich extensions that helps you to get the best out of Magento. Unfortunately, sometimes the functionality of the extensions can be hindered by the conflicts with the 3rd party extensions. Have you experienced any difficulties of this sort?    

Here we have collected the most effective methods to fix conflicts with the 3rd party extensions:

1) Deactivate a conflicting module

First, check if the functionality of a 3rd party conflicting module is necessary for your Magento store.

• Mostly, the conflicting extensions have similar functionality. And often the Amasty extensions include the functionality of similar plugins, so the functionality of the 3rd party extension is simply redundant.
• Also, there are cases, when the 3rd party extension is enabled, but either is not functioning or not supported any longer. And, in this case, it is better to disable it.

To disable a module, do the following steps:

• Open a file app/etc/modules/MODULE.xml  
• Edit the file, changing true to false.
• Flush the cache.

This way you completely disable the extension and it doesn't affect any Magento functionality.

NOTE: Disabling an extension in System -> Configuration -> Advanced does not deactivate the extension totally. It may be still partially working.

2) Troubleshooter

You can try to fix the conflict via our troubleshooter. Though this method cannot guarantee 100% solution, in some cases this can be really effective:

• Go to admin panel -> System -> Amasty Extensions -> Extensions & Notifications -> Troubleshooter
• Look for the conflicts that relate to Amasty conflicting extension and click Fix.
• Flush the cache, and check the performance. In case a problem remains and the extension is not working, click Rollback and try out other offered solutions.

3) Dependencies

Besides the above-mentioned methods, you can as well fix the conflicts with a help of manipulation with dependencies.

Magento has a special <depends> module configuration, that helps to cope with the conflicts between the modules.

For instance, there is a conflict with Amasty_X and some 3rd party extension, say, Company_Module. To create the dependency properly, you have to define the right loading order. For instance, we want to run Amasty_X extension after the 3rd party extension for the appropriate work. We need to do the following:

• 1) Open the file app/etc/modules/Amasty_X.xml
• 2) Edit:

<config>

 <module>

  <Amasty_X>

   <depends>

     <Company_Module/>

   </depends>

  </Amasty_X>

 </module>

</config>

If you still experience any difficulties, please don't hesitate to contact our support engineers.