[Flow] Worst configuration bug ever [Was: Doctrine code generation problems on PHP 5.4/5.5]

[Christian Müller]

Hi,

Andreas Wolf wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> I invested quite a few hours into this problem, not being able to
> solve or even narrow it further down.
>
> It turned out now that this was totally unrelated to Doctrine, but
> instead came from some misconfiguration in the Settings.yaml file. I
> had enabled SQL logging in there and later on commented it out, like this:
>
> TYPO3:
>    Flow:
>      persistence:
>        doctrine:
> #        sqlLogger: TYPO3\Flow\Persistence\Doctrine\Logging\SqlLogger
>      session:
> [...]
>
> The thing is that now the configuration totally broke down and the
> __CG__*.php files in Data/Temporary/<Context>/Doctrine/Proxies/ were
> not generated anymore. Totally obvious, right? ;-)
>
> The problem can be fixed by removing/commenting out the
> persistence.doctrine hierarchy. I suppose that the Yaml parser somehow
> trips when encountering such a hierarchy without a value at the bottom.

It basically means you clear the configuration key (and therefor all 
subkeys)

>
> I hope this will one day help some lost soul and keep them from doing
> the things I did (install a VM, experiment for hours with different
> PHP versions, thinking of the odds that RAM/Harddisk/whatever might be
> broken etc.)...


I think for such configuration as persistence we could trigger an 
exception if it is that incomplete...

Cheers,
Christian