Review 14.3 Merged

95017[TASK] Identify remote packages by key, version and remote

Benni Mack CR +2 V +2 Hard +326 −85 updated 07/30/26, 11:54

Commit message

Whenever the extension manager wanted to download or install a
package from TER, it addressed it by the uid of its row in
tx_extensionmanager_domain_model_extension. This made the whole
download and install flow depend on a package being stored in the
local database first, which stands in the way of browsing a remote
in real-time and installing from it without importing everything
into the database beforehand.

A package is now addressed by what actually identifies it: its
package key, a concrete version and the remote it comes from. A
small PackageIdentifier value object carries this triple, and
ExtensionRepository::findOneByPackageIdentifier() resolves it. Since
the table has a unique key over exactly these three fields, this
addresses the very same record the uid did, which makes the change
behaviour neutral.

The download and distribution controllers, the download ViewHelper
and the related Fluid templates hand over the identifier instead of
the uid. Extension::getIdentifier() returns it as request arguments,
so templates can pass a package on in one go:

  arguments="{identifier: extension.identifier}"

The uid based counterparts findByUid() and getByUid() are replaced by
findOneByPackageIdentifier() and getByPackageIdentifier(). The latter
keeps the guard introduced with #110290: a package taken from a view
that was rendered before an extension list update does not resolve
anymore, and still raises a speaking ExtensionNotFoundException
instead of running into a fatal error.

Resolving still happens against the database, and the download guard
in ExtensionManagementService deliberately stays untouched, so
nothing changes for the user. The difference is that a package no
longer needs a uid to be addressed, which is the groundwork for a
remote that does not populate the database.

Review

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

Issues 4

Files 13

Review log 34

  1. Benni Mack commented on patch set 1 07/30/26, 11:37

    Cherry Picked from branch main.
  2. core-ci voted on patch set 1 V +1 07/30/26, 11:44 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/105687

  3. Benni Mack voted on patch set 1 CR +2 V +2 07/30/26, 11:54

  4. Benni Mack merged patch set 2 07/30/26, 11:54