Yep - stapling always sounds like what you want, but rarely meets what you
need - more caveats than a lawyers office.
Caveat Utilitor Stapling
Paul Noone To
<[email protected] "[email protected]"
atholic.edu.au> <[email protected]>
Sent by: cc
[email protected]
Subject
RE: Feature attributes - default
activation on new sites
23/01/2009 01:19 PM
Please respond to
[email protected]
Oh joy. I was hoping another complication would come along. J
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]> 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]] On Behalf Of Clayton
James
Sent: Thursday, 22 January 2009 3:33 PM
To: [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]] On Behalf Of Paul Noone
Sent: Thursday, 22 January 2009 1:53 PM
To: [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]] On Behalf Of Ari Bakker
Sent: Thursday, 22 January 2009 9:48 AM
To: [email protected]
Subject: RE: Feature attributes - default activation on new sites
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
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
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]
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
______________________________________________________________________
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
