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!
Hi ssquires,
Thanks very much for this follow-up. Based on your response, I spent several hours last week re-examining my configuration. I do use term-driven pages.I think the issue was that, while I had an entry for Level 0 (site collection home), I did not have a URL specifically configured for it. It was never required for the link to work in classic managed navigation. Once I added that URL and let things sit overnight, all the child links fell into place. So that is a huge win for us, and will enable us to start to use modern libraries in our existing site collections. Also, the fact that the text in the drop-down and fly-out items is no longer truncated is a great improvement.
I've noticed three other differences in managed navigation as deployed in modern libraries:
1. If a level 2 (drop-down) item does not have a level 3 (fly-out) child, the URL "preview" appears as expected in the lower left corner of the browser when you hover over the level 2 item. If it does have a level 3 (fly-out) child, no URL "preview" appears when you hover over it. All level 0, 1, and 3 "previews" appear as expected. The links function correctly, but it would be nice if the level 2 previews appeared consistently, as they do in classic mode.
2. The response in the appearance of the navigation drop-downs and fly-outs is noticeably slower than in classic mode. Not bad, but not the lightning-fast feel we're used to.
3. If one hovers over a level 1 (global nav) item to display the level 2 drop-down and then does not click on one of the level 2 or level 3 items but simply moves the cursor away from the navigation area, the drop-down (and, if chosen, the fly-out) menu remains open until one clicks elsewhere on the page. In classic mode, the drop-downs disappear immediately when the cursor is no longer hovering over the navigation item. This need for an extra click contributes to the feeling that the response is a bit more cumbersome than in classic navigation.
Nonetheless, the fact that all levels of managed navigation now appear to lead to the correct URLs is a great breakthrough for us, and I very much appreciate your sticking with this!
My next task is to get this to work in classic publishing sites that don't use managed navigation. Right now, when viewed from a modern library the drop-downs display all the contents of the level 1 sites as well as the links to the level 2 sites, which is not the desired behavior. Is that your experience, as well, or am I doing something wrong?
Thanks again for all your help!
Richard
MicrosoftHi RichardSharp11 - thanks for the detailed reply/feedback. Great to hear that the recent updates are enabling you to move forward with using modern library ux. I'll take a look at that behavior w/ "no url" to evaluate whether there's more we should do there. I am keen to get this functionality working w/ modern templates so we'll keep the community posted on our progress there. RE: other items:
#1 - inconsistent status toast of L2 items - I've bugged so we can take a look at. Thanks for reporting.
#2 - interesting; I'd thought w/ the client-side improvements we'd made here it was faster. We'll take a look, but let me know if this persists.
#3 - yes, I'm seeing that now, too - and agree the flyouts shouldn't persist when you move cursor focus away. I've bugged for investigation
Re: your last comment on classic publishing template - there is likely more work to do there on our side. We haven't done much w/ that template in favor of the new communication template. I'll note and forward feedback to the team.
Thanks again!
Sean
- Yes, they are gone now this end too.
- Yeah, had those boxes as well in the last couple of days, not sure why, but they're gone now.
Plus one for faster appearance of menu.
Or at least let the menu appear when the header is selected. Currently nothing happens and that confuses users. It is not intuitive to only select the little triangle.
On that note, our global nav currently has these boxes around the headers? Anyone else seeing this? This is only in modern UI not classic.
- unclickable headers would be great, as I have many users that click on them before waiting.
Can you make the top-level in global navigation not be a clickable link? For example, would like Departments to not be clickable. Appears to require a URL.
