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 < [email protected]> 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:* [email protected] [mailto:[email protected]] *On Behalf Of *Sezai > Komur > *Sent:* Monday, 22 June 2009 2:48 PM > *To:* [email protected] > *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 <[email protected]> > 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:* [email protected] [mailto:[email protected]] *On Behalf Of *Paul > Noone > *Sent:* Monday, 22 June 2009 4:00 PM > *To:* [email protected] > *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: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > 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: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > 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: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > 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: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > 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: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
<<image001.jpg>>
