Review main Abandoned

94663[TASK] Use TER REST API in Extension Manager

Benni Mack CR 0 V 0 Expert +1706 −166 updated 09/10/26, 08:50

Commit message

The "Get Extensions" backend module talked to the TYPO3 Extension
Repository (TER) by downloading the weekly extensions.xml.gz dump,
importing it into the tx_extensionmanager_domain_model_extension
table and querying that local mirror for every browse, search and
install action. This coupled the whole download and install flow to a
database mirror that was refreshed at most once per week.

The module now browses TER live through its REST API at
https://extensions.typo3.org/api/v1. A new TerRestExtensionRemote
implements the new BrowsableRemoteInterface (search, extension
details, versions and a batch latest-versions lookup) and the existing
ExtensionDownloaderRemoteInterface. Extensions are downloaded as .zip
archives, verified via SHA-256 and extracted with the ZipSlip-hardened
ZipService, replacing the .t3x format and its MD5 checksum. Responses
are cached briefly in the new "extensionmanager_ter_api" cache.

A PackageResolver turns a PackageIdentifier (key, version, remote)
into a transient Extension model, resolving it from the browsable
remote or, for any other remote, from the local database as a
fallback. DownloadController, DistributionController, DependencyUtility
and the update flow resolve through it, so downloading and installing
no longer requires the catalogue to be imported into the database
first. ListUtility detects available updates for all installed
extensions in a single batch request instead of per-extension queries.

Consequences:

* The extension catalogue is no longer available offline.
* Requests to TER carry a "TYPO3 <version>" User-Agent header.
* Official distributions are recognised by a fixed list of extension
  keys, as the REST API exposes no "official" flag.
* Upload comments are consumed forward-compatibly: they are read from
  the API's "upload_comment" field once TER exposes it, and default to
  empty until then.

The legacy XML-based TerExtensionRemote is still shipped but no longer
registered as a remote. It, the extensions.xml.gz handling, the
database mirror and ListableRemoteInterface are scheduled for removal
in a future version.

Review

  • Code review CR 0
  • Verified V 0
    • core-ci +1 CI

Issues 1

Files 28

Show 8 more files

Review log 35

  1. Benni Mack uploaded patch set 1 07/02/26, 21:56

  2. core-ci voted on patch set 1 V -1 07/02/26, 22:04 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/104243

  3. Benni Mack uploaded patch set 2 V -1 07/03/26, 06:44

  4. core-ci voted on patch set 2 V +1 07/03/26, 06:53 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/104263

  5. Benni Mack abandoned the change 09/10/26, 08:50

    wont do like this