Zend_Application add Log to Translate, Cachemanager

[croensch]

I'd like to configure my loggers for Translate and Cachemanger for example via Zend_Config_Ini. Naturally the log array will be passed to the resource, resulting in an exception that it's not an instance of Zend_Log. So i added some checks in these resources to make them so.

This is a purely optional feature, please take consideration to add it.

Some documentation, not yet included:

Zend_Application_Resource_Translate
The following configuration keys are recognized:
log : Configuration will be passed to the Zend_Log::factory() method, allowing you to specify combinations of log writers and filters.

Zend_Application_Resource_Cachemanager
Example #2 Logger configuration

resources.cachemanager.database.frontend.options.logger.stream.writerName = "Stream"
resources.cachemanager.database.frontend.options.logger.stream.writerParams.stream = APPLICATION_PATH "/../data/logs/application.log"
resources.cachemanager.database.frontend.options.logger.stream.writerParams.mode = "a"
resources.cachemanager.database.frontend.options.logger.stream.filterName = "Priority"
resources.cachemanager.database.frontend.options.logger.stream.filterParams.priority = 4

Initial source: https://github.com/croensch/zendcastle/

[froschdesign]

@croensch
Why different index names? "log" vs. "logger"

• Zend_Application_Resource_Translate: $options['log']
• Zend_Application_Resource_Cachemanager: $value['frontend']['options']['logger']

[croensch]

@froschdesign
I know it looks odd. The index names are the same as the component specifies. You can already pass "log" to Zend_Translate, as well as "logger" to Zend_Cache_Manager. So i rather kept the consistency between the resource and the component than between the resources itself.

[froschdesign]

Ah, okay.

Thanks for your feedback.

[froschdesign]

Thanks! 😄