| Summary | fatal error Call to a member function setIteratorFilter |
| Queue | IMP |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | rsalmon (at) mbpgroup (dot) com |
| Created | 09/08/2010 (5612 days ago) |
| Due | |
| Updated | 09/13/2010 (5607 days ago) |
| Assigned | 09/08/2010 (5612 days ago) |
| Resolved | 09/13/2010 (5607 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
changes that changed the format of that file.
Everything works fine now.
tanks.
changes that changed the format of that file.
apache's log file.
I still can't see folders in the sidebar using traditional mode, but
everything is fine using dynamic mode!
I use prefs.php.dist and hooks.php.dist
I still do not see any error in /tmp/horde.log. I do see a few of
those (which is good):
DEBUG: HORDE [imp] Hook mbox_label in application imp not called. [pid
12262 on line 1697 of "/var/www/html/horde/libs/Horde.php"]
DEBUG: HORDE [imp] Hook display_folder in application imp not called.
[pid 12262 on line 1697 of "/var/www/html/horde/libs/Horde.php"]
State ⇒ Feedback
Assigned to Michael Slusarz
Bug #9239: Make sure instance is a tree objecthttp://git.horde.org/diff.php/imp/lib/Injector/Binder/Imaptree.php?rt=horde-git&r1=6e1c57025b1661dd1a5a0e226241ef0fa2223209&r2=0397f464bb48d2d448ec094252bb11380d15f021
Priority ⇒ 1. Low
State ⇒ Unconfirmed
New Attachment: imaplog.txt
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ fatal error Call to a member function setIteratorFilter
Type ⇒ Bug
$conf['auth']['params']['app'] = 'imp';
I can login fine (traditional mode).
No folders appear in sidebar.
If I click on mailbox, I get the following fatal error :
PHP Fatal error: Call to a member function setIteratorFilter() on a
non-object in /var/www/html/horde/imp/lib/IMP.php on line 196,
referer: http://127.0.0.1/horde/services/portal/
var_dump($imaptree) gives me : bool(false)
imap trace (login, then click on mailbox) attached.
I didn't see anything unusual in horde.log
this issue appears only recently.