[TYPO3-core] RFC #16463: Bug: Custom configured modules can't be enabled for non-admins

Bastian Waidelich bastian.waidelich at typo3.org
Thu Nov 25 09:59:53 CET 2010


Bastian Waidelich wrote:

REMINDER #1
I think, it's crucial that this one is fixed in the release

> Hi all,
>
> This is an SVN patch request.
>
> Type: Bugfix
>
> Bugtracker references:
> http://bugs.typo3.org/view.php?id=16463
>
> Branches:
> trunk, 4.4(?)
>
> Problem:
> When registering a BE module in your extension by specifying a custom
> configureModuleFunction handler (in
> $GLOBALS['TBE_MODULES']['_configuration'][$name]['configureModuleFunction']),
> the module won't show up in the BE user / BE group TCE form, making it
> impossible to enable it for non-admins.
>
> Solution:
> The problem is, that the method checkModAccess() is not called in
> t3lib_loadModules. This method has the side effect of adding the module
> to the modListUser/modListGroup array. See attached patch.
>
> Notes:
> Without the patch, the module won't show up in the BE user / BE group
> TCE form but it will be visible to all users!
> So actually the module will be *always active* unless the module checks
> the access again.
> Sidenode: This affects all Extbase modules. There the access is checked
> again in the bootstrap, leading to an exception when the user tries to
> load the module.
>
> All the best and happy birthday, beta1
> Bastian



More information about the TYPO3-team-core mailing list