Controlling navigation options from the onet.xml

Controlling publishing features from onet.xml

Vesa "vesku" Juvonen — Sun, 14 Oct 2007 21:32:34 GMT

In the previous post, I promised to try to find time to share additional information concerning the onet.xml

re: Controlling navigation options from the onet.xml

Silverdragon — Mon, 21 Jan 2008 11:01:02 GMT

When setting OrderingMethod to "Manual", is there a way to move the individual navigation items into required positions?

Do I need to create a custom feature which sorts the items, after the main navigation feature has been installed?

re: Controlling navigation options from the onet.xml

sonofthesun — Mon, 21 Jan 2008 20:06:33 GMT

Unfortunately there's no out-of-the-box feature to sort the main navigation as requested.

One of the key challenges in this requirement is also the fact, that the sub sites are created only after the features have been activated... so you cannot manipulate these settings using features... this has to be done using some another approach.

Maybe a custom web control in the master page of the root site, which manipulates the navigation during first request and then stores the status to SPWeb.properties, so that manipulation is only done once.

re: Controlling navigation options from the onet.xml

Beat — Fri, 28 Mar 2008 18:22:40 GMT

Thanks for the post!

I was wondering why i can't hide pages the same way, at least they won't hide the way i try to hide them ;-)

i have a site definition for a publishing site where i defined a module 'Content' to deploy some default pages

<Module Name="Content"

Url="$Resources:cmscore,List_Pages_UrlName;"

Path="">

<File Url="sitemap.aspx"

Type="GhostableInLibrary"

Path="default.aspx"

Level="Draft" >

<Property Name="Title"

Value="Sitemap" />

<Property Name="PublishingPageLayout"

Value="~SiteCollection/_catalogs/masterpage/PageLayoutDefault.aspx,~SiteCollection/_catalogs/masterpage/PageLayoutDefault.aspx" />

<Property Name="IncludeInGlobalNavigation"

Value="false" />

</File>

According to the SDK, the PublishingPage class exposes a public property called 'IncludeInGlobalNavigation'.

Can somebody point me to the right direction.

re: Controlling navigation options from the onet.xml

sonofthesun — Fri, 11 Apr 2008 08:54:25 GMT

Good question... and actually quote logical due the misleading element names within the Module element structures.

The properties (Property element) here are actually columns within the list (site columns of the content type of the page) where the page is uploaded... not actual properties of the .NET class...

There's no direct way of setting the actual .NET class properties from the Module / File elements. If this is however required, you have to create a feature receiver, which manipulates the actual objects using APIs.

re: Controlling navigation options from the onet.xml

hkossu — Thu, 25 Sep 2008 13:07:46 GMT

can i include navigation groups(dropdownlists) to topnavi trough site definition(onet.xml).

would like to create group "documentlibs" with the dropdownitems pointing to documentlibs

re: Controlling navigation options from the onet.xml

Michael Hofer — Sat, 22 Nov 2008 19:42:03 GMT

Really good post - thanks. I wonder why MS cannot come up with a documentation like this...

re: Controlling navigation options from the onet.xml

Sudhir Kesharwani — Mon, 14 Sep 2009 15:41:58 GMT

Some real interesting facts of navigation properties:

- It is a typo from MS for AutomaticSortingMethod it is typed as **AutomaticSortingMathod**

- While specifying navigation properties following properties take value in small case:-

* InheritGlobalNavigation (true/false)

* InheritCurrentNavigation (true/false)

* IncludeSubSites (true/false)

while some of the properties accept values in Camel Case

* IncludePages (True/False)