[BUGFIX] Avoid loading console commands before container is current
The shortcut handling added in #86248 caused the matching command to be loaded before the symfony DI container was made available to GeneralUtility::makeInstance (FailsafeContainer was still active). This caused services (e.g in #93442) that are instantiated using the GeneralUtility::makeInstance-to-DI-Container bridge to fail as these services are not available in the FailsafeContainer. Background: the symfony Application:find() method did not just search for a matching command, but it also initialized it, once found. Therefore shortcut resolving is now handled within the TYPO3 command application to ensure commands are only instantiated once the symfony container (and localconf) is fully loaded. Resolves: #93569 Related: #86248 Related: #93442 Releases: master Change-Id: I717df6aa03f4f474e437f98eef62d291e39010fc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68254 Tested-by:core-ci <typo3@b13.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Helmut Hummel <typo3@helhum.io>
Please register or sign in to comment