Cacti Graph tree automatically expands in 13.04

[Jackie Hunt]

Cacti graph subtrees are expanding automatically without being selected. Here's a sample setup:

Tree 1
---Subtree St1
------Graph a1
---Graph b1
---Graph c1
Tree 2
Tree 3
---Subtree St2
------Graph d1
---Graph e1
---Graph f1

The issue I'm seeing is when I do the following:

Open Tree 1
Open Subtree St1
Close Tree 1 (leaving Subtree St1 expanded)
Open Tree 3
Select Graph e1

At that point Tree 1 is expanded automatically in the left panel, even though I had closed it. If instead I

Open Tree 1
Open Subtree St1
Close Subtree St1
Close Tree 1
Open Tree 3
Select Graph e1

it works, no graph trees are automatically expanded.

 The problem happens when I have Tree 3 selected and am trying to open a graph in Tree 3. So you could say I'm "standing" in Tree 3. I'm not collapsing Tree 1, it has already been collapsed. I select a graph in Tree 3, and in the left panel Tree 1 is expanded.

The issue seems to be related to an expanded subtree in a tree that is collapsed. When the graph tree is redrawn, if a subtree was not manually collapsed, the parent tree is expanded automatically, even though it wasn't selected.

I am running on

Description: Ubuntu 12.04.3 LTS
Release: 12.04

However cacti 0.8.8a was installed by pinning 1304.

cacti:
  Installed: 0.8.8a+dfsg-4
  Candidate: 0.8.8a+dfsg-4
  Package pin: 0.8.7i-2ubuntu1
  Version table:
 *** 0.8.8a+dfsg-4 -10
        100 /var/lib/dpkg/status
     0.8.7i-2ubuntu1 -10
        990 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

This bug has been discussed on the Cacti Forum under the topic "Graph Tree expanding automatically in 0.8.8a". Paul Gevers requested I file this bug report.

[Paul Gevers (paul-climbing)]

I have forwarded this bug to jstree, the upstream for the javascript code responsible for the tree, as this javascript stuff is too difficult for me at the moment.

https://github.com/vakata/jstree/issues/390

[Paul Gevers (paul-climbing)]

This bug has been fixed in jstree in 2013 and the version containing the fix is now since long available, closing this bug.