Skip to content
This repository was archived by the owner on Mar 19, 2025. It is now read-only.
This repository was archived by the owner on Mar 19, 2025. It is now read-only.

navigation nodes on child web client context are provisioned on root site instead #1140

@maratbakirov

Description

@maratbakirov

Brief description

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"
    };

SharePoint API

Which version of SharePoint runtime do you use?

SPMeta2 API

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.

var info = SPMeta2Diagnostic.GetDiagnosticInfo();

https://www.nuget.org/packages/SPMeta2.CSOM.Foundation-v16/1.2.140?_src=template

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions