Bug #24122
closed
Custom configured modules can't be enabled for non-admins
0%
Description
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.
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
(issue imported from #M16463)
Files
Updated by Bastian Waidelich about 14 years ago
To clearify the current behavior: without the patch, the module won't show up in the BE user / BE group TCE form but it will be visible to the user!
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.
Updated by 
Updated by
Updated by Andreas Kießling almost 13 years ago
The backport for 4.4 does not work for me, since the configureModule function from extbase 1.2 does not return the needed $MCONF['access'] config like it does from TYPO3 4.5 / extbase 1.3
Something like this at the end of the method should do it:
$modconf['access'] = $config['access'];