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

[Andreas Wolf]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi again,

Am 23.01.2014 11:39, schrieb Andreas Wolf:
> since my recent upgrade to Fedora 20 I noticed some woes in at
> least one of my Flow installations (didn't test the others until
> now): The __CG__ classes are not generated anymore. I did not trace
> the problem until its very root, but it seems to be that somewhere
> the Doctrine configuration is not correctly read (from
> annotations?).
> 
> The problem also exists with PHP 5.5.8 and 5.4.24 on a CentOS 6 
> installation (both PHP versions from Remi Collet's repository).

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.

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


Cheers
Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iF4EAREIAAYFAlLhPoUACgkQVRefK2MMWg4AJwD+NqVRubuvQmR899RPh4oMgHll
b0/bJUecu364lhqUu/MA/jZhbAPCe47NkvVgVn3CoYl5I2iL9amfyuu7IZ6ygTHJ
=IbOf
-----END PGP SIGNATURE-----