Issue Bug Rejected

#105493typo3/cms-extensionmanager still declared as partOfMinimalUsableSystem: true

S P 10/28/24, 10:01 updated 11/12/26, 16:09

Description

According to this changelog entry: https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.0/Breaking-102935-OverhauledExtensionInstallationInExtensionManager.html

> The EXT:extensionmanager extension is now optional.

However, in its composer.json:

"Package": {
    "protected": true,
    "partOfFactoryDefault": true,
    "partOfMinimalUsableSystem": true
},

What is correct here? An optional extension is surely not “partOfMinimalUsableSystem”.

Reviews 1

History 56

  1. Andreas Kienast commented <span data-processor="relativetime" data-value="2024-10-28T10:18:41+00:00" > 10/28/24, 10:18 </span>

    IMO it’s correct to have partOfMinimalUsableSystem here. In non-Composer scenarios, there would be no way to enable EXT:extensionmanager ever again.

  2. Benjamin Franzke commented and changed priority Should have Could have TYPO3 Version 13 14 <span data-processor="relativetime" data-value="2024-10-28T11:06:39+00:00" > 10/28/24, 11:06 </span>

    Good catch, although there is more work to be done to change that.

    First and foremost we need to adapt https://github.com/TYPO3/typo3/blob/84e9083c50ad4bd4c42d4a846f78d470e379ab87/typo3/sysext/core/Classes/Package/PackageManager.php#L214 to respect partOfMinimalUsableSystem instead of protected, otherwise a change to partOfMinimalUsableSystem = false would have no effect, as the package would still always be activated due to it being present in classic mode.

    With that in mind we need to think about the following usecases:

    PackageStates.php is corrupt and therefore removed and needs to be recreated by the installtool:
    In this case we still need the extension-manager to be enabled by default, as the integrator would otherwise not be able to activate it later.
    (We’d need a minimimal extension-manager in EXT:install in order to allow extensionmanager activation from within install tool)

    It would probably be fine to deactivate the extension manger via CLI in classic mode, but that CLI tool is currently provided by extensionmanager itself.
    That means this tool would need to be moved somewhere (where?) else.

    That’s something that could be addressed in v14, but in v13 extensionmanager is optional for composer mode and will probably keep always-active in classic mode.

  3. Benni Mack commented <span data-processor="relativetime" data-value="2026-11-12T16:09:18+00:00" > 11/12/26, 16:09 </span>

    for classic mode this is still needed, for composer mode the extension can be removed. in classic mode, this would be a self-destructing part: We can remove the extension in Extension Manager, and then never activate it again.