Forum Discussion
Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
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!
Abhimanyu Singh -- right, my point was that I hope that isn't what is supposed to be happening. That's what I see as well and it certainly isn't what I consider to be working correctly.
Yup. Sad part is that Microsoft people aren't as active here as they had been on the older Yammer group. ssquires are you listening?
- ssquires
Microsoft
Hi Abhimanyu Singh (and others on this thread!) - my apologies for the radio silence on our part. I was away on family business and inquries on this thread were missed by others. I will review w/ the feature crew this morning and get back to everyone. We are trying to as attentive as we can to folks questions and feedback on this platform - so please do continue reaching out (and @mentioning us to ensure we get the notification)!
A quick summary:
- There was a related issue that delayed the rollout of this feature fix - so some of you may not have seen the fix in your tenant yet. It is currently at 50% WW and will be fully rolled out in the next two days to all of production (read: 100% WW this week). Thank you for your patience.
- Fair ask/feedback about inclusion on the roadmap - we work closely w/ our marketing partners to try and provide the right level of notice/visibility on feature announcements and major fixes; I will discuss w/ them further about adding this one there.
- As noted, this fix is specifically to enable the modern page navigation controls to read from the same publishing provider as classic pages do (for team sites where publishing feature is enabled); in other words, excepting functional differences between the classic (i.e., "recent" node) and modern controls themselves, the rendered data should be the same (per the settings you designate on the areanavigationsettings page. Some of the discrepancies noted here sound like bugs - so thank you for reporting and we'll look into it immediately.
Thanks!
ssquires does the structured navigation on a Classic site with modern pages and libraries uses the same techniques to retrieve the navigation? So does it use object cache, etc. and does not perform well with larger structures? Can we also expect this structured navigation on Modern sites too?
Thanks in advance.
- ssquires
Hi Robert Schouten - yes, it's currently using the same nav provider (the work we did earlier this year was effectively to ensure the modern control behaved similarly to classic one for consistency on those classic sites where publishing infra feature was enabled) - so it will be bound by the same functionality and limitations. As for support on modern sites - yes, something we are looking into, but no specifics I can share at this time. Thanks.
- Any idea @Sean on who to mention / ping for UI/UX (on modern lists) feedback?
- Thanks a lot @sean. Much appreciated. Hope the fix lands soon.
- This is a major flaw. I'd even open a support ticket just to get this documented, not that there is a solution for it.
