You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 19, 2025. It is now read-only.
Please provide short description covering two areas:
the navigation nodes are provisoned on the wrong site.
we have a client context that is on a child web.
we run the code below and the navigation nodes are added to the root site instead of the site we are actually on
//var webModel = SPMeta2Model.NewWebModel(web =>
//{
// web.AddWebNavigationSettings(NavigationDefinitions.ClientNavigationSettings);
// web.AddQuickLaunchNavigationNode(NavigationDefinitions.GetRegionHomeNavigationNode(context.Web.ParentWeb.Title));
// web.AddQuickLaunchNavigationNode(NavigationDefinitions.ClientHomeNavigationNode);
// //});
provisioningService.DeploySiteModel(context, webModel);
#region Client Site Nodes
public static QuickLaunchNavigationNodeDefinition ClientHomeNavigationNode = new QuickLaunchNavigationNodeDefinition()
{
Title = "Client Home",
Url = "~site"
};
Which version of SPMeta2 do you use? Use the following code snippet for your convenience. It shows all the details on SPMeta2 and SharePoint runtime used.