Zend Framework

Zend_Wildfire_Channel_HttpHeaders flushes postDispatch

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.0RC2
  • Fix Version/s: 1.6.0
  • Component/s: Zend_Wildfire
  • Labels:
    None
  • Fix Version Priority:
    Must Have

Description

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.

Activity

Hide
Matthew Weier O'Phinney added a comment -

Scheduling for RC3

Show
Matthew Weier O'Phinney added a comment - Scheduling for RC3
Hide
Christoph Dorn added a comment -

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

Show
Christoph Dorn added a comment - How do I register a plugin on the dispatchLoopShutdown and ensure it is executed last by default?
Hide
Christoph Dorn added a comment -

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);
Show
Christoph Dorn added a comment - 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);
Hide
Wil Sinclair added a comment -

Updating for the 1.6.0 release.

Show
Wil Sinclair added a comment - Updating for the 1.6.0 release.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: