Forum Discussion

kiran bellala's avatar
kiran bellala
Brass Contributor
Mar 08, 2017

Re: Modern Team Site - Global navigation

Christian Enghaug
I am doing the same thing which is to enable publishing features and setup navigation. However, the global navigation is not inheriting to sub sites. Did you have the same issue? Did you setup global in each sub site manually?

13 Replies

  • Ivan54's avatar
    Ivan54
    Bronze Contributor

    I'm having different issues with enabling metadata global navigation in my tenant.

    I've successfully enabled the publishing site collection features, but whenever I want to switch to metadata navigation I get "Access Denied" for our root sharepoint online site collection.

    I'm Global Admin, Site Collection Admin and have manually assigned me Owner Permissions for the root site. Still Access Denied.

     

    Anyone else?

    • Florian Siegel's avatar
      Florian Siegel
      Copper Contributor
      Powershell is the key: Connect to Sharepoint and try this.
      Set-SPOsite https://yourURL.sharepoint.com/sites/sitename -DenyAddAndCustomizePages 0
    • Oliver Bartholdson's avatar
      Oliver Bartholdson
      Brass Contributor
      Same experience here. I can get Structural navigation to work properly, but Managed Navigation throws and "Access Denied".
      • Helios Comms's avatar
        Helios Comms
        Iron Contributor

        Well I'm glad I found this thread because I was pulling my hair out with all the modern pages, not just the Office 365 site. Our first problem was that global navigation entries (inherited through the entire tree) were duplicated so one got "Library Library Admin Admin" etc on the top bar - but only on modern Wiki pages. That bug appears to have now been fixed as the global navigation is now working as expected on modern Wiki pages. But my client has recently had to switch to using Office 365 groups as Microsoft have turned off new site mailboxes (lead balloon time) and I've just noticed that the global navigation menu is missing from Office 365 groups as shown below. And "Site settings" isn't there either. From a quick read of above, it appears the root global navigation settings isn't being inherited. I'm guessing because it's a completely different weird hidden site collection?

         

        Office 365 user interface experience does appear rather rushed!

         

        BTW - why is the standard Edge spell checker disabled in this editor?

         

  • Christian Enghaug's avatar
    Christian Enghaug
    Brass Contributor

    Yes, sub sites were configured to inherit the global navigation, but instead of displaying the parent global navigation, the local navigation was displayed as the global navigation on sub sites. In my developer tenant inherit of the global navigation seems to be fixed now.

     

    I configured the global navigation manually on each sub site, but you could use PnP PowerShell and the Provisioning engine to do this. Something like this:

     

     

    $cred = Get-Credential
    Connect-PnPOnline -Url "<URL to site where you have configured the global navigation>" -Credentials $cred
    Get-PnPProvisioningTemplate -Out "c:\NavigationTemplate.xml" -Handlers Navigation

    Then remove the CurrentNavigation from the template (c:\NavigationTemplate.xml). And then apply that template to all sub sites.

     

     

    Connect-PnPOnline -Url "<URL to site where you have configured the global navigation>" -Credentials $cred
    $subWebs = Get-PnPSubWebs -Recurse 
    
    foreach($web in $subWebs){
        $web.Navigation.UseShared = $false
        $web.Update()
        $web.Context.ExecuteQuery()
    
        Apply-PnPProvisioningTemplate -Path "c:\NavigationTemplate.xml" -Handlers Navigation -Web $web -ClearNavigation
    }

     

     

    This is not tested, and is just an example of how you could do this by PowerShell. 

Resources