Deploying the RadEditor SharePoint feature to all existing sites

So, the RadEditor solution is not scoped globally, meaning that after you install it, it is not used on users sites unless they activate it in their site settings. What is the way around this? The answer (big surprise) is STSADM.

We again use:
STSADM -o enumsites to collect all existing site URLs. We cleverly strip out the site URLs from the (I hate) XML output. We then save these URLs to a text file (one URL per line) and use this to feed a FOR loop on the CMD shell.

Use:
STSADM -o activatefeature -id 747755CD-D060-4663-961C-9B0CC43724E9 -url [site URL]
To activate the RadEditor for SharePoint lists for a given site (initially this will activate the tool for Mozilla users only).
Then use:
STSADM -o activatefeature -id F374A3CA-F4A7-11DB-827C-8DD056D89593 -url [site URL]
To activate the RadEditor for IE users.

Where did we get those ID strings you ask? Look in the “Feature.xml” file in the following locations:
C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12TEMPLATEFEATURESRadEditorFeature
and
C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12TEMPLATEFEATURESRadEditorFeatureIE

The feature ID is listed in this document between the (big surprise) Id tags.

Now, how to I activate this feature so that it will be on for all future sites? Perhaps the answer is “Feature Stapling”:
http://blogs.msdn.com/cjohnson/archive/2006/11/01/feature-stapling-in-wss-v3.aspx

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s