Forum Discussion
MicrosoftUPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Hi everyone! Thank you for the feedback around wanting to move to the “modern” team site experiences, and needing support for structured/managed navigation. We’re pleased to announce that we have addressed this issue and will be rolling out the fix to the worldwide production environment in the coming days. Thank you for your patience – and to the community for helping us identify some issues during the initial First Release preview!
With this update if you have enabled publishing on a classic team site, your structured or managed navigation will now render correctly in the modern experience (both global and current navigation), including any scoped or audience-targeted links. We haven’t pulled all the classic settings into the modern panels yet, so when you need to edit the navigation elements, the edit link will direct you to the classic settings page.
Navigation settings on a classic team site:
Now render correctly on a modern page:
Additionally, subsites will correctly inherit from the parent web when structural navigation is used.
Parent site:
Subsite:
We hope this unblocks you as you move to the modern user experience (UX). Try it out, and let us know if you have any questions. Thanks, Sean!
112 Replies
We still are not seeing all our navigation rendered correctly when we move to the new UI. We are using Managed Navigation. We have the main level of sites listed, then subsites, then a third level of fly-out. I was told this would still be supported in the new UI. Please could someone confirm what the truth is??? We absolutely cannot move to the new UI without this.
- ssquiresThanks for reporting, Adrienne - as confirmed w/ Scott and Richard we should be supporting three levels (Parent > Child > Grandchild) in horizontal managed navigation. We are actively investigating a fix and should have something out soon.
Hi Sean - It appears that our 'grandchild' links are rendering when in the view of the library, but NOT in the modern page. When can we expect this functionality to appear consistently throughout the system?
Will you be adding support for second level menu navigation? Currently it appears that you only have top levels displayed. Also, if the label is too long to display in the current width, can you add a rollover popup to show the full name?
- ssquires
Hi Scott Joyner - the goal is to ensure functionality w/ classic publishing provider (and that behavior) - so for structured left and top that would be two-levels (parent-child), but for managed top it looks like it's not rendering the third level (grandchild). We're investigating the issue, so thanks to you and Adrienne for reporting.
As for long labels, yes, we should be truncating and providing full preview in the tooltip. We'll take another look at this one (thought it was previously fixed!).
Please don't tructuate menu items!
I know Microsoft are a huge fan of the ... but in a menu this really should not happen.
I currently see both options, so no trunctuation does seem possible!
Would it be possible to have the submenus fly out a little snappier?
I always see users click the headers since the menus just take that bit too long to appear.
Still waiting for a response to my question. We were told the new UI would support the flyouts in the managed navigation. We are still unable to move to the new UI because although we see one level of subsites, we do not see the next level as flyouts, which we rely on in our existing navigation. Please confirm. Thanks!
- ssquires
Adrienne Kidd - apologies, I didn't see your inquiry last week. Yes, the new control does support flyout, but currently only two levels (parent and child) - which is parity for structured navigation, but not managed nav on global. I've opened a bug and we'll see if we can get this amended.
Thank you! I can now fully support rolling out modern lists to our entire user base.
Great job!
Aaron
We were told the new UI would support the flyouts in the managed navigation. We are still unable to move to the new UI because although we see one level of subsites, we do not see the next level as flyouts, which we rely on in our existing navigation. Please confirm. Thanks!
- Great Job !
But what about the mobile view. When I open the modern UI Site with the activated global Metadata Navigation on my phone, the global Navigation disappears :-( I hoped there would be an Integration with the hamburger menu or something like this.- ssquires
Thanks Bernd Diel - that is the plan, to ensure parity of settings across devices. Adding Nate Clinton for notice/comment (I'll also follow-up on this one).
Bernd Diel We are also seeing this and its a massive problem for us. How can we rely on a Global Navigation that is not present on all devices (or resolutions)?
ssquires Is this a bug, a known limitation, or by design? What is the recommendation for shared global navigation across site collections which works on all devices?
- ssquiresCharlie - known limitation, but let me or Nate get back to thread w/ more detail. Thanks.
- ssquires
Hi Deleted - no, this fix is specific to ensuring support for modern pages in classic team sites only. We do not recommend enabling classic publishing infrastructure service feature on a modern, group-connected team site (see: https://msdn.microsoft.com/en-us/pnp_articles/modern-experience-customizations-customize-sites); it is technically possible to do, but an unsupported configuration at this time. Hope that helps!
Great to see this in my tenancy this morning - thanks team for resolving!
- Not sure if this is still rolling out, but my first release account doesn't correctly display the structural global navigation in a sub site. It's missing the root site "Home" link in the child sites.
In classic I get (when visiting subsite: Child 1):
Home (/sites/sitea)
Child 1 (/sites/sitea/child1)
Child 2 (/sites/sitea/child2)
In modern I get (when visiting subsite: Child 1):
Child 1 (/sites/sitea/child1)
Child 2 (/sites/sitea/child2)Just wondering if you got any replies or fixes for this issue. I'm having the same problem in my site collection and enabling publishing isn't fixing it.
The structural navigation is now broken for me. It worked for a couple of days and now the submenu in the structural navigation opens the Site above the Site I have set. Editing at "quicklinks.aspx" or "AreaNavigationSettings.aspx" doesn't help. The links are correct and it still opens the Site above. Adding new items also results in the same behavior. The order for both the structural and global navigation was also randomized on it's own today. Also tried adding a sub menu in the global nav and the items all open blank pages. Don't even want to fix the global nav anymore. Would be nice if something as basic as navigation would simply work. Regret having adviced the customer to make use of the modern pages. It's kind of hard to explain to a customer that you had to spend more than a day to fix something as basic as the navigation.
edit- just noticed that you mentioned that the fix should be deployed by the end of this week in the other post. Have advised the customer to wait and create a ticket if it's still not working after Friday.
We are having a simlar issue. Submenus are always directing users to the URL of the site above. For example using the new Managed Metadata option with the menu, we may have Dept...HR...Benefits, but it take to the HR link for this and all other submenu items.
- ssquires
Glenn Goldberg, DenisT Scott Joyner, - Sorry I missed these comment last week - yes, we learned there was a regression that broke the rendering of the L3 URL. A fix has already been patched and should be rolling to PROD. Apologies - thanks for your patience!
- ssquiresYes, let me know if you still have issues after next Monday. Thanks!
Issue is still there. The submenu in the structural navigation opens the Site above while the config is correct at /_layouts/15/quiklnch.aspx and /_layouts/15AreaNavigationSettings.aspx
