Open Power Template 2.x family
PLEASE PROVIDE THE TEMPLATES AND/OR PHP CODE IN THE TASK DESCRIPTION (Not URL-s to them). THAT ALLOWS US TO REPRODUCE THE PROBLEM! OTHERWISE WE ARE NOT ABLE TO HELP YOU!
Remember to hide all the security-related pieces of code from the task description, like passwords, server paths etc. for your own safety. Once we close the task, we cannot edit it anymore!
PLEASE PROVIDE THE TEMPLATES AND/OR PHP CODE IN THE TASK DESCRIPTION (Not URL-s to them). THAT ALLOWS US TO REPRODUCE THE PROBLEM! OTHERWISE WE ARE NOT ABLE TO HELP YOU!
Remember to hide all the security-related pieces of code from the task description, like passwords, server paths etc. for your own safety. Once we close the task, we cannot edit it anymore!
FS#96 - In Opt_Class::__destruct() all active output buffers are flushed and ended
Attached to Project:
Open Power Template
Opened by Anonymous Submitter - Friday, 17 July 2009, 10:09 GMT-7
Last edited by Zyx (Zyx) - Wednesday, 01 September 2010, 00:11 GMT-7
Opened by Anonymous Submitter - Friday, 17 July 2009, 10:09 GMT-7
Last edited by Zyx (Zyx) - Wednesday, 01 September 2010, 00:11 GMT-7
|
DetailsDon't you think everyone should close only its own buffers?
My particular case is an ob_start() callback function that sets some HTTP headers (Content-Length and such). The problem is it is not called in the end but after OPT renders a template (which is just a part of the page). -- Francesc Rosàs |
This task depends upon
Closed by Zyx (Zyx)
Wednesday, 01 September 2010, 00:11 GMT-7
Reason for closing: Fixed
Additional comments about closing: Should be fixed in Git now.
Wednesday, 01 September 2010, 00:11 GMT-7
Reason for closing: Fixed
Additional comments about closing: Should be fixed in Git now.
BTW. If OPT generates only a part of the page, you should consider not to use the Opt_Output_Http output system.
I have an OB handler in the front controller that adds some HTTP headers: ob_start(array(new Pct_Web_HttpOutputHandler, 'execute'), 4096). I attached Pct_Web_HttpOutputHandler class for completeness.
In this case, after executing an OPT template, ETag and Content-Length headers are already sent and I can't echo anything else (well, I can but headers won't be valid then).
This is just one of the cases I've found but I have more. The point is that OPT shouldn't touch other's handlers.