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!
It seems that whilst latest fix has resolved a number of issues with the global navigation, including the "Page not found" link showing, it appears we are now seeing a 0 character being added to the end of each global navigation node. Additionally our global navigation appears to have stopped working completely when a user clicks on the link.
Is anyone else seeing this? We've raised a ticket with MS to investigate.
Is anyone else seeing this? We've raised a ticket with MS to investigate.
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!
- ssquires
Adding Jeremy Coleman, MattyVx, bart_vermeersch, and Marc Wenning for notice - thanks all for the prompt reports. We've identified the issue and have paused/recalled the build to address before we roll any further. Thanks.
ssquires -- pleasantly surprised tonight as I tested to see if the by some change the navigation fix made it to our tenant already. Sure enough, it did, and................. it works perfectly! Publishing enabled at the root site and navigation propogates perfectly to all subsites.
That said, I needed to go into /_layouts/15/topnav.aspx and /_layouts/15/quiklnch.aspx on the top level and clear up some of the old links from when things were broken.Nice to have this working.... much better than running a powershell script to fix all sites/sub-sites..... thanks!
The one problem I have run into is that links in global nav dropdowns (second level) just flat out don't work on modern document libraries. Click, nothing, click, nothing.......
@Sean Squires -- you're killin us! So close..... :)
