Sharepoint 2007 breadcrumb includes default.aspx

Are you seeing default.aspx after Pages in your SharePoint breadcrumb navigation?

I found a simple fix for this problem in MOSS, modify the master page.

Open the master page and look for PlaceHolderTitleBreadcrumb

Change SiteMapProvider="SPContentMapProvider" to

SiteMapProvider="CurrentNavSiteMapProviderNoEncode"

To quote from my reference

When you’re creating a new Page Layout, make sure you override the Title Breadcrumb with something that uses the CurrentNavSiteMapProviderNoEncode provider.

Heather Solomon has written a great post detailing the behaviour of out of the box page layouts breadcrumbs. She has also linked to other resources for how to modify and use the breadcrumb.

Ghost – ReGhost

What is ReGhost?

ReGhost is an application that was built quite some time ago, to deal with the unghosting issues prominant in Windows SharePoint Services 2.0, and SharePoint Portal Server 2003.  Whenever a page/item was customised in an application such as SharePoint Designer – the content would become what they call ‘unghosted’.  Meaning that the content is now stored and served from the database – it now exists as totally independant, rouge content.

The main issue for people has been the upgrade from WSS v2.0 / SPS 2003 to Windows SharePoint Services v3.0 / MOSS.  In order to successfully migrate your content, you needed to find an easy, reliable, safe way to “reghost” the content.

This is where ReGhost comes in – it will locate all of your content databases on the network, and examine them for unghosted pages – it then allows you to select which content you wish to revert.  Once selected, it will essentially reset the content, aka “reghost” the content – making it possible for your migration to complete successfully.

There are other uses for the product – when a company is managing a large intranet, a lot of customisations can occur – sometimes it’s nice to be able to revert some of the sites or pages back to their original state – ReGhost can do this for you – and it can do it very quickly and effectively.

Some of it’s current features include:

1. Individual item/page reghosting – being able to select individual content is crucial for most organisations

2. Content backup – ReGhost will let you execute a database backup before performing the reghost operation – keeping your data safe.

3. Content Searching – it will find your content databases for you – making the whole process a lot quicker.

4. Remote Reghosting – you don’t need to have the software installed on your servers, just point it at your SQL Server instance with appropriate permissions, and away you go!

5.  Transactional database access – if anything goes wrong during the reghost operation – everything will be rolled back, and your data is kept safe.

6. Automatic update facility – the application has a really nice software update facility, where it’s possible to check for the latest version, as well as a comment on what features are included in the new version, it will then on request, download and update your software for you – hassle free.

Due to the sheer amount of effort put into the product, it’s been released for a small purchase price.  You can register and subscribe to the download here.

SharePoint: Howto disable editing sites with SharePoint Designer

I just saw this Microsoft KB here. This is very interesting – prevent users from using SharePoint Designer to modify your site!

To quote the exact article, it details steps you can undertake to prevent users from changing a Windows SharePoint Services 3.0 site or a SharePoint Server 2007 site by disabling the authoring feature in SharePoint Designer 2007.

All you have do is edit the Onet.xml file.

By default, the Onet.xml file for Windows SharePoint Services 3.0 and for SharePoint Server 2007 is in the following folder:

\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\<Service>\xml

Note Replace the <Service> placeholder with the name of the Windows SharePoint Service that is installed on the server.

On the server that is running Windows SharePoint Services 3.0 or SharePoint Server 2007, locate the site template that you want to modify. Site templates are located in the following folders on the server:

•SharePoint Team Site: Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extentsions\12\Template\LangID\STS\XML.

•Meeting Workspaces: Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extentsions\12\Template\LangID\MWS\XML

Note Replace the Drive placeholder with the drive where Windows is installed. Replace the LangID placeholder with the language version of Windows SharePoint Services 3.0 that is installed on the server.

2.Right-click the Onet.xml file, click Open With, and then click Notepad.

3.Locate the Project Title tag, and then add the following line:

DisableWebDesignFeatures=wdfopensite

Then, click Save.
The complete Project Title tag is as follows:

<Project Title=”Team Web Site” ListDir=”Lists” xmlns:ows=”Microsoft SharePoint” DisableWebDesignFeatures=wdfopensite>

4.Restart Internet Information Services (IIS). To do this, follow these steps:

a.Click Start, click Run, type cmd, and then click OK.

b.At the command prompt, type iisreset computer_name /restart, and then press ENTER.
Note Replace the computer_name placeholder with the name of the computer that is running IIS.

After you follow these steps, users who try to open a site that is based on the site template that has the DisableWebDesignFeatures=wdfopensite attribute will receive the following message:

This web site has been configured to disallow editing with FrontPage. Contact your web site administrator for more information

By default, if you try to change a Windows SharePoint Services 3.0 site or a SharePoint Server 2007 site by using Microsoft Office FrontPage 2003, you receive the following error message:

Web Site Editing is Disabled. This web site has been configured to disallow editing with FrontPage. Contact your web site administrator for more information.

Source | Microsoft KB