Get documents about "Zend Framework Issue Tracker Zend Framework Issue Tracker Displaying 147
Document Sample
Zend Framework Issue Tracker
Displaying 147 issues at 04/May/11 8:32 PM.
Project Key Summary Issue Type Status Priority Resolution
Zend Framework ZF-11294 Zend_Log_Formatters has a spelling Docs: Problem Open Trivial Unresolved
error
Zend Framework ZF-11262 typo "paramaters" in Zend_Ldap API Docs: Problem Resolved Trivial Fixed
reference
Zend Framework ZF-11161 RegisterErrorHandle not work with Xml Bug Reopened Major Unresolved
formatter
1 of 510
Zend Framework ZF-11160 RegisterErrorHandle not work in Bug Open Major Unresolved
bootstrap
Zend Framework ZF-11123 ZF2: Bug in Zend\Log\Writer\Syslog Bug Resolved Major Fixed
2 of 510
Zend Framework ZF-11096 Wrong sample for Zend_Log::factory() Docs: Problem Resolved Trivial Fixed
Zend Framework ZF-11057 Zend_Log_Writer_Mail not usable Bug Open Major Unresolved
several times
Zend Framework ZF-10990 Zend_Log::factory() doesn't support Improvement Resolved Minor Fixed
options like timestampFormat
Zend Framework ZF-10985 Wrong namespace in doc of Zend_Log Docs: Problem Resolved Minor Fixed
Zend Framework ZF-10885 Zend_Log_Formatter_Firebug: add unit Unit Tests: Improvement Closed Major Fixed
tests
3 of 510
Zend Framework ZF-10863 Incompatible Property/Method Visibility in Bug Resolved Minor Fixed
Zend_Log_Writer_Db
4 of 510
Zend Framework ZF-10859 Zend_Log_Writer_Syslog does not work Bug Resolved Major Fixed
when 'facility' param is set
5 of 510
Zend Framework ZF-10798 tab cleanup Coding Standards Violation Resolved Trivial Fixed
6 of 510
Zend Framework ZF-10769 lost the facility in syslog Patch Resolved Major Fixed
7 of 510
Zend Framework ZF-10698 monitor_custom_event() signature wrong Bug Resolved Major Fixed
in ZendMonitor.php
8 of 510
Zend Framework ZF-10617 Instanciating Zend_Log_Writer_Firebug Patch Resolved N/A Not an Issue
using the factory crashes
Zend Framework ZF-10537 File & Line info is incorrect for FirePHP Bug Closed Minor Fixed
messages sent via Zend_Wildfire
9 of 510
Zend Framework ZF-10498 Exception thrown in destructor Bug Open Major Unresolved
Zend Framework ZF-10472 Zend_Log: review tests Unit Tests: Problem Resolved Major Fixed
Zend Framework ZF-10470 Zend_Log_Formatter_SimpleTest don't Unit Tests: Problem Resolved Major Fixed
call TestHelper
Zend Framework ZF-10443 Adding a new Log writer to allow log data New Feature Open Minor Unresolved
to be sent to the view
10 of 510
Zend Framework ZF-10427 Zend_Log_Formatter_Simple must print Bug Open Major Unresolved
extra info event
Zend Framework ZF-10326 An easy way to log any SQL query in a New Feature Open Minor Unresolved
specified logfile
11 of 510
Zend Framework ZF-10323 French documentation : refactoring Docs: Problem Resolved Minor Fixed
around the word Émail
Zend Framework ZF-10308 BC Break in Bug Resolved Major Fixed
Zend_Log_Writer_ZendMonitor
12 of 510
Zend Framework ZF-10170 Zend_Log:>addPriority() allowed priority Bug Resolved Trivial Fixed
duplicates
Zend Framework ZF-10089 Zend_Log_Writer_Db::setFormatter Bug Resolved Trivial Fixed
should be compatible with should be
compatible with that of
Zend_Log_Writer_Abstract::setFormatter
Zend Framework ZF-10081 Zend_Log_Writer_ZendMonitor Wrong Bug Resolved Minor Fixed
parameter type for
monitor_custom_event()
13 of 510
Zend Framework ZF-10062 writerNamespace/filterNamespace not Bug Resolved Minor Not an Issue
working
Zend Framework ZF-10015 add tests Zend_Log_Writer_SyslogTest Unit Tests: Improvement Resolved Major Fixed
and Zend_Log_Writer_ZendMonitorTest
Zend Framework ZF-9992 Allow Zend_Log_Writer_Mail to specify a Patch Open Major Unresolved
transport
Zend Framework ZF-9990 Zend_Log_Writer_Mail : implement New Feature Resolved Major Fixed
factory()
14 of 510
Zend Framework ZF-9956 Zend_Log::_constructFilterFromConfig(), Bug Resolved Minor Fixed
undefined variable $filterName,
parentheses missing
15 of 510
Zend Framework ZF-9955 Zend_Log::_constructWriterFromConfig() Bug Resolved Minor Fixed
, undefined variable $writerName
16 of 510
Zend Framework ZF-9870 Zend_Log - line 303 - Allow us to define Improvement Resolved Minor Fixed
timestamp
17 of 510
Zend Framework ZF-9790 allow to attach a formatter from .ini Improvement Resolved Major Fixed
configuration and do not hardcode
formatter class in Log_Writer class
Zend Framework ZF-9674 Zend_Log_Filter_Abstract has wrong Docs: Problem Closed Trivial Fixed
subpackage
18 of 510
Zend Framework ZF-9544 Zend_Log Writer chapter typo, Firebox - Docs: Problem Resolved Major Fixed
> Firebug
Zend Framework ZF-9536 No accent support in Bug Resolved Minor Not an Issue
Zend_Log_Writer_Firebug
19 of 510
Zend Framework ZF-9429 Can't log to virtual host stderr Bug Closed Major Not an Issue
Zend Framework ZF-9390 Zend_Log::Factory should use new self() Bug Resolved Minor Fixed
20 of 510
Zend Framework ZF-9362 Bug in Zend_Log factory Bug Resolved Major Not an Issue
21 of 510
Zend Framework ZF-9331 Zend_Log should have event creation Improvement Resolved Major Fixed
extracted to a method
Zend Framework ZF-9197 Modifiy the default date timezone without Unit Tests: Problem Open Major Unresolved
reverting it back to it's previous value
22 of 510
Zend Framework ZF-9192 Add an errorHandler for Zend_Log New Feature Resolved Minor Fixed
Zend Framework ZF-9176 Zend_Log::factory() does not support Improvement Resolved N/A Fixed
formatters
Zend Framework ZF-9112 undefined method, Bug Resolved Major Fixed
Zend_Config::asArray()
Zend Framework ZF-9096 Calling non-existing method Bug Resolved Minor Fixed
Zend_Config::asArray() in
Zend_Log_Filter_Abstract::_parseConfig
23 of 510
Zend Framework ZF-9064 Zend_Log::_constructFromConfig Bug Resolved Minor Fixed
require_once fails on
Zend_Log_Exception.php
Zend Framework ZF-9029 Multiple files in library/ or in tests/ don't Coding Standards Violation Resolved Trivial Fixed
have the svn:keywords=id
24 of 510
Zend Framework ZF-8953 All public methods of Zend_Log should Improvement Closed Minor Fixed
return the current instance
25 of 510
Zend Framework ZF-8889 Zend_Log_Writer_Mail cant connect to Bug Resolved Major Not an Issue
server
26 of 510
Zend Framework ZF-8715 Inconsistent encoding across several Bug Resolved Major Fixed
view helpers
27 of 510
Zend Framework ZF-8602 Setting Bug Resolved Major Fixed
resources.log.stream.filterParams.priority
= 4 in application.ini throws error
Zend Framework ZF-8516 Zend_Log_Writer_Abstract::_parseConfi Bug Resolved Major Fixed
g($config) method asArray() not exists in
Zend_Config
28 of 510
Zend Framework ZF-8512 Zend_Log_Writer doesn't test all filters Bug Closed Critical Not an Issue
before reject the message.
Zend Framework ZF-8491 Create Zend Monitor log writer for Task Resolved Major Fixed
Zend_Log
29 of 510
Zend Framework ZF-8382 Zend_Log_Writer_Syslog does not utilize Patch Closed Trivial Fixed
formatter
30 of 510
Zend Framework ZF-8365 Zend_Log_Writer_Db fails on MySQL Improvement Resolved Minor Fixed
Zend Framework ZF-7959 Add callback support for log events Improvement Open Minor Unresolved
Zend Framework ZF-7604 No Docs: Problem Resolved Minor Fixed
Zend_Log_Writer_Syslog::setApplication
() hence documentation
31 of 510
Zend Framework ZF-7603 Syslog writer facility should be long Bug Resolved Major Fixed
32 of 510
Zend Framework ZF-7596 Firefox Firebug support not working Bug Resolved Major Not an Issue
using view_helper-json();
Zend Framework ZF-7522 Zend_Log_Writer_Stream opens files Improvement Closed Major Duplicate
unnecessarily
Zend Framework ZF-7398 Zend_Log_AllTest path should not be Unit Tests: Improvement Resolved Major Fixed
hardcoded
33 of 510
Zend Framework ZF-7335 Multiple files in library/ or in tests/ don't Coding Standards Violation Resolved Trivial Fixed
have the svn:keywords=id
34 of 510
Zend Framework ZF-7316 Cleaning all the code Coding Standards Violation Resolved Trivial Fixed
35 of 510
Zend Framework ZF-6972 Writer_Firebug calculates wrong Bug Open Major Unresolved
occurence of "log" in stack trace
Zend Framework ZF-6946 Add Config functionality New Feature Open Minor Unresolved
36 of 510
Zend Framework ZF-6469 Exception thrown in destruct method of Bug Resolved Major Fixed
Zend_Log by Zend_Log_Writer_Mail
Zend Framework ZF-6197 testShutdownRemovesReferenceToData Unit Tests: Problem Resolved Major Fixed
baseInstance(Zend_Log_Writer_DbTest)
unit test failure
37 of 510
Zend Framework ZF-6086 Bogus formatter given to Bug Resolved Minor Duplicate
Zend/Log/Writer/Abstract.php should
throw an exception
Zend Framework ZF-6085 Bogus formatter given to Bug Resolved Minor Fixed
Zend/Log/Writer/Abstract.php should
throw an exception
38 of 510
Zend Framework ZF-5971 Make Zend_Log_Writer_Db test DB Bug Resolved Minor Not an Issue
connection
39 of 510
Zend Framework ZF-5884 change exception message raised in Improvement Open Minor Unresolved
Zend_Log::__call() to not be context
sensitive.
40 of 510
Zend Framework ZF-5852 Zend_Log_Writer_Stream throws Bug Resolved Major Fixed
Zend_Log_Exception without loading the
Zend/Log/Exception.php first
41 of 510
Zend Framework ZF-5778 Filtering messages which are not strings Bug Open Major Unresolved
42 of 510
Zend Framework ZF-5741 Create the log file only if there is Improvement Open Minor Unresolved
something to log
43 of 510
Zend Framework ZF-5729 Add default error code priority. Improvement Closed Major Won't Fix
Zend Framework ZF-5470 ZF-5442 Fix all spelling, grammar and Sub-task: Docs Resolved Minor Won't Fix
formatting issues for Zend_Log in the
reference guide
Zend Framework ZF-5235 typo in manual/en section 30.2.1 Docs: Problem Resolved Trivial Fixed
Zend_Log_Writer_Stream
Zend Framework ZF-5095 Zend_Log with no writers Improvement Closed N/A Won't Fix
44 of 510
Zend Framework ZF-5087 Allow to log with format string with Improvement Resolved Major Won't Fix
parameters
45 of 510
Zend Framework ZF-4934 testAdvancedLogging(Zend_Log_Writer_ Unit Tests: Problem Resolved Major Fixed
FirebugTest) unit tests error
Zend Framework ZF-4913 testBasicLogging(Zend_Log_Writer_Fire Unit Tests: Problem Resolved Major Duplicate
bugTest) takes too much time.
46 of 510
Zend Framework ZF-4529 testAdvancedLogging(Zend_Log_Writer_ Unit Tests: Problem Resolved Major Fixed
FirebugTest) failure
Zend Framework ZF-4442 include only required for addFilter() Improvement Resolved Trivial Fixed
47 of 510
Zend Framework ZF-4431 Zend causes php error or notice when Bug Closed Minor Not an Issue
using the log method
48 of 510
Zend Framework ZF-4375 Runtime Exception while running Unit Tests: Problem Resolved Major Fixed
AllTests
Zend Framework ZF-4309 ZF Cert Study Guide: Zend_Log Docs: Problem Resolved Minor Not an Issue
Formatting XML Example Missing
49 of 510
Zend Framework ZF-4306 using ReflectionClass Improvement Resolved Trivial Not an Issue
Zend Framework ZF-4257 testBasicLogging(Zend_Log_Writer_Fire Unit Tests: Problem Resolved Major Fixed
bugTest) unit test failure
50 of 510
Zend Framework ZF-4190 Zend_Log_Formatter_Xml and invalid Bug Resolved Major Fixed
xml
Zend Framework ZF-4155 Zend_Log_Writer_Firebug dissapeared Bug Resolved Trivial Not an Issue
51 of 510
Zend Framework ZF-3960 Zend_Log_Writer_Firebug breaks CLI Bug Resolved Major Fixed
app
Zend Framework ZF-3943 Zend_Db_Profiler_Firebug does not Bug Resolved Major Fixed
initialize header's sending
52 of 510
Zend Framework ZF-3883 Zend_Log_Writer_FirebugTest_Request Unit Tests: Problem Resolved Blocker Fixed
unit test problem
Zend Framework ZF-3741 make Zend Log handle more than just Improvement Resolved Major Fixed
strings
53 of 510
Zend Framework ZF-3663 Zend Log does not work with an Oracle Bug Resolved Critical Not an Issue
Database
Zend Framework ZF-3581 Add Zend_Log::getWriters() to return list Improvement Postponed Major Unresolved
of attached writers
54 of 510
Zend Framework ZF-3519 Multiple filters not working Bug Closed Minor Not an Issue
55 of 510
Zend Framework ZF-3464 setEventItem calls passed function Bug Resolved Major Incomplete
immediately
56 of 510
Zend Framework ZF-3424 Zend_Log returns "Fatal error: Call to a Bug Resolved Minor Not an Issue
member function shutdown() on a non-
object in .../Zend/Log.php on line 87"
57 of 510
Zend Framework ZF-3396 Zend_Cache - Zend_Log - When using Bug Resolved Major Cannot Reproduce
the php://output stream
58 of 510
Zend Framework ZF-3108 make Zend_Log classes iterable + other Improvement Open Minor Unresolved
improvements
59 of 510
Zend Framework ZF-3107 Use INSERT DELAYED for Improvement Postponed Major Unresolved
Zend_Log_Writer_Db
60 of 510
Zend Framework ZF-2658 More Flexible Mapping For Improvement Postponed Minor Unresolved
Zend_Log_Writer_Db
61 of 510
Zend Framework ZF-2657 Make Zend_Log_Writer_Db Easier For Improvement Resolved Trivial Not an Issue
Subclassing
62 of 510
Zend Framework ZF-2618 Timestamp format an timezone through Improvement Postponed Major Unresolved
Zend_Date
63 of 510
Zend Framework ZF-2428 Patch to make line and file information Patch Postponed Minor Unresolved
available in log events
Zend Framework ZF-2364 Purging and Rotating Log Files New Feature Resolved Minor Duplicate
64 of 510
Zend Framework ZF-2214 Lazy database quering by Improvement Resolved Minor Won't Fix
Zend_Log_Writer_Db
65 of 510
Zend Framework ZF-2062 Ampersand in message causes warning Patch Resolved Minor Fixed
DOM_Element::__construct() when using
Zend_Log_Formatter_Xml()
66 of 510
Zend Framework ZF-1910 Remove Zend_Log_Writer_Null and Improvement Resolved Minor Won't Fix
instead make Zend_Log configurable
Zend Framework ZF-1833 Methods to remove log writers, filters and Improvement Open Trivial Unresolved
event items.
67 of 510
Zend Framework ZF-1791 Zend_log attributes should be protected Bug Resolved Major Fixed
instead of private
68 of 510
Zend Framework ZF-1790 Use exact equals test to compare fwrite() Bug Resolved Major Fixed
=== false
69 of 510
Zend Framework ZF-1627 Incorrect example in the manual for Bug Resolved Trivial Fixed
Zend_Log_Writer_Db
Zend Framework ZF-1621 Zend_Log methods should return $this Improvement Resolved Trivial Won't Fix
for convienence
Zend Framework ZF-1375 Error Level shows like %level% on Log Bug Closed Minor Not an Issue
File
70 of 510
Zend Framework ZF-1322 Zend_Log_Writer_Mail to send log New Feature Resolved Minor Fixed
messages to an email address
Zend Framework ZF-1242 Mistake in Zend_Log_Formatter code Docs: Problem Resolved Major Fixed
example
71 of 510
Zend Framework ZF-1240 Implement a method to close resources Improvement Resolved Major Fixed
in Zend_Log writers
Zend Framework ZF-1237 Docs: Change Zend_Log_Formatter to Docs: Problem Resolved Trivial Duplicate
Zend_Log_Formatter_Simple
Zend Framework ZF-1232 Zend_Log_Filter: Minimum Log-Level New Feature Resolved Minor Not an Issue
and Level-Mask
Zend Framework ZF-1231 Global Formatter for all writers New Feature Resolved Minor Not an Issue
72 of 510
Zend Framework ZF-1220 Stream class used in doc example where Docs: Problem Resolved Major Fixed
Db class should be used
73 of 510
Zend Framework ZF-1219 CLONE -Zend_Log_Exception' with Bug Resolved Trivial Not an Issue
message 'No instance of log
74 of 510
Zend Framework ZF-1212 Move new object-oriented design of Task Resolved Major Fixed
Zend_Log from incubator to core
75 of 510
Zend Framework ZF-1196 Zend_Log_Adapter_File::open() throws Bug Resolved Trivial Duplicate
an exception with an invalid message
Zend Framework ZF-728 Wrong use of Patch Resolved Minor Fixed
Zend_Db_Adapter_Abstract::insert() in
Zend_Log_Adapter_Db::write()
76 of 510
Zend Framework ZF-582 Zend_Log_Exception' with message 'No Bug Resolved Major Not an Issue
instance of log
Zend Framework ZF-563 Limit log file size New Feature Resolved Major Duplicate
Zend Framework ZF-467 Fix for empty filename in Bug Resolved Major Fixed
Zend_Log_Adapter_File when throwing
an exception
77 of 510
Zend Framework ZF-401 Support output of log levels as string or Improvement Resolved Minor Fixed
as integer
78 of 510
Zend Framework ZF-397 Zend_Log_Adapter_File exception Bug Resolved Minor Fixed
thrown in __destruct
Zend Framework ZF-368 Unit Tests for Zend_Log Unit Tests: Task Resolved Major Fixed
79 of 510
Zend Framework ZF-293 Zend_Log lets you unregister a default Bug Resolved Minor Won't Fix
logger
Zend Framework ZF-282 add method debug(), info() for Improvement Resolved Trivial Fixed
supplement to log()
80 of 510
Zend Framework ZF-281 add more predefined field, like %date% Improvement Resolved Trivial Fixed
Zend Framework ZF-271 Setting multiple default loggers raises Bug Resolved Major Duplicate
exeption
81 of 510
Zend Framework ZF-270 Trying to log to multiple loggers raises Bug Resolved Major Fixed
exeption
Zend Framework ZF-263 Rolling File Appender New Feature Resolved Trivial Incomplete
82 of 510
Zend Framework ZF-100 Zend_Log_Adapter_Db calls non- Bug Resolved Critical Fixed
existent methods (TRAC#96)
83 of 510
Zend Framework ZF-32 Zend Log throwing an error without a Improvement Resolved Minor Won't Fix
default logger (TRAC#16)
84 of 510
Zend Framework ZF-5 Zend_Log Should Log Error Level Text Improvement Closed Minor Fixed
Instead of Numeric Value
Zend Framework ZF-3 Zend_Log Level Ignored Bug Closed Minor Fixed
Generated at Wed May 04 20:32:35 UTC 2011 using JIRA 4.3#614-r144677.
85 of 510
Assignee Reporter Created Updated Resolved
Eddo Rotman Zoran Zaric 4/15/2011 15:46 4/15/2011 22:33
Satoru Yoshida Filipus Klutiero 4/5/2011 5:18 4/29/2011 3:29 4/29/2011 3:29
Adam Lundrigan Fabio Ginzel 3/10/2011 19:20 5/4/2011 17:53
86 of 510
Adam Lundrigan Fabio Ginzel 3/10/2011 19:17 4/30/2011 15:43
Benoît Durand Sven Paulus 3/1/2011 5:34 3/26/2011 11:56 3/26/2011 11:56
87 of 510
Benoît Durand Benoît Durand 2/19/2011 21:01 2/19/2011 21:07 2/19/2011 21:07
Eddo Rotman Andy 2/9/2011 2:07 2/20/2011 8:29
Benoît Durand Lucas Corbeaux 1/24/2011 3:20 3/2/2011 7:54 2/19/2011 21:45
Benoît Durand Benoît Durand 1/23/2011 0:15 1/23/2011 0:27 1/23/2011 0:26
Benoît Durand Benoît Durand 12/30/2010 7:06 12/30/2010 7:14 12/30/2010 7:14
88 of 510
Benoît Durand Christopher Manning 12/22/2010 13:52 3/26/2011 17:09 3/26/2011 17:09
89 of 510
Ramon Henrique Ornelas Peter Voringer 12/21/2010 14:44 12/23/2010 15:26 12/23/2010 15:26
90 of 510
Marc Hodgins Marc Hodgins 12/8/2010 23:42 12/9/2010 20:06 12/9/2010 20:06
91 of 510
Ramon Henrique Ornelas Siad Ardroumli 12/3/2010 1:03 3/26/2011 11:51 12/5/2010 8:03
92 of 510
Matthew Weier O'Phinney Jonathan Marston 11/17/2010 7:25 11/17/2010 9:05 11/17/2010 7:32
93 of 510
Ramon Henrique Ornelas Frédéric MENU 10/31/2010 15:00 11/23/2010 21:54 11/1/2010 2:11
Christoph Dorn Christoph Dorn 10/9/2010 13:27 10/9/2010 17:08 10/9/2010 17:08
94 of 510
Eddo Rotman Marcin Kowalski 9/27/2010 1:02 1/16/2011 3:03
Benoît Durand Benoît Durand 9/19/2010 3:06 1/20/2011 11:33 9/19/2010 5:46
Benoît Durand Benoît Durand 9/18/2010 13:53 9/19/2010 3:07 9/18/2010 14:12
Eddo Rotman Kevin Schroeder 9/10/2010 14:17 9/13/2010 4:40
95 of 510
Benoît Durand Benoît Durand 9/7/2010 10:43 9/19/2010 3:10
Ralph Schindler Mathieu Decaffmeyer 8/17/2010 6:30 9/2/2010 22:33
96 of 510
Mickael Perraud Benoît Durand 8/16/2010 10:46 8/19/2010 12:00 8/19/2010 12:00
Matthew Weier O'Phinney Margus Sipria 8/13/2010 2:08 11/17/2010 7:31 11/16/2010 10:19
97 of 510
Ramon Henrique Ornelas Ramon Henrique Ornelas 7/16/2010 22:29 7/16/2010 23:12 7/16/2010 23:12
Ramon Henrique Ornelas Faolan Cheslack-Postava 7/1/2010 6:09 7/1/2010 7:13 7/1/2010 7:13
Ramon Henrique Ornelas Christian Ruffer 6/30/2010 2:46 8/13/2010 2:22 7/6/2010 19:40
98 of 510
Ramon Henrique Ornelas Satoru Moriwaki 6/28/2010 0:23 7/17/2010 14:16 7/17/2010 14:14
Ramon Henrique Ornelas Ramon Henrique Ornelas 6/18/2010 18:17 7/6/2010 19:33 7/6/2010 19:33
Eddo Rotman Juan Pablo Civile 6/15/2010 14:13 6/15/2010 15:02
Benoît Durand Benoît Durand 6/15/2010 13:06 9/18/2010 10:10 9/18/2010 10:10
99 of 510
Ramon Henrique Ornelas Andreas Möller 6/7/2010 6:08 7/4/2010 9:09 7/4/2010 9:09
100 of 510
Ramon Henrique Ornelas Andreas Möller 6/7/2010 5:49 7/4/2010 9:10 7/4/2010 9:10
101 of 510
Jan Pieper Mike Purcell 5/20/2010 22:21 5/31/2010 11:59 5/31/2010 11:58
102 of 510
Benoît Durand Remy Damour 5/2/2010 14:07 2/10/2011 0:48 1/23/2011 12:04
Juozas Kaziukenas Michael Chinigo 4/13/2010 13:33 4/16/2010 12:15 4/16/2010 12:15
103 of 510
Wil Moore III (wilmoore) Halil Köklü 3/26/2010 2:17 5/21/2010 12:53 5/21/2010 12:53
Shawn Stratton Didier TRESSE 3/25/2010 6:56 4/29/2011 4:12 4/29/2011 4:12
104 of 510
Benoît Durand Louis-Simon Houde 3/15/2010 13:42 1/20/2011 11:09 1/20/2011 11:09
Benoît Durand Mickael Marchal 3/10/2010 7:20 9/19/2010 4:59 9/19/2010 4:59
105 of 510
Eddo Rotman Jan Dvorak 3/8/2010 3:02 3/9/2010 1:39 3/9/2010 1:39
106 of 510
Dolf Schimmel (Freeaqingme) David Abdemoulaie 3/4/2010 14:41 8/8/2010 5:11 8/8/2010 5:11
Thomas Weidner Marc Easen 2/17/2010 3:43 12/24/2010 5:36
107 of 510
Eddo Rotman Michael Rehbein 2/16/2010 11:43 3/23/2010 2:45 3/23/2010 2:45
Benoît Durand Mario Dees 2/14/2010 16:16 1/23/2011 12:04 1/23/2011 12:04
Matthew Weier O'Phinney Ramon Henrique Ornelas 2/7/2010 11:10 2/8/2010 7:51 2/8/2010 7:51
Eddo Rotman Benjamin Steininger 2/5/2010 13:11 2/8/2010 7:52 2/8/2010 7:52
108 of 510
Satoru Yoshida Benjamin Steininger 2/2/2010 13:16 2/2/2010 20:21 2/2/2010 20:21
Mickael Perraud Mickael Perraud 1/31/2010 1:24 3/18/2010 12:16 3/12/2010 2:05
109 of 510
Ramon Henrique Ornelas Ota Mares 1/27/2010 8:31 7/19/2010 16:59 7/18/2010 11:33
110 of 510
Ramon Henrique Ornelas bram vogelaar 1/21/2010 6:12 7/21/2010 20:31 7/21/2010 20:31
111 of 510
Matthew Weier O'Phinney Matthew Weier O'Phinney 1/5/2010 13:16 2/18/2010 6:14 1/6/2010 13:28
112 of 510
Matthew Weier O'Phinney Akeem Philbert 12/21/2009 18:45 1/12/2010 13:29 1/12/2010 13:29
Matthew Weier O'Phinney Ramon Henrique Ornelas 12/10/2009 7:06 12/12/2009 6:58 12/12/2009 6:58
113 of 510
Eddo Rotman Sébastien Debrard 12/10/2009 2:12 2/23/2010 10:54 2/23/2010 10:54
Matthew Weier O'Phinney Matthew Weier O'Phinney 12/7/2009 12:24 12/8/2009 5:07 12/8/2009 5:07
114 of 510
Benoît Durand Markus Warg 11/24/2009 5:51 12/30/2010 9:43 12/30/2010 9:43
115 of 510
Ramon Henrique Ornelas Sander Bol 11/20/2009 19:09 1/9/2011 18:22 1/9/2011 18:22
Matthew Weier O'Phinney Jean-Marc Fontaine 9/27/2009 11:17 9/27/2009 14:24
Satoru Yoshida Péter Nagy 8/15/2009 2:59 8/15/2009 7:30 8/15/2009 7:30
116 of 510
Ramon Henrique Ornelas Péter Nagy 8/15/2009 2:48 6/21/2010 6:00 6/21/2010 5:16
117 of 510
Matthew Weier O'Phinney Holger Schäfer 8/14/2009 5:44 8/15/2009 13:56 8/15/2009 13:56
Benoît Durand Stanislav Malyshev 8/7/2009 12:56 1/20/2011 11:16 1/20/2011 11:15
Benoît Durand Keno Fischer 7/27/2009 10:29 1/20/2011 11:34 1/20/2011 11:34
118 of 510
Mickael Perraud Mickael Perraud 7/21/2009 4:38 3/18/2010 7:56 8/18/2009 15:11
119 of 510
Thomas Weidner Mickael Perraud 7/20/2009 2:53 12/8/2010 23:43 11/12/2009 5:35
120 of 510
Matthew Weier O'Phinney Sebastian Krebs 6/10/2009 0:16 6/26/2010 1:22
Matthew Weier O'Phinney George Cooksey 6/7/2009 21:07 1/20/2011 11:36
121 of 510
Brian DeShong swepp GmbH 4/29/2009 6:01 6/23/2009 13:45 4/29/2009 19:15
Wil Sinclair Alexander Veremyev 4/2/2009 14:02 4/3/2009 9:59 4/3/2009 9:57
122 of 510
Dolf Schimmel (Freeaqingme) Sergio Vaccaro 3/22/2009 1:48 3/22/2009 17:54 3/22/2009 17:54
Ramon Henrique Ornelas Sergio Vaccaro 3/22/2009 1:47 6/30/2010 18:54 6/30/2010 18:54
123 of 510
Wil Sinclair julien PAULI 3/9/2009 8:09 3/16/2009 14:25 3/16/2009 14:25
124 of 510
Eddo Rotman Chance Garcia 2/25/2009 13:12 1/20/2011 11:47
125 of 510
Wil Sinclair Shahar Evron 2/21/2009 12:00 2/21/2009 12:26 2/21/2009 12:26
126 of 510
Eddo Rotman Aspra Flavius Adrian 2/13/2009 8:02 11/18/2009 13:38
127 of 510
Eddo Rotman Mathieu Decaffmeyer 2/11/2009 0:48 1/20/2011 11:16
128 of 510
Wil Sinclair Puli Kutya 2/10/2009 8:28 3/16/2009 10:58 3/16/2009 10:55
Thomas Weidner Wil Sinclair 1/9/2009 14:13 2/28/2010 10:36 2/28/2010 10:36
Satoru Yoshida Remy Damour 12/12/2008 14:11 12/21/2008 5:03 12/12/2008 17:38
Wil Sinclair Zoran Lazic 11/28/2008 6:31 1/14/2009 13:40 1/14/2009 13:40
129 of 510
Wil Sinclair Erwin Derksen 11/28/2008 2:12 1/21/2009 12:11 1/21/2009 12:11
130 of 510
Christoph Dorn Alexander Veremyev 11/12/2008 10:59 1/13/2009 18:01 1/13/2009 18:01
Christoph Dorn Alexander Veremyev 11/11/2008 13:11 1/13/2009 17:12 1/13/2009 17:12
131 of 510
Wil Sinclair Alexander Veremyev 10/9/2008 1:34 11/13/2008 14:10 10/9/2008 14:04
Satoru Yoshida Jan Pieper 10/1/2008 12:14 12/26/2008 6:19 12/26/2008 6:18
132 of 510
Wil Sinclair jl 9/30/2008 15:30 1/21/2009 11:06 1/21/2009 11:06
133 of 510
Wil Sinclair Thomas Weidner 9/24/2008 23:44 12/1/2008 13:50 10/10/2008 10:15
Wil Sinclair Matthew Turland 9/16/2008 9:26 11/25/2008 12:27 11/25/2008 12:27
134 of 510
Matthew Weier O'Phinney Piotr Kabacinski 9/16/2008 6:49 12/30/2008 8:50 12/30/2008 8:50
Alexander Veremyev Alexander Veremyev 9/11/2008 12:34 9/14/2008 9:45 9/14/2008 9:45
135 of 510
Benjamin Eberlei Vladimir Michailenko 9/4/2008 12:24 11/13/2008 14:10 11/7/2008 2:46
Matthew Weier O'Phinney Ruben Resino 9/1/2008 9:40 9/2/2008 6:10 9/2/2008 6:10
136 of 510
Christoph Dorn Martin Hujer 8/15/2008 11:47 9/2/2008 10:39 8/24/2008 17:47
Christoph Dorn Martin Hujer 8/13/2008 8:07 9/2/2008 10:39 8/24/2008 0:36
137 of 510
Alexander Veremyev Alexander Veremyev 8/7/2008 5:32 9/2/2008 10:39 8/7/2008 5:56
Christoph Dorn Karol Grecki 7/24/2008 8:21 8/6/2008 9:43 8/6/2008 9:43
138 of 510
Mickael Perraud Gabriel Baez 7/17/2008 6:16 9/11/2008 14:27 9/11/2008 14:27
Eddo Rotman Lars Strojny 7/4/2008 8:08 6/21/2010 12:32
139 of 510
Eddo Rotman Filipe Carvalho 6/26/2008 8:37 2/23/2010 10:59 2/23/2010 10:59
140 of 510
Wil Sinclair Ashley Kitson 6/16/2008 10:26 1/21/2009 23:55 1/21/2009 12:30
141 of 510
Wil Sinclair Victor Shih 6/9/2008 15:04 1/21/2009 15:36 1/21/2009 15:27
142 of 510
Unassigned Helgi Hrafn Halldórsson 6/5/2008 10:03 1/9/2009 9:53 1/9/2009 9:53
143 of 510
julien PAULI julien PAULI 4/14/2008 11:45 1/21/2009 11:47
144 of 510
Ralph Schindler Nils Caspar 4/13/2008 2:24 3/23/2011 18:01
145 of 510
Eddo Rotman Arthur Kang 2/14/2008 15:17 3/26/2011 17:22
146 of 510
Wil Sinclair Arthur Kang 2/14/2008 14:34 10/11/2010 12:47 1/26/2009 11:16
147 of 510
Eddo Rotman Rainer Collet 2/11/2008 19:53 11/18/2009 13:40
148 of 510
Unassigned Mark Maynereid 1/13/2008 19:47 1/8/2010 4:39
Wil Sinclair fc 12/29/2007 19:28 6/2/2008 6:42 6/2/2008 6:42
149 of 510
Wil Sinclair Alan Gabriel Bem 11/17/2007 20:40 1/5/2009 14:02 1/5/2009 14:02
150 of 510
Benjamin Eberlei Menno Holtkamp 10/12/2007 11:47 11/13/2008 14:10 11/7/2008 2:47
151 of 510
Wil Sinclair Taylor Ettema 9/5/2007 10:27 12/30/2008 7:11 12/30/2008 7:11
julien PAULI Martin Pärtel 8/8/2007 11:52 4/25/2008 10:24
152 of 510
Bill Karwin matthieu 7/30/2007 11:03 1/23/2008 18:28 8/9/2007 21:27
153 of 510
Bill Karwin matthieu 7/30/2007 10:58 1/23/2008 18:28 8/9/2007 21:38
154 of 510
Bill Karwin Geoffrey Tran 6/25/2007 19:56 7/5/2007 14:44 6/26/2007 12:01
Bill Karwin Geoffrey Tran 6/24/2007 18:45 7/5/2007 14:44 6/26/2007 11:19
Mike Naberezny Carlos Medina 5/12/2007 12:59 12/19/2008 11:33 5/13/2007 4:33
155 of 510
Brian DeShong Marc Bennewitz (GIATA mbH) 4/28/2007 9:10 2/2/2009 14:18 1/18/2009 8:36
Bill Karwin Nils Caspar 4/11/2007 2:15 6/15/2008 14:17 4/11/2007 12:27
156 of 510
Bill Karwin Bill Karwin 4/10/2007 16:25 7/5/2007 14:44 4/20/2007 3:01
Bill Karwin Sebastian Krebs 4/10/2007 10:42 7/5/2007 14:44 4/11/2007 12:28
Bill Karwin Sebastian Krebs 4/9/2007 17:46 7/5/2007 14:44 4/11/2007 12:46
Bill Karwin Sebastian Krebs 4/9/2007 17:27 7/5/2007 14:44 4/11/2007 12:57
157 of 510
Bill Karwin Bill Karwin 4/7/2007 12:21 6/15/2008 14:17 4/9/2007 18:26
158 of 510
Bill Karwin Mikael Österberg 4/7/2007 8:39 7/5/2007 14:44 4/9/2007 18:24
159 of 510
Bill Karwin Bill Karwin 4/6/2007 9:32 7/5/2007 14:44 4/6/2007 18:26
160 of 510
Bill Karwin Bill Monkman 4/3/2007 21:00 7/5/2007 14:44 4/11/2007 13:02
Bill Karwin Jan Pieper 1/8/2007 16:56 7/5/2007 14:43 2/15/2007 12:09
161 of 510
Bill Karwin Mikael Österberg 11/21/2006 18:21 7/5/2007 14:43 4/6/2007 19:19
Bill Karwin Shekar Reddy 11/18/2006 6:26 6/2/2008 6:34 4/11/2007 12:59
Bill Karwin Lars Strojny 10/31/2006 4:04 7/5/2007 14:43 4/11/2007 13:03
162 of 510
Bill Karwin Darby Felton 9/26/2006 12:46 7/5/2007 14:43 4/6/2007 19:16
163 of 510
Bill Karwin Simon R Jones 9/25/2006 7:41 7/5/2007 14:43 4/11/2007 13:04
Bill Karwin Darby Felton 9/12/2006 11:18 7/5/2007 14:43 4/6/2007 19:14
164 of 510
Richard Thomas Keith Pope 7/30/2006 6:21 7/5/2007 14:43 11/4/2006 9:14
Bill Karwin Superbiji 7/24/2006 4:27 7/5/2007 14:43 4/6/2007 19:14
165 of 510
Richard Thomas Superbiji 7/24/2006 4:14 7/5/2007 14:43 4/6/2007 19:13
Bill Karwin Sergey Belov 7/19/2006 3:38 7/5/2007 14:43 4/6/2007 19:12
166 of 510
Bill Karwin Sergey Belov 7/19/2006 3:36 7/5/2007 14:43 4/6/2007 19:11
Richard Thomas Superbiji 7/17/2006 3:52 7/5/2007 14:43 6/28/2007 20:19
167 of 510
Richard Thomas Zend Framework 6/21/2006 21:45 7/5/2007 14:43 9/22/2006 18:16
168 of 510
Richard Thomas Zend Framework 6/19/2006 22:59 7/5/2007 14:43 9/22/2006 19:38
169 of 510
Darby Felton Darby Felton 6/16/2006 12:56 7/5/2007 14:44 6/16/2006 16:36
Darby Felton Darby Felton 6/16/2006 9:44 2/26/2008 14:34 6/16/2006 9:57
170 of 510
Affects Version/s Fix Version/s Component/s Due Date Votes
1.11.5 Zend_Log 0
1.11.0 Next Mini Release Zend_Ldap, Zend_Log, 0
Zend_Service_Amazon_Ec2
1.11.4 Next Mini Release Zend_Log 0
171 of 510
1.11.4 Zend_Log 0
Next Major Release Zend_Log 0
172 of 510
1.11.3 1.11.4 Zend_Log 0
1.11.3 Zend_Log 0
1.11.2 1.11.4 Zend_Log 0
1.11.2 1.11.3 Zend_Log 0
1.11.3 Zend_Log 0
173 of 510
1.11.1 Next Major Release Zend_Log 0
174 of 510
1.11.1 1.11.2 Zend_Log 0
175 of 510
1.11.1 1.11.2 Zend_Application_Resource, 0
Zend_Auth_Adapter_Ldap,
Zend_Barcode, Zend_Captcha,
Zend_Controller, Zend_Db,
Zend_Feed_Writer, Zend_Gdata,
Zend_Http_Client, Zend_Ldap,
Zend_Log, Zend_Markup,
Zend_Rest_Route,
Zend_Service_Amazon,
Zend_Service_WindowsAzure,
Zend_View
176 of 510
1.11.1 1.11.2 Zend_Log 0
177 of 510
1.10.8, 1.11.0 1.11.1 Zend_Log 0
178 of 510
1.10.7, 1.10.8, 1.11.0 Zend_Log 0
1.10.8 1.11.1 Zend_Log, Zend_Wildfire 0
179 of 510
1.10.8 Zend_Log 0
1.11.0 Zend_Log 0
1.10.8 1.11.0 Zend_Log 0
Zend_Log 0
180 of 510
1.10.8 Zend_Log 1
Zend_Db, Zend_Log 1
181 of 510
1.10.7 1.11.0 Zend_Auth, Zend_Log, Zend_Mail, 0
Zend_Mime, Zend_Service_Flickr,
Zend_Session, Zend_Validate
1.10.7, 1.10.8, 1.11.0 1.11.1 Zend_Log 0
182 of 510
1.10.6 1.10.7 Zend_Log 0
1.10.6 1.10.7 Zend_Log 0
1.10.4 1.10.7 Zend_Log 0
183 of 510
1.10.6 Zend_Log 0
1.10.5 1.10.7 Zend_Log 0
1.10.2 Zend_Log, Zend_Mail 1
1.11.0 Zend_Log 2
184 of 510
1.10.5 1.10.7 Zend_Log 0
185 of 510
1.10.5 1.10.7 Zend_Log 0
186 of 510
1.10.4 1.11.0 Zend_Log 0
187 of 510
1.10.4 1.11.3 Zend_Log 7
1.10.3 1.10.4 Zend_Log 0
188 of 510
Zend_Log 0
1.10.2 Next Mini Release Zend_Log 0
189 of 510
1.10.2 Zend_Log 1
1.10.2 1.11.0 Zend_Log 2
190 of 510
1.10.3 Zend_Log 0
191 of 510
1.11.0 Zend_Log 0
1.9.2 Zend_Amf, Zend_Cache, 2
Zend_Db_Profiler, Zend_InfoCard,
Zend_Log, Zend_Pdf, Zend_Queue,
Zend_View, Zend_Wildfire
192 of 510
1.11.0 Zend_Log 0
1.10.1 1.11.3 Zend_Log 0
1.10.0 1.10.1 Zend_Log 0
1.10.0 1.10.1 Zend_Log 0
193 of 510
1.10.0 1.10.1 Zend_Log 0
1.10.0 1.10.0 Zend_Application_Resource, 0
Zend_Cache, Zend_Controller,
Zend_Currency,
Zend_Feed_Pubsubhubbub,
Zend_Feed_Reader, Zend_Feed_Writer,
Zend_Filter, Zend_Http_Client,
Zend_Http_Response, Zend_Log,
Zend_Oauth, Zend_Paginator,
Zend_Pdf, Zend_Queue,
Zend_Service_WindowsAzure,
Zend_Tool, Zend_Validate, Zend_View,
Zend_XmlRpc_Server
194 of 510
1.9.7 1.11.0 Zend_Log 1
195 of 510
1.9.7 Zend_Log 0
196 of 510
1.9.7 Zend_Dojo, Zend_Feed, Zend_Form, 0
Zend_Log, Zend_Service_Twitter,
Zend_Tag, Zend_View
197 of 510
1.10.0 1.10.0 Zend_Application_Resource, Zend_Log 1
1.10.0 Zend_Log 0
198 of 510
1.9.7 Zend_Log 0
1.10.0 Zend_Log 0
199 of 510
1.9.5 1.11.3 Zend_Log 3
200 of 510
1.9.4 1.11.0 Zend_Log 2
1.9.3 Zend_Log 0
1.9.1 1.9.2 Zend_Log 0
201 of 510
1.9.0 1.10.6 Zend_Log 0
202 of 510
1.9.1 Zend_Log 0
1.9.0 Zend_Log 2
Zend_Log 0
203 of 510
1.10.0 Zend_Acl, Zend_Amf, Zend_Application, 0
Zend_Auth, Zend_Auth_Adapter_Ldap,
Zend_Auth_Adapter_OpenId,
Zend_Cache, Zend_Captcha,
Zend_CodeGenerator, Zend_Config,
Zend_Config_Writer,
Zend_Console_Getopt, Zend_Controller,
Zend_Crypt, Zend_Db,
Zend_Db_Adapter_Db2,
Zend_Db_Adapter_Mysqli,
Zend_Db_Adapter_Oracle,
Zend_Db_Profiler, Zend_Db_Select,
Zend_Db_Table, Zend_Debug,
Zend_Dojo, Zend_Dom_Query,
Zend_Feed, Zend_Feed_Reader,
Zend_File_Transfer, Zend_Filter,
Zend_Filter_Inflector, Zend_Filter_Input,
Zend_Form, Zend_Gdata,
Zend_Http_Client, Zend_Http_Cookie,
Zend_Http_CookieJar,
Zend_Http_Response,
Zend_Http_Server, Zend_InfoCard,
Zend_Json, Zend_Json_Server,
Zend_Layout, Zend_Ldap, Zend_Loader,
Zend_Locale, Zend_Log, Zend_Mail,
Zend_Mail_Storage, Zend_Measure,
Zend_Memory, Zend_Mime,
Zend_Navigation, Zend_OpenId,
Zend_Paginator, Zend_Pdf,
204 of 510
Zend_Acl, Zend_Amf, Zend_Application, 0
Zend_Auth, Zend_Cache,
Zend_Captcha, Zend_CodeGenerator,
Zend_Config, Zend_Config_Writer,
Zend_Controller, Zend_Db,
Zend_Db_Adapter_Db2,
Zend_Db_Adapter_Mysqli,
Zend_Db_Adapter_Oracle,
Zend_Db_Profiler, Zend_Db_Select,
Zend_Db_Table, Zend_Dojo,
Zend_Feed, Zend_Feed_Reader,
Zend_File_Transfer, Zend_Filter,
Zend_Filter_Inflector, Zend_Filter_Input,
Zend_Form, Zend_Gdata,
Zend_InfoCard, Zend_Json,
Zend_Json_Server, Zend_Layout,
Zend_Ldap, Zend_Loader, Zend_Log,
Zend_Mail, Zend_Mail_Storage,
Zend_Paginator, Zend_Pdf,
Zend_ProgressBar, Zend_Reflection,
Zend_Search_Lucene,
Zend_Server_Reflection,
Zend_Service_Akismet,
Zend_Service_Amazon,
Zend_Service_Amazon_Ec2,
Zend_Service_Audioscrobbler,
Zend_Service_Delicious,
Zend_Service_Flickr,
Zend_Service_Nirvanix,
205 of 510
Zend_Log 2
1.8.2 Zend_Log 1
206 of 510
1.8.0 Zend_Log 0
1.8.0 Zend_Log 0
207 of 510
1.7.6 Zend_Log 0
1.7.6 1.10.7 Zend_Log 0
208 of 510
Zend_Log 0
209 of 510
Zend_Log 0
210 of 510
1.7.5 Zend_Log 0
211 of 510
1.7.4 Zend_Log 0
212 of 510
Zend_Log 0
213 of 510
Zend_Log 0
1.7.2 1.10.3 Zend_Log 0
1.7.1 1.7.2 Zend_Log 0
1.7.0 Zend_Log 0
214 of 510
Zend_Log 0
215 of 510
1.7.0 1.7.3 Zend_Log 0
1.7.0 Zend_Log 0
216 of 510
1.7 Preview Release 1.7.0 Zend_Log 0
1.7.2 1.7.3 Zend_Log 0
217 of 510
Zend_Log 0
218 of 510
1.7.3 1.7.1 Zend_Log 1
Zend_Log 0
219 of 510
Zend_Log 0
1.6.1 Zend_Log 0
220 of 510
1.6.0 1.7.0 Zend_Log 1
1.5.3 Zend_Log 0
221 of 510
1.6.0RC2 1.6.0 Zend_Log, Zend_Wildfire 0
1.6.0RC2 1.6.0 Zend_Log, Zend_Wildfire 1
222 of 510
1.6.0 Zend_Log 0
1.6.0RC2 Zend_Log 1
223 of 510
1.6.0RC1, 1.6.0 1.6.1 Zend_Log 0
Zend_Log 3
224 of 510
1.5.2 Zend_Log 0
225 of 510
1.5.1 Zend_Log 0
226 of 510
Zend_Log 0
227 of 510
1.5.2 Zend_Log 0
228 of 510
Zend_Log 1
229 of 510
1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, Zend_Log 2
1.5.0RC1, 1.5.0RC2, 1.5.0RC3, 1.5.0,
1.5.0PL1, 1.5.1, 1.5.3, 1.6.0RC2, Next
Major Release
230 of 510
Zend_Log 0
231 of 510
Zend_Log 0
232 of 510
Zend_Log 1
233 of 510
Zend_Log 5
Zend_Log 0
234 of 510
1.0.2 Zend_Log 0
235 of 510
1.0.2 1.7.0 Zend_Log 1
236 of 510
1.0.1 Zend_Log 0
1.0.1 Zend_Log 0
237 of 510
1.0.0 1.0.2 Zend_Log 0
238 of 510
1.0.0 1.0.2 Zend_Log 0
239 of 510
1.0.0 RC3 1.0.0 Zend_Log 0
1.0.0 RC2 1.0.0 Zend_Log 0
0.9.3 Zend_Log 12-May-07 0
240 of 510
0.9.2, Next Major Release Zend_Log 1
0.9.2 0.9.3 Zend_Log 0
241 of 510
0.9.2 0.9.3 Zend_Log 0
0.9.2 Zend_Log 0
Zend_Log 0
0.9.2 Zend_Log 0
242 of 510
0.9.2 0.9.3 Zend_Log 0
243 of 510
0.2.0 0.9.3 Zend_Log 0
244 of 510
0.9.1 0.9.2 Zend_Log 0
245 of 510
0.9.1 Zend_Log 0
0.6.0 0.8.0 Zend_Log 0
246 of 510
0.2.0 0.9.2 Zend_Log 1
0.2.0 Zend_Log 3
Zend_Log 0
247 of 510
0.1.5 0.9.2 Zend_Log 0
248 of 510
0.1.5 Zend_Log 0
0.1.5 0.9.2 Zend_Log 0
249 of 510
0.1.5 Zend_Log 0
0.9.2 Zend_Log 1
250 of 510
0.1.5 0.9.2 Zend_Log 1
0.1.5 0.9.2 Zend_Log 0
251 of 510
0.1.5 0.9.2 Zend_Log 0
1.0.0 Zend_Log 1
252 of 510
0.1.3 0.2.0 Zend_Log 1
253 of 510
0.1.3 0.2.0 Zend_Log 0
254 of 510
0.1.3 0.1.4 Zend_Log 1
0.1.3 0.1.4 Zend_Log 16-Jun-06 0
255 of 510
Images Original Estimate Remaining Estimate Time Spent Work Ratio Sub-Tasks
256 of 510
257 of 510
258 of 510
259 of 510
260 of 510
261 of 510
262 of 510
263 of 510
264 of 510
265 of 510
266 of 510
267 of 510
268 of 510
269 of 510
270 of 510
271 of 510
272 of 510
273 of 510
274 of 510
275 of 510
276 of 510
277 of 510
278 of 510
279 of 510
280 of 510
281 of 510
282 of 510
283 of 510
284 of 510
285 of 510
286 of 510
287 of 510
288 of 510
289 of 510
0 900 ZF-7476, ZF-7497, ZF-7498, ZF-7524,
ZF-7525, ZF-7526, ZF-7527, ZF-7528,
ZF-7529, ZF-7530, ZF-7531, ZF-7532,
ZF-7533
290 of 510
291 of 510
292 of 510
293 of 510
294 of 510
295 of 510
296 of 510
297 of 510
298 of 510
0 600
299 of 510
300 of 510
301 of 510
0 600
302 of 510
303 of 510
11544_snapshot.png
304 of 510
305 of 510
306 of 510
307 of 510
308 of 510
309 of 510
310 of 510
311 of 510
312 of 510
313 of 510
314 of 510
315 of 510
316 of 510
300 300 0%
317 of 510
318 of 510
319 of 510
320 of 510
321 of 510
322 of 510
323 of 510
324 of 510
325 of 510
11337_Email_Example.jpg 0 43200
326 of 510
327 of 510
328 of 510
329 of 510
330 of 510
331 of 510
332 of 510
333 of 510
334 of 510
335 of 510
336 of 510
337 of 510
338 of 510
339 of 510
340 of 510
Issue Links Description Security Level Progress Σ Progress Σ Time Spent
"Eingache Formatierung" should be
"Einfache Formatierung"
The description for Zend_Ldap
bind(string $username, string
$password) contains:
If both paramaters are omitted the
binding will be carried out with the
credentials given in the connection and
binding parameters.
"paramaters" should be spelled
"parameters".
http://framework.zend.com/manual/en/ze
nd.ldap.api.html
By the way, I didn't understand what this
is saying. I now understand after reading
the connect() description:
All parameters are optional and will be
taken from the LDAP connection and
binding parameters passed to the
instance via the construtor or via
Zend_Ldap::setOptions() when set to
NULL.
There is another typo here, "construtor"
instead of "constructor".
If I call the Registererrorhandle
Zend_Log with the xml formatter its not
works and give error
341 of 510
If I call the Registererrorhandle from the
bootstrap, it does not work on the errors
that occur within the controller
ZF-10769 In Zend Framework 2
Zend\Log\Writer\Syslog contains a bug
where _facility gets overwritten by the
current object which leads to subsequent
openlog() calls to fail.
A patch to fix this can be found on
https://github.com/zendframework/zf2/pul
l/137 and is given below:
{code}
--- a/library/Zend/Log/Writer/Syslog.php
+++ b/library/Zend/Log/Writer/Syslog.php
@@ -105,7 +105,7 @@ class Syslog
extends AbstractWriter
$runInitializeSyslog = true;
if (isset($params['facility'])) {
- $this->_facility = $this-
>setFacility($params['facility']);
+ $this->setFacility($params['facility']);
$runInitializeSyslog = false;
}
{code}
342 of 510
Documentation appears as:
filterParams -> format
but you must to use:
formatterParams -> format
Reported by [~neofraktal] in this
[comment|http://framework.zend.com/iss
ues/browse/ZF-9790#comment-44332-
open].
I'm using the class in a Daemon context.
So I need to send that log entries several
times.
The implementation of the class only
allows a one-time-usage, even though
the function shutdown is public and
therefore callable several times.
Hi there,
Zend_Log::factory() doesn't support the
timestampFormat option, and then it's
not possible to define a timestamp format
from the Application's configuration.
I think it could be really useful to add this
feature.
Zend_Log_Writer_Suppress instead of
Zend_Log_Filter_Suppress in Zend_Log-
Factory.xml line 447
Add unit tests for
Zend_Log_Formatter_Firebug
343 of 510
Zend_Log_Writer_Db is not final, so I
expected that it could be extended. I am
providing a custom ORM in the
constructor($_db) and then extending
from Zend_Log_Writer_Db to implement
a custom _write().
The problem is when overriding the
protected function _write(), access to the
$_db, $_table, and $_columnMap is
restricted since those variables are
declared as private in
Zend_Log_Writer_Db. This prevents you
from effectively extending
Zend_Log_Writer_Db.
It seems like the visibility of those
variables should be protected. If we
aren't to extend this class, then declare
Zend_Log_Writer_Db as final.
344 of 510
Zend_Log_Writer_Syslog uses method
chaining for setApplicationName() and
setFacility() (also doc-comment is
wrong),
but in factory() the result of setFacility ()
is set as the facility attribute.
$this->_facility = $this-
>setFacility($params['facility']);
Fix:
106: $this->setFacility($params['facility']);
179: * @return Zend_Log_Writer_Syslog
213: * @return Zend_Log_Writer_Syslog
345 of 510
ZF-4881, ZF-10669, ZF-7316 Replacement of tabs to spaces is
necessary in files:
{noformat}
Zend/Log/Writer/Mail.php
Zend/Log/Writer/Abstract.php
Zend/Service/Amazon/Item.php
Zend/Service/Amazon/SimpleDb.php
Zend/Service/Amazon/SimpleDb/Attribut
e.php
Zend/Service/Amazon/S3.php
Zend/Service/WindowsAzure/Storage/Dy
namicTableEntity.php
Zend/Service/WindowsAzure/Storage/Qu
eueMessage.php
Zend/Service/WindowsAzure/Storage/Ba
tchStorageAbstract.php
Zend/Service/WindowsAzure/Storage/Blo
bInstance.php
Zend/Service/WindowsAzure/Storage/Pa
geRegionInstance.php
Zend/Service/WindowsAzure/Storage/Qu
eueInstance.php
Zend/Service/WindowsAzure/Storage/Ta
bleEntityQuery.php
Zend/Service/WindowsAzure/Storage/Ta
bleInstance.php
Zend/Service/WindowsAzure/Storage/Si
gnedIdentifier.php
346 of 510
ZF-11123 If the constructor of
Zend_Log_Writer_Syslog is called with
$params array, the _facility property will
set by setFacility method. The Problem
is, that setFacility will return $this or
return void in older versions, the facility
property will be overwritten.
Index:
library/Zend/Log/Writer/Syslog.php
===============================
===============================
=====
--- library/Zend/Log/Writer/Syslog.php
(revision 23466)
+++ library/Zend/Log/Writer/Syslog.php
(working copy)
@@ -103,7 +103,7 @@
$runInitializeSyslog = true;
if (isset($params['facility'])) {
- $this->_facility = $this-
>setFacility($params['facility']);
+ $this->setFacility($params['facility']);
$runInitializeSyslog = false;
}
347 of 510
ZF-10308 I'm getting this warning when using
ZendMonitor
Warning: monitor_custom_event()
expects at most 3 parameters, 4 given in
/usr/local/zend/share/ZendFramework/lib
rary/Zend/Log/Writer/ZendMonitor.php
on line 106
taking a look at the ZendMonitor.php
code, the call looks like this:
{noformat}
protected function _write($event)
{
$priority = $event['priority'];
$message = $event['message'];
unset($event['priority'],
$event['message']);
if (!empty($event)) {
monitor_custom_event($priority,
$message, false, $event);
} else {
monitor_custom_event($priority,
$message);
}
}
{noformat}
348 of 510
If you try using the factory to create a
new firebug logger like this
{code}
Zend_log::factory(array(
array(
"writerName" => "Firebug",
"filterName" => "Priority",
"filterParams" => array(
"priority" => Zend_Log::INFO,
),
),
));
{code}
you've got the following fatal error:
Fatal error: Cannot redeclare class
Zend_Log in PATH/Zend/Log.php on line
30
Using normal instanciation does work
though:
{code}
$writer = new
Zend_Log_Writer_Firebug();
$logger = new Zend_Log($writer);
$logger->log('Test message',
Zend_Log::INFO);
{code}
The file and line info is offset for FirePHP
messages sent via Zend_Wildfire.
This is a result of a change in stack
depth for backtraces (used to determine
this info) likely due to some refactoring
work unrelated to Zend_Wildfire.
349 of 510
Zend_Log's __destruct method may
throw exceptions in case any writer's
shutdown() does. According to PHP's
manual, it is a bug to throw exceptions
inside destructors.
ZF-10470, ZF-7398 Refactor all tests about *Zend_Log* :
- should run each test class in
standalone
- add missing _require_once_ in
Zend_Log_Filter_Suppress, and
Zend_Log_Writer_Syslog
- add a test suite class by kind (filter,
formatter, or writer)
- correct some PHPDoc blocks
ZF-10472 *Zend_Log_Formatter_SimpleTest* don't
call *TestHelper*. The consequence is
that it includes the class
*Zend_Log_Formatter_Simple* from the
directive _include_path_ instead of using
the working copy of this class. And,
*Zend_Log_Formatter_Simple* has no
static method _main()_.
This patch contains a new log writer and
its tests that allows you to log to a view
placeholder. This allows developers to
set a log writer for their development
environment that automatically dumps to
the screen.
350 of 510
I wrote a unit test that is showing that the
default format of the formatter does not
include the info log event. The log
resource does not configure the
formatter writer currently.
In the error controller, the message to
log is only 'Application error', and the
stack trace is the extra information. The
default behavior does not log the
message and the stack trace of the
exception. But it is the most important
information to report!
{code:title=Zend_Log_Formatter_Simple
(line 41)|borderStyle=solid}
// Actual
const DEFAULT_FORMAT =
'%timestamp% %priorityName%
(%priority%): %message%';
// Expected
const DEFAULT_FORMAT =
'%timestamp% %priorityName%
(%priority%): %message% -- %info%';
{code}
Maybe a newline instead of the separator
'--'. We should let the possibility to filter
It would be nice to have a simple way to
have all the SQL query strings that have
been executed, in a logfile which you
could specify. Additionally, be able to
activate in an easy way the profiler for
each SQL query. So each log would
include the SQL query string and
possibly the profiling of that query.
351 of 510
It is disturbing to Frenchify the word
"email" by "Émail", and leave invariant in
the plural because the plural suffix "ail" is
"aux". I would therefore replace it by
"courriel" translation, or "adresse mail".
The specific case of the phrase "email
list" by "liste de diffusion".
ZF-10698, ZF-10081 After holiday I upgraded to Zend
Framework 1.10.7 and made my first bug
and found out that
Zend_Log_Writer_ZendMonitor was
failing using Zend Server 5.0.2.
After doing some research i found this
bug
http://framework.zend.com/issues/brows
e/ZF-10081 that is been fixed for 1.10.7.
User who filled out that bug was using
Zend Platform (product that has come
discontinued).
Zend_Log_Writer_ZendMonitor is ment
to use with Zend Server Monitor, says
Reference Guide so I did some digging
and found that api for monitor has
changed from Platform to Server:
- http://files.zend.com/help/Zend-
Platform/monitor_functions.htm
- http://files.zend.com/help/Zend-
Server/zend_monitor_-
_php_api.htm#function-
zend_monitor_custom_event
from: void monitor_custom_event(string
$class, string $text[, integer $severe,
mixed $user_data])
352 of 510
Zend_Log:>addPriority(), fires a
exception, case assigned priority already
existing.
Except to priorityName=emerg
Reproduced sample code:
{code}
Zend_Log:>addPriority('emerg', 8);
{code}
Expected a Exception
Zend_Log_Writer_Db issues a warning
in strict mode because its setFormatter
declaration does not have the
Zend_Log_Formatter_Interface type hint
for its argument while
Zend_Log_Writer_Abstract does.
ZF-10308 Warning: monitor_custom_event()
expects parameter 3 to be boolean, array
given in [...]/ZendMonitor.php on line 106
example Code:
$writer = new
Zend_Log_Writer_ZendMonitor();
$log = new Zend_Log($writer);
$log->log('testtext', Zend_Log::INFO);
Zend_Log_Writer_ZendMonitor->write();
should use bool value instead of arrray
$event.
used in Zend Platform Version 3.6.2
353 of 510
The manual for Zend_Log said that you
can specify writerNamespace and
filterNamespace, but they don't work
because Zend_Log-
>_constructWriterFromConfig() and the
Zend_Log->_constructFilterFromConfig()
do not pass the specified namespace to
the Zend_Log->_constructFromConfig().
http://framework.zend.com/manual/ja/zen
d.log.factory.html
ZF-7603 The issue ZF-7603 was reopened (by
Freeaqingme) request that the tests were
added, but not exists
*Zend_Log_Writer_SyslogTest*.
Also not exists test to
*Zend_Log_Writer_ZendMonitor*.
Freeaqingme suggested (in discussion
#zftalk.dev) adding of:
Zend_Log_Writer_SyslogTest
Zend_Log_Writer_ZendMonitorTest
Added a 3rd param to the
Zend_Log_Writer_Mail constructor to
optionally accept a
Zend_Mail_Transport_Abstract instance
to use as transport when sending the
mail.
ZF-4955 Implement the factory method for the
class Zend_Log_Writer_Mail in order to
configure all writers of Zend_Log with a
Zend_Config.
354 of 510
In
{code}
Zend_Log::_constructFilterFromConfig($
config);
{code}
on line 159, the variable {{$filterName}}
is undefined and an line 156 parentheses
are missing.
{code}
if (!$filter instanceof
Zend_Log_Filter_Interface) {
/** @see Zend_Log_Exception */
require_once 'Zend/Log/Exception.php';
throw new
Zend_Log_Exception("{$filterName}
does not implement
Zend_Log_Filter_Interface");
}
{code}
A fix could be (again, use of double
quotation marks is discouraged, by the
way):
{code}
if (!($filter instanceof
355 of 510
In
{code}
Zend_Log::_constructWriterFromConfig(
$config);
{code}
on line 135, the variable {{$writerName}}
is undefined and on line 132 parentheses
are missing.
{code}
if (!$writer instanceof
Zend_Log_Writer_Abstract) {
/** @see Zend_Log_Exception */
require_once 'Zend/Log/Exception.php';
throw new
Zend_Log_Exception("{$writerName}
does not extend
Zend_Log_Writer_Abstract!");
}
{code}
A fix could be (use of double quotation
marks is discouraged, by the way):
{code}
if (!($writer instanceof
Zend_Log_Writer_Abstract)) {
356 of 510
As mentioned in summary, the
timestamp value is hardcoded as
date('c'). For some of us we use a
specific time stamp pattern for our
logging to allow for easy parsing via pre-
defined regexes. It would be nice if we
could override the value before being
passed to $event var.
For now I have created a child class
which extends Zend_Log and copied the
Log() function contents to the child class
to override, kinda messy but gets us by.
Thanks.
357 of 510
ZF-9176 It would be great if we could attach a
formatter directly through application.ini
file AND without having to subclass a
writer either.
Currently we can define the following
entries for Zend_Log:
resources.log.stream.writerName =
"Stream"
resources.log.stream.writerParams.strea
m = APPLICATION_PATH
"/../logs/app.log"
resources.log.stream.writerNamespace =
"Library_Log_Writer"
resources.log.stream.filterName =
"Priority"
resources.log.stream.filterParams.priority
= Zend_Log::WARN
It would be great if we could add
something like:
resources.log.stream.formatterName =
"MyFormaterName"
resources.log.stream.formatterNamespa
ce = "My_Formater_Namespace"
This would improve logging
customization a lot and make it easier.
It would be absolutely necessary to
358 of 510
In the headline for
Zend_Log_Writer_Firebug there is a
typo.
"An Firebox schreiben" must be "An
Firebug schreiben"
See:
http://framework.zend.com/manual/de/ze
nd.log.writers.html
Affects doc versions: 1.10, 1.9, 1.8, 1.7,
1.6
When logging accent using
Zend_Log_Writer_Firebug, we get
*NULL* log in FireBug Console.
{quote}
require_once 'Zend/Application.php';
require_once
'Zend/Log/Writer/FireBug.php';
$writer = new
Zend_Log_Writer_Firebug();
$logger = new Zend_Log($writer);
$logger->info( 'Un événement !' ) ;
{quote}
In the FireBug console I get *NULL*
instead of my string.
359 of 510
I put this code in Boostrap.php :
{code}
protected function _initLogger(){
$logger = new Zend_Log();
$writer = new
Zend_Log_Writer_Stream("php://stderr");
$logger->addWriter($writer);
Zend_Registry::set('logger', $logger);
$logger->log("Logger created",
Zend_Log::ERR);
}// _initLogger
{code}
It logs into global Apache log file instead
of logging to virtual host log file.
trigger_error logs in the virtual host file
as it is supposed to do.
I think it is a bug. Sorry if it is not.
Hi,
The Zend_Log factory method should
use
$log = new self();
instead of
$log = new Zend_Log();
to create the log instance, so it would be
possible to extend Zend_Log without
extending the factory method.
360 of 510
Hi, I think that in class Zend_Log in
factory function should be instead of this
code
{code:javascript}
if (!is_array(current($config))) {
$log->addWriter(current($config));
} else {
foreach($config as $writer) {
$log->addWriter($writer);
}
}
{code}
this:
{code:javascript}
if (!is_array(current($config))) {
$log->addWriter(current($config));
} else {
foreach(current($config) as $writer) {
$log->addWriter($writer);
}
}
{code}
With this bug it is impossible to add more
writers using
Zend_Application_Resource_Log.
361 of 510
I recently found myself needing to use
{{Zend_Log}} to create entries with a
UTC timestamp (using {{gmdate()}}).
However, in order to do this with the
existing {{Zend_Log}} I have to override
the _entire_ 50 line {{Zend_Log::log()}}
method, which makes my subclass very
brittle.
I propose moving the event creation to a
method like so:
{noformat}
$event = $this->_packEvent($message,
$priority);
// ...
protected function
_packEvent($message, $priority)
{
return array_merge(array(
'timestamp' => date('c'),
'message' => $message,
'priority' => $priority,
'priorityName' => $this-
>_priorities[$priority]),
$this->_extras
);
}
{noformat}
Some of the tests for the selected
components include calls to the PHP
function date_default_timezone_set() to
change the date.timezone to allow the
their tests to execute correctly. The
problem is that these test don't change it
back to its previous value after the test
has executed, therefore changing the
test environment and invalidating any
tests which execute after wards.
362 of 510
Add a way to link php errors to a
Zend_Log object so that:
{code}
$log = Zend_Log::factory(...);
$log->registerErrorHandler();
{code}
would allow this to show up in the log:
{code}
trigger_error("Hello Notice",
E_USER_NOTICE);
{code}
ZF-9790 It is not possible to set options such as
the formatter via the config and
Zend_Application_Resource_Log. The
factory function accepts the parameter
but ignores it, the constructor does not
have any support to pass in options or
setting them.
ZF-9096 In
Zend_Log_Filter_Abstract::_parseConfig
() line 50, call Zend_Config::asArray().
current code
{code}
$config = $config->asArray();
{code}
change for
{code}
$config = $config->toArray();
{code}
ZF-9112 Method should be toArray()
363 of 510
Instead of
{code}
if (!is_array($config) || empty($config)) {
require_once 'Zend_Log_Exception.php';
throw new Zend_Log_Exception(
'Configuration must be an array or
instance of Zend_Config'
);
}
{code}
it should be
{code}
if (!is_array($config) || empty($config)) {
require_once 'Zend/Log/Exception.php';
throw new Zend_Log_Exception(
'Configuration must be an array or
instance of Zend_Config'
);
}
{code}
ZF-7335 I will add them. Currently we have this
page:
http://framework.zend.com/wiki/display/Z
FDEV/Subversion+Standards#Subversio
nStandards-TipSVNautoprops
364 of 510
All public methods of Zend_Log should
return the current instance (return $this)
so a fluent usage is possible.
Sometimes its necessary to add more
writers or event items at once and a
fluent interface makes this nicer to
implement.
There should be no downside because in
its current state all public methods return
nothing.
{code}$logger->addWriter($writer);
$logger->setEventItem('foo1', 'bar1');
$logger->setEventItem('foo2',
'bar2');{code}
vs.
{code}$logger->addWriter($writer)
->setEventItem('foo1', 'bar1')
->setEventItem('foo2', 'bar2');{code}
365 of 510
While running running script1 below i get
the following warning
{quote}
Warning: unable to send log entries via
email; message = Unable to write to
stream; code = 0; exception class =
Zend_Log_Exception in
/Users/attachmentgenie/Devschuur/Proje
cts/fam-
vogelaar/trunk/library/Zend/Log/Writer/M
ail.php on line 275
{quote}
but when i run script2 below the email
gets delivered as expected
i traced the error down to
{quote}
( if (!$this->_validHost->isValid($host)) {
{quote}
on row 190 in class
Zend_Mail_Protocol_Smtp
where script1 throws an error and script2
returns true
{code}
$config = array('ssl' => 'tls',
366 of 510
ZF-9205 Zend_Dojo's _renderLayers() method
includes a call to htmlentities().
Unfortunately, it does not pull the
encoding from the view object, which
means it will only work on ASCII
characters, which can potentially open
multibyte XSS vectors.
Zend_View_Helper_Placeholder_Contain
er, line 29, hardcodes the encoding
(instead of using the view object's), and
should likely use htmlspecialchars()
instead.
Zend_Form_Decorator_HtmlTag,
Zend_Service_Twitter,
Zend_Feed_Element, and
Zend_View_Helper_Navigation_Sitemap
hardcode htmlspecialchars() calls to use
UTF-8.
Zend_Log_Formatter_Xml,
Zend_Tag_Cloud_Decorator_HtmlTag,
Zend_Tag_Cloud_Decorator_HtmlCloud,
and Zend_View_Helper_HeadStyle do
not pass encoding information at all.
Zend_Filter_HtmlEntities defaults to ISO-
8859-1, but should default to UTF-8
367 of 510
The error is thrown because the constant
doesn't exist in that class found in
Zend_Log_Filter_Priority version 1.9.10
alpha. the potential fix is attached:
{code}
@@ -78,12 +78,12 @@
), $config);
// Add support for constants
- if (is_string($config['priority'])) {
- $config['priority'] =
constant($config['priority']);
+ if (!is_numeric($config['priority'])) {
+ $config['priority'] =
constant("Zend_Log::".$config['priority']);
}
return new self(
- $config['priority'],
+ (int) $config['priority'],
$config['operator']
);
}
{code}
The actual error
Warning: constant(): Couldn't find
constant 4 in
Class Zend_Log_Writer_Abstract,code in
trunk, in line 117.
call $config->asArray(), change for
$config->toArray().
368 of 510
Class Zend_Log_Writer_Abstract
function write($event)
Zend_Log_Writer doesn't test all filters
before reject the message.
How to test it:
{code}
$logger = new Zend_Log();
$writer = new
Zend_Log_Writer_Stream('php://output');
$logger->addWriter($writer);
$filter1 = new
Zend_Log_Filter_Priority(Zend_Log::EM
ERG, "==");
$writer->addFilter($filter1);
$filter2 = new
Zend_Log_Filter_Priority(Zend_Log::INF
O, "==");
$writer->addFilter($filter2);
// blocked but should not !
$logger->info('Informational message');
// blocked but should not !
$logger->emerg('Emergency message');
Create a Zend Monitor log writer for
Zend_Log, along with a bootstrap
resource.
369 of 510
You can set an formatter for an
Zend_Log_Writer_Syslog object. But as
it seems this formatter is never used.
In my opinion the formatter should be
utilized, once you are allowed to set
one... See this very trivial patch to
Zend/Log/Writer/Syslog.php:
--- Syslog.php (revision 19)
+++ Syslog.php (working copy)
@@ -170,6 +170,8 @@
$this->_initializeSyslog();
}
- syslog($priority, $event['message']);
+ $line = $this->_formatter-
>format($event);
+
+ syslog($priority, $line);
}
}
370 of 510
Zend_Log_Writer_Db fails on MySQL
due to an incorrect date format being
used.
Zend_Log creates timestamps in an ISO-
8601 format including the timezone,
using date('c').
MySQL can not write this data to a
datetime field:
Input: 2009-11-21T03:35:13+01:00
Output: Zend_Db_Exception with text:
SQLSTATE[22007]: Invalid datetime
format: 1292 Incorrect datetime value:
'2009-11-21T03:56:33+01:00' for column
'timestamp' at row 1
Problem seems to be with the timezone;
MySQL manual makes no mention of the
timezone at all, and removing it from the
input renders it valid to MySQL.
Current Zend_Log_Writer_Db is
unusable with MySQL in its default state
(no column mapping), so considering this
a major issue.
Currently Zend_Log events are static
values. Sometimes defining a callback
instead would be very useful.
In documentation the setApplication()
method written although it is called
setApplicationName() in code.
371 of 510
ZF-10015 In Zend_Log_Writer_Syslog::_facility is
defined as string and it is sent to
openlog() this way hence openlog()'s 3rd
parameter should be long, choosen from
the predefined PHP constans LOG_*.
I would recommend to use the string with
constant($this->_facility) and document
that user should specify the constant
name to use if required.
So the patch:
{code}
protected function _initializeSyslog()
{
self::$_lastApplication = $this-
>_application;
self::$_lastFacility = $this->_facility;
openlog($this->_application, LOG_PID,
cnstant($this->_facility));
}
{code}
372 of 510
Using The Log Extension
Zend_Log_Writer_Firebug i can output
debug statements to the firefox plugin
in the normal view rendering process.
The same log statement in an action
controller right before
$this->_helper->json($response);
is not added to the response!
The used action controller implements
the default Zend_Controller_Action
I think especially in such a case it makes
the most sense.
ZF-5741 When I use Zend_Log_Writer_Stream to
write to file, the file is opened even
though no data is actually written to the
log. It would save unnecessary
filesystem accesses if the file would be
opened only in case something is
actually written (e.g. on the first write).
ZF-10472 I think it would be better to not hardcode
the path in line 63, but use the
$zfCoreLibrary variable from
TestHelper.php
373 of 510
ZF-9029 I will add them if necessary.
Currently we have this page:
http://framework.zend.com/wiki/display/Z
FDEV/Subversion+Standards#Subversio
nStandards-TipSVNautoprops
If it's important, perhaps we could add it
into coding standards.
374 of 510
ZF-8085, ZF-10798 Some files contain CRLF: 100% 100% 900
{code}
find . -name '*.php' -print0 | xargs -0 sed -
-regexp-extended --in-place 's/\r\n/\n/g'
{code}
Some files contain TABS:
{code}
find . -name '*.php' -print0 | xargs -0 sed -
-regexp-extended --in-place 's/\t/ /g'
{code}
Some files contain endline spaces:
{code}
find . -name '*.php' -print0 | xargs -0 sed -
-regexp-extended --in-place 's/[ ]*$//g'
{code}
By running this 3 commands on the top
of standard directory. It could be applied
to library and tests.
After that, a pre-commit hook could be
added to test all of them (but it's another
history ;) )
375 of 510
In Writer_Firebug::_write() the
traceOffset is hardcoded at line 185. The
leads to the problem, that in some cases
it calculated the wrong file and line, in
which the log should occur.
Somewhere in a function or class-
method
{code}// Simple file
$log = new Zend_Log(new
Zend_Log_Writer_Firebug();
function test($log) {
$log->info('test');
$log->log('test', 6);
}
test ($log);{code}The first one works
correctly, it gives the correct file and line.
The second one (in this case) sends no
file and line, in this and all other cases it
goes one step "too far".
The hardcoded value expects, that the
log is called via __call() in every case,
but if I call log() directly there is one
stack-entry to less, or if I overwrite
Zend_Log::log() or Zend_Log::__call()
(or both), the stack trace is "too big" and
will return some file/line from some of the
log-classes.
Please add setConfig(Zend_Config
$config) & setOptions(array $options)
functionality to Zend_Log &
Zend_Log_Writer_Abstract.
376 of 510
Hi everyone,
If you use Zend_Log_Writer_Mail with
Zend_Log and Zend_Log calls the
desctruct method, then
Zend_Log_Writer_Mail sends all Logs
per email. But if an error occurs while
sending the email,
Zend_Mail_Transport_Sendmail throws
an exception and you get the following
error:
Output: Fatal error: Exception thrown
without a stack frame in Unknown on line
0
{panel}
2)
testShutdownRemovesReferenceToData
baseInstance(Zend_Log_Writer_DbTest)
Failed asserting that <string:Database
adapter is null> matches PCRE pattern
"/shutdown$/i".
{panel}
377 of 510
ZF-6085 If I give a bogus formatter to a writer, the
formatter is accepted silently.
If I try to use the writer, a fatal error (eg
"Fatal error: Call to a member function
format() on a non-object in
/usr/share/php5/Zend/Log/Writer/Stream.
php on line 93") is outputted.
I think that the fatal error should be
avoided and an exception should be
thrown when the bogus formatter is set.
Regards,
HUjuice
ZF-6086 If I give a bogus formatter to a writer, the
formatter is accepted silently.
If I try to use the writer, a fatal error (eg
"Fatal error: Call to a member function
format() on a non-object in
/usr/share/php5/Zend/Log/Writer/Stream.
php on line 93") is outputted.
I think that the fatal error should be
avoided and an exception should be
thrown when the bogus formatter is set.
Regards,
HUjuice
378 of 510
I'm actually surprised that
Zend_Log_Writer_Db doesn't test the DB
connection before using it.
Also, it doesn't even catch any exception
from Zend_Db, which could lead, in
some rare cases, to infinite loops.
Consider a Zend_Log that logs DB
connection errors. What if a
Zend_Log_Writer_Db has been provided
into it , and the DB is down ?
2 things :
The heavy one would be to use in the
Zend_Log_Writer_Db's constructor
{code}
try {
$this->_db->getConnection();
} catch (Zend_Db_Exception $e) {
// some stuff like throw new
Zend_Log_Exception($e-
>getMessage());
}
{code}
That is heavy as it requires a physical
connection to the DB even if it won't use
it in the future.
379 of 510
right now the exception message shown
is "Bad log priority".
But that may not be the actual reason for
the error. Suppose in my code I have
$log->addEventItem('foo','bar');
This would throw the "Bad log priority"
exception message since __call() is
overridden to provide a convenience
method for doing
$log->priorityName('message');
instead of
$log->log('message',
Zend_Log::PRIORITY_NAME);
the current exception message thrown
isn't helpful because it is context
sensitive. A more useful message would
be "__call() is unable to trap the method
$method" or something to that effect.
380 of 510
Zend_Log_Writer_Stream throws
Zend_Log_Exception (in several places)
without calling
require_once('Zend/Log/Exception.php')
first.
This ends up in a fatal error being thrown
instead of the proper exception:
Fatal error: Class 'Zend_Log_Exception'
not found in
/home/shahar.e/Zend/workspaces/Defaul
tWorkspace/ZendFramework/library/Zen
d/Log/Writer/Stream.php on line 66
381 of 510
Hi.
Some log writers like the firebug one are
capable of logging arrays, but
Zend_Log_Filter_Message only accepts
strings (by passing $event['message'] to
preg_match() directly).
Proposed modification:
public function accept($event)
{
$message = $event['message'];
if(is_array($event['message'])) {
$message =
var_export($message,TRUE);
}
return preg_match($this->_regexp,
$message) > 0;
}
Such that it won't throw the warning
"preg_match() expects parameter 2 to be
string, array given in
/usr/share/httpd/ZendFramework-
1.7.4/library/Zend/Log/Filter/Message.ph
p"
382 of 510
ZF-7522 When you initialize the logger in the
bootstrap file,
for every request a log file will
automatically be created if it doesn't
exist, even when you do not plan to log.
I suggest to create the logfile only the
first time something has to be logged.
Example:
$logger = new Zend_Log();
$writer = new
Zend_Log_Writer_Stream($path . "logfile-
" . date("Ymd-H") . ".log");
$logger->addWriter($writer);
I create a logfile per hour.
If there is nothing to log for a specific
day, this will create 24 empty logfiles,
because the logfile is created in the
constructor of Zend_Log_Writer_Stream.
383 of 510
Please add this default value with the
default error code to make faster the
debugging and for debugging doesn't
necessary.
{code}
/**
* Zend_Log (line 119)
*/
public function log($message, $priority)
// change to:
/**
* Set the default priority, it it hasn't set
*/
public function log( $message, $priority =
7)
{code}
In currently available online manual 100% 100% 600
(http://framework.zend.com/manual/en/z
end.log.writers.html), section 30.2.1
"Zend_Log_Writer_Stream", it's written
on line 2: "Alternatively, you *can may
like*"
Maybe it would be more convenient if
Zend_Log didn't throw exception (No
writers were added) when trying to log
and there were no writers set.
I kinda don't want to add Null writers just
to make all my log calls quiet.
Wouldn't it be better (and faster) if that
sanity check inside Zend_Log::log() was
removed and just return if there are no
writers?
384 of 510
As a developer I want log functionality to:
- be terse, and compact, but still
readable
- provide me the information I need,
when inspecting it.
The latter requirement asks for formatted
messages including values of variables.
The former requirement tells me that a
syntax like
$log->log(sprintf($format, ...), $level)
could be expressed better like:
$log->log($level, $format, ...)
I implemented this in a class derived
from Zend_Log. I think it would be nce to
add this to the framework class itself.
Note that for reasons of backward
compatibility I changed the (in my opinion
preferred) order of the arguments to:
$log->log($format, $level, ...)
Though, by inspecting type it is probably
possible to support both. But for the
shortcut methods this isn't a problem
385 of 510
ZF-4927 {panel}
6)
testAdvancedLogging(Zend_Log_Writer_
FirebugTest)
[json] (json_encode_r) type is
unsupported, encoded as null.
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Json.php:100
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Json.php:100
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Protocol/J
sonStream.php:150
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Protocol/J
sonStream.php:97
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:448
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:401
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Log/Writer/Firebug
.php:185
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Log/Writer/Abstrac
t.php:80
/home/cawa/ZendFramework/svn/framew
testBasicLogging(Zend_Log_Writer_Fire
bugTest) takes more than 15 minutes if
it's started using whole ZF tests suite.
386 of 510
{panel}
4)
testAdvancedLogging(Zend_Log_Writer_
FirebugTest)
ReflectionProperty::getValue() expects
exactly 1 parameter, 0 given
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:522
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:514
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:562
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:514
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:562
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:562
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
Php.php:562
/home/cawa/ZendFramework/svn/framew
ork/trunk/library/Zend/Wildfire/Plugin/Fire
There is a require_once statement at top 100% 100% 600
of Zend/Log.php that is *only* required
for addFilter(). So I think we should move
it to addFilter() where it is needed.
387 of 510
ZF-2618 My code uses a custom error handler,
which is used to trap some errors and
throw exceptions instead.
Zend_Log::log() is triggering my error
handler and breaking my code. Here is
the output:
1) testGetMessage(ImapClientTest)
Exception: Imap
error(Zend/Log.php:138): date(): It is not
safe to rely on the system's timezone
settings. Please use the date.timezone
setting, the TZ environment variable or
the date_default_timezone_set()
function. In case you used any of those
methods and you are still getting this
warning, you most likely misspelled the
timezone identifier. We selected
'America/New_York' for 'EDT/-4.0/DST'
instead
388 of 510
While running AllTests for ZF (r11515)
under WindowsXP, PHP 5.2.6, PHPUnit
3.3.0 the following Exception occurs.
{code}
RuntimeException: Log.php does not
exist in C:\php\PEAR\PHPUn
it\Util\Filter.php on line 189
Call Stack:
0.0051 222224 1. {main}()
C:\php\PEAR\PHPUnit\TextU
I\Command.php:0
0.9964 4158848 2.
PHPUnit_TextUI_Command::main() C:\
php\PEAR\PHPUnit\TextUI\Command.ph
p:685
0.9976 4168280 3.
PHPUnit_Runner_BaseTestRunner-
>getTest() C:\
php\PEAR\PHPUnit\TextUI\Command.ph
p:88
201.1284 122332640 4.
ReflectionMethod->invoke() C:\php\
PEAR\PHPUnit\Runner\BaseTestRunner
.php:221
201.1284 122332640 5. AllTests::suite()
C:\Zend Framewor
k\tests\AllTests.php:0
The example in the Formatting to XML
subsection of the Zend_Log section of
the Zend Framework Certification Study
Guide is the same as the Simple
formatter example directly before it, likely
as the result of a copy and paste error.
389 of 510
Is it real necessary to use
ReflectionClass in __constructor? It
looks like additional dependence and
maybe it could be resolved in more
convinient way.
$r = new ReflectionClass($this);
$this->_priorities = array_flip($r-
>getConstants());
Output:
{panel}
4)
testBasicLogging(Zend_Log_Writer_Fire
bugTest)
Failed asserting that <boolean:false> is
true.
{panel}
390 of 510
ZF-2062 {quote}
$logger = new Zend_Log();
$writer = new
Zend_Log_Writer_Stream('php://output');
$writer->setFormatter(new
Zend_Log_Formatter_Xml());
$logger->addWriter($writer);
$logger->err('&');
{quote}
got error:
{quote}
DOMElement::__construct() [<a
href='function.DOMElement---
construct'>function.DOMElement---
construct</a>]: unterminated entity
reference amp' in
\library\Zend\Log\Formatter\Xml.php:78
{quote}
The file with the class of
Zend_Log_Writer_Firebug is disapeared
in the 1.5.3 version.
391 of 510
When running this code from command
line (on Windows)
{code}
<?php
require_once "Zend/Loader.php";
Zend_Loader::registerAutoload();
$log = new Zend_Log();
$writerFirebug = new
Zend_Log_Writer_Firebug();
$log->addWriter($writerFirebug);
$log->log('hi', 2);
{code}
It dies with:
{quote}Catchable fatal error: Argument 1
passed to
Zend_Controller_Plugin_Abstract::setRe
sponse() must be an instance of
Zend_Controller_Response_Abstract,
null given, called in
\library\Zend\Wildfire\Channel\HttpHeade
rs.php on line 248 and defined in
\library\Zend\Controller\Plugin\Abstract.p
hp on line 75{quote}
You also need to register the plugin:
$front-
>registerPlugin(Zend_Wildfire_Channel_
HttpHeaders::getInstance());
It should be done automatically or
mentioned in docs
[detail|http://www.nabble.com/Db_Profiler
_Firebug-documentation-
td18904176.html#a18904176]
392 of 510
Unit test passing stops with the following
output:
{panel}
Fatal error: Cannot redeclare class
Zend_Log_Writer_FirebugTest_Request
in
/home/cawa/ZendFramework/svn/framew
ork/trunk/tests/Zend/Log/Writer/FirebugT
est.php on line 204
{panel}
Newly added FirePHP works great and it
handles more than strings, so a nicely
formatted array or exception can be
printed in firebug console.
Unfortunately standard zend log
writer/formatter don't support anything
else than a string and if multiple writers
are used it's causing notices eg.
{code}
$logger = new Zend_Log();
$fireWriter = new
Zend_Wildfire_FirebugLogWriter();
$logger->addWriter($fireWriter);
$streamWriter = new
Zend_Log_Writer_Stream("/dev/null");
$logger->addWriter($streamWriter);
$logger->info(range(1,10));
{code}
triggers Notice: Array to string
conversion in
/home/sites/shared/library/Zend/Log/For
matter/Simple.php on line 72
It would be nice if the formatter ignored
393 of 510
Zend_Log dosen't seem to work for an
oracle database at all, but when I switch
to mysql or postgresql it works fine. here
is the code.
{code:none}
$db = Zend_Registry::get('db');
/** Logging * */
$log = new Zend_Log();
//Log either to database or file
if (strcasecmp($config->log->adapter,
'database') == 0) :
$columnMapping = array('lvl' => 'LVL',
'msg' => 'MSG');
$log->addWriter(new
Zend_Log_Writer_Db($db, 'LOGS',
$columnMapping));
//$log->info('Informational message');
elseif (strcasecmp($config->log-
>adapter, 'file') == 0 && $config->log-
>file):
$log->addWriter(new
Zend_Log_Writer_Stream(realpath(
rtrim($config->paths->logs, '/\\') .
DIRECTORY_SEPARATOR . $config-
>log->file
)));
else:
$log->addWriter(new
Zend_Log should have a getWriters()
method to return the list of attached
writes for better testing.
394 of 510
If we want only log two specific level, we
will do something like:
{quote}
$filter1 = new
Zend_Log_Filter_Priority(Zend_Log::ER
R,'eq');
$writer->addFilter($filter1);
$filter2 = new
Zend_Log_Filter_Priority(Zend_Log::ALE
RT,'eq');
$writer->addFilter($filter2);
{quote}
This will only log Zend_Log::ERR
because in the writer, it will be return if
we send an event Zend_Log::ALERT,
because the loop will return at the first
false match and will not test the second
filter.
{quote}
foreach ($this->_filters as $filter) {
if (! $filter->accept($event)) {
return;
}
}
{quote}
A possible solution could be:
{quote}
$accepted= false;
395 of 510
The ->setEventItem() method calls the
passed function reference immediately
and sets the value straight away. i.e. it
binds the value before a log message is
even sent. This may be the intended
functionality or it may not but it makes it
unuseable in a dynamic environment.
Consider this scenario:
You want to set up logging for an
application and want to log the user id of
the logged on user. You can't do this if
your authentication service is not yet
running or if the user hasn't yet logged
on. Binding the value this early on will not
allow you to log the actual user id. Thus
the following code fails:
self::$_logHandler[$tag]-
>setEventItem('uid',$this->getUid());
$format =
'%uid%|%timestamp%|%priorityName%|
%priority%|%message%' . PHP_EOL;
$formatter = new
Zend_Log_Formatter_Simple($format);
$writer->setFormatter($formatter);
because getUid relies on a service
(based on Zend_Auth) that, although
396 of 510
I am run the following code with
PHPUnit:
---
<?php
set_include_path(get_include_path() .
PATH_SEPARATOR . '/path/to/Zend...');
ini_set('display_errors', 'on');
require 'Zend/Loader.php';
Zend_Loader::loadClass('Zend_Log_Writ
er_Stream');
Zend_Loader::loadClass('Zend_Log');
$writer = new
Zend_Log_Writer_Stream('php://output');
$logger = new Zend_Log($writer);
//$writer = null; // uncomment for work-
around
class tst extends
PHPUnit_Framework_TestCase {
public function test1() { }
}
---
which causes
Fatal error: Call to a member function
397 of 510
My coworkers and I found this out the
VERY hard way .. but here it comes.
When using _logging_ with Zend_Cache
but not setting the _logger_ option.
Zend_Cache uses
Zend_Log_Writer_Stream('php://output')
as default logger. This can cause some
trouble. Because on destruction the
Zend_Log_Writer_Stream does a
*fclose* on its stream. So if the
Zend_Cache is destroyed, no more
output can be sent. In our opinion the
_php://output_ should never be closed.
This can therefor be thought of as a bug
in PHP (hmm :D). But as a fix for the
ZendFramework we suggest this patch ..
{code}
Index: Log/Writer/Stream.php
===============================
===============================
=====
--- Log/Writer/Stream.php (revision 9612)
+++ Log/Writer/Stream.php (working
copy)
@@ -43,6 +43,13 @@
protected $_stream = null;
398 of 510
Hi, I found some improvements to add to
different Zend_Log files.
First, the $event treated in
Zend_Log_Writer_Abstract and all its
children should be casted to Array in the
function definitions ( for safety ).
Second, I think that Zend_Log should be
iterable to give back the Writers it has
been provided, and additionaly all the
writers should be "toStringable" to reflect
the name of their own class
Same for Zend_Log_Writer_Mock : it
should be recursive Iterable so that a
simple foreach loop on it would give back
all the messages it's been containing.
All those patches are ready in my local
copy and waiting for approvement.
I can as well take care of the other
improvements asked for that component,
such as ZF-2618 that could lead to a
warning show if default timezone has not
been set in PHP, ZF-2428 as well....
Let me know.
399 of 510
ZF-9484 {quote}
The DELAYED option for the INSERT
statement is a MySQL extension to
standard SQL that is very useful if you
have clients that cannot or need not wait
for the INSERT to complete. *This is a
common situation when you use MySQL
for logging* (...)
{quote}
Using INSERT DELAYED would improve
the speed of Zend_Log_Writer_Db. But
you can't check, if the INSERT was
successful. So maybe it should be an
optional feature.
400 of 510
In my opinion, the mapping logic is too
rigid. If there is a mapping present, the
insertion of log messages includes those
fields *and only those fields* each and
every time. This produces undesired
results when:
# New fields are added using the
setEventItem method and there is no
mapping for them. These fields will never
be inserted.
# When fields are empty and must be
inserted as NULL, insertion failure. Since
the fields are all named, these should
just be skipped.
# Fields that don't need to be mapped
still must have a mapping entry, just so it
is included ('message' => 'message').
I think most people would use mapping
as an overload of field names. That
would address all the issues above.
Fields that are not overloaded (name
wise) would be inserted as is. Something
like the following:
Database (
creation,
priority,
401 of 510
Since the _write function is protected, it 0% 0%
can't be overloaded, so it should remain
as lean as possible for easier
subclassing.
In my opinion, the _write function should
be trimmed down to:
{code}
protected function _write($event)
{
if ($this->_db === null) {
throw new
Zend_Log_Exception('Database adapter
instance has been removed by
shutdown');
}
$this->_db->insert($this->_table,
$dataToInsert);
}
{code}
All of the mapping functions should be
done in write():
{code}
/**
* Log a message to this writer.
402 of 510
ZF-4431 At the moment the format and the
timezone of the timestamp in the log is
hardcoded (date('c')).
This is very unattractive because of at
least two reasons:
1. It is not possible to change the format
e.g. to see milliseconds for performance
profiling in the log
2. It is not possible to have a log with
UTC timestamps even if the web
application has other locale settings.
My recommendation is to give the
possibility to assign a Zend_Date object
to a Zend_Log object (or even better to a
Zend_Date_Formatter object) which
defines format and timezone for the log.
403 of 510
I personally find it hard to track down
where log entries are originating from
sometimes, so I wanted to add line and
file info to my log format like this:
$format = '%timestamp%
%priorityName% (%priority%):
%message% at line %line% in file
%file%' . PHP_EOL;
$formatter = new
Zend_Log_Formatter_Simple($format);
$writer->setFormatter($formatter);
However, "line" and "file" are not
currently available in Zend_Log's $events
array. So I wrote a patch to provide it.
Hope it might be considered for
inclusion.
Regards,
Mark Maynereid
{code:none}
diff Log.php LogNew.php
106c106
< $this->log(array_shift($params),
$priority);
---
ZF-563 It would be great if the log component
could provide a mechanism for purging
and rotating log files. This will allow
developers to rotate log files manually or
by setting up cron jobs.
404 of 510
I noticed that every log event database is
queried with log message.
I know components should be universal
and it could be problematic to use
destructor by default - in case of
uncatched exception it won't be called.
So how about optional flag in
constructor, which indicates that writer
should use lazy load?
Since front controller catches all
exceptions, destructors problem
disapears and It could be interesting
improvement for developers using ZF
MVC.
{code}
/*
* Normal behaviour, every event saves
message to database
*/
$writer1= new
Zend_Log_Writer_Db($db,
'log_table_name', $columnMapping);
/*
* Lazy loading is on, all messages are
saved at the end of script
*/
$writer2 = new
405 of 510
ZF-4190 When using the
Zend_Log_Formatter_Xml() formatter
during logging, a message which
contains an ampersand results in a
warning thrown by the constructor of
DOM_Element:
{code}
$writer = new
Zend_Log_Writer_Stream(logfile.xml);
$formatter = new
Zend_Log_Formatter_Xml();
$writer->setFormatter($formatter);
$logger = new Zend_Log($writer);
$testString = 'Posted something to
server?key=value&key2=value2';
$logger->log($testString,
Zend_Log::INFO);
{code}
Results in:
{code}
Warning: DOMElement::__construct()
[function.DOMElement---construct]:
unterminated entity reference
key2=value2
{code}
406 of 510
From the manual: "The
Zend_Log_Writer_Null is a stub that
does not write log data to anything. It is
useful for disabling logging or stubbing
out logging during tests."
I would recommend removing
Zend_Log_Writer_Null, and instead
making either Zend_Log_Writer or
Zend_Log configurable with an "enabled"
boolean.
For example:
{code}
[config.ini]
log.enable = true
[test.php]
$config = new Zend_Config('config.ini');
$log = new Zend_Log(new
Zend_Log_Writer, $config->log-
>toArray());
{code}
Alternatively, individual writers can be
configurable, or both.
Patching in a value for enable/disable of
logging is far easier than changing the
I'd like to remove a log writer, and it's not
difficult to imagine situations where one
would want to remove filters or unset
custom event items as well. Perhaps
priorities ought to be removable too, for
completeness.
407 of 510
I was able to extend several other Zend
Framework classes as they provide their
attributes as "protected" members.
For Zend_Log the attributes are provided
as "private" and are not accessible in
child classes.
Here are the attributes concerned
{code}
protected $_priorities = array();
protected $_writers = array();
protected $_filters = array();
protected $_extras = array();
{code}
I had to manually edit the Zend Code
which is not acceptable of course ;-)
It would break my app if I upgrade to a
next ZF release without manually
patching the changes.
I set the type to "Bug" as I consider it
being a design bug. Thanks for fixing it!
408 of 510
When using fwrite, the result should be
tested against the false boolean value.
Currently in Zend/Log/Writer/Stream.php
it is tested as ! @fwrite() which is true
when the fwrite was called with an empty
string.
When called with an empty string, 0
bytes are written and it is the normal
behaviour.
Here is the trivial patch:
{code}
Index:
/home/matt/dev/piwiktrunk/libs/Zend/Log/
Writer/Stream.php
===============================
===============================
=====
---
/home/matt/dev/piwiktrunk/libs/Zend/Log/
Writer/Stream.php (revision 14)
+++
/home/matt/dev/piwiktrunk/libs/Zend/Log/
Writer/Stream.php (working copy)
@@ -92,7 +92,7 @@
{
$line = $this->_formatter-
409 of 510
h4. Overview
In the manual for Zend_Log at "19.2.2.
Writing to Databases" the example there
seems to be incorrect.
It uses array(array( when it should be
array(
{code}
<?php
$params = array ('host' => '127.0.0.1',
'username' => 'malory',
'password' => '******',
'dbname' => 'camelot');
$db = Zend_Db::factory('PDO_MYSQL',
$params);
$columnMapping = array(array('lvl' =>
'priority', 'msg' => 'message'));
$writer = new Zend_Log_Writer_Db($db,
'log_table_name', $columnMapping);
$logger = new Zend_Log($writer);
$logger->info('Informational message');
?>
{code}
It appears Zend_Log does not return an
instance of itself at the moment, but for
convenience it might be a good idea to
return $this where possible
By using Zend_Log_Adapter_File the the
format in the Options dont replace.
Assume bad name (%level% -
>%priorityName% instead)
410 of 510
{code} 100% 100% 43200
class Zend_Log_Writer_Mail
extends Zend_Log_Writer_Mock {
private $mail = null;
public function __construct(Zend_Mail
$mail) {
$this->mail = $mail;
}
public function shutdown() {
if (!$this->shutdown) {
try {
if (count($this->events)) {
$body = $this->mail->getBodyText();
foreach ($this->events as $i => $event) {
$body.= $this->_formatter-
>format($event);
}
$this->mail->setBodyText($body);
$this->mail->send();
}
} catch (Exception $e) {
// loggen ?
throw $e;
}
}
parent::shutdown();
ZF-1237 {code}$formatter = new
Zend_Log_Formatter($format);{code}
Should be
{code}$formatter = new
Zend_Log_Formatter_Simple($format);{c
ode}
411 of 510
Feedback from mailing list:
Please implement a method to explicitly
close resources (file handles, Db
connections) in Zend_Log_Writer
classes.
It won't matter for 99% of users, but
since ZF can be used CLI and potentially
for long-lived apps, it probably wouldn't
hurt to use an explicit close.
ZF-1242 There is no Formatter
Zend_Log_Formatter. In the next
example its correctly written as
Zend_Log_Formatter_Simple
http://framework.zend.com/manual/en/ze
nd.log.formatters.html#zend.log.formatte
rs.simple
There should be a way to set a minimum
level and/or a level-mask (like it was
before api-change).
Its annoying to add a single formatter to
all existing writers, so it would be easier
to allow to define a global formatter to
the log and single writers are able to
overwrite it (if needed).
412 of 510
There's a line in the documentation, in
the section on using the Log Db Writer
{code}
$writerDB = new
Zend_Log_Writer_Stream($dbAdapter,
'logs',
array(array('lvl' => 'priority', 'msg' =>
'message')) );
{code}
This should use Zend_Log_Writer_Db.
413 of 510
--- File: data/bootstrap.php ---
require_once 'Zend.php';
Zend::loadClass('Zend_Log');
Zend::loadClass('Zend_Log_Adapter_Fil
e');
Zend_Log::registerLogger(new
Zend_Log_Adapter_File('data/logs/ecmc.
log'),'File');
Zend_Log::log('First logging message.');
--- File EOF ---
--- Start output ---
<b>Fatal error</b>: Uncaught exception
'Zend_Log_Exception' with message 'No
instance of log named "LOG"'
in /html/Zend/Log.php:178
Stack trace:
#0 html/Zend/Log.php(337):
Zend_Log::_getInstance('LOG')
#1 html/Zend/Log.php(405):
Zend_Log::getFields('LOG')
#2 data/bootstrap.php(47):
Zend_Log::log('First logging m...')
#3 html/index.php(23):
require_once('data/bootstr...')
#4 {main}
414 of 510
We have a new design for Zend_Log,
that avoids the use of static method calls
and provides much more functionality
than the old design.
When it reaches a state of completion,
please move it from incubator to core.
Remember to move the unit tests and
documentation too, and remove
references to unit tests and docs from
AllTests.php and manual.xml in the
incubator.
415 of 510
This is extremely minor, but in
Zend_Log_Adapter_File::open() an
exception is thrown if the fopen call fails.
The fopen call acts upon $this-
>_filename, but the exception references
$filename in it's message.
This means that if this fails when open()
is called with no arguments, but the
filename member of the object is set, the
exception will say:
'Log file "" could not be opened'
I would assume that this also affects the
other adapters.
The solution is simple, change the
following on line 189:
throw new
Zend_Log_Adapter_Exception("Log file
\"$filename\" could not be opened");
to:
throw new
Zend_Log_Adapter_Exception("Log file
\"{$this->_filename}\" could not be
opened");
Zend_Log_Adapter_Db::write() is using
the insert()-method of
Zend_Db_Adapter_Abstract in a wrong
way so you have to create a workaround
to use it for your own Zend_Db_Adapter.
I think I´ve created a good patch which
will solve this problem:
http://download.flabben.net/Zend_Log_A
dapter_Db-Patch.phps
http://download.flabben.net/Zend_Log_A
dapter_Db-Test.txt
416 of 510
--- File: data/bootstrap.php ---
require_once 'Zend.php';
Zend::loadClass('Zend_Log');
Zend::loadClass('Zend_Log_Adapter_Fil
e');
Zend_Log::registerLogger(new
Zend_Log_Adapter_File('data/logs/ecmc.
log'),'File');
Zend_Log::log('First logging message.');
--- File EOF ---
--- Start output ---
<b>Fatal error</b>: Uncaught exception
'Zend_Log_Exception' with message 'No
instance of log named "LOG"'
in /html/Zend/Log.php:178
Stack trace:
#0 html/Zend/Log.php(337):
Zend_Log::_getInstance('LOG')
#1 html/Zend/Log.php(405):
Zend_Log::getFields('LOG')
#2 data/bootstrap.php(47):
Zend_Log::log('First logging m...')
#3 html/index.php(23):
require_once('data/bootstr...')
#4 {main}
ZF-2364 We need an option to limit the file-size to
keep it under.
TIA
417 of 510
As different logging styles are
appropriate for varied situations,
Zend_Log should be able to support
logging:
# the log level value (e.g., "16")
# the log level name or string (e.g.,
"SEVERE")
# both the log level name and value, in
whatever order (e.g., "16 SEVERE")
This currently affects the "format" option
of the adapter classes.
418 of 510
When using Zend::log with the simple
text logging I ran a test to see what
happened if the file is not writeable. I.e.
$data = 'some string';
Zend_Log::registerLogger(new
Zend_Log_Adapter_File('/path/to/log.txt')
);
Zend_Log::log($data);
This crashes PHP since the __destruct
function in Zend_Log_Adapter_File calls
$this->flush() which throws an exception
if the file cannot be written to. During my
learning of PHP5 I have seen that a
__destruct method cannot throw an
exception. The error returned is:
Fatal error: Exception thrown without a
stack frame in Unknown on line 0
I am not sure the best practise in this
case, though I presume testing if the file
can be written to should be done
elsewhere than the destructor (i.e. as
part of the Zend_Log::registerLogger
method).
Zend_Log needs unit tests.
419 of 510
I dont think you should be able to
unregister the default logger as this will
produce errors if you are using multiple
loggers.
{code}
require_once 'Zend/Log.php'; //
Zend_Log base class
require_once
'Zend/Log/Adapter/File.php'; // File log
adapter
require_once
'Zend/Log/Adapter/Console.php'; //
Console log adapter
Zend_Log::registerLogger(new
Zend_Log_Adapter_File('framework.txt'),'
File');
Zend_Log::registerLogger(new
Zend_Log_Adapter_Console(),
'Console');
Zend_Log::setDefaultLogger('File');
Zend_Log::unregisterLogger('File');
Zend_Log::log('Log Text Here');
{code}
Produces error:
add method debug(), info(), warning(),
error() for supplement to log()
Thanks
420 of 510
add more predefined field, like %date%,
%time%, %datec% for formatting
Zend_Log::registerLogger(new
Zend_Log_Adapter_File('log/mylogfile.txt'
));
Zend_Log::setAdapterOption("format","%
date% (%level%) %message%");
So I don't have to add 'date' each time I
call log
Zend_Log::log("Param: $noid $what" ,
Zend_Log::LEVEL_DEBUG,
array("date"=>date("c")) );
Thanks
ZF-270 Setting multiple default loggers like this
{code}
Zend_Log::setDefaultLogger(array('Cons
ole', 'File'));
{code}
raises exeption
421 of 510
ZF-271 Trying to log such this
{code}
Zend_Log::log('Log text here',
Zend_Log::LEVEL_DEBUG, array('File',
'Console'));
{code}
raises exeption
{panel}
Fatal error: Uncaught exception
'Zend_Log_Exception' with message 'No
instance of log named "Array"' in
w:\usr\svn_libs\zend\library\Zend\Log.ph
p:178 Stack trace: #0
w:\usr\svn_libs\zend\library\Zend\Log.ph
p(337): Zend_Log::_getInstance(Array)
#1
w:\usr\svn_libs\zend\library\Zend\Log.ph
p(405): Zend_Log::getFields(Array) #2
w:\home\framework\www\index.php5(58)
: Zend_Log::log('Total queries: ...', 1,
Array) #3 \{main} thrown in
w:\usr\svn_libs\zend\library\Zend\Log.ph
p on line 178
{panel}
Please add feature "Rolling File
Appender" to Zend_Log.
For example every 20MB log file will be
rolled, at maximum 10 log files.
Thanks
422 of 510
The 'write()' method seems to utilise
outdated calls to the _dbAdapter object,
including an obsoleted 'escapeString'
method. In addition, there are a few lines
of sql generation that could easily be
passed directly to the _dbAdapter itself.
Requires a simple change from:-
{code}
public function write($fields)
{
/**
* If the field defaults for 'message' and
'level' have been changed
* in the options, replace the keys in the
$field array.
*/
if ($this->_options['fieldMessage'] !=
'message') {
$fields[$this->_options['fieldMessage']] =
$fields['message'];
unset($fields['message']);
}
if ($this->_options['fieldLevel'] != 'level') {
$fields[$this->_options['fieldLevel']] =
$fields['level'];
unset($fields['level']);
}
423 of 510
http://framework.zend.com/developer/tick
et/16
Zend Log throws an error if you register
all log adapters with a name (or without a
default name to be exact).
Copy and paste from the manual -
section 9.4:
{code}
require_once 'Zend/Log.php'; //
Zend_Log base class
require_once
'Zend/Log/Adapter/File.php'; // File log
adapter
require_once
'Zend/Log/Adapter/Console.php'; //
Console log adapter
Zend_Log::registerLogger(new
Zend_Log_Adapter_File('framework.txt'),
'File');
Zend_Log::registerLogger(new
Zend_Log_Adapter_Console(),
'Console');
Zend_Log::log('First logging message.');
{code}
Results in:
424 of 510
Superbiji <superbiji@gmail.com> wrote:
> I wonder if :
>
Zend_Log::setAdapterOption("format","%
date% (%level%) %message%");
>
> Can produce something like:
> 2006-06-16T23:42:44+07:00 (DEBUG)
Result: 1170079 Static information
>
> Not:
> 2006-06-16T23:42:44+07:00 (1)
Result: 1170079 Static information
>
Because of using a bitwise OR operator
between the selected log level and the
logger level mask, Zend_Log logs all
levels, ignoring the level mask.
425 of 510
Σ Remaining Estimate Σ Original Estimate Labels Tags Fix Version Priority
documentation
426 of 510
427 of 510
428 of 510
429 of 510
430 of 510
431 of 510
432 of 510
433 of 510
434 of 510
435 of 510
436 of 510
437 of 510
438 of 510
439 of 510
440 of 510
441 of 510
442 of 510
443 of 510
444 of 510
445 of 510
446 of 510
447 of 510
448 of 510
449 of 510
450 of 510
451 of 510
Must Have
452 of 510
453 of 510
Must Have
454 of 510
455 of 510
documentation, method, syslog
456 of 510
openlog, parameter, syslog, type
457 of 510
Zend_Log_Writer_Firebug
Zend_Log_AllTests, hardcode, path
458 of 510
459 of 510
0
460 of 510
config, log
461 of 510
Zend_Log, Zend_Log_Writer_Mail
Should Have
462 of 510
Exception, Zend_Log,
Zend_Log_Formatter_Simple
Zend_Log, exceptions
463 of 510
464 of 510
bad_log_priority, exception_message,
zend_log, zend_log_exception_message
465 of 510
466 of 510
467 of 510
Log, Zend_Log,
Zend_Log_Writer_Stream, logging, logs
468 of 510
0 Nice to Have
469 of 510
470 of 510
Nice to Have
471 of 510
Must Have
0 Nice to Have
472 of 510
473 of 510
474 of 510
475 of 510
476 of 510
Must Have
Must Have
477 of 510
Must Have
478 of 510
479 of 510
480 of 510
481 of 510
482 of 510
483 of 510
484 of 510
485 of 510
486 of 510
300 300
487 of 510
488 of 510
489 of 510
490 of 510
491 of 510
492 of 510
493 of 510
494 of 510
495 of 510
0
496 of 510
497 of 510
498 of 510
499 of 510
500 of 510
501 of 510
502 of 510
503 of 510
504 of 510
505 of 510
506 of 510
507 of 510
508 of 510
509 of 510
510 of 510
