So the site definition is responsible for which features are enabled at time of creation?
That sounds like it could present some real problems in the likelihood that those features were retracted over time. I was hoping that the feature itself could provide the informational internally. I mean, if you've set the scope to farm or site then it stands to reason you would not just want the feature to be available to every new site, but also have the ability to set its activation status. Am I just being naïve or is there really no easy way to achieve this? The feature in question is non-dependent one that simply provides item-leveling auditing. Having to activate this every time someoene creates a site seems a little onerous. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, 22 January 2009 1:12 PM To: [email protected] Subject: RE: Feature attributes - default activation on new sites >From memory, feature stapling won't activate those at a web scope. You may also hit issues with; a. the site not being fully provisioned if you have a mechanism to activate them though code (ensure you test the provisioning status property). b. The order of the 'staplee' features is not as you list them in the 'stapler', so you may not have dependent I think the activate by default flag does works with feature stapling, but the previous issues can them bite you. I'm not sure if feature dependencies will help with the ordering - anyone? My experience has been feature stapling is useful in a limited set of customisation circumstances - as soon as you got to a large number of modular features you are using as a menu to build your template, you hit issues. That's why I go with the provisioning class instead and activate features when and in the order I want - you can drive this from an xml file the provisioner reads that goes in with your wsp cab so code doesn't have to be changed once written. This also enables you to do your own 'new' site def/template for the user to pick, but behing the scenes optionally provision an OOTB template first and then modify if with your features. That way you don't have to copy a onet if you need to do something simialr to an existing def. Your mileage may vary though, so I'm always open to being 'edumacated'. Kind regards, Mike Ari Bakker To <ari.bak...@uniquewo "[email protected]" rld.net> <[email protected]> Sent by: cc [email protected] Subject RE: Feature attributes - default activation on new sites 22/01/2009 07:48 AM Please respond to [email protected] Hi Paul, Feature Stapling 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]] On Behalf Of Paul Noone Sent: Thursday, 22 January 2009 9:30 AM To: [email protected] Subject: RE: Feature attributes - default activation on new sites Curse you Outlook and your Ctrl-Enter shortcut. J 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]] On Behalf Of Paul Noone Sent: Thursday, 22 January 2009 9:27 AM To: [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] 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 ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ 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 _______________________________________________________________________________ Unencrypted electronic mail is not secure and may not be authentic. If you have any doubts as to the contents please telephone to confirm. This electronic transmission including any attachments is intended only for those to whom it is addressed. It may contain copyright material or information that is confidential, privileged or exempt from disclosure by law. Any claim to privilege is not waived or lost by reason of mistaken transmission of this information. If you are not the intended recipient you must not distribute or copy this transmission and should please notify the sender. Your costs for doing this will be reimbursed by the sender. We do not accept liability in connection with computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment. _______________________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -------------------------------------------------------------------------------- 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 -------------------------------------------------------------------------------- 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
