Issue Bug Closed

#106700Classic installation: Starting with distribution fails

Lina Wolf 05/15/25, 06:45 updated 11/17/26, 22:12

Description

Starting with a fresh tarball install of TYPO3 13.4

I follow the installation Wizard, then chose option “Download Distributions”

I now choose the installation wizard and first thing I get is:

(1/1) ArgumentCountError
Too few arguments to function BK2K\BootstrapPackage\ExpressionLanguage\ExtensionConfigurationWrapper::__construct(), 0 passed in /var/www/html/public/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 2847 and exactly 1 expected

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 5

  1. Lina Wolf commented <span data-processor="relativetime" data-value="2025-05-15T06:53:47+00:00" > 05/15/25, 06:53 </span>

    Afterwards the installation package was installed, however my first impression was an Exception…

  2. Oliver Bartsch commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-17T22:12:18+00:00" > 11/17/26, 22:12 </span>

    Hey,

    thanks for the report. This was a core bug, not one in bootstrap_package. When the Extension Manager activated a package in classic mode, it flushed the caches of the container that was serving the current request. The Extbase backend request then cleared some frontend caches on teardown, which evaluated TypoScript conditions. That loaded the expression language providers of the extension that had just been installed. The old container does not know the services of that extension, so ExtensionConfigurationWrapper was created without its constructor arguments. That explains why the distribution still got installed and you saw the exception afterwards.

    This was fixed in #108980 (“Do not flush current runtime caches when activating a package”), which is in main and in 13.4.26 and later. Installing the distribution with a current 13.4 release should work without the exception. I’m closing this issue. If it still happens on 13.4.26 or later, please reopen and add the full stack trace.

    Cheers, Oli