Forum Discussion
MicrosoftUPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Microsoft
Hi ssquires - As far as I can see, neither structured nor managed navigation work in modern sites when the Publishing site collection feature is turned on. Is your group continuing work in this area to resolve these issues, or is this now considered the end state? Thanks,
Richard
- ssquires
Hi RichardSharp11 - apologies if I missed an earlier comment - this work was to support structured/managed nav on modern pages in classic team sites. Enabling the publishing feature in a modern team site is not a supported state as it causes other issues - most pertinently, edits to settings cannot be persisted (please see https://msdn.microsoft.com/en-us/pnp_articles/modern-experience-customizations-customize-sites for more details). Thanks, Sean
Hi ssquires - Thanks for the reply. As you'll see in the description and pictures in my post on 4-Apr-2017, the site I'm working on is a Classic SharePoint site with publishing turn on for the site collection and the top level site, using Managed navigation for global and Structured navigation for the Quick Launch. It is not a Modern site, but I did create a Modern page and I set the view for the document libraries to show the Modern view to see how the navigation would appear on those pages. On other pages the navigation appears as it always has. When I'm on a modern page or a document library with a modern view, the navigation loses the flyouts (labeled level 3 in my screenshots) and does not follow the simple alternate CSS file I use simply to make each entry wider, put an outline around each entry, and add a highlight color when you mouse over an entry. The links (which omitted the "/sites/synctest/" part of each link in my earlier description) are now correct, so that's an improvement! But the existing dropdowns have no outline or mouse-over highlight color, so they're very hard to see, and the flyout level is missing. So my question is, is there work still going on that will address these issues, or is the current state the intended end state?
My goal is primarily to be able to turn on the modern views for document libraries and lists in existing Classic SharePoint sites, but I can't afford to lose the functionality of our current navigation. Thanks very much,
Richard
- ssquires
Hi RichardSharp11 - thanks for the clarification. No, goal for pub provider support in modern control is to provide parity on key functionality to unblock folks from moving to modern. The support for level 3 nodes is specific to horizontal managed navigation that we thought our previous fix addressed, so we're looking to address now (I'll keep thread apprised w/ that status). The support for alt CSS is one we're also investigating further, as we need to see how this aligns w/ the Fabric controls we are now using. I'm hoping that our Fabric improvements (design and interaction behavior) mitigate the need for alternate CSS, but acknowledge the feedback that we might need to provide affordances here. Thanks.