IMP 6.0.5

Changes have been made in Git (master):

commit c7805744696beb18993461a4e12867eb93e31905
Author: Michael M Slusarz <slusarz@horde.org>
Date:   Mon Feb 18 23:02:09 2013 -0700

     [mms] Fix possible issue creating folder tree if multiple special 
mailboxes appeared in the same branch (Bug #12050).

  imp/docs/CHANGES      |    2 ++
  imp/lib/Imap/Tree.php |   17 ++++++++++++-----
  imp/package.xml       |    4 ++--
  3 files changed, 16 insertions(+), 7 deletions(-)

http://git.horde.org/horde-git/-/commit/c7805744696beb18993461a4e12867eb93e31905

Missed attachment

I've drilled it down a bit further, these are the steps to reproduce 
with a new folder:
- 2 Identities (for example: A and B)
- A and B have their sent items folder assigned to 'Sent Items'
- Start with no subfolders under 'Sent Items'
- Create a subfolder 'foo' under 'Sent Items'
- Create a subfolder 'Bar' under 'foo'
- Folder list still loads correctly (good_request.txt in attachment)
- Assign id B sent items to 'foo'
- Folder list won't load (bad_request.txt in attachment)

When I add more subfolders under 'Sent Items', the folder list will 
load correctly.

I've attached a zip file with 2 traces with the body of the 
listMailboxes AJAX call.

"Special" means a mailbox identified with some sort of advanced MUA 
function.  i.e. templates, sent-mail, drafts, spam, trash
No.

All of these should work, and I can't reproduce locally.

Pretty much will need to see the data sent to the browser used to 
build the mailbox tree.  In IMP 6.0 this should be the return from the 
listMailboxes AJAX call.  You can use something like Firebug to grab 
this information.  If it is private, you can attach the ticket and 
make it visible only to the Horde developers.

What is special and non-special? Does special mean it's assigned as a 
sent items folder to an identity?

It's probably also relevant that I upgraded from horde 4 to 5.
When I create a new subfolder under Sent, and assign it to an 
identity, it works fine. It still works fine if I create subfolders 
under that folder. So I cannot reproduce it either with a newly 
created folder.

However, I have a Sent.bar folder that existed before the upgrade. 
This folder has multiple subfolders, which also existed before the 
update. When I remove the subfolders, the folder list displays. When I 
add a new subfolder to Sent.bar, the folder list won't display anymore.

Is there anything stored horde-specific in the imap folder that hasn't 
been updated in the upgrade?

I have (folder list won't display):
Sent (assigned to identity 1)
Sent.bar (assigned to identity 2) (created before upgrading to horde 5)
Sent.bar.foo (not assigned to any identity) (created before upgrading 
to horde 5)
Sent.bar.foo2 (not assigned to any identity)
Sent.bar.foo3 (not assigned to any identity)

This also doesn't work:
Sent (assigned to identity 1)
Sent.bar (assigned to identity 2) (created before upgrading to horde 5)
Sent.bar.newfoo (not assigned to any identity) (newly created)

This works:
Sent (assigned to identity 1)
Sent.bar (assigned to identity 2) (created before upgrading to horde 5)

Perhaps it's a small upgrading bug and I should just use a new folder. 
But I didn't expect older imap folders would cause trouble after an 
upgrade.

I can't reproduce.  I have the following setup:

Sent (special)
Sent.horde (special)

and this displays fine.  I added both of these mailboxes:

Sent.foo (non-special)
Sent.horde.foo (non-special)

and it continues to display fine.

What is your mailbox structure that is causing issues?

When a special folder, like 'Sent items' has subfolders, the folder 
list in DIMP will remain at 'loading' and will never display any 
folders.

I've tracked down the bug to a javascript exception thrown:
Exception: TypeError: parent_e is null
And the source:
dimpbase.js:3207
f_node = parent_e.childElements().find(function(node) {


parent_e is nullified in code block in dimpbase.js:3197
if (!ob.s) {
        div.addClassName(ob.ch ? 'exp' : (ob.cl || 'folderImg'));
        parent_e = ob.pa
                ? this.getSubMboxElt(ob.pa)
                : $('imp-normalmboxes');
}

In this.getSubMboxElt(ob.pa) it looks like it's trying to display 
subfolders which aren't loaded by the imp/listmailboxes call.