Question

There is an existing third-party module that overrides existing Mage functionalities. Let’s call it “Foo”. Obviously, it resides in the local folder in order to override Core functionalities. As I started working on the project, I had yet to create another module to override few features of the Foo module. Let’s call it “Bar”. Both are successfully loaded (backend says it is loaded). The problem is that Foo module still takes precedence over Bar and Bar modules don’t seem to work. I have two questions regarding this:

1. Am I right to speculate that Magento prioritize modules not only by
   Core, Enterprise, local model but also in reverse alphabetical
   order, that is, even if both modules are in local folder, Foo
   superceeds Bar?

2. If this is true, how can I make Bar have precedence over Foo module?

Thanks and hoping somebody could shed some light on this issue.

Answer 1

I assume that you have 2 modules, My_Foo and My_Bar, and you want the Foo to be loaded before Bar.
To do it, in your Bar module xml file (Under /app/etc/modules/My_Bar.xml), just add:

<depends>
<My_Foo/>
</depends>

Now the My_Foo module is loaded before the My_Bar