MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds


  Asked By: Ronald    Date: Aug 10    Category: MOSS    Views: 684

I have done an enormous amout of searching on how to customize our Sharepoint 2007 implementation, and have just a few questions left unanswered. Mark Kruger has an outstanding listing of links at www.sharepointblogs.com/.../7570.aspx, and i have found the following page to have a very good example of the basics for creating a custom master page; www.sharepointblogs.com/.../12984.aspx

I have copied the code from the above link, and created a template called custom.master, and this is where my questions begin.

How do i add Web Part Zones to the master page?
To customize the look and feel of the page, how and where can i insert custom HTML?
How can i go about adding other ASP.NET controls to the page?



9 Answers Found

Answer #1    Answered By: Michelle White     Answered On: Aug 10

The code for creating a master page from that article is the bare minimum required for the master page, and doesn’t leave much insight as to what can be done with a master page. I suggest you open up (for viewing purposes only) one of the master pages that ship with 2007. There you will see how you wrap HTML code around the ContentPlaceholder controls to form the layout and design of your page.

The web part zones are stored in the page layouts, and those files can be found in the same gallery as the master pages. If you open one of those ASPX files, you will see how within the asp:Content tags there are the field controls, SharePoint user controls, and web part zones.

Answer #2    Answered By: Sheena Ray     Answered On: Aug 10
Answer #3    Answered By: Jaime Weaver     Answered On: Aug 10

Excellent write up this will be a big help in my future quests to modify our portal.

Working with a Microsoft Rep on a different issue today, he sent the following links for reference.





Answer #4    Answered By: Damon Garner     Answered On: Aug 10

Sorry to say it but I think that Master Pages in WSS v3 are going to
disappoint. While they aren't hard to work with and they do a nice job
of customizing the interface including navigation and zones, there is
not a good way to customize  your entire site.

There are two major outages:

1. The list item edit/view for all lists
2. All pages in the _layouts pages

These two areas use a global look and feel that is not easy to overcome
using master pages for branding.

To overcome the first you must either edit Microsoft's Template Pages,
modify Microsoft's list templates, create all your own custom lists, or
programmatically change the default master on every page in every site
created (still leaves the _layouts problem).

To overcome the second you must either implement an HTTP handler or
override every class in the _layouts folder and edit every ASPX page in
that directory.

All solutions either lead you to a non-supported solution or will a
solution that will consume an inordinate amount of time.

Answer #5    Answered By: Karla Morrison     Answered On: Aug 10

One of our developers downloaded this utility - www.codeplex.com/.../View.aspx – which allows you to select a master page and optionally apply it to all sub-sites. We use it pretty frequently, which helps a lot with the point you mentioned about having to change the default.master programmatically across the site collection.

Answer #6    Answered By: Patricia Richardson     Answered On: Aug 10

We are implementing WSS v3 now and we want to have a a common banner
logo appear at the top of every page in our entire site collection.
To make this happen, should we create a modified MasterPage, apply
it to the top-level site and then use this tool to apply it to all
subsites? Is there anything else we need to do to make this happen
in v3?

Answer #7    Answered By: Alexandra Patterson     Answered On: Aug 10

Just log into which ever computer or computers are your web front end
servers and add it to your default.master page.

This will get 70 - 80 percent of your site, there are list view that
it won't work with ect... but you can deal with those later if you
feel it necessary.

Overall the average user will be fine with it on every site homepage
this way.

Answer #8    Answered By: Christop Mcfadden     Answered On: Aug 10

I highly recommend creating a Control Feature that overrides the
AdditionalPageHead Delegate Control on all out of the box Master Pages.
It only requires a few files:

Feature header
Elements detail
User Control

Ping me if you'd like me to post a simple sample.

Answer #9    Answered By: Stefanie Ruiz     Answered On: Aug 10

If you look closely, Stramit (Renaud Comte) wrote that code based on my
Master Page problems project. While I agree that most of the Master Page
issues can be overcome, they shouldn't exist at all. Microsoft dropped
the ball on Master Pages.

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