Btw, BETA2 should be released November 18th
From: [email protected] [mailto:[email protected]] On Behalf Of Nigel Hertz Sent: Wednesday, 28 October 2009 11:09 AM To: ozMOSS Subject: RE: SharePoint Site Directory I'm desperately hoping to obtain a beta copy of SPS 2010 soon. I want to start planning how to convince the powers-that-be that we NEED it :p From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Wednesday, 28 October 2009 10:10 AM To: ozMOSS Subject: RE: SharePoint Site Directory Just as a follow up, I'm trying to achieve a per site collection replacement using the Table Of Contents web part but the filtering leaves a bit to be desired. Is there any easy way to hack this to show ONLY sites and subsites? None of the filter web parts let me define a contentclass value. I don't want to use CQWP (which is always restircited to a list type anyway) because I like the current hierachy and column display options. From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Wednesday, 28 October 2009 8:37 AM To: ozMOSS Subject: RE: SharePoint Site Directory That's just about the best news I've heard all week. J Will they be replacing it with a cross site lookup that can query ALL site collections and sites from a master list, and present them in the expected tree view? From: [email protected] [mailto:[email protected]] On Behalf Of Michael Nemtsev Sent: Tuesday, 27 October 2009 9:51 PM To: 'ozMOSS' Subject: RE: SharePoint Site Directory Just delete Site Directory J SharePoint 2010 doesn't support it any longer http://tinyurl.com/sp2010uichanges From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 27 October 2009 2:39 PM To: ozMOSS Subject: SharePoint Site Directory 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 _____ Stockland Notice: If this communication has been sent to you by mistake, please delete and notify us. If it has been sent to you by mistake, legal privilege is not waived or lost and you are not entitled to use it in any way. Stockland and its subsidiaries reserve the right to monitor e-mail communication through its networks.
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
