Tickets :: [#3342] Wrong tree in drop down

6.0.0-git

2020-02-20

Summary	Wrong tree in drop down
Queue	IMP
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	3. High
Owners	jan (at) horde (dot) org, slusarz (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	2006-01-25 (5139 days ago)
Due
Updated	2006-02-15 (5118 days ago)
Assigned	2006-02-15 (5118 days ago)
Resolved	2006-02-15 (5118 days ago)
Milestone	4.1
Patch	No

2006-02-15 23:30:24	Jan Schneider	State ⇒ Resolved

2006-02-15 23:26:45	Jan Schneider	Comment #15	Reply to this comment
That fixed it finally. Many thanks.

2006-02-15 23:14:14	Michael Slusarz	Comment #14	Reply to this comment
Try again (crossing my fingers). The hang up on my side was the fact I didn't have the public namespace with an empty value - that appears to be what was causing the issue.

2006-02-15 23:04:13	Michael Slusarz	Comment #13	Reply to this comment
This breaks the tree for me, because Inbox (which is Posteingang in German) is not the first folder anymore, but sorted inside the middle of the tree. This part should be working again.

2006-02-15 22:36:32	Jan Schneider	Comment #12 New Attachment: badget_maker1.png	Reply to this comment
Here's a screenshot of what I see (w/personal namespace = 'INBOX.', #mbox is a public namespace and, as you can see, it appears intermixed within my personal namespace boxes). Did you login/logout to clear your folder cache? Yes. These are my namespaces: NAMESPACE (("INBOX." ".")) (("user." ".")) (("" "."))

2006-02-15 22:31:51	Jan Schneider	Comment #11	Reply to this comment
I do realize I need to make the same fix to our graphical tree rendering code (i.e. folders.php) - namely, if there is a non-blank namespace for personal mailboxes we need to strip out the namespace before we sort. This has been fixed. This breaks the tree for me, because Inbox (which is Posteingang in German) is not the first folder anymore, but sorted inside the middle of the tree.

2006-02-15 20:55:13	Michael Slusarz	Comment #10	Reply to this comment
I do realize I need to make the same fix to our graphical tree rendering code (i.e. folders.php) - namely, if there is a non-blank namespace for personal mailboxes we need to strip out the namespace before we sort. This has been fixed.

2006-02-15 20:37:26	Michael Slusarz	Comment #9 New Attachment: Clipboard01.png	Reply to this comment
Here's a screenshot of what I see (w/personal namespace = 'INBOX.', #mbox is a public namespace and, as you can see, it appears intermixed within my personal namespace boxes). Did you login/logout to clear your folder cache? I do realize I need to make the same fix to our graphical tree rendering code (i.e. folders.php) - namely, if there is a non-blank namespace for personal mailboxes we need to strip out the namespace before we sort.

2006-02-15 18:37:05	Jan Schneider	Comment #8	Reply to this comment
No difference.

2006-02-15 18:11:42	Michael Slusarz	Comment #7 State ⇒ Feedback	Reply to this comment
Try now.

2006-02-15 08:47:50	Jan Schneider	Comment #6 State ⇒ Assigned	Reply to this comment
This fixes the container, but now all folders of the personal namespace are displayed as subfolders of inbox again.

2006-02-15 02:33:03	Michael Slusarz	Comment #5 State ⇒ Feedback	Reply to this comment
Try what I just committed. I have no idea if this fixes your problem since I couldn't replicate it here in the first place.

2006-02-05 22:30:41	Jan Schneider	Comment #4 Version ⇒ HEAD	Reply to this comment
This is happening in HEAD too. Any more information I can provide to track this down?

2006-02-05 08:09:49	Michael Slusarz	Comment #3 Assigned to Jan Schneider	Reply to this comment
I don't see this.

2006-02-05 07:11:15	Michael Slusarz	Comment #2 Priority ⇒ 3. High	Reply to this comment
Reprioritize.

2006-01-25 11:30:22	Jan Schneider	Comment #1 Type ⇒ Bug State ⇒ Assigned Priority ⇒ 2. Medium Summary ⇒ Wrong tree in drop down Queue ⇒ IMP Assigned to Michael Slusarz	Reply to this comment
The flist drop down tree is a bit off at the moment if dealing with subfolders without parents. I use subscriptions and have a tree like: INBOX INBOX.sent.sent-foo INBOX.sent.sent-bar INBOX.xxx Public This is currently rendered as (replace dots with spaces): INBOX ....sent-foo ....sent-bar xxx sent Public