I believe that the output buffering should not be used unless it is
really really needed for some very specific tests of which we now they
will not provide "headers are already sent" errors.
Best regards
Sven
--
Met vriendelijke groeten
Sven Vanpoucke
Digitaal Leren
Directie Onderwijs
Hogeschool Gent
http://digitaal-leren.hogent.be/
Op 14/01/11 12:59, Peter Bex schreef:
On Fri, Jan 14, 2011 at 12:46:12PM +0100, Sven Vanpoucke wrote:
Hello
Output buffering used to be turned on. But many developers, including
myself, created to many architectural mistakes in the product where the
header was outputed even when a redirect was needed. There were also
many performance problems with installation, migration and other batch
scripts because of the output buffering settings. Therefor we decided
that output buffering should be turned off.
Maybe you can enable output buffering for your specific script with a
php command?
The problem is that this will mean false positives. Some tests will
succeed because output buffering is being used to run the tests, while
the code being tested would fail in production because output buffering
needs to be off (causing the dreaded "headers already sent" message).
Cheers,
Peter Bex
Solide ICT - http://www.solide-ict.nl
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
