Review main Merged

95815[BUGFIX] Stop reading ext_emconf.php in the extension manager

Benni Mack CR +2 V +2 Hard +193 −134 updated 09/18/26, 16:58

Commit message

ext_emconf.php is no longer evaluated for package metadata since
TYPO3 v15, yet the extension manager still read it in three places.
Two of them were harmless leftovers, one hid a real defect.

The extension list rendered the description of an extension from a
merge with the ext_emconf.php array, because getAvailableExtensions()
never took it from the package metadata although MetaData carries it.
Without an ext_emconf.php the description was empty. The description
now comes from the package metadata, the merge is gone and the
remaining method is named after what it still does:
enrichExtensionsWithTerInformation().

The dependency check compared against the ext_emconf.php version when
the metadata version was missing. It never is; the fallback is gone.

Uploading a zip archive that carries no composer.json raised a
TypeError from json_decode(), because the file was read without a
check. It is an ExtensionManagerException now, as is an unreadable
composer.json. The version of an uploaded archive was read from
ext_emconf.php when composer.json declared none, although the upload
controller already parses "my_ext_1.2.3.zip" for the extension key.
The controller passes that version on. When neither the archive name
nor composer.json carries one, the upload is refused with a message
saying how to fix it. Until now such an extension was unpacked and
then dropped by the next package scan without any error, because a
package without a version is not registered in classic mode.

The 15.0 changelog claimed that loading such an extension throws an
exception. It does not: the package scan unregisters it silently and
only an explicit reload of the package information throws. The entry
describes this now. The 14.2 feature entry on ext_emconf.php linked
the form database storage feature where it meant the entry on the
extension title from composer.json.

EmConfUtility stays for the t3x download path, which still writes an
ext_emconf.php and goes away with the t3x.

Review

  • Code review CR +2 Done
    • Benni Mack +2
    • Georg Ringer +1
    • Jochen Roth +1
  • Verified V +2 Done
    • Benni Mack +2
    • Georg Ringer +1
    • Jochen Roth +1
    • core-ci +1 CI

Issues 1

Files 11

Review log 810

  1. Benni Mack uploaded patch set 1 09/14/26, 15:53

  2. Benni Mack marked it work in progress 09/14/26, 15:53

  3. core-ci voted on patch set 1 V +1 09/14/26, 16:06 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/108541

  4. Benni Mack marked it ready for review 09/14/26, 16:28

  5. Benni Mack updated the commit message in patch set 2 V +1 09/14/26, 18:25

  6. core-ci voted on patch set 2 V +1 09/14/26, 18:33 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/108548

  7. Georg Ringer voted on patch set 2 CR +1 V +1 09/17/26, 21:05

  8. Jochen Roth voted on patch set 2 CR +1 V +1 09/17/26, 21:22

  9. Benni Mack voted on patch set 2 CR +2 V +2 09/18/26, 16:58

  10. Benni Mack merged patch set 3 09/18/26, 16:58