Forum Discussion
Solved
Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
Creating a dedicated post to track this. Lots of discussion on this from Yammer, and havent really seen this anywhere here yet.. What is the status of new "Modern" capabilities to support struct...
Brent Ellis (and others) - good news! We're finally pushing out a fix to support structured and managed navigation on modern pages/apps in classic sites.
With this update, if you have enabled publishing on a classic team site, your structured or managed navigation nodes will now render correctly in the modern pages (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 nodes the edit link will direct you back to the classic settings page (/areanavigationsettings.aspx).
We hope this unblocks folks who have been eager to move to the modern UX. Do try it out let us know if you have any questions. Thanks!
ssquires
Microsoft
MicrosoftThanks James-Brennan - a regression has resulted in several UI issues w/ this build. We have postponed and rolled-back until we can get fixes in place. I'll keep this list apprised of that progress. Apologies for the inconvenience - and thanks for your patience!
ssquires That's great, thanks for the update, it felt like an issue with the latest patching for the navigation. And thanks for monitoring this thread too.
Great job ssquires and MS team for monitoring this thread. Lots of good info.
I have set my tenant to first release.
My issue: top nav in modern pages always opens in new tab. Does anyone see similar behavior? Can we set the top nav links to open in same window?
Thanks in advance
- ssquires
Thanks kiran bellala - I missed your follow-up question. We are evaluating providing an affordance to specify the link opening behavior (yes, a departure from classic). Current design is links w/in same site path will open in same tab; links in a different path will open in a new tab. We're trying to minimize friction here, but can you elaborate on the business scenario to have more control over this behavior? Thanks!
People always have the simple option of right-clicking and opening a link in a new tab whenever they want. I would want to see the same default behavior as we see today in classic sites: any link in the global navigation should open in the same tab. Otherwise people will have the same maddening experience we see in O365 Groups, where navigating back and forth between the various functional parts of the Group ends up in a screen full of duplicate tabs.
This behavior (opening in same tab) should be observed when just the Publishing feature is turned on and also when Publishing is turned on *and* Managed Navigation is in use. (I use Managed Navigation in the global nav, and structured navigation in the local nav.)
If, in addition, you want to specify an option we can set to force opening in a new tab for a specific link, that would be fine; but the default should be as it is today - open in same tab for all links. It's easy for anyone to override and open in a new tab whenever they want, but there's no way for a person to override and open a link in the same tab.
Richard
Also, I have every site use the same global nav as the parent, so every site shows the same global nav as the top of the site collection.
- I've seen the same thing happen, but only for links to Contents and Subsites on the Site Contents page
I have one library in one subsite set-up as modern experience. It is showing all the correct navigation links in the top, global, navigation bar, yet they are not grouped into drop-down menus as per the rest of my site(s).
Looks like they fixed the weird numbers in the global navigation, but Im still seeing the page not found links in both the quick links and global navigation. This should not show as it is a hidden page.
- ssquires
Marc Wenning - the page not found fix is rolling out - are you still seeing this issue?
