However all the files are merged together during the parsing process.It will help to understand the XML structure. It is the reason that the module name is repeated as an XML element name (represented below as <(modulename)>) several times through every file - this is necessary to segregate configuration for each module. Without these elements, the configuration in these sections would be overwritten by the configuration files in other modules.
so let us understand the XMl and its ELements ans tructure
Every Config.xml has following elements
The XML sub-structure of each element is described separately below.
1)Modules
<modules>
<(NameSpace_ModuleName)>
<active>[true|false]</active>
<codePool>[core|community|local]</codePool>
<depends>
<(AnotherNameSpace_ModuleName) />
</depends>
<version>(version_number)</version>
</(NameSpace_ModuleName)>
</modules>
so let us understand the XMl and its ELements ans tructure
Every Config.xml has following elements
| modules | global | admin | adminhtml | install | frontend | default | stores | websites |
1)Modules
<modules>
<(NameSpace_ModuleName)>
<active>[true|false]</active>
<codePool>[core|community|local]</codePool>
<depends>
<(AnotherNameSpace_ModuleName) />
</depends>
<version>(version_number)</version>
</(NameSpace_ModuleName)>
</modules>
| active | codePool | depends | version |
