SharePoint Designer Cache

Clearing SharePoint Desinger Web Part Cache:
After deploy the new assembly to the server you might see that new properties are not reflected in SharePoint Designer. You can correct the issue by clearing the C:\Documents and Settings\[User]\Local Settings\Application Data\Local\Microsoft\WebsiteCache

Clearing the Assembly Cache for SharePoint Designer:
There might be issue with loading workflow with custom activities that you have deployed for SPD workflows, which will result in "Failed to load the workflow" !!
Getting rid of cached file from:C:\Documents and Settings\[user]\Application Data\Microsoft\SharePoint Designer\ProxyAssemblyCache\. Then delete the folder (12.x.x.xxxx)

How to disable Contributor Settings in SharePoint Designer

When you install Microsoft Office SharePoint Server 2007 (MOSS 2007), By Default the Contributor Settings will be enabled on your site(s). You will notice this in the SharePoint Designer task pane.

This is because your account is present in the Content Authors group, wich may “restrict the use of some features” as the task pane mentions.This behavior can be modified if you turn off the "Contributor Settings" in SPD.

How to get this above window:

1. Open The site in SharePoint Designer

2. Site Menu

3.choose Contributor Settings.

4.Click on Disbale Contributor settings

5. Refresh the page and U will not see that message again !!!!

Limit SharePoint Designer to Certain Users

For this post, I am going to concentrate on using security permissions to limit access to SPD.

Below is a quick way to limit only certain users the ability to SPD.
-Out-of-the-box, users who have Full Control and Contribute security permissions can open SPD and make changes.
-Assuming you want only users with Full Control access to have access to SPD, the easiest way is to turn off access to the site from SPD for users under the Contribute permission level.
-Open the site
-Select Site Actions > Site Settings.
-Under the “Users and Permissions” group, click the “Advanced permissions” link.
-Select Settings > Permission Levels from the toolbar.
-Click on the Contribute link.
-Under Site Permissions, uncheck the “Use Remote Interfaces - Use SOAP, Web DAV, or SharePoint Designer interfaces to access the Web site.” option.
-Click OK

The issue with the above steps is now any user with Contribute access cannot use SPD. You may have some users who you still want access to SPD but do not want to give Full Control to. For that scenario, you could create a new permission level.

-Open the site
-Select Site Actions > Site Settings.
-Under the “Users and Permissions” group, click the “Advanced permissions” link.
-Select Settings > Permission Levels from the toolbar.
-Click on the Contribute link.
-Scroll to the bottom and click the “Copy Permission Level” button.
-For the Name, type in “Contribute (With SPD)” (without the quotes).
-For the Description, type in “Can view, add, update, and delete. With SPD support.” (without the quotes).
-Under Site Permissions, check the “Use Remote Interfaces - Use SOAP, Web DAV, or SharePoint Designer interfaces to access the Web site.” option.
-Click Create

Now the out-of-the-box Contribute permission level can contain all the users who need contribute access but no SPD. For those users you want to give SPD access to, they can be added to the “Contribute (With SPD)” group. One caveat is if you have other applications access the SharePoint web services for the site, they will no longer work.

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

To prevent users from changing a Windows SharePoint Services 3.0 site or a SharePoint Server 2007 site, disable the authoring feature in SharePoint Designer 2007 by editing 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\\xml

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

For example, if the English (United States) version of Windows SharePoint Services is installed on the server, the SharePoint Team Site site template is located in the following folder:
Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\XML

To do this, follow these steps:
1.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\SiteTemplates\XML.-Meeting Workspaces: Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extentsions\12\SiteTemplates\MPS\XML

Note Replace the Drive placeholder with the drive where Windows is installed.

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=wdfopensiteThen, click Save.
The complete Project Title tag is as follows:

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

-Click Start, click Run, type cmd, and then click OK.
-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.
 
Warning: Do not edit a Windows SharePoint Services 3.0 site or a SharePoint Server 2007 site by using Microsoft Office FrontPage 2003. If you do this, you run a major risk of corrupting the site. Instead, always use SharePoint Designer 2007 to edit the site.