#94673Install Tool not accessible when entry in PackageStates.php is missing
Description
When the entry for ‘install’ is missing in the PackageStates.php, The install tool is not accessible.
Trying to access domain.xy/typo3/install.php produces a TYPO3 exception:
@Container entry “TYPO3\CMS\Install\Http\Application” is not available@
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 6
-
Simon Gilli commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2021-07-30T12:22:42+00:00" > 07/30/21, 12:22 </span> -
Marco Kuprat commented <span data-processor="relativetime" data-value="2021-07-30T13:02:44+00:00" > 07/30/21, 13:02 </span>
It is a non-composer installation. I had to find out why the install tool is not accessible on a TYPO3 site from a different provider. That web seems to have been updated from a prior TYPO3 version to 9.5.28, but I don’t know what actually was done.
I saw that the entry for ‘install’ (and also for ‘backend’) was missing in the PackageStates.php, so neither backend nor install tool were accessible.
In order to reproduce this, I manually deleted these entries in a local TYPO3 10.4.18 instance and got the same result. -
Riccardo De Contardi changed category <span data-processor="relativetime" data-value="2021-08-08T08:03:22+00:00" > 08/08/21, 08:03 </span>
-
Benni Mack commented <span data-processor="relativetime" data-value="2021-12-18T08:40:07+00:00" > 12/18/21, 08:40 </span>
Hmm, but how can a PackageStates.php be created without these entries? If no PackageStates.php exists, then these entries are ALWAYS added. I mean, sure we can add a check for “always installed extensions” when we have a corrupted PackageStates.php but this would add a huge complexity for our code-base, when people manually modify this file. This isn’t intended, maybe we need to clarify this in the Documentation?
-
Xavier Perseguers commented <span data-processor="relativetime" data-value="2022-04-01T12:47:59+00:00" > 04/01/22, 12:47 </span>
Just had this bug with a composer-based installation. Info here helped me fix the problem.
I made a copy-paste typo in my
AdditionalConfiguration.phpwith something like that:$GLOBALS['TYPO3_CONF_VARS']['BE'] = 'be_MYPROJECT_user'; $GLOBALS['TYPO3_CONF_VARS']['FE'] = 'fe_MYPROJECT_user';
instead of
$GLOBALS['TYPO3_CONF_VARS']['BE']['cookieName'] = 'be_MYPROJECT_user'; $GLOBALS['TYPO3_CONF_VARS']['FE']['cookieName'] = 'fe_MYPROJECT_user';
Running
composer updatebroke the loading of extensions and generated a nearly emptytypo3conf/PackageStates.phpbut I didn’t see it.From there on, no way to get back to a working install until I deleted that file
PackageStates.php. Only then could it be properly regenerated after my typo.Possibly this helps someone else.
-
Benni Mack commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-11-19T14:01:15+00:00" > 11/19/26, 14:01 </span>Thanks, Xavier, for your last comment.
In the meantime, we’ve been improving this and we cut down PackageStates – not needed in composer mode anymore, and for non-composer mode, we’ve been hardening the system as well.
Thanks for your report. Can you please provide more information about how to reproduce this issue? Also the information if it’s a Composer install or not is missing, I currently guess it’s a Composer install. If yes, how do you create the PackageStates.php, with scripts like shown in the typo3/cms-base-distribution or do you use typo3-console/composer-auto-commands?