Case 1: AllowDeletion
There might be a case where you have custom document libraries in your SharePoint-solution bound to a customer specific custom content type. It might be confusing for the customer to have the default libraries, which come when the Office SharePoint Server Publishing feature has been activated.
“Some user will at some point inevitably put…
Read more »
If you are working with SharePoint 2010, see this article by Todd Carter:
An Expected Error Has Occurred
Mike has also written a nice article of the other options:
SharePoint 2010 Custom Error Messages for Public Facing Deployments
SharePoint doesn’t have an out-of-the-box support for custom error pages. Or at least it’s a little bit problematic to implement custom error pages…
Read more »
SharePoint’s out-of-the-box breadcrumb control is kinda a strange animal. Basically you have three different kinds of breadcrumbs in SharePoint. Each of these breadcrumbs are using different provider for their back-end:
- Layout Pages / Administration Pages use SPXmlContentMapProvider,
- Publishing Pages use CurrentNavSiteMapProviderNoEncode, and
- Form Pages (AllItems.aspx, EditForm.aspx, DisplayForm.aspx, etc.) use SPContentMapProvider
This is all fine, when you have different master…
Read more »
SharePoint 2007 (and 2010) has a very comprehensive but somewhat confusing navigation system built-in. The main limitation of SharePoint navigation system is, that it doesn’t work over site collection boundaries, and by default it produces real horrible <table> structured output. The output can be altered by writing a custom menu control adapter (or by using CSS friendly control adapters). The…
Read more »