The approach we are taking for a large deployment is to have a master site collection directory list. This list can then be presented how we want across any of the site collections and also searched against.
Matthew Hallam On 27 Oct 2009 03:37, "Paul Noone" <[email protected]> wrote: After dozens of user complaints about how lame this template is I’m now in a position where I’m being forced to either get it to list ALL sites (collections) or delete it. I’m sure all of you have encountered the following when trying to apply a site directory URL that is outside the current site collection. “The location entered is not a site collection relative path, or the specified Site Directory does not exist in the current Site Collection.” But what good is a Site Directory if it’s limited to one collection?! And given this limitation, why bother having a Master Site Directory setting in Central Administration!? I briefly considered creating a new site directory for each site collection but quickly scrapped that idea when I realised it’d be even *more* confusing to end users. I then looked at cross-site lookups, scope result page, and even a custom sitemap provider. But all of these would mean a loss of functionality (categorisation, listing settings per site etc). So now I’m back to simply deleting it. Which kinda sucks. I’d be very interested to hear what others have done in this area. Regards, Paul Online Developer, ICT CEO Sydney _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
