Issue Details (XML | Word | Printable)

Key: ZF-3963
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Christoph Dorn
Reporter: Matthew Purdon
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Google issue summary
Zend Framework

Zend_Wildfire_Channel_HttpHeaders flushes postDispatch

Created: 15/Aug/08 02:54 PM   Updated: 02/Sep/08 10:38 AM   Resolved: 24/Aug/08 06:38 PM
Return to search "Fixed in 1.5.1"
Component/s: Zend_Wildfire
Affects Version/s: 1.6.0RC2
Fix Version/s: 1.6.0

Time Tracking:
Not Specified

Fix Version Priority: Must Have


 Description  « Hide

Zend_Wildfire_Channel_HttpHeaders flushes on postDispatch meaning that I can't log from my dispatchLoopShutdown plugins. Moving the flush to a new dispatchLoopShutdown method in Zend_Wildfire_Channel_HttpHeaders allows logging to Firebug in the normal manner.



Matthew Weier O'Phinney added a comment - 22/Aug/08 03:00 PM

Scheduling for RC3


Christoph Dorn added a comment - 24/Aug/08 12:20 AM

How do I register a plugin on the dispatchLoopShutdown and ensure it is executed last by default?


Christoph Dorn added a comment - 24/Aug/08 06:38 PM

All wildfire HTTP messages are now flushed on dispatchLoopShutdown() and by default the front controller plugin index is set to 999.

You can specify a different plugin stack index with the following code. This needs to be called before the first logging call.

Zend_Wildfire_Channel_HttpHeaders::setControllerPluginStackIndex(999);

Wil Sinclair added a comment - 02/Sep/08 10:38 AM

Updating for the 1.6.0 release.