||View All MessagesBack to WebFX|
Sorry, I gave you a bad description, the error is actually a client-side popup dialog box, not a returned html page. I believe the URL assigned to the node is bad but why would that affect the tree's code? Here's an example of the URL:
I think it's having trouble parsing the minus (-) sign in the URL?
From: Emil A Eklund
Sent: August 6, 2003
Subject: Re:XLoadTree Not Functioning After Access Denied
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?