Summary | mailbox views broken |
Queue | IMP |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | mrubinsk (at) horde (dot) org |
Requester | mrubinsk (at) horde (dot) org |
Created | 04/13/2010 (5535 days ago) |
Due | |
Updated | 04/14/2010 (5534 days ago) |
Assigned | 04/13/2010 (5535 days ago) |
Resolved | 04/14/2010 (5534 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Taken from Michael Slusarz
State ⇒ Resolved
These methods are not provided by IMP therefore we must check for them
before calling.
This was preventing ALL of imp's prefs from being loaded, since
Horde_Prefs::_loadDefaults()
was catching the exception and returning. This fixes Bug:
# 8962andpossibly
Bug: #8961http://git.horde.org/diff.php/imp/config/prefs.php.dist?rt=horde-git&r1=375ca9376b445764324b61a623a9a4b2c9fac567&r2=a874d22a44cd43c6c0c67be106e8055c7dd54df1
the prefs code. I would suggest looking at
Horde_Prefs::_setDefaults() to see why the default value is not being
set in the current user's prefs.
Also, line 134 doesn't have
(although maybe that's how PHP reports errors with array_merge).
the last line of mulitline commands.
that value is coming from.
but I have no idea where it is coming from. The prefs.php file's value
is set to '[]'.
State ⇒ Feedback
code on it - it is the closing parenthesis for the array_merge call
(although maybe that's how PHP reports errors with array_merge).
If these fail, check to see what value 'msgflags_user' is, and where
that value is coming from.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ mailbox views broken
Queue ⇒ IMP
Assigned to Michael Slusarz
Milestone ⇒
Patch ⇒ No
State ⇒ Assigned
Numerous messages in the log related to IMP_Imap_Flags that seems to
start off with:
(mod_fastcgi.c.2570) FastCGI-stderr: PHP Warning: array_merge() [<a
href='function.array-merge'>function.array-merge</a>]: Argument
#1isnot an array in /horde/horde/imp/lib/Imap/Flags.php on line 134
Normal IMP mailbox views display the mailbox, but do not seem to show
any new messages, and also result in the same error messages being
logged. I can provide the full stack trace if needed...