June 2008 - Posts - Neil's IW Space

Inserting "Content Placeholders" into a New "Derived" Master Page using Sharepoint Designer

I am currently busy re-designed a web site for a company using the "Publishing Feature" in Sharepoint that will be hosted on the Internet. This process is going to keep me busy for a couple of months and I am learning a lot about publishing web sites through Sharepoint. One of the most critical things that you need to learn is the ability to insert the "Content Placeholders" required by Sharepoint into a normal web page and then converting that to a "Master Page".

The unique challenge that Sharepoint causes most IT companies is the fact that it is a "Content Management" tool and not a web design tool and it takes more than a tool to design a web site. If you actually sit down and think about designing a web site in Sharepoint, there are a number of skills required:

DBA for SQL Server
Network Engineer for IP, DNS, Firewall.
Sharepoint Architect/Consultant for design and Implementation.
Web Designers for look and feel.
Content Managers to upload the content.
Project Managers to organize everything.
Users/Testers to verify the solution.

I am not saying that each of the job roles I defined above is a separate person, but in a lot of instances they might be. Being a technical person myself, I will deploy Sharepoint and Architect the design, but do not ask me to design a "funky" looking web page. The problem expands in the fact that "Web Designers" refuse to use Microsoft tools as they all have their preferences like "Dream Weaver" , "Adobe Flash", PHP, etc. I believe that "Share Point Designer" is a very good tool, but I seem to be in the minority. So where does that leave us?

The only solution I found that works practically in the industry is the following:

"Web Designer" will design the "Look and Feel" using whatever tools they prefer as long as the output is HTML.
"Content Manager" will create a new "Publishing site" in Sharepoint using the HTML and insert the content placeholders required by Sharepoint using SPD.
The new "Web page" will be converted to a "Master page" and uploaded to Sharepoint.
New "aspx" pages will be derived from this "Master Page" to have the same look and feel.

The bullet points above basically outline what I will be explaining in this blog. At this point I am making the assumption that the "Web Pages" have already been designed and we are going to continue by inserting the placeholders using SPD.

Deriving a New "Master Page" from a HTML Page

I am going to start this section by showing you how to rip and entire page with content from an Internet web site and saving it into "Sharepoint Designer". Once we have done that, we will convert the page into a "Master Page".

The first step is to launch and instance of SPD and select "New -> Web Site" from the file menu.

The dialogue box that opens will then provide you with an option called "Import Web Site Wizard". Select this option and then select "OK". This action will then launch the wizard.

The first page of the wizard provides you with a number of options that allow you to import a web site using different protocols. In this particular example the web site is located on the Internet and therefore I will be using HTTP to import it into the solution. Once you have define the URL, select "Next" to continue.

The second page is where people get confused. The Web location that the wizard is prompting you with is going to be located on your local machine. This is purely for testing purposes and this will not be an "Sharepoint Enabled" site, so do not attempt to test it here later and wonder why it is not working. This also requires you to be running a local instance of IIS, so ensure that you have done this before attempting the steps in this blog. Click "Next".

The third page in the wizard is asking you to limit how much information you will be pulling from the web site that you are referencing. It will default to the "Home" page with content, but it does allow you to go deeper into the site if required. Keep the amount of disk space required in mind. In this case we only require the "Home Page" as we are going to convert it into a "Master Page". Click "Next".

The final page of the wizard is purely a confirmation before initiating the process. Click "Finish" and wait.

The wizard will now import all the HTML, images, script files, etc. as used by the web site that you are referencing and add it to you local copy. This will now be available in SPD for editing and should look something like the image below.

There are a couple of interesting things to note at this point:

In the "Folder List" a number of additional folders have been created that duplicate what was on the web site and contain the content as referenced by the "Home Page. There will be folders like CSS, Images, JS and a couple of others.
The "Home Page" is sitting in the root of the site as "Default.htm". This is the page that we will be converting to a master page.

The "Default.htm" page can be converted to a "Master Page" by merely changing it's file extension.

Of course this does not really make it a "Master Page" as we still require "Content Placeholders", but we will fix that problem later. We first need to create a test site in Sharepoint.

Setting up a "Test Site" in Sharepoint:

The feature in Sharepoint that allows us to use "Content Placeholders" is called the "Publishing Feature". This feature can be enabled at "Site Collection" and "Site" level. The easiest way to do this is merely to create a new "Publishing Site" or "Publishing Portal" in Sharepoint and use that as the testing site. I already have a "Site Directory" setup so I will create it from there.

