I am working through a migration from SP 2010 to SP 2013 using Metalogix. I am experiencing an issue with SharePoint 2013 where managed metadata navigation does not show on non-root sites in a site collection.
It seems global navigation was finally solved in SP 2013 with the introduction of managed metadata navigation. Pinned terms sets appear to provide true cross site collection global navigation. I was able to implement managed navigation for a bunch of new site collections, which appeared to work like a charm for top level sites...
…until I clicked into sites within those site collections. These sites don’t pick up the global navigation. Even though the navigation settings of those sites is set to ‘Display the same navigation items as the parent site (Parent is using Managed Navigation )’, the navigation only shows a link to the top level site collection:
Only when I go into the Navigation settings for the site, change the Global Navigation radio from ‘Display the same navigation items as the parent site’ to ‘Managed Navigation’ and back, click ok (mind you, nothing changed), the navigation now appears correctly for the site:
I tried creating a Powershell script to explicitly set global navigation to structured navigation, then back to display from parent, but that did not work either. Apparently, only performing those actions through the UI works.
FWIW, the root site collection is a document center, while most of the other site collections contains team sites. The custom master page is deployed using a site collection feature. There are 200-400 sites on average in each of the site collections.
This post here speaks of the same kind of issue, but only when creating new sites in UI: http://blog.jussipalo.com/2013/03/sharepoint-2013-managed-navigation-not_12.html
Any ideas what might be going on here? This is a bummer because this one ripple throws the entire idea out of the window. I would love for the navigation to be all OOTB and not have to write any custom code.
Appreciate any info anyone can provide.