Hi Danilo,
On 05 Oct 2011, at 00:01, Danilo Ghirardelli wrote: > > Hi all, > is there in Magnolia a way to listen when a module is stopped and started? I > mean, outside the module's start/stop methods themselves. > My case: we customized the menu for the data module in a project, removing a > couple of the trees shown, but the data module forcefully recreates every > menu item every time the module is restarted (both at startup and after any > change to /modules/data/config). At the moment I have two solutions in mind, > one is to delete the extra menu items at my module startup, which is after > data because depends on it, but this does not cover the case in which data > module is restarted. This is something we've considered (again) recently: restart dependent modules of a given module after it was restarted. Given the time frame and the possible implications, it probably won't make it into 4.5 though. > The other is to deny permission to the extra menu items, even for the > superuser role, but still I don't like this solution, I don't know if there > may be side effects. Overwriting the data module class seems a bit overkill > to me. > The end user will see only the right menu items anyway, because they have > permissions just for those, but I'd like to keep everything clean anyway. > Suggestions welcome as always... :-) Well - perhaps there is room for improvement. I don't know much about the data module, but what with the nested types, it seems like a decent idea to not generate a tree and menu item for every type. Is that your use case ? Are there other cases where the menu entry can generally be superfluous ? Perhaps this could be a simple flag in the type definition/dialog - feel free to report it on Jira and provide a patch ! ;) Cheers, -greg ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
