[TYPO3-core] Dispatch extbase extension without registering it as module.

Fabien Udriot fabien.udriot at ecodev.ch
Fri Oct 11 10:42:22 CEST 2013


After discussing the topic with Steffen Müller again, it looks this could be achieved by adding some
User TSconfig without touching the (Extbase) BE Module API.

I put more details about the syntax and how it can be tested at the bottom of the ticket

I also changed the feature title to be more generic "Control visibility of modules in the BE".


On 10/10/13 4:10 PM, Steffen Müller wrote:
> Hi.
> On 08.10.2013 10:52 Philipp Gampe wrote:
>> We have to different things here:
>> * Modules and their menu structure
>> * Dispatching of scripts (e.g. modules, wizards, etc)
>> Those should be separated in the API instead of faking menu entries that are 
>> hidden, because they are not supposed to be rendered as menu items.
> I agree.
> What about the following solution:
> 1) Leave registerModule() as it is and refactor the API in 6.2+
> 2) Add a feature to 6.2 which allows to hide a module globally, e.g. via
> userTS:
> options.hiddenModules := addToList(web_func)
> This would be much cleaner than putting the configuration into
> registerModule(). Even better: this solution would not be limited to
> extbase modules.
> As a side effect, ControllerActions could be registered for dispatching
> without appearing as a BE module. And that's what is wanted in this
> particular thread :)
> One drawback I see so far: The module would show up in the access list
> list of BE groups.

More information about the TYPO3-team-core mailing list