ZF-3963: Zend_Wildfire_Channel_HttpHeaders flushes postDispatch

Issue Type: Bug Created: 2008-08-15T14:54:47.000+0000 Last Updated: 2008-09-02T10:38:51.000+0000 Status: Resolved Fix version(s): - 1.6.0 (02/Sep/08)

Reporter: Matthew Purdon (mpurdon) Assignee: Christoph Dorn (cadorn) Tags: - Zend_Wildfire

Related issues: Attachments:


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.


Posted by Matthew Weier O'Phinney (matthew) on 2008-08-22T15:00:24.000+0000

Scheduling for RC3

Posted by Christoph Dorn (cadorn) on 2008-08-24T00:20:52.000+0000

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

Posted by Christoph Dorn (cadorn) on 2008-08-24T18:38:32.000+0000

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.

<pre class="highlight">

Posted by Wil Sinclair (wil) on 2008-09-02T10:38:51.000+0000

Updating for the 1.6.0 release.

Have you found an issue?

See the Overview section for more details.


© 2006-2016 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.