Edit web.config setting C# debug to true and changing customErrors mode to "Off", from "RemoteOnly". These should be changed back once problem found.
Get a Stack-Trace by appending "?umbDebugShowTrace=true" to the page url.
List page elements by appending "?umbDebug=true" to the page url.
How to disable using url redirection (to discourage snoopers).
I just got a funny server 404 error after attempting to move a content branch with Internet Explorer. The custom url name was causing the problem. It was odd, because I have a custom 404 page that catches most not founds, but this was an asp error page. I re-applied the move using Firefox, which can handle the Content Picker control, and also changed the custom Url Name of the moved page. This cleared up the problem, and all sub-nodes of the moved page were also moved. If I was worried about breaking links I would try and change back to the old url name, but there aren't any links to this yet. I tried re-Publishing the site before re-applying the move, and that did not solve it in this case.
