Tnx for the reply, and Ok, I see that Parent Sit ID is meant as a hook, however its an 'old school' hook that ignores the patently obvious.
Site Directory potentially fills a HUGE omission by Microsoft, but is about one line of code away
from achieving that. All it needs is to just include the human readable Parent Site URL which completely solves the whole tree view issue ? Nothing to do with interface here - its just recognizing that Site List is a
tree structure and treating that data type properly and completely.
Just one line of code short of perfect. Its hard to understand why you wouldn't finish such a potentially great solution by not copying the human readable Site URL of the Parent Site ID into its own column. Its probably already there in memory when you write
the Parent Site ID column. Even if you need to make a create a subroutine and call to fetch Site URL for the Parent Site ID, why wouldn't you ?
It just doesnt make sense.
I'll setup the codeplex project and make the change myself if I have to, but cant one of the ppl already on this project just make this small tweak ??