Project

General

Profile

Actions

Feature #49643

closed

Allow flexible configuration for BE submodules, disable the page tree for submodules

Added by Benni Mack almost 11 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2013-07-03
Due date:
% Done:

100%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Previously Backend modules could be configured
via a conf.php file that had $MCONF and $MLANG
variables. Additionally, a Extbase extension could
add more configuration via another API method.
However, the building of the module list
(ModuleLoader) and the internal rendering for
ExtJS (ModuleMenuView) is quite tricky and hard
to override.

The public API call
ExtensionManagementUtility::addModule() has another
parameter now to ship additional configuration that will
override $MCONF from conf.php, or even replace
that information completely, so conf.php will be obsolete.

This is a prerequisite for overriding the configuration
"navigationComponentId" to allow the page tree in other areas
than the web module. Additionally, the if the new option
"inheritNavigationComponentFromMainModule" is set to
FALSE (TRUE if not set), then e.g. a web_* module can have
the page tree disabled.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #56809: Missing icons for main modules in backend group/users record access listsClosed2014-03-12

Actions
Related to TYPO3 Core - Task #64921: Document needed changes if you remove conf.phpClosedWouter Wolters2015-02-07

Actions
Actions

Also available in: Atom PDF