Forum Discussion
MicrosoftUPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
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!
- Sad to report we have the same experience.
Same here, in IE Level 3 just takes us to Level 2
in other browsers Level 3 items are not clickable. there is no link underneath
- 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
- ssquiresPooya - flight rollout didn't complete until probably early afternoon yesterday. Can you confirm you are still seeing the issue? Thanks.
Thank you ssquires. I can see that the navigation elements are now fixed. This resolves by earlier problem of inconsistent navigation between classic and modern.
However, now another problem remains (I haven't done a comprehensive testing yet):
We have headers in our current navigation (left-pane), and these headers do not have links. While this works correctly as intended in the classic-mode, the modern-mode adds a link to the root site-collection for these link-less (I don't know what you call those) headers.
These comparative screenshots show you what I am talking about:
Modern-Mode (headers are linked)Classic-Mode (headers remain unlinked)
- ssquires
Thanks Abhimanyu Singh - yes, the intended design pattern of modern nav where nesting is used is for the parent header to have an expand/collapse target and a link target. Currently, if the parent/header doesn't have a link it gets treated like a self-referencing link (in this case to the root site collection). Let me discuss w/ the team to see whether there are other options.
