possibly (if users rely on the incorrect behaviour)
Deprecations?
no
Tests pass?
yes
Fixed tickets
-
License
MIT
For the 1.x branches of PropelBundle, the verbosity is apparently inverted to the expected behaviour.
$bufferPhingOutput is initially set to Symfony's kernel.debug parameter.
However, the conditional for checking the buffer works the other way round:
If buffering is enabled, the buffer is discarded, otherwise it is output.
This commit fixes that issue. Now if $bufferPhingOutput is true,
the detailed output of the command is displayed.
For the 1.x branches of PropelBundle, the verbosity is apparently inverted to the expected behaviour.
$bufferPhingOutput is initially set to Symfony's kernel.debug parameter. However, the conditional for checking the buffer works the other way round: If buffering is enabled, the buffer is discarded, otherwise it is output.
This commit fixes that issue. Now if $bufferPhingOutput is true, the detailed output of the command is displayed.