[TYPO3-english] Order of extensions get changed in PackageStates.php

[Patrick Schriner]

Hi Armin,

looking at DCE's ext_emconf.php I can see that it neither depends on nor  
suggests "dbal" as a requirement.

If I understand the DependencyResolver (e.g.  
https://github.com/TYPO3/TYPO3.CMS/blob/TYPO3_6-2/typo3/sysext/core/
Classes/Package/DependencyResolver.php) correctly it will try to ensure  
that any extension in "depends" will be loaded before those you "suggest".

Afaik the "old" ExtensionManager was working the same way.

If you *need* to have dbal loaded before dce, you might therefore have to  
add it to the "suggests" section - even if you don't really want to  
"suggest" using dbal with dce ;D

Note: All analysis based on the code only - I haven't tried this!

Patrick

On Mon, 29 Sep 2014 15:32:42 +0200, Armin Ruediger Vieweg  
<armin at v.ieweg.de> wrote:

> Hi,
> I have a strange behaviour of the PackageStates.php which contains the  
> installed extensions and their order.
>
> The DCE extension requires that DBAL is loaded before, if DBAL is  
> installed. Otherwise DCE will throw an exception. I realized this  
> behaviour just because of this exception.
>
> First the PackageStates is perfect. It starts with extensions like core,  
> felogin, ..., dbal, ..., dce.
>
> When I clear the system cache and the general cache in backend, I get  
> the exception from DCE in frontend, now. When I check the PackageStates  
> and compare it with original one, I see that the order of extensions has  
> changed massive.
>
> Custom and third party extensions are now the first extensions in  
> PackageStates.php, including DCE. And extensions like core or dbal  
> appear later.
>
> We have the server twice. A development machine and a test machine. On  
> development everything works fine. This error appears just on the test  
> machine (after clearing caches). First I thought that TYPO3 has no write  
> rights for PackagesStates on dev, but this was not true. It has.
>
> I have no clue where to start to investigate further to figure out why  
> the order of installed extensions changes.
>
> Thanks for any hint!