Microsoft Land

Posts Tagged ‘Sharepoint Designer

If you have a webpart on the Page which has a customized XSL for changing the user interface and getting the below error

Error while executing web part: Microsoft.SharePoint.WebPartPages.WebPartPageUserException: Personalization has been disabled for this zone.     at Microsoft.SharePoint.WebPartPages.SPWebPartManager.ThrowIfCantModifyZone(String zoneID, Boolean throwIfLocked)     at Microsoft.SharePoint.WebPartPages.SPWebPartManager.ProcessZoneId(WebPart webPart, Boolean throwIfLocked)     at Microsoft.SharePoint.WebPartPages.SPWebPartManager.SaveChangesInternal(SPLayoutProperties layoutProperties, Boolean skipRightsCheck, Boolean skipSafeAgainstScriptCheck)     at Microsoft.SharePoint.WebPartPages.BaseXsltListWebPart.get_CustomizedXsl()     at Microsoft.SharePoint.WebPartPages.BaseXsltListWebPart.LoadXslCompiledTransform(WSSXmlUrlResolver someXmlResolver)     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.GetXslCompiledTransform()     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform)

and if the error is NOT being thrown for Owners of the site,

1. Delete / Add the user account again to the site.

2. Make sure the user has Manage Lists permission level.

Though i am not quite clear how it solves the issue, it worked for me.

Just wanted to share something related to SharePoint Designer.  It’s an Annoying issue.  Couldn’t get time to see what the problem is, but when changes are made to the file (Like master page / Layouts / Style sheets) and checking, SharePoint designer for some reason does’nt show up the latest file that’s checked in / approved along with the content of the file.

To resolve the issue, just make sure that whenever you start opening the Designer, clear the Temporary cache so that designer loads everything afresh again.


Hope this helps.

When using List View webpart / Data form webpart there will be many occasions where we need to customize the XSL associated with the webpart.  By default this XSL is pulled from the OOB delivered XSL’s which are in the 14 / 12 Hive, and obvisouly we do not want to make changes to this XSL.

We can take a copy (keep in the file system / Sharepoint Document Library) of the same XSL customize , it in the way that we need and associate them to the webpart, by chaging the XSL path in the webpart properies – When opened with Sharepoint Designer. If the XSL is not being applied make sure that the property ddwrt:ghost propery is completly removed / set to empty.

My Tweets


Get every new post delivered to your Inbox.

Join 121 other followers