Timeline for routers and updates node relation in config.xml
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24, 2013 at 7:01 | vote | accept | zamil | ||
| May 17, 2013 at 9:02 | comment | added | zamil | mee to was thinking like that. but for my two installations the above said rule came true,so that created some confusion on me.thats y i decided to put this question in the first place, any way i vl make another isntallation and try again.meanwhile i should say i am using CE 1.7 | |
| May 16, 2013 at 14:43 | comment | added | benmarks |
"if i want any layout updates to work with my custom module the immediate child node that follows the <routers> node should match the <frontName> node value" - There is nothing in the code enforcing this. In fact, all of the core Enterprise modules do not follow this convention and they work fine. The only connection is that the node name at e.g. frontend/routers/[node name] is part of the full action name and therefore is "part" of layout update handles for your module.
|
|
| May 16, 2013 at 6:12 | vote | accept | zamil | ||
| May 24, 2013 at 7:01 | |||||
| May 16, 2013 at 4:56 | comment | added | zamil |
:thanks. but i find that if i want any layout updates to work with my custom module the immediate child node that follows the <routers> node should match the <frontName> node value. or at least it is working like that for me. But routing will work perfect regardless of above said point.please share some knowledge on this
|
|
| May 15, 2013 at 21:00 | history | answered | benmarks | CC BY-SA 3.0 |