Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The fast answer is that there is no complete list of those tags. Magento doesn't use a strict grammar for XML files because they can be extended without any trouble. Looking at the 1.4 codebase, I performed the following command from a terminal:</p> <pre><code>cd /path/to/magento grep -r global/ . 2&gt;/dev/null | grep -v pearlib | grep php | sort </code></pre> <p>And got back about 75 lines where the global config path is invoked specifically. Some of these are simple:</p> <pre><code>global/page/layouts global/pdf/totals global/template/email global/payment/cc/types </code></pre> <p>And others are far more obscure:</p> <pre><code>global/catalog/product/type/configurable/allow_product_types global/helpers/core/encryption_model global/widget/related_cache_types </code></pre> <p>On top of that, there are several which are invoked dynamically, such as your mentioned routers, rewrites, etc:</p> <pre><code>global/models/'.$model.'/resourceMode global/'.$groupType.'s </code></pre> <p>In fact, I even found 4 references in my own extension code that added to the global space. Knowing all that, a complete reference of valid global tags would be a misnomer, and will likely change even during minor updates. To your last point, you cannot go forward with complete assurance that you will be in compliance w/ Magento's configuration model. Do your best to use the objects that are provided with the library, use samples from the rest of the app when possible, and forge ahead bravely when no help is given. :)</p> <p>Hope that helps!</p> <p>Thanks, Joe</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