Hannah Scott's Blog: Features

Showing posts with label Features. Show all posts

Wednesday, January 05, 2011

MOSS 2010 Team Site Pages

First impressions of MOSS 2010 Team Sites

MOSS 2010 Team sites are slightly different from their 2007 counterparts in that they are based more on Wiki pages, meaning that you can mix content and web parts within a rich text area.

By default when a team site is created it contains a default.aspx file (located as before in the site root directory) and a home.aspx file. The home.aspx is now the site homepage and is located in a document library called "Site Pages" (/sitepages/home.aspx), generated by a feature dependency of the "WikiPageHomePage" feature called "WebPageLibrary" (see: 14\TEMPLATE\FEATURES).

New pages created using the "Site Actions / New Page" button by default will create new Wiki pages, which will reside in the "Site Pages" document library. If the "Site Pages" document library does not exist you will be prompted to create one before new pages can be created.

New pages created via "View All Site Content / Create" or "View All Site Content / Pages / ... ribbon ... New Page" allow editors the choice to create either a basic page or a web part page. Selecting a web part page prompts choices of page layouts (one col, two col etc) and available document libraries (Pages, Site Pages, Documents, Custom etc). Note that these Web part pages do not display the Quick Navigation panel on the left side of the website, which if integral to your site navigation / heirachy display will pose some important decision making with regards whether or not to activate publishing.

Friday, January 04, 2008

Microsoft.Office.Workflow.Feature file not found

This comes from: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1692100&SiteID=1

Found out it was to do with the Visual Studio templates.

There are 2 sets of templates:

Windows SharePoint Service (WSS 3.0)
Microsoft Office SharePoint Server (MOSS 2007)

If you are developing on a WSS 3.0 box and you try and use a MOSS template then it adds a reference to the "Microsoft.Office.Workflow.Feature" namespace (which is part of the "Microsoft.Office" set of files that come with MOSS.

Change to the correct templates

Otherwise you can just remove those ReceiverAssembly and ReceiverClass references from your Feature.XML and you should find it works just fine.

The Feature.xml should then look like:

Monday, April 02, 2007

Creating a Custom Master Page & Deploying it as a Feature

First of all thanks to Heather Soloman who posted a great article about this Create a Feature: Master Pages for Site Collections.

Here's how i set up the Custom Masterpages and depoyed them as a feature:

Create the Feature

Create a folder called CustomMasterPages under the Features directory on the web server.
Inside the CustomMasterPages folder create the folders:
- en-us
- Images
- Styles
- MasterPages
- PageLayouts
- JavaScript
Copy these two files from the Features directory PublishingLayouts:
- Feature.xml, and
- ProvisionedFiles.xml
Create a file in the MasterPages folder called CustomMaster.master
Open CustomMaster.master in notepad and paste the following minimal master page code from Microsoft.
Alternatively Heather Soloman has created another version of the minimal master page which is the version I used in the end. The reason for this is that Heather's version is a stripped out version of the default.master master page which includes all the functionality available. The Microsoft version has only the minimal elements included.
Format the master page with XHTML tags & CSS.
Change the doc type to XHTML transitional.

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/transitional.dtd">

Edit the ProvisionedFiles.xml file to provision the master page, CSS files & images etc.



<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<Module Name="OSGMasterPages" Url="_catalogs/masterpage" Path="MasterPages" RootWebOnly="TRUE">
<File Url="tr_portalMaster.master" Type="GhostableInLibrary">
<Property Name="ContentType" Value="Teleport Master Page - DEFAULT PORTAL LAYOUT" />
<Property Name="PublishingPreviewImage" Value="~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/tr_teleportLogo100.gif, ~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/tr_teleportLogo100.gif" />
<Property Name="MasterPageDescription" Value="This is the TelePort master page (DEFAULT CSS LAYOUT) for use with collaboration or publishing sites." />
</File>
</Module>
<Module Name="PublishingLayoutsPreviewImages" Url="_catalogs/masterpage" IncludeFolders="??-??" Path="" RootWebOnly="TRUE">
<File Url="tr_teleportLogo100.gif" Name="Preview Images/tr_teleportLogo100.gif" Type="GhostableInLibrary">
</File>
</Module>
<Module Name="Images" Url="Style Library/Images" Path="Images" RootWebOnly="TRUE">
<File Url="tr_telerealLogo102.gif" Name="tr_telerealLogo102.gif" Type="GhostableInLibrary" />
</Module>
<Module Name="OSGStyles" Url="Style Library" Path="Styles" RootWebOnly="TRUE">
<File Url="tr_core.css" Type="GhostableInLibrary" />
<File Url="tr_portalMaster.css" Type="GhostableInLibrary" />
<File Url="tr_portalMaster_IE6.css" Type="GhostableInLibrary" />
<File Url="tr_portalMaster_IE55.css" Type="GhostableInLibrary" />
</Module>
</Elements>
Add a preview image to the language folder (en-us).
Create a unique GUID
In the Feature.xml file:
- Change the feature ID to the unique GUID
- Change the title to Custom Master Pages
- Change the Hidden state to False
Recycle the app pool on the WFE website

Deploying the Feature

On the web server (DEV02) launch command prompt and change dir to:

cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

Install the feature using STSADM:

stsadm -o installfeature -name CustomMasterPages

Go to Site Collection Features on the portal top level site and activate the feature.

To use the master page select from the drop down list on Site Settings / Site Master Page Settings

Redeploying a Feature

Changes made to the feature require that the feature is redeployed. For example; adding new master pages, css files etc. To do this:

On the web server (DEV02) launch command prompt and change dir to:

cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

Reinstall the feature using STSADM:

stsadm -o installfeature -name CustomMasterPages -force

Reactivate the feature in Site Collection Features by deavctivating and the activating it.

Hannah Scott's Blog