[Tickets #12094] Re: during ActiveSync Horde::LogMessage is broken

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12094
------------------------------------------------------------------------------
  Ticket             | 12094
  Updated By         | o+horde at immerda.ch
  Summary            | during ActiveSync Horde::LogMessage is broken
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


o+horde at immerda.ch (2013-03-06 09:41) wrote:

> $this->_logger is only different than the logger returned from the  
> injector if you select custom AS logging. Even then, only the  
> ActiveSync library uses $this->_logger. The global logger available  
> from the injector (which is what Horde::logMessage() uses) is  
> unchanged.

well i'm unsure about the technical reasons, but for a fact on our  
setup nothing is logged.

if i choose custom log, then everything logged via this->logger is  
written to the custom log, everything else gets lost.
if i choose horde log, then everything is lost.
this only happens for active sync sessions.

so please reopen this bug. tell me if you need more info