Quantcast
Channel: SharePoint 2013 - Setup, Upgrade, Administration and Operations forum
Viewing all articles
Browse latest Browse all 21070

Quick Launch Customization: Why Staticdisplaylevels settings don't work smoothly like MaximumDynamicDisplayLevels?

$
0
0

Background:

Clients need the quick launch can support 3 levels of menu, the menu links will all be redirected to document libraries/sites/folders within current site, I realized that via SharePoint Designer 2013 + Managed Navigation, and it can support fly out menus like below now:

The question is how can I show 3 levels of menu not in the fly out menu but in more traditional quick launch menus.

Scenarios:

Here're the scenarios I have taken to realize the fly out effect above:

1. Unassociate the seattle.html from seattle.master;

2. Open seattle.master from SharePoint designer 2013:

3. Find codes below and update the value of StaticDisplayLevels & MaximumDynamicDisplayLevels as below:

<SharePoint:AspMenu id="V4QuickLaunchMenu" runat="server" EnableViewState="false" DataSourceId="QuickLaunchSiteMap" UseSimpleRendering="true" Orientation="Vertical" StaticDisplayLevels="1" AdjustForShowStartingNode="true" MaximumDynamicDisplayLevels="3" SkipLinkText="" />

Questions:

No matter How I set the value of StaticDisplayLevels & MaximumDynamicDisplayLevels(E.g. MaximumDynamicDisplayLevels=1, StaticDisplayLevels=4 or MaximumDynamicDisplayLevels = 0, StaticDisplayLevels=4), the traditional menu just support 2 levels of menu the 3rd level links will only be showed in parallel with 3nd level links(See picture below, Level0401 link should be a lower level under Level0301):


Best Regards.

Johnson


Viewing all articles
Browse latest Browse all 21070

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>