Question

I am using a jqgrid’s treegrid and the data for the child nodes is being loaded on request.
But when user clicks on a node (say node1) to expand it and immediately clicks on another node (say node2) then the children of first node (node1) are being displayed for the second node (node2), the icon of node2 changes to show as expanded but it has data of node1’s children and collapsing node2 doesn’t do anything but collapsing node1 collapses node1’s children which are displayed as node2’s children.

Did someone else face such a problem? data for jqgrid is adjacency model in json format.

Answer 1

It looks like a bug in jqGrid. I looked in the code and I think I understand the problem.

Every time the user click on the “expand” icon the code will be executed which call expandRow and expandNode methods. The code of expandNode first overwrite the current value of the treeANode parameter of jqGrid which are used internally to identify the row after which the new data will be added. Then the nodeid, parentid (or n_left and n_right for the 'nested' grid model) and n_level parameters of the new request to the server will be set and after that the reloadGrid will be triggered.

The problem is that later, during processing of the reloadGrid at the beginning of the internal populate method, the internal .grid.hDiv.loading property will be tested and if it was set be the previous still pending request then the second reloading of the grid will be skipped. The problem is that the value of the treeANode parameter is already changed. So the items returned as the children of the first expending node will be added as clidren of the last clicked node.

As the bug fix I suggest to modify the line of code to the following

} else if (!this.grid.hDiv.loading) {

In the way the treeANode parameter will be not overwritten by the click on the second if another pending request is still processing.

You can download from here the modified version of the jquery.jqGrid.src.js and test whether the problem will be solved after the bug fix. If it will solve the problem I’ll post the corresponding bug report with my suggestion how to fix the problem on the trirand forum.

As another workaround you can use loadui: 'block' option of jqGrid which will not allow any user interactions during the processing of the pending requests to the server.