[commits] Horde branch master updated. e99ee0db6b1c1e95cc7e9e135c653e95411ad39a

[Gunnar Wrobel]

The branch "master" has been updated.
The following is a summary of the commits.

from: 136e667a74917b1e3be6889a909d7b91ca5c1f8e

e99ee0d Ensure that the log level is indeed an integer.

-----------------------------------------------------------------------

commit e99ee0db6b1c1e95cc7e9e135c653e95411ad39a
Author: Gunnar Wrobel <p at rdus.de>
Date:   Mon Jun 27 07:19:17 2011 +0200

    Ensure that the log level is indeed an integer.
    
    We frequently use statements such as Horde::logMessage($e, 'INFO');
    when an exception occurs. logMessage() directly uses
    Horde_Log_Logger::log() which expects an integer level when logging
    but logMessage() transmits the priority name as string. An alternative
    to my fix might be to use
    
    $GLOBALS['injector']->getInstance('Horde_Log_Logger')->$priority($event);
    
    within Horde::logMessage(). There is also an $options parameter in
    Horde::logMessage() which seems obsolete.

 framework/Log/lib/Horde/Log/Logger.php |   22 +++++++++++++++++++++-
 1 files changed, 21 insertions(+), 1 deletions(-)

http://git.horde.org/horde-git/-/commit/e99ee0db6b1c1e95cc7e9e135c653e95411ad39a