[TYPO3-core] Extensions automatically removed in PackageStates.php causing fatal errors
Philipp Gampe
philipp.gampe at typo3.org
Tue Nov 12 16:31:36 CET 2013
Hi Dmitry,
Dmitry Dulepov wrote:
> Ernesto Baschny wrote:
>> So the "breaking change" is now that the "depends" constraint of your
>> extension are vitally important to define the loading order of them
>> (which makes sense and was ugly anyway before).
>
> This was not the case for me because I had all correct dependencies but
> fluid was not loaded before the extension that used it.
Yes, this has been fixed by Helmut, Markus and others. The extensions have
not been sorted by dependency shortly after Package Manager merge (AFAIK
even in beta1).
Therefore the entries in the PackageStates.php have the wrong order,
resulting in the wrong order for the ext_*.php files.
This has been fixed in the meantime, thus if you use your backup copy of
your LocalConfiguration.php and run the upgrade again, this should be fixed.
Best regards
--
Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
Documentation – Active contributor TYPO3 CMS
TYPO3 .... inspiring people to share!
More information about the TYPO3-team-core
mailing list