Comments on: zend_log_exception ‘bad log priority’ https://phpprotip.com/2009/02/zend_log_exception-bad_log_priority/ Together we can defeat the internet Mon, 27 Jun 2016 06:38:41 +0000 hourly 1 https://wordpress.org/?v=4.7.31 By: Gdewilde https://phpprotip.com/2009/02/zend_log_exception-bad_log_priority/comment-page-1/#comment-11510 Fri, 09 Sep 2011 17:10:40 +0000 http://phpprotip.com/?p=117#comment-11510 I get this error when I add $log->registerErrorHandler(); to my log object

]]> By: 網站製作學習誌 » [Web] 連結分享 https://phpprotip.com/2009/02/zend_log_exception-bad_log_priority/comment-page-1/#comment-12 Mon, 02 Mar 2009 08:01:35 +0000 http://phpprotip.com/?p=117#comment-12 […] zend_log_exception ‘bad log priority’ […]

]]> By: chance https://phpprotip.com/2009/02/zend_log_exception-bad_log_priority/comment-page-1/#comment-11 Wed, 25 Feb 2009 21:15:01 +0000 http://phpprotip.com/?p=117#comment-11 Matthew,

I filed an issue like you suggested.
http://framework.zend.com/issues/browse/ZF-5884

]]> By: Matthew Weier O'Phinney https://phpprotip.com/2009/02/zend_log_exception-bad_log_priority/comment-page-1/#comment-9 Tue, 24 Feb 2009 23:35:36 +0000 http://phpprotip.com/?p=117#comment-9 Actually, this sounds like a classic error when using __call() — making sure that any exceptions raised actually make sense and are not context sensitive. Typically it’s best to simply raise an exception with the message “__call() is unable to trap the method $method”.

If you haven’t already, can you file an issue asking to change the exception message raised by __call() in Zend_Log?

]]>