---
title: "Feature: #64921 - Needed changes for flexible configuration of submodules"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-64921"
source: "Changelog/7.1/Feature-64921-FlexibleSubmoduleConfiguration.rst"
typo3-version: "7.1"
typo3-major: 7
type: "feature"
issue: 64921
forge: "https://forge.typo3.org/issues/64921"
tags: ["PHP-API", "Backend"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Feature: #64921 - Needed changes for flexible configuration of submodules {#feature-64921}

See [forge#64921](https://forge.typo3.org/issues/64921)

## Description {#description}

The additional configuration for submodules can now be configured with an extra
parameter in `ExtensionManagementUtility::addModule()` since [https://forge.typo3.org/issues/62880](https://forge.typo3.org/issues/62880).
This makes it possible to remove the conf.php file by setting the configuration within `ExtensionManagementUtility::addModule()` in ext_tables.php.

When doing so you might have some issues with $this->MCONF not being set. This happens if your backend module extends
from `TYPO3CMSBackendModuleBaseScriptClass`.

To fix this problem you need to add the module name in $this->MCONF.

```php
/**
 * The name of the module
 *
 * @var string
 */
protected $moduleName = 'file_list';

/**
 * Constructor
 */
public function __construct() {
	$this->MCONF = array(
		'name' => $this->moduleName
	);
}
```