Site features vs site collection features
Hi all, After a quick audit of my sites I've come looking for some clarification as to what the difference is between site features and site collection features. For example, If I have enabled the following features at the site collection level, do I also need to activate them for each new sub site. It doesn't appear to be the case but it does make it confusing to determine which features are actually set for a specific site. [cid:image002.jpg@01C9F352.8885FCC0] Regards, Paul Online Developer, ICT CEO Sydney Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists inline: image002.jpg
RE: Site features vs site collection features
The difference is in the scope. You will need the Site Collection Features and the Site Features both activated to get all the features. Most of the Site Templates will do this for you, but if you are doing it after the fact, you should activate them at both if you need them. This is a more granular way to allocate Features to particular sites underneath a site collection. For publishing...you don't have to, but you won't get certain functionality in new sites if you don't activate it. I may be wrong, but off the top of my head the Page Editing Toolbar won't be there on a sub site if you don't active the Publishing Site Feature on it, even if the Publishing Site Collection feature is there. From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Noone Sent: Monday, 22 June 2009 4:00 PM To: ozmoss@ozmoss.com Subject: Site features vs site collection features Hi all, After a quick audit of my sites I've come looking for some clarification as to what the difference is between site features and site collection features. For example, If I have enabled the following features at the site collection level, do I also need to activate them for each new sub site. It doesn't appear to be the case but it does make it confusing to determine which features are actually set for a specific site. [cid:image001.jpg@01C9F354.FE12FEF0] Regards, Paul Online Developer, ICT CEO Sydney Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists inline: image001.jpg
Re: Site features vs site collection features
You are right about the Office SharePoint Server Publishing site feature, a ton of things are not available without it active, if you create a basic Team Site you can't manage navigation, switch the master page, create publishing pages etc, you'll notice a big difference in the number of options available in the site actions menu. The page editing toolbar only displays on publishing pages. Activating the Office SharePoint Server Publishing will create a pages library and other lists and libraries required to support publishing. It also depends on the site template used to create the subsites, if you create a new publishing site and view the site features you'll notice that the Office SharePoint Server Publishing site feature is already activated for the new site (because it is referenced in the Onet.xml for the publishing site). Whether or not you need the features enabled depends on what you need to use the site for really, I've seen this cause confusion before, by default if you create a basic team site in a publishing enabled site collection it won't have the publishing feature enabled in the team site. Then users wonder why they can't create publishing pages and need to use a content editor web part instead. Sezai. On Mon, Jun 22, 2009 at 2:17 PM, Jeremy Thake jeremy.th...@readify.netwrote: The difference is in the scope. You will need the Site Collection Features and the Site Features both activated to get all the features. Most of the Site Templates will do this for you, but if you are doing it after the fact, you should activate them at both if you need them. This is a more granular way to allocate Features to particular sites underneath a site collection. For publishing...you don’t “have to”, but you won’t get certain functionality in new sites if you don’t activate it. I may be wrong, but off the top of my head the Page Editing Toolbar won’t be there on a sub site if you don’t active the Publishing Site Feature on it, even if the Publishing Site Collection feature is there. *From:* ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] *On Behalf Of *Paul Noone *Sent:* Monday, 22 June 2009 4:00 PM *To:* ozmoss@ozmoss.com *Subject:* Site features vs site collection features Hi all, After a quick audit of my sites I’ve come looking for some clarification as to what the difference is between site features and site collection features. For example, If I have enabled the following features at the site collection level, do I also need to activate them for each new sub site. It doesn’t appear to be the case but it does make it confusing to determine which features are actually set for a specific site. Regards, Paul Online Developer, ICT CEO Sydney -- Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists -- Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists image001.jpg
RE: Site features vs site collection features
The RTM version of the product J From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Bill Williamson Sent: Monday, 22 June 2009 4:59 PM To: ozmoss@ozmoss.com Subject: Re: Site features vs site collection features What's the sharepoint analogy to suing your own fans though? Attempting migration/using CMS features? On Mon, Jun 22, 2009 at 6:13 PM, Paul Culmsee paul.culm...@sevensigma.com.au wrote: Here’s a dodgy analogy that I have used to explain the difference to people – (I like dodgy analogies ;-) Take an example of a Metallica concert. Metallica (the band) is the site feature. Without them you have no concert as they play the music. However if you removed the stage, the roadies, the lighting, the alcohol and the soundsystem then you wouldn’t have a Metallica concert, despite Metallica standing around looking lost. So the site collection feature can be viewed as “setting the stage” for the site feature. It puts all the necessary pre-requisites into place for the site scoped feature to work. Regards Paul www.cleverworkarounds.com From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Sezai Komur Sent: Monday, 22 June 2009 2:48 PM To: ozmoss@ozmoss.com Subject: Re: Site features vs site collection features You are right about the Office SharePoint Server Publishing site feature, a ton of things are not available without it active, if you create a basic Team Site you can't manage navigation, switch the master page, create publishing pages etc, you'll notice a big difference in the number of options available in the site actions menu. The page editing toolbar only displays on publishing pages. Activating the Office SharePoint Server Publishing will create a pages library and other lists and libraries required to support publishing. It also depends on the site template used to create the subsites, if you create a new publishing site and view the site features you'll notice that the Office SharePoint Server Publishing site feature is already activated for the new site (because it is referenced in the Onet.xml for the publishing site). Whether or not you need the features enabled depends on what you need to use the site for really, I've seen this cause confusion before, by default if you create a basic team site in a publishing enabled site collection it won't have the publishing feature enabled in the team site. Then users wonder why they can't create publishing pages and need to use a content editor web part instead. Sezai. On Mon, Jun 22, 2009 at 2:17 PM, Jeremy Thake jeremy.th...@readify.net wrote: The difference is in the scope. You will need the Site Collection Features and the Site Features both activated to get all the features. Most of the Site Templates will do this for you, but if you are doing it after the fact, you should activate them at both if you need them. This is a more granular way to allocate Features to particular sites underneath a site collection. For publishing...you don’t “have to”, but you won’t get certain functionality in new sites if you don’t activate it. I may be wrong, but off the top of my head the Page Editing Toolbar won’t be there on a sub site if you don’t active the Publishing Site Feature on it, even if the Publishing Site Collection feature is there. From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Noone Sent: Monday, 22 June 2009 4:00 PM To: ozmoss@ozmoss.com Subject: Site features vs site collection features Hi all, After a quick audit of my sites I’ve come looking for some clarification as to what the difference is between site features and site collection features. For example, If I have enabled the following features at the site collection level, do I also need to activate them for each new sub site. It doesn’t appear to be the case but it does make it confusing to determine which features are actually set for a specific site. Regards, Paul Online Developer, ICT CEO Sydney _ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists http://www.codify.com/lists _ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists http://www.codify.com/lists _ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss http://www.codify.com/lists/ozmoss Other lists
RE: Site features vs site collection features
LOL. Thanks guys. Believe it or not that actually makes sense. What has got me stumped is that the site in question (team site without publishing enabled) does in fact have a page library, publishing master and layout pages, edit toolbar, search, profiles etc. This site was created via content deployment so I’m wondering if the features were made available without actually having to enable them again at the destination? Are these features also responsible for the switch from usageDetails.aspx to SpUsageWeb.aspx when accessing Site Usage Report? Both are quit useless but I’ve always been confused by the difference from site to site. Anyway, I’ll take the collective advice and enable them for the subsites too. From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Monday, 22 June 2009 7:45 PM To: ozmoss@ozmoss.com Subject: RE: Site features vs site collection features The RTM version of the product ☺ From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Bill Williamson Sent: Monday, 22 June 2009 4:59 PM To: ozmoss@ozmoss.com Subject: Re: Site features vs site collection features What's the sharepoint analogy to suing your own fans though? Attempting migration/using CMS features? On Mon, Jun 22, 2009 at 6:13 PM, Paul Culmsee paul.culm...@sevensigma.com.aumailto:paul.culm...@sevensigma.com.au wrote: Here’s a dodgy analogy that I have used to explain the difference to people – (I like dodgy analogies ;-) Take an example of a Metallica concert. Metallica (the band) is the site feature. Without them you have no concert as they play the music. However if you removed the stage, the roadies, the lighting, the alcohol and the soundsystem then you wouldn’t have a Metallica concert, despite Metallica standing around looking lost. So the site collection feature can be viewed as “setting the stage” for the site feature. It puts all the necessary pre-requisites into place for the site scoped feature to work. Regards Paul www.cleverworkarounds.comhttp://www.cleverworkarounds.com From: ozmoss@ozmoss.commailto:ozmoss@ozmoss.com [mailto:ozmoss@ozmoss.commailto:ozmoss@ozmoss.com] On Behalf Of Sezai Komur Sent: Monday, 22 June 2009 2:48 PM To: ozmoss@ozmoss.commailto:ozmoss@ozmoss.com Subject: Re: Site features vs site collection features You are right about the Office SharePoint Server Publishing site feature, a ton of things are not available without it active, if you create a basic Team Site you can't manage navigation, switch the master page, create publishing pages etc, you'll notice a big difference in the number of options available in the site actions menu. The page editing toolbar only displays on publishing pages. Activating the Office SharePoint Server Publishing will create a pages library and other lists and libraries required to support publishing. It also depends on the site template used to create the subsites, if you create a new publishing site and view the site features you'll notice that the Office SharePoint Server Publishing site feature is already activated for the new site (because it is referenced in the Onet.xml for the publishing site). Whether or not you need the features enabled depends on what you need to use the site for really, I've seen this cause confusion before, by default if you create a basic team site in a publishing enabled site collection it won't have the publishing feature enabled in the team site. Then users wonder why they can't create publishing pages and need to use a content editor web part instead. Sezai. On Mon, Jun 22, 2009 at 2:17 PM, Jeremy Thake jeremy.th...@readify.netmailto:jeremy.th...@readify.net wrote: The difference is in the scope. You will need the Site Collection Features and the Site Features both activated to get all the features. Most of the Site Templates will do this for you, but if you are doing it after the fact, you should activate them at both if you need them. This is a more granular way to allocate Features to particular sites underneath a site collection. For publishing...you don’t “have to”, but you won’t get certain functionality in new sites if you don’t activate it. I may be wrong, but off the top of my head the Page Editing Toolbar won’t be there on a sub site if you don’t active the Publishing Site Feature on it, even if the Publishing Site Collection feature is there. From: ozmoss@ozmoss.commailto:ozmoss@ozmoss.com [mailto:ozmoss@ozmoss.commailto:ozmoss@ozmoss.com] On Behalf Of Paul Noone Sent: Monday, 22 June 2009 4:00 PM To: ozmoss@ozmoss.commailto:ozmoss@ozmoss.com Subject: Site features vs site collection features Hi all, After a quick audit of my sites I’ve come looking for some clarification as to what the difference is between site features and site collection features. For example, If I have enabled the following features at the site collection level, do I also need to activate them for each new sub site. It doesn’t appear to be the
BrowserHttpWebRequest_WebException_RemoteServer
Hi All, Just wondering if anyone has come across this issue: [BrowserHttpWebRequest_WebException_RemoteServer] Arguments:NotFound Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663 http://go.microsoft.com/fwlink/?linkid=106663Version=2.0.31005.0File=Syst em.Windows.dllKey=BrowserHttpWebRequest_WebException_RemoteServer Version=2.0.31005.0File=System.Windows.dllKey=BrowserHttpWebRequest_WebEx ception_RemoteServer This was from a Silverlight app deployed that was previously working and was redeployed after some interface changes were made. The app connects to a remote web service which is where I think the error is occurring. The web.config connection information is the same as the previous version and IIS settings appear correct. It is on a client site I am returning this afternoon so any suggestions would be much appreciated! Thanks, Simon Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
RE: BrowserHttpWebRequest_WebException_RemoteServer
Oops wrong list sorry, it's early in perth yet From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Simon Reed Sent: Tuesday, 23 June 2009 7:34 AM To: ozmoss@ozmoss.com Subject: BrowserHttpWebRequest_WebException_RemoteServer Hi All, Just wondering if anyone has come across this issue: [BrowserHttpWebRequest_WebException_RemoteServer] Arguments:NotFound Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663 http://go.microsoft.com/fwlink/?linkid=106663Version=2.031005.0File=Syste m.Windows.dllKey=BrowserHttpWebRequest_WebException_RemoteServer Version=2.0.31005.0File=System.Windows.dllKey=BrowserHttpWebRequest_WebEx ception_RemoteServer This was from a Silverlight app deployed that was previously working and was redeployed after some interface changes were made. The app connects to a remote web service which is where I think the error is occurring. The web.config connection information is the same as the previous version and IIS settings appear correct. It is on a client site I am returning this afternoon so any suggestions would be much appreciated! Thanks, Simon _ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists http://www.codify.com/lists Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
Usage analysis processing
Hi all, My Process Settings for usage analysis are 1am-3am. I'm pretty sure these were the default. I'd assumed these settings worked in the same way as search crawls and were intended to run out of business hours but The Compete Reference MOSS 2007 book states the opposite. The Processing Settings determine when to run usage processing and allow you to fine tune it to a specific period during the day (you might, for example, want to monitor only peak activity in the afternoons). Can anyone confirm this? It seems ridiculous but would certainly explain the whacky stats I'm getting. :) Regards, Paul Online Developer, ICT CEO Sydney Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
RE: Site features vs site collection features
I’m glad Metallica helped J. Now if you want to understand document management look no further than death metal (Opeth) and to understand site definitions vs site templates I use boy-bands (cleverworkarounds site). Anyway back to your observations... I meddled with the forces you are meddling with a long time ago. If you disable the features after enabling, they do not get removed and that’s quite deliberate and I blogged about the behaviour in my 2007 branding series. Mind you, if you manually create a pages library and then try and activate the publishing feature, it barfs about it already being there. Based on that presumption, I think that your prognosis is likely right but I’m not an expert on content deployment. It sounds like content deployment tries to ensure that all required artefacts are there and doesn’t rely on the feature being there (this is counter intuitive to me but as I said I’m not an expert on content deployment). From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Noone Sent: Tuesday, 23 June 2009 7:00 AM To: ozmoss@ozmoss.com Subject: RE: Site features vs site collection features LOL. Thanks guys. Believe it or not that actually makes sense. What has got me stumped is that the site in question (team site without publishing enabled) does in fact have a page library, publishing master and layout pages, edit toolbar, search, profiles etc. This site was created via content deployment so I’m wondering if the features were made available without actually having to enable them again at the destination? Are these features also responsible for the switch from usageDetails.aspx to SpUsageWeb.aspx when accessing Site Usage Report? Both are quit useless but I’ve always been confused by the difference from site to site. Anyway, I’ll take the collective advice and enable them for the subsites too. From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Culmsee Sent: Monday, 22 June 2009 7:45 PM To: ozmoss@ozmoss.com Subject: RE: Site features vs site collection features The RTM version of the product J From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Bill Williamson Sent: Monday, 22 June 2009 4:59 PM To: ozmoss@ozmoss.com Subject: Re: Site features vs site collection features What's the sharepoint analogy to suing your own fans though? Attempting migration/using CMS features? On Mon, Jun 22, 2009 at 6:13 PM, Paul Culmsee paul.culm...@sevensigma.com.au wrote: Here’s a dodgy analogy that I have used to explain the difference to people – (I like dodgy analogies ;-) Take an example of a Metallica concert. Metallica (the band) is the site feature. Without them you have no concert as they play the music. However if you removed the stage, the roadies, the lighting, the alcohol and the soundsystem then you wouldn’t have a Metallica concert, despite Metallica standing around looking lost. So the site collection feature can be viewed as “setting the stage” for the site feature. It puts all the necessary pre-requisites into place for the site scoped feature to work. Regards Paul www.cleverworkarounds.com From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Sezai Komur Sent: Monday, 22 June 2009 2:48 PM To: ozmoss@ozmoss.com Subject: Re: Site features vs site collection features You are _ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists http://www.codify.com/lists right about the Office SharePoint Server Publishing site feature, a ton of things are not available without it active, if you create a basic Team Site you can't manage navigation, switch the master page, create publishing pages etc, you'll notice a big difference in the number of options available in the site actions menu. The page editing toolbar only displays on publishing pages. Activating the Office SharePoint Server Publishing will create a pages library and other lists and libraries required to support publishing. It also depends on the site template used to create the subsites, if you create a new publishing site and view the site features you'll notice that the Office SharePoint Server Publishing site feature is already activated for the new site (because it is referenced in the Onet.xml for the publishing site). Whether or not you need the features enabled depends on what you need to use the site for really, I've seen this cause confusion before, by default if you create a basic team site in a publishing enabled site collection it won't have the publishing feature enabled in the team site. Then users wonder why they can't create publishing pages and need to use a content editor web part instead. Sezai. On
