Issue Bug Under Review Stale

#110292Dependency on system extension removed from core cannot be resolved

Stefan Bürk 07/24/26, 22:04 updated 07/26/26, 10:07

Description

Problem

System extensions removed from the core and merged into another system extension
are declared as replacements in the composer manifest of the absorbing extension.
EXT:setup was removed in v14, and the composer manifest of EXT:backend lists
typo3/cms-setup in its replace section.

Extension releases made for older core versions still declare the extension key
setup in their ext_emconf.php constraints, and carry it in their TER dependency
data. Resolving such a dependency fails, because the replacement is only known by
composer name, never by extension key.

PackageManager::registerPackage() builds the alias map from
Package::getPackageReplacementKeys(), which returns the replace section of the
composer manifest. That map is therefore keyed by composer names, and
PackageManager::getPackageKeyFromComposerName() – used by
PackageManager::isPackageActive() – only ever hits it with a composer name.
Passing the extension key misses the map and is returned unchanged.

Verified at runtime in a functional test on main:

bc. isLoaded with setup results in false
isLoaded with backend results in true
getPackageKeyFromComposerName with setup results in setup
getPackageKeyFromComposerName with typo3/cms-setup results in backend
isPackageActive with typo3/cms-setup results in true

Impact

DependencyUtility::checkExtensionDependency() receives the extension key setup.
isDependentExtensionLoaded() is false, isDependentExtensionAvailable() is false,
and downloadExtensionFromRemote() therefore raises:

bc. The extension setup is not available from TER.

In the Extension Manager of a classic, non composer installation the extension
can be downloaded, but not activated – the activation button stays disabled and
the dependency check reports the missing extension setup. Composer mode is not
affected, because composer resolves the replace section itself.

Reported for the TER extensions deepltranslate_core and deepltranslate_glossary
on TYPO3 14.3, whose shared base extension deepl_base declares setup in the
release line built for v12 and v13.

Affected versions

main and 14.3. In 13.4 EXT:setup still exists as a system extension, so the
dependency resolves there.

Reviews 1

History 24