Tickets :: [#9628] Two Horde_Tree instances on one page don't work

Summary	Two Horde_Tree instances on one page don't work
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	jan (at) horde (dot) org
Created	03/07/2011 (5241 days ago)
Due
Updated	03/07/2011 (5241 days ago)
Assigned	03/07/2011 (5241 days ago)
Resolved	03/07/2011 (5241 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/07/2011 07:43:57 PM	Jan Schneider	Comment #3 Taken from Michael Slusarz State ⇒ Not A Bug	Reply to this comment
Yes, we do. I thought this was a general problem.

03/07/2011 07:21:00 PM	Michael Slusarz	Comment #2 State ⇒ Feedback	Reply to this comment
This doesn't sound correct - we are successfully running two Horde_Tree instances in other locations, such as IMP's folders.php (when sidebar is active). I'm guessing that the datatree display code has not been updated completely. I personally have no data in the datatree, so I can't really debug myself. And IIRC, aren't we removing the datatree browser anyway?

03/07/2011 10:52:20 AM	Jan Schneider	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ Assigned to Michael Slusarz Queue ⇒ Horde Framework Packages Summary ⇒ Two Horde_Tree instances on one page don't work Type ⇒ Bug State ⇒ Assigned	Reply to this comment
I'm not sure what exactly happens, but it looks like something in the pretty complex tree initialization is working like a singleton. If adding a second Horde_Tree to the same page, the first tree is rendered (at least in HTML) twice. This can be seen in the DataTree browser.