||View All MessagesBack to WebFX|
The Access Denied message is probably not returned as a valid xml document, hence the tree cannot parse it properly.|
The simplest, obvious, solution is to either make sure you don't access recourses that returns a Access Denied http response, or use a custom error document for that error, that _is_ valid xml.
My tree seems to load and function fine until I hit a link that returns an HTTP Access Denied message. Any subsequent clicks on the node, or any other node results in the same Access Denied message. Refreshing the browser clears the problem. Any idea on what would cause this?