In system and widget xml file of custom module I use source_model tag. First I used this:


but then there was conflict with another extension because modulename was the same. After that I changed it to this:


I am wondering if there is any downside of using the second one or if there can be be any problems with Magento compilation?

1 Answer 1


Take a look at Same module name with different namespace conflicting in magento

I would strongly suggest renaming your module. By default when magento merge all the config files it will only use the last module config (in alphabetical order or using the depend option order). So anything within your module that uses the model e.g Mage::getModel('modulename/xyz') should not work (since your module seem to be the first one loaded during the merge).

  • I need to keep the same name because of old customers who upgrade extension with new version. There is no problem with model because you can add company to model (e.g. Mage::getModel('companyname_modulename/xyz')) if you define such in config file. So my only question is now about if there is any potential problem when using the mentioned name convention for source_model tag inside system xml.
    – JohnyFree
    Jun 20, 2015 at 15:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.