Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Customizing MySites

  Asked By: Nadia    Date: Aug 24    Category: Sharepoint    Views: 1725

I have never attempted to customize MySites..but that is a requirement
for a project that I am working on.
Does anyone know the best way to do this?
Where is the master page for the MySite kept?
Is it as simple as modifying that page, or do I need to do anything
I am reading a blog entry about the stapler and staplee feature, but
since I have never created a feature before, the entry is not making
much sense to me.
Can anyone point me in the right direction?



12 Answers Found

Answer #1    Answered By: Damini Dande     Answered On: Aug 24

There are two pages involved in customizing  a MySite. The default.aspx
page is the one used for the Private view of the MySite. It uses the
normal default.master file that is stored in the MasterPage gallery of
the site and ghosted to each site from the Global directory of the 12
hive. The public.aspx page  is the one that provides the public view of
the mySite. This page uses the default.master file that is Ghosted from
the global directory to the top level site of the Site collection. By
default that will be the same default.master as the default.aspx page.
But the token used to get the masterpages is different. For
default.aspx its ~masterurl/default.master and for public.aspx its
~sitecollection/_catalogs/masterpage/default.master. See the following
msdn article for an explanation of the tokens involved.


Answer #2    Answered By: Addison Peck     Answered On: Aug 24

I am using SPS2003 and a user was configuring the OWA Calendar webpart
on their mysite  and instead of the server address they made a typo and
put in their email address.

Now everytime they try to access their private mysite, it just says
syntax error. Bad thing is that I cannot get into the page  in order to
reconfigure/remove the ill-configured webpart.

Does anyone have any ideas on how to resolve this situation?

Answer #3    Answered By: Lalit Bhattacharya     Answered On: Aug 24

Try adding '?contents=1' to the end of the URL used to access his
MySite. This will normally take you directly to the WebPart Maintenance

Answer #4    Answered By: Gwendolyn Acosta     Answered On: Aug 24

No, that didn't work.. it did take me into his webpart maintenance but
the OWA part is not listed. I clicked reset and it didn't appear to have
changed anything.

When he click's mysite  from the portal it tries to go to this URL:


and it tries to open the mysite (I see a flash of blue as the background
is loaded) and then immediately goes to a white screen "Page cannot be

Answer #5    Answered By: Kyle Hernandez     Answered On: Aug 24

Ok I think I got it... I was using:
server.com/personal/<username>/?contents=1 and it was showing no
webparts to modify

I tried it using server.com/MySite/?contents=1 and it opened up and the
owa parts were there. Switched to shared view and selected it and
closed it. Now the page  opens!

Answer #6    Answered By: Kedar Phule     Answered On: Aug 24

Append the URL with a QueryString variable: Contents=1

So, if your URL is currently http://site/default.aspx
You would use start a QueryString using a question mark like this:

If your URL is currently something like
You would use aded a QueryString variable using an ampersand like this:

Contents=1 tells SharePoint to show the contents (1 means true) of the
page rather than render the actual page. This will display the Web Part
Page Maintenance page  with a list of WebParts that will be displayed
when the QueryString variable is removed. From here you can Close |
Reset | Delete Web Parts.

Answer #7    Answered By: Chanel Gaines     Answered On: Aug 24

Not sure why but my responses to the group seems delayed. Glad that you
got it working.

Answer #8    Answered By: Timmy Whitney     Answered On: Aug 24

So then all I need to do is customize  the correct default.master page  depending
on which view of the MySite I want to customize?
If that is true, then what is the deal with the stapler/staplee features?

Answer #9    Answered By: Harihar Sonnad     Answered On: Aug 24

First, customizing  the default.master in the global directory is not
supported by Microsoft. If you change it your changes may be
overwritten by a service pack or upgrade.

Second, The default.master file is used by most of the SharePoint pages,
and not just MySites.

So here is what I would recommend.

1) Modify the default.aspx and public.aspx to make use of a
different custom master  file. (Again this is technically not supported
if you make the changes directly to the files. But this is less
intrusive than making changes to default.master. )

2) Deploy the custom master or masters to the Masterpages gallery
of the MySite when it is created. This can be done either by modifying
the onet.xml of the site definition (not supported) or by using a
Feature and stapling the Feature to the existing Site Definition
(supported, but more work)

Take a look at the following blog  post that discusses how to add a
custom master as a Feature.


Answer #10    Answered By: Deven Gajjar     Answered On: Aug 24

How do I access the MySite masterpage gallery without creating a MySite

Answer #11    Answered By: Latisha Schneider     Answered On: Aug 24

If you navigate manually to the Settings.aspx page  of the top level site
of the root of the mysite  host you can access the gallery. For example
if the Webapp hosting mysites  is http://server:12345
<http://server:12345> then browse directly to
http://server12345/settings.aspx <http://server12345/settings.aspx> as
the Site Collection administrator. However, since each mysite is its
own site collection I don't know how many of the changes made here will
apply to new mysites that are created. Some, like the portal connection
property will apply. But I'm not sure editing the default.master here
would do you any good on new mysites.

The editing I was talking about in the email below was in the file
system of the web front end servers in the 12 hive. This is where the
default files are retrieved from when a new site collection is created.

Answer #12    Answered By: Nora Maxwell     Answered On: Aug 24

Stapling Features to existing Site Definitions is really an exciting
option in WSS v3.

In WSS v2, you were not allowed to modify the out of the box Site
Definitions; this is still true in WSS v3. *However*, you can "staple"
new functionality onto any Site Definition, including those out of the
box like MySites.

Look for the FeatureSiteTemplateAssociation element of a Feature. It
simply relates the GUID of another Feature with the ID of a Site
Definition. The next time the Site Definition is used to provision a
Site, the Feature will be activated too.

Didn't find what you were looking for? Find more on Customizing MySites Or get search suggestion and latest updates.