[Tickets #14257] Re: HORDE [imp] Call to a member function getFlags()
noreply at bugs.horde.org
noreply at bugs.horde.org
Wed Mar 9 13:42:48 UTC 2016
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: https://bugs.horde.org/ticket/14257
------------------------------------------------------------------------------
Ticket | 14257
Updated By | gerard.breiner at ias.u-psud.fr
Summary | HORDE [imp] Call to a member function getFlags()
Queue | IMP
Version | 6.2.12
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
gerard.breiner at ias.u-psud.fr (2016-03-09 13:42) wrote:
> So, this error occurs *after* the email is deleted, while it
> attempting to load the next email?
Yes it is...
To summarize :
I applied Horde::debug as you ask me, it I get a file horde_debug.txt:
Just before I delete the mail, I get from horde_debug.txt this information :
----------------------------------------
class Horde_Imap_Client_Fetch_Results#629 (3) {
protected $_data =>
array(1) {
[123069] =>
class Horde_Imap_Client_Data_Fetch#611 (1) {
protected $_data =>
array(3) {
...
}
}
}
protected $_keyType =>
int(2)
protected $_obClass =>
string(28) "Horde_Imap_Client_Data_Fetch"
}
After having deleted the message, I get from horde_debug.txt that
$_data is empty:
class Horde_Imap_Client_Fetch_Results#1130 (3) {
protected $_data =>
array(0) {
}
protected $_keyType =>
int(2)
protected $_obClass =>
string(28) "Horde_Imap_Client_Data_Fetch"
}
The backtrace is the same in each case:
Backtrace:
1. IMP_Basic_Base->__construct() /www/horde5/imp/basic.php:34
2. IMP_Basic_Message->_init() /www/horde5/imp/lib/Basic/Base.php:69
3. IMP_Maillog->getLog() /www/horde5/imp/lib/Basic/Message.php:913
4. IMP_Maillog_Storage_Composite->getLog() /www/horde5/imp/lib/Maillog.php:67
5. IMP_Maillog_Storage_Mdnsent->getLog()
/www/horde5/imp/lib/Maillog/Storage/Composite.php:64
6. Horde::debug() /www/horde5/imp/lib/Maillog/Storage/Mdnsent.php:70
I guess that getLog() should not be triggered again ?
Best regards.
Gerard Breiner
More information about the bugs
mailing list