[TYPO3-core] Extensions automatically removed in PackageStates.php causing fatal errors

Ernesto Baschny ernesto.baschny at typo3.org
Tue Nov 12 15:48:48 CET 2013

Hi Peter,

could you provide us your previous extList and in which order the
extensions used to be loaded in your environment previous to beta1?

I suspect there is a missing "depends" in one of your extensions that
might trigger this "bug", because previously the order of extList
defined the "loading order" of extensions, where we now sort by
dependency which are explicitly set in the extensions ext_emconf.php
(the patch you mention).

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).


Peter Beernink schrieb am 12.11.2013 14:41:
> Hi,
> After upgrading a project from TYPO3 6.2b1 to the latest master I fatal
> errors about extensions not being loaded anymore.
> This is because most extensions are automatically removed from the
> PackageStates.php
> When resetting the PackageStates.php to 'beta1' and removing the
> typo3temp/Cache the first page hit works correctly, but the second one
> gives an error like
> BadFunctionCallException: TYPO3 Fatal Error: Extension key "phpunit" is
> NOT loaded! in
> /....../typo3_src/typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php
> on line 104
> I have traced this issue to commit a71add78 (issue 52828), but I'm not
> sure if this is a breaking change for which I need to modify the
> extensions or that a bug has been introduced in this change.
> Greets,
> Peter

Ernesto Baschny
TYPO3 CMS Core Developer
Release Manager TYPO3 4.5 & 6.2 LTS

TYPO3 .... inspiring people to share!
Get involved: typo3.org

More information about the TYPO3-team-core mailing list