Issue Bug Resolved

#110400Classic mode extension dependency not fetched from TER

Raphael Zschorsch 08/07/26, 18:18 updated 10/10/26, 05:10

Description

I have a simple setup in TYPO3 14:

ext_emconf.php

<?php

$EM_CONF[$_EXTKEY] = [
    'title' => 'Test',
    'description' => 'Test',
    'category' => 'misc',
    'author' => 'Raphael Zschorsch',
    'author_email' => '',
    'state' => 'stable',
    'version' => '14.3.0',
    'constraints' => [
        'depends' => [
            'content_blocks' => '',
        ],
        'conflicts' => [],
        'suggests' => [],
    ],
];

composer.json

{
    "name": "test/test",
    "type": "typo3-cms-extension",
    "description": "Test",
    "license": "GPL-2.0-or-later",
    "require": {
        "friendsoftypo3/content-blocks": "*"
    },
    "autoload": {
        "psr-4": {
            "GG\\Test\\": "Classes/"
        }
    },
    "extra": {
        "typo3/cms": {
            "extension-key": "test",
            "version": "14.3.0",
            "Package": {
                "providesPackages": {}
            }
        }
    }
}

If the extension, in this case content_blocks is not yet available in the system, it won’t be fetched from TER and instead a warning message is shown:

Required extension “friendsoftypo3/content-blocks“
The extension friendsoftypo3/content-blocks is not available from TER.

I also tried this with specific extension versions, but nothing helped.

Reviews 7

History 513

  1. Raphael Zschorsch commented <span data-processor="relativetime" data-value="2026-08-08T16:39:42+00:00" > 08/08/26, 16:39 </span>

    Yes, I just tested it again with a fresh Git v14 checkout, and the problem still persists.

    If the extension is already present in the system, the problem disappears. So my guess is that there’s an issue with the TER/Packagist sync during the initial fetch.

  2. Raphael Zschorsch commented <span data-processor="relativetime" data-value="2026-08-11T14:03:28+00:00" > 08/11/26, 14:03 </span>

    Also still happens with newest release 14.3.6.
    If I leave this part out in composer.json, it works:

                "Package": {
                    "providesPackages": {}
                }

    Which is weird, because it says in documentation, that this is required:
    https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/ComposerJson.html#extra-typo3-cms-package-providespackages

  3. Gerrit Code Review pushed patch set 1 for main to change 95294 status Needs Feedback Under Review <span data-processor="relativetime" data-value="2026-08-12T14:37:40+00:00" > 08/12/26, 14:37 </span>

  4. Anton Danilov commented <span data-processor="relativetime" data-value="2026-08-12T15:01:30+00:00" > 08/12/26, 15:01 </span>

    Raphael Zschorsch wrote in #note-3:
    > Also still happens with newest release 14.3.6.
    > If I leave this part out in composer.json, it works:
    >
    > […]
    >
    > Which is weird, because it says in documentation, that this is required:
    > https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/ComposerJson.html#extra-typo3-cms-package-providespackages

    The reason it works without the “Package” block is that TYPO3 then treats the extension as a “legacy” extension and falls back to the deprecated ext_emconf.php file for dependency resolution instead of composer.json. In ext_emconf.php dependencies are declared by extension key (content_blocks), which the EM can resolve in TER – whereas composer.json declares them by composer package name (friendsoftypo3/content-blocks), which the EM can’t currently map to the TER extension key.

  5. Anton Danilov commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-10-10T05:10:14+00:00" > 10/10/26, 05:10 </span>

    Applied in changeset commit:19927369b3e499b17d37577365bbcfe97c7b6456.