Oh joy. I was hoping another complication would come along. :) From: [email protected] [mailto:[email protected]] On Behalf Of Bunsen Sent: Friday, 23 January 2009 2:51 PM To: [email protected] Subject: Re: Feature attributes - default activation on new sites
Paul, be aware that if you have any custom site templates, you may run into problems with Feature Stapling. It works well with OOTB templates, but anything custom becomes a bit more fiddly. I am having problems with this particular scenario. On Thu, Jan 22, 2009 at 2:40 PM, Paul Noone <[email protected]<mailto:[email protected]>> wrote: Thanks Clayton. That sounds like the ticket. The feature is not dependent on any particular site definition (at least, not that I know of). It just adds a new Action to libraries (where applicable) and an ECB item (again where applicable). Both have a URL action to globally available ASPX pages with the specified source URL as a param. Will give it a go and let you know. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Clayton James Sent: Thursday, 22 January 2009 3:33 PM To: [email protected]<mailto:[email protected]> Subject: RE: Feature attributes - default activation on new sites Paul There is a Global Site Definition that is called in the provisioning process before the selected Site Template (site definition). This contains reusable components that are relevant to all sites. You could try and staple a feature to the Global Site Definition (located in the GLOBAL folder in the 12 hive). Let me know if this works, as I am not sure how it will handle the provisioning process of a Feature that is dependent on the underlying site definition that hasn't yet been created. Clayton James From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Paul Noone Sent: Thursday, 22 January 2009 1:53 PM To: [email protected]<mailto:[email protected]> Subject: RE: Feature attributes - default activation on new sites This still sounds like the best bet for my purposes, providing if it can live up to its description. Do you know if it's possible to specify ALL sites somehow. i.e. is there a base site type in the same way there is a base library ID? Auditing is one of our base requirements and I'd really like to automate this task as much as possible. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Ari Bakker Sent: Thursday, 22 January 2009 9:48 AM To: [email protected]<mailto:[email protected]> Subject: RE: Feature attributes - default activation on new sites Hi Paul, Feature Stapling<http://msdn.microsoft.com/en-us/library/bb861862.aspx> is what you want to activate features for specific site definitions - "Causes the attachment of a Feature to all new instances of sites that use a given site definition, without modifying the site definition or creating code routines to activate the Feature on each site. Also known as a feature site template association" Also see: http://blogs.msdn.com/cjohnson/archive/2006/11/01/feature-stapling-in-wss-v3.aspx http://www.sharepointnutsandbolts.com/2007/05/feature-stapling.html And stsadm -o upgradesolution should do the trick for upgrading From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Paul Noone Sent: Thursday, 22 January 2009 9:30 AM To: [email protected]<mailto:[email protected]> Subject: RE: Feature attributes - default activation on new sites Curse you Outlook and your Ctrl-Enter shortcut. :) To finish: what is the correct process for upgrading a feature deployed by a solution? Do I increment versions for both the solution and feature and then then just run stsadm -upgradesolution? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Paul Noone Sent: Thursday, 22 January 2009 9:27 AM To: [email protected]<mailto:[email protected]> Subject: Feature attributes - default activation on new sites Hi all, How can I specify that a feature is activated by default on all new sites? Or should this be defined in the solution manifest?? The ActivateOnDefault flag seems only to refer to installation and web app creation. Also, what is the correct process for upgrading a feature deployed by a solution? Do I increment versions for both the solution and feature and ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[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]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[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]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[email protected]> List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.10/1906 - Release Date: 21/01/2009 09:15 PM ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[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]<mailto:[email protected]> Subscribe: [email protected]<mailto:[email protected]> Unsubscribe: [email protected]<mailto:[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
