Change the Subsites and Pages navigation setting by code

February 27, 2008 11:12

It took me quite some time to figure out how to change the Subsites and Pages settings by code. I finally manged to change them. The setting “Show subsites” can be altered in 2 ways. I was only able to change the “Show pages” on a publishing site.

Method 1 (”Show subsites” only)
With this code you will access the AllProperties setting of the Sharepoint Site and change the __IncludeSubSitesInNavigation value. Somehow there is no such property for the “Show pages”.

SPWeb web = new SPSite(webCollection).OpenWeb();
web.AllProperties["__IncludeSubSitesInNavigation"] = “False”;
web.Update();
web.Close();
web.Dispose();

Method 2
With this code the “Show pages” and “Show subsites” option are disabled. To access these properties your site must be a publishing site.

SPWeb web = new SPSite(webCollection).OpenWeb();
PublishingWeb publishingWeb = PublishingWeb.GetPublishingWeb(web);
publishingWeb.IncludePagesInNavigation = false;
publishingWeb.IncludeSubSitesInNavigation = false;
publishingWeb.Update();
publishingWeb.Close();
web.Close();
web.Dispose();

Tags: code, IncludePagesInNavigation, IncludeSubSitesInNavigation, pages, publishing, site, subsites, __IncludeSubSitesInNavigation.

Posted in Sharepoint | Permalink | Post first comment

Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 12.0.1.0 of Microsoft.Office.Server. Search.Upgrade.SearchServiceInstanceSequence failed

February 1, 2008 14:14

Migrating your SharePoint environment inside a virtual machine might cause some unexpected behaviour. It can be possible that you bump into this error:

(more…)

Tags: Configuration Wizard, exception, registry, SearchServiceInstanceSequence, Sharepoint, unexpected behaviour.

Posted in Errors, Sharepoint | Permalink | Read 5 comments

The content expressed in this blog are those of Edwin Vriethoff and do not represent his employer's view in anyway. The contents of this blog has been carefully put together, but Edwin Vriethoff is not responsible in any way for any direct or indirect harm caused by individuals or organizations using the content of this blog in any way.