Select "Create Site" from the "Site Actions" menu or create a new "Site Collection" using the administration console.

Give the site a name and then select one of the publishing templates that are available as standard in MOSS. This does not work in WSS as the publishing feature was actually migrated from a previous MS product called "Content Management Server" and MS needs to make some money on this.

Now that the test site has been created, we need to finish the "Master page" we started with, but where do I find these content place holders?

Adding the "Minimal Master Page" to the Sharepoint Designer Project:

Quite some time ago, I was struggling with the "Default.Master" that comes with Sharepoint, trying to pull it apart. After a couple of frustrating hours I gave up and started searching the Internet for a easier way to do this. I stumbled upon an article on the MS site that gave me some ideas and I even wrote a blog about it.

I revolves around the concept of an "Minimal Master Page" that has everything stripped out of it except the bare minimum of placeholders that Sharepoint will expect. In that blog I explain how to add a new "Master Page" to a SPD project and how to add the content placeholder to it. You can find the hyperlink in this paragraph and at the bottom of this blog.

To continue the process in the rest of the blog I am going to assume that you have read this blog and added the "Minimal Master" page to the current project.

If you look at the "Minimal Master" page in the image above, you will note that there is almost no HTML in that page and the "Content Placeholders" are stacked neatly below each other.

The next part of the project will be the process of moving the placeholders from the "Minimal Master" page into our new derived "Master Page".

Moving the "Content Placeholders" into the new Master:

Unfortunately this process is not as easy as it sounds and the best way to do this is in the "Code" view of the page and not using the GUI interface of SPD. I have broken the various HTML pieces into sections and I will explain how to move them piece by piece. This might take you a couple of attempts depending on the complexity of the derived "Master" page, so just be patient. All the example HTML section will be copied from the "Minimal Master" and pasted into the "New Master"

The first part that we need to move is the reference section that refers to all the Sharepoint assemblies and controls.

This section of the HTML code must be pasted right at the top of your "New Master" page. It has to be above the "<HTML>" tag.

The second slice of the HTML must be placed below the "<HTML>" tag. This starts the "Web Part Manager" in the Sharepoint site that allows web parts to function.

The third slice of HTML must be placed below the "<Head>" tag of the new page. This placeholder is used for the "Title" of the site.

The fourth slice of HTML places a "<Form>" tag section inside the "<Body>" tag of the new master. Also note that a "Java" script needs to be referenced inside the "<BODY>" tag itself at the top. I do not have an image of it, but you will see it in the "Minimal Master" page. This section will generate the additional placeholders required by Sharepoint. You can place it anywhere in the "<Body>" tag, but I prefer placing it at the bottom so that the placeholders are out of the way and I can move them into place later.

Now that the "New Master" page has been built, we need to publish it to the test Sharepoint site.

Publishing the "New Master" page to the test site:

To publish the "New Master" page from our local site to the test site, we need to use the publishing feature built into SPD.

This can be done by selecting the "Publish Site" option from the "File" menu in SPD.

The corresponding dialogue box that opens allows you to publish the current site content to another location. In our case that would be the "Test" site we created earlier in Sharepoint. Select the option "Sharepoint Services", type in the URL to the Sharepoint site and select "OK".

This action will then open a split window in SPD showing the "Local Web Site" on the left and then "Remote Sharepoint Site" on the right. It now becomes a simple matter of using the arrows in the middle to move the content from the one site to the other, but I will give you some advise:

Rename you "New Master" page to something other than "Default.master". If you do not do this, you will end up overwriting the "Default.master" page in the Sharepoint site and this will cause other problems.
Publishing sites store all their pages in a folder called "Pages". Move your pages into this folder on the remote site otherwise you will note be able to see it.
Remember to move all the dependant folders like "Images", "CSS", "JS" with your pages.
You can also use "Drag and Drop" capabilities to move things around.
Remember the relative paths between your pages and the content so that the links are not broken.

Now that the "New Master" page has been published, we still need to create a content page from the "Master" before we will have anything to view.

Create a new "Content Page" from the "Master Page":

Master pages can not be displayed directly in the browser as they are only templates for "aspx" pages. This therefore requires us to derive a content page from the new "Master Page". To do this, launch a new instance of SPD by selecting "Open Site" from the file menu in SPD and then selecting the URL of the "Test" site we created earlier in Sharepoint.

Navigate to the "New Master" page we published earlier and "Right Click" on it. One of the options that will appear on the drop down menu is "New from Master Page". Select this option.

This action will derive a new "aspx" from the master page and they will look identical. There are only one or two things left to do before we can view the result.

