I'm not sure if this post should be under here or under the Prometheus TreeView. We have a Prometheus TreeView with and Prometheus Ajax
Manager that is handling all of its postbacks. In the TreeView, there
are a considerable number of nodes. Only the first two levels are
"visible" and the rest are hidden until the node expanded. At that
point, the control postbacks through the ajax manager and the nodes
under the node that was expanded are set to visible and then the expand
and collapsing is set to be client side so it doesn't need to go to the
server anymore.
A user is able to right click on a node and then add a level through the context menu. The user can then right click the new node and choose to edit the text of the node that was added. The issue we are having as that during this process, there are postbacks through the ajax manager. They are able to edit the node, but it appears that after the selection changes and it is posting back the name change, we sometimes get an "Invalid JSON Primitive" popup box. It doesn't always happen, and happens during different postbacks as well, but this is a common set of steps that people take. As soon as a person performs an action that does a true postback that doesn't go through the Ajax manager, the "Invalid JSON Primitive" shows up in the browser window.
So, I'm guessing this problem is related to the Ajax manager. Is there something that I can do to make it not do this anymore. I have been unable to duplicate it on my computer, but have seen it done on the production server.
A user is able to right click on a node and then add a level through the context menu. The user can then right click the new node and choose to edit the text of the node that was added. The issue we are having as that during this process, there are postbacks through the ajax manager. They are able to edit the node, but it appears that after the selection changes and it is posting back the name change, we sometimes get an "Invalid JSON Primitive" popup box. It doesn't always happen, and happens during different postbacks as well, but this is a common set of steps that people take. As soon as a person performs an action that does a true postback that doesn't go through the Ajax manager, the "Invalid JSON Primitive" shows up in the browser window.
So, I'm guessing this problem is related to the Ajax manager. Is there something that I can do to make it not do this anymore. I have been unable to duplicate it on my computer, but have seen it done on the production server.