Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat are the possible tags inside the "global" tag in Magento "config.xml" file?
    text
    copied!<p>Can some professional experienced Magento developer tell me how to accomplish the following in Magento?</p> <p><strong>I want to know what are the possible tags that can fit in the "global" tag of the "config.xml" page of every module's etc folder?</strong></p> <p>I have tried searching for this answer at many places in Internet but in vain.</p> <p>Please provide the full details along with it for <strong>Magento version >= 1.4.0.0</strong>, because I want at least the users accessing this website find it useful enough, instead of scratching their heads.</p> <p>I really want a detailed explanation, because every newbie like me gets totally confused at this point. From what I know till now, is that in this page, you can set routers, rewrites, cron jobs, admin html, front-end html and many more. But without any strong concepts, none can go ahead with the belief that his code is 100% correct w.r.t. the Magento MVC architecture.</p> <p>So please I want that strong fundamental concept, getting underlined here, with a detailed explanation about it, so that no one gets into this pitfall ever again.</p> <p>I can understand one thing - for many it looks that a complete reference of valid global tags of Magento would be a misnomer, but I would like to clarify that there must be a set of those valid limited number of tags that goes under the global tag.</p> <p>For example, I cannot just write a "stack" or "overflow" or "joseph" tag, which I'm quite sure that it will not be taken by Magento as a valid one. It is because the valid tags (like "models", "resources", "resource" &amp; so on) are defined somewhere in Magento configuration, that they work.</p> <p>This is my point actually, which I want to emphasize.</p> <p>Many many thanks to those who can answer only upon knowing the total concept clearly.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload