It dies with: {quote}Catchable fatal error: Argument 1 passed to Zend_Controller_Plugin_Abstract::setResponse() must be an instance of Zend_Controller_Response_Abstract, null given, called in \library\Zend\Wildfire\Channel\HttpHeaders.php on line 248 and defined in \library\Zend\Controller\Plugin\Abstract.php on line 75{quote}

Comments

Posted by Martin Hujer (mhujer) on 2008-08-20T12:41:57.000+0000

To make it completely clear:

I have general Log class (writers - Db, Firebug) used in webapp. And I need to run some cron import scripts which should report errors in the Log.

Scheduling for RC3; Christoph, please see my previous comment for a solution.

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

I can fix the error described, however the intent is to throw an exception if the response object is not initialized to make it clear to the developer that the logged data will not make it into the response likely due to improper initialization. This is the intended behavior for WEB apps.

We have several options to solve this issue:

Make it the developer's responsibility to disable the Zend_Wildfire_Plugin_FirePhp component when running in CLI mode

Zend_Wildfire_Plugin_FirePhp::getInstance()->setEnabled(false);

Automatically disable the Zend_Wildfire_Plugin_FirePhp component when running in CLI mode

Removing the exception altogether to not provide any feedback if the Zend_Wildfire_Plugin_FirePhp component is not properly initialized.