Save the new "aspx" page and call it "Default.aspx".
Ensure that you either save or move this new page to the "Pages" folder.
Save the entire solution.

Now it is time to view the result of all this effort. Open your browser and navigate to the URL of the Sharepoint we used for testing. Scroll down to the bottom of the page.

You will notice that the "Switch Account" and "Site Action" components are now available in the bottom left hand corner. If you did not receive any errors and you can view these components, then your site is now Sharepoint enabled. The other placeholders are invisible, because at this point in time, they have not content to display.

The next thing that needs to be done is to move the content placeholders to the correct areas in the page, but that is a blog for another time. I hope you found this blog useful and good luck with your publishing sites.

SharePoint default.master page placeholders

Access Denied on a Sharepoint Site when editing Master Pages

Posted Jun 28 2008, 01:07 PM by Neil with 2 comment(s)

Controlling security in Sharepoint using "Web Application Policies"

I received some interesting comments on a blog I wrote sometime ago about "Access Denied on a Sharepoint Site". The comments ultimately culminated in a fix based on adding user accounts to the "Web Application Policy" using the Sharepoint admin console. Up to this point I have never really spent any time trying to understand this component of Sharepoint and therefore I thought it was time to do so.

To understand the implication of using "Web Application Policy's" we need to do a quick review of how Sharepoint is structured and how the security model impacts on this.

Security is implemented on a number of distinct levels:

Farm Level - used purely by administrators to configure the environment on which Sharepoint is based.
Web Application Level - this is area where I will be focusing the attention for this blog as this is normally completely ignored. This controls access to an entire web application in Sharepoint.
Site Collection Level - controls security through inheritance between all sites in the collection. The problem comes in the fact that there can be up 50 000 site collections per "Web application".
Site Level - controls security for an individual site. This is normally done via inheritance from the site collection and there can be up to 250 000 sites in an collection.
Object Level - individual objects like "Lists" , "Libraries" and "Web Parts" can also have their own security defined.
Item Level - individual "List Items", "Documents" and "Folders" can also have their own security. It is my general belief that if you have to do security at this level, their was a serious design flaw during the planning phase.

As I have already mentioned, the focus of this blog is around "Web Application" level security and this is implemented via "Web Application Policies". These policies can be define by using the "Sharepoint Admin Console".

The link can be found by navigating to the "Operations" Tab" and then selecting the link called "Policy for Web Application" under the section labelled "Application Security".

Different policies can be define for different web applications. It therefore becomes very important to ensure that the correct web application is selected in the top right hand corner of the screen. Once the application has been selected you will be able to view the entire list if user accounts and groups that have been granted access at this level and what permissions they have been assigned.

Another aspect to take into consideration is that the "Admin" accounts used on the network, even if they are "Domain Admin" accounts, have no rights on any "Web application by default. It therefore becomes an requirement to add these accounts to the "Web application Policy" if they are intended to have access to these sites. The tendency is to normally add these accounts to the "Site Collection" level and this can become tedious as there might be many site collections.

The other use for this would be to grant all "Anonymous" users "Read" access to all sites in a "Web application" without having to do this at "Site Collection" level.

To add a new user to this list is a simple matter of selecting the option called "Add Users" from the toolbar.

This process will start a two page wizard to guide you through the process. The first screen merely prompts for the "Web Application" to which this account or group will be added and the "Zone" to which this applies. The "Zones" are used to expose the same site to the Intranet and Internet at the same time with different security privileges. Most people use "Default" as this will use the "Authentication Providers" to determine the "Zone.

The second screen in the process allows you to specify the user and group accounts as well as the security permissions that apply at this level. Selecting the accounts is easily done by using the "Browse" button under the "Users" section. The permissions are broken into four distinct categories:

Full Control - this would be that same as giving someone "Administrator" rights on the web application.
Full Read - this is normally used for anonymous users.
Deny Write - used for denying access if a user belongs to more than one group.
Deny All - user will never have access.

Once you have completed the wizard, select "Finish" to commit the changes.

At this point the user account or group you selected has permissions across the entire web application without the need of applying it at "Site Collection" level.

Referenced Blogs:

http://blogs.msdn.com/joelo/archive/2007/04/02/web-application-policies.aspx

Access Denied on a Sharepoint Site when editing Master Pages

Setting up Dual Authentication on Windows SharePoint Services 3.0 (Forms and NTLM)

Giving Anonymous Access to Users on a SharePoint Site

Posted Jun 23 2008, 01:42 PM by Neil with 1 comment(s)

Filed under: Sharepoint

