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
MicrosoftBrent 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, we are yet to see this.
Although the navigation is now settled up and the "page not found" link is gone, but the global (top) and current (left-pane) navigations are now the same. The actual global menu is now gone!! We have set it on our sub-sites to inherit from the parent site-collection, but somehow the new nav ignores that and makes the global navigation exactly same as the current (left) one. In our case, both are structural and not managed.
Further, the modern list/library still does not allow metadata filtering! We have set filters on term-sets, but in modern view that is not available. This new style is getting more furstating day by day. Our users still find the classic view more neat and clean. The new view looks very unpolished and unncessarily big.
- Miceile Barrett
Hello Abhimanyu Singh, I am working on creating the modern list/lib metadata filtering experience and wanted to give you some updates on the progress. Currently, we have released a feature called "filters pane" Filters Pane Help Article. We have just rolled out to PROD so you can expect to see it within the week if you don't already have it!
This feature is the first iteration for replacing metadata nav. The next months will be focused on cleaning up the UI, supporting term set filtering, and making sure metadata nav will no longer force users to back to SP classic.
Best,
Miceile
Thank you Miceile Barrett. Yes, we can see the filter pane, but that includes only a limited number of the list fields and no metadata terms. We look forward for the full metadata filtering options. It is good to know that you are working on this.
Abhimanyu Singh wrote:Thank you Miceile Barrett. Yes, we can see the filter pane, but that includes only a limited number of the list fields and no metadata terms. We look forward for the full metadata filtering options. It is good to know that you are working on this.
Miceile Barrett Any update on this please? It's been a long time and we are yet to see comprehensive metadata filtering in the filter pane of the modern UX. Please undertand that this is one of the friction sources for us which is preventing us from switching to modern from classic.
Pinging ssquires again.
FYI, for those people having issues where the global and current navigation is the same, an alternative is to use managed navigation for the top level for global navigation. It seems that modern pages DO seem to inherit the managed navigation correctly. Yes, I know, it's not perfect but things are inherited just fine that way.
Hey, it's a step.............
- ssquires
That's correct - thanks Clint Lechner for posting. As noted in my other reply, we've identified the issue w/ the REST API and are working on a fix.
- ssquires
Thanks Abhimanyu Singh - sounds like RobOK is reporting same. We'll take a look; the intended design is the modern page/controls use the same publishing provider navigation settings and render the data similarly.
As for metadata filtering on lists/libraries, we are working on a new experience for this that should be rolling out soon. Adding Miceile Barrett for notice/comment on that feature.
- Thank you @Sean. Hope to see this fixed soon. And thank you for pinging @Miceile on metadata filtering.
ssquires -- to be clear, you're saying the intended functionality should have the modern pages duplicate/inherit the global navigation and current navigation? Meaning the global and current navigation should not be the same, correct?
- ssquiresCorrect. We've identified the issue (specifically w/ the REST API to get the Navigation Provider Type) and are working on a fix (the issue is specific to structural nav from parent web (it works fine w/ managed nav). Thanks for reporting - and sorry for the inconvenience!
Abhimanyu Singh -- there's no way that what you're seeing with the global and quick launch being the same is how it is supposed to be (I hope). At least, I hope that's not what Microsoft thinks is "fixed" or reasonable......... if so, they have pretty much destroyed the global navigation and any hope that people will move to modern sites quickly.
Clint Lechner see the screenshots that I took for both the classic mode (what it is supposed to be) and the modern mode (what is messed up):
ClassicSo-called Modern
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.
