[Tickets #8937] Re: Horde::logMessage calls Horde_Log_Logger::log bad values

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8937
------------------------------------------------------------------------------
  Ticket             | 8937
  Updated By         | jonathan at findyourfans.com
  Summary            | Horde::logMessage calls Horde_Log_Logger::log bad
                     | values
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


jonathan at findyourfans.com (2010-03-26 22:06) wrote:

> No - it is perfectly acceptable to pass a string to the logger.   
> Horde_Core_Log_Logger should do the conversion.  However, there was  
> a certain case where this conversion wasn't happening and that has  
> been fix.  Additionally, this same case was exiting the entire  
> script, which wasn't necessary.

Well, Horde::logMessage calls Horde_Log_Logger::log not  
Horde_Core_Log_Logger::log, despite the comment's reference to the  
latter. Horde_Core_Log_Logger extends Horde_Log_Logger, changing the  
behavior of the log method. I'm not sure exactly how this should be  
fixed, but the inconsistency between those two log methods seems  
unnecessarily confusing.