Preparation Guide for Exam 70-631: WSS 3.0

Of the two "install and configure" exams for Sharepoint, this is probably the more difficult of the two depending on your IT background and experience. The "MOSS" exam:07-630 focuses more on the product itself and how to install, configure and use it. The WSS exam is all about the environment surrounding Sharepoint and how to build a Farm. It therefore requires a lot more knowledge on networking and server architecture and less on WSS itself.

Once again, all the information that I have consolidated in this blog is freely available on the Internet, but here it is on a silver platter.

Audience profile

A typical candidate for this exam has a minimum of one year of experience in configuring Windows SharePoint related technologies. In addition, candidates for this exam should have expertise in the following areas:

Web administration/Internet Information Services 6.0
General Windows Server 2003 directory administration
General networking infrastructure
General knowledge of Windows SharePoint Server 2007
General understanding of Microsoft .NET 2.0 as it relates to Windows SharePoint Services 3.0
General understanding of Internet Security and Acceleration (ISA) Server
Network load-balancing for applications
Administering SQL Server 2000 or 2005 for Windows SharePoint Services 3.0
General security and authentication practices
Back-up and restoration of data

Credit toward certification

When you pass Exam 70-631 TS: Windows SharePoint Services 3.0, Configuring, you complete the requirements for the following certification:

Microsoft Certified Technology Specialist: Windows SharePoint Services 3.0 â€“ Configuration

Preparation tools and resources

In addition to your hands-on experience working with the product, Microsoft Learning recommends that you use the following tools and training to help you prepare for this exam. These training resources do not necessarily cover all of the topics listed in the "Skills measured" section.

Classroom training
Microsoft E-Learning
Microsoft Press books
Practice tests

Course 5060: Implementing Windows SharePoint Services 3.0 (two days)

Collection 5403: Implementing Microsoft Windows SharePoint Services 3.0

There are no Microsoft Press books currently available.

MeasureUp
(Measureup.com)

Self Test Software
(Selftestsoftware.com)

Microsoft online resources

Learning Plan: Get started by creating a step-by-step study guide that is based on recommended resources for this exam.
Product information: Visit the Windows SharePoint Services Web site for detailed product information.
Microsoft Learning Community: Join newsgroups and visit community forums to connect with your peers for suggestions on training resources and advice on your certification path and studies.
TechNet: Designed for IT professionals, this site includes how-to instructions, best practices, downloads, technical resources, newsgroups, and chats.
MSDN: Designed for developers, the Microsoft Developer Network (MSDN) features code samples, technical articles, downloads, newsgroups, and chats.

Skills measured

This exam measures your ability to accomplish the following technical tasks using Windows SharePoint Services 3.0.

KEY:
= The course includes material to prepare you for this task. = The course includes some material to prepare you for this task. You will need to supplement the course with additional work. = The course provides a general introductory overview of this task. You will need to supplement the course with additional work.

Additional Resources:

Corro'll Driskell (MCT/MODL): Preparation Guide for Exam 70-631 ...

Exam 70-290 study guide, training, braindumps, bootcamp for 70-290 ...

MICROSOFT 70-631 Exam: online 70-631 Study Guide and Practice ...

TestKing 70-631 Exam Study Guide, Practice Exam, Labs, Audio exams

Related Blogs:

Official MS Site for this Blog

Course 5061- Implementing Microsoft Office SharePoint Server 2007

Course 5060 - Implementing Windows SharePoint Services 3.0

Course 50050A: Architecting Documents and Records Management Solutions with Microsoft Office SharePoint Server 2007

Course 50051A: Architecting Microsoft Office SharePoint Server 2007 Portals and Collaboration Solutions

Course 50049A: Architecting Web Content Management Solutions with Microsoft Office SharePoint Server 2007

Course 50048A: Enterprise Search Solution Architect Workshop

Course 50047A : Advanced IT Pro Course for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0

Course 50003A: Customizing and Extending Enterprise Content Management Solutions

Course 50004A: Implementing Advanced Portals and Collaboration Solutions

Course 50064A: Advanced SharePoint 2007 Development

Trandumper Rules

Posted Jun 20 2008, 09:32 AM by Neil with 3 comment(s)

Filed under: Sharepoint, Exam

Preparation Guide for Exam 70-630: MOSS 2007

A lot of people have been emailing me about exam tips on passing the MOSS 2007 exam. Even though this information is freely available on the Internet, it seems that people struggling to find this information. I have therefore decided to find the relevant information on the Internet and consolidate it into this blog. I hope you find this blog useful and good luck with the exam.