SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I made my farm level stapler and my site level staple features, for SPSPER#0 it fires on MySite creation, so I presumed SPSMSITEHOST#0 would be MyContent, but nothing gets fires at all.

I set the stapler for both templates to be sure but it only activates on SPSPER#0 on MySite and only updates the master page on MySite.

This is the first time we have had a client who wanted MyContent branding so we just aren't sure if we have the right template

share|improve this question
up vote 1 down vote accepted

I suggest you check out the following codeplex project. It includes a VS2010 solution for branding My Site Content Sites.

You will want to feature staple to SPSPER#0, that is the site template that is used when a My Site Content site collection is created, i.e. once per user as each user gets their own My Site content site collection.

If you want to brand you my site host site simply open that in SPD and modify that site collection's branding. There is only one My Site Host site for each farm, all uses share this one site collection.

share|improve this answer
We did the actual mysite with the onet file since we are doing multi stage testing and re-wipes and tests on certain things. Now the problem is why is it opening up the mysite url when it fires as the feature parent? – Hugh Wood Sep 11 '12 at 21:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.