[Anonymous]

Hi John,

  The procedure to replace the OOB quick launch/top bar menus in SP2013 is similar with SP2010.

Please note that the master page name has changed from v4.master to seattle.master

As a reference, you can use the site templates (CRM, Help Desk, etc) that we distribute with QuickApps.

If you have any difficulties please let me know.

Thanks,

[Anonymous]

It's worth to mention that you need to use SharePoint Designer 2013 to perform this operation.

n

n

In this tread there is more details about how you do it.

n

http://en.community.dell.com/techcenter/sharepoint-for-all/f/4782/t/19560164#81612

n

n

n

n

PS

n

This additional note is for people that haven't done any OOB menu replacement with QAs menus.

[Anonymous]

Hi , thanks for the response.

The issue we have is that SDP2013 has no GUI to set the location of the webpart on the Master Page. We are trying to define a procedure to address this configuration. Placement of the CascadingMenu is quite tricky as it spans the page and sits across a number of other controls.

I would be keen to hear from anyone with a method to solve this issue.

From memory the 2010 Quest Site based templates [Project, CRM HelpDesk] only use a PanelMenu. Do the 2013 versions use the CascadingMenu or just the PanelMenu?

Thanks again for the response. Regards

[Anonymous]

Hi John,

The goal here is to replace OOB Quick Launch web part with one of the QA's menu web parts.

Please backup your master page before doing any manual modifications.

This is how I do it step by step:

– create a page, create a menu list and drop a qCascadingMenu or a qPanelMenu on it

– complete the configuration of the above web part (including the skin lists, etc)

– open the page using SP Designer and copy the xml text. It looks like this (please note that I cut off some text here)

<Navigation:PanelMenu webpart="true" runat="server" __webpartid="{22DA81BD-25E4-4D60-AFE2-C4B862D1DB8C}">

<WebPart xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/WebPart/v2">

<Title />

  <FrameType>None</FrameType>

  <Description>Panel Menu webpart</Description>

  <IsIncluded>true</IsIncluded>

  <ZoneID>FullPage</ZoneID>

….

– use SP Designer and open the master page (SP2010 v4.master, SP2013 seattle.master)

– at the top of the page add the following :

<%@ Register TagPrefix="Navigation" Namespace="WA.Navigation" Assembly="WA.Navigation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=2b4b09f1c57c8f0b"%>

The header would look similar to this

<%@Master language="C#"%>

<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Import Namespace="Microsoft.SharePoint" %> <%@ Assembly Name="Microsoft.Web.CommandUI, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Import Namespace="Microsoft.SharePoint.ApplicationPages" %>

<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/15/Welcome.ascx" %>

<%@ Register TagPrefix="Navigation" Namespace="WA.Navigation" Assembly="WA.Navigation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=2b4b09f1c57c8f0b"%>

– localize the following control (text)

SharePoint:SPNavigationManager

and add Visible="false"

– copy the xml text that we saved in the first steps and paste it after the SPNavigationManager (see above)

– save the master page

-refresh the page

If you see that the page doesn't render correctly or you get any errors then restore from your backup copy and do it in baby steps saving after each operation and rendering the page after each step.

If is still not clear please let me know.

I'd suggest you to try in a non Production env. until you have it working.

[Anonymous]

Hello All, Does Quest/DELL have a recommended best practice method for setting the qCascadingMenu Web part in a SharePoint 2013 Master Page?

[Anonymous]

Hi John,

To answer your question regarding the templates, they haven't changed from SharePoint 2010.  As a result the PanelMenu is still being used with the templates for SharePoint 2013.

[Anonymous]

Hi John,

To answer your first question, if you are using SharePoint Designer 2013 try the instructions below.  Let us know if you have any questions.

It is highly suggested that the following steps are implemented and verified in a DEV environment and “elevated” to a production environment as a part of a change control process.

1.  Create a web part page

2.  Add either a qCascadingMenu or qPanelMenu to the page (Steps are the same for both).  Similar to the screenshot below.  You need to add the web part to the page first so you can copy out needed XML.

3.  Configure the web part using ezEdit. For more info on configuring each web part please see the following video (Cascading

     Cascading Menu: http://bcove.me/a0a231pm

     qPanelMenu: http://bcove.me/bnw4loee

4.  Keep the page above open because we will come back and copy out some xml needed for steps later in the process.

5.  Using SharePoint Designer right click the master page and select “Edit the File in Advanced Mode” (page name = “seattle.master”)

add the following node to the header of the page:

<%@ Register TagPrefix="Navigation" Namespace="WA.Navigation" Assembly="WA.Navigation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=2b4b09f1c57c8f0b"%>

When done the header should look like this:

<%@Master language="C#"%>

<%@ Register TagPrefix="Navigation" Namespace="WA.Navigation" Assembly="WA.Navigation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=2b4b09f1c57c8f0b"%>

6.  In the master page, find theSPNavigationManager node and add the following attribute (visible=”false”).  This step hides the default navigation menu provided by SharePoint.

The node should look like the following when complete:

<SharePoint:SPNavigationManager id="QuickLaunchNavigationManager" runat="server" QuickLaunchControlId="V4QuickLaunchMenu" ContainedControl="QuickLaunch" EnableViewState="false" Visible="false">

7.  Go back to the page created in step 1 and open the page (right click the page in SP designer and select “Edit the File in Advanced Mode”).

8.  Search for and copy the code for the CascadingMenu or PanelMenu web part node similar to the one below.

Be sure to copy the ENTIRE node:

<WpNs0:PanelMenu runat="server" __MarkupType="xmlmarkup" WebPart="true" __WebPartId="{3939452E-0166-4A1E-8A21-71FA00AE0300}" ><WebPart xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/WebPart/v2"><Title>qPanelMenu</Title>

  <FrameType>Default</FrameType>

  <Description>Panel Menu webpart</Description>

  <IsIncluded>true</IsIncluded>

  <ZoneID>Header</ZoneID>

  <PartOrder>2</PartOrder>

  <FrameState>Normal</FrameState>

  <Height />

  <Width />

  <AllowRemove>true</AllowRemove>

  <AllowZoneChange>true</AllowZoneChange>

  <AllowMinimize>true</AllowMinimize>

  <AllowConnect>true</AllowConnect>

  <AllowEdit>true</AllowEdit>

  <AllowHide>true</AllowHide>

  <IsVisible>true</IsVisible>

  <DetailLink />

  <HelpLink>/_layouts/15/QuestSoftware/WAResources/Invariant/Help/HTML/QuestWebParts.html?context=QuestWebParts&amp;topic=PanelMenu</HelpLink>

  <HelpMode>Modeless</HelpMode>

  <Dir>Default</Dir>

  <PartImageSmall />

  <MissingAssembly>Cannot import this Web Part.</MissingAssembly>

  <PartImageLarge>/_layouts/15/QuestSoftware/WAResources/Invariant/Images/PanelMenuWebPart.gif</PartImageLarge>

  <IsIncludedFilter />

  <ExportControlledProperties>true</ExportControlledProperties>

  <ConnectionID>00000000-0000-0000-0000-000000000000</ConnectionID>

  <ID>g_3939452e_0166_4a1e_8a21_71fa00ae0300</ID>

  <PanelMenuConfiguration xmlns="http://www.workplacearchitects.com/Navigation">&lt;Configuration&gt;

  &lt;Menu SiteUrl=&quot;.&quot; ListName=&quot;PMMenuExample&quot; TextFieldName=&quot;Text&quot; MenuIdFieldName=&quot;Menu ID&quot; ParentMenuIdFieldName=&quot;Parent Menu ID&quot; TargetUrlFieldName=&quot;Target URL&quot; TargetFieldName=&quot;Target&quot; IconUrlFieldName=&quot;Icon URL&quot; CultureFieldName=&quot;Culture&quot; /&gt;

&lt;/Configuration&gt;</PanelMenuConfiguration>

  <RibbonTabName xmlns="http://www.workplacearchitects.com/Navigation" />

</WebPart></WpNs0:PanelMenu>

9.  Paste the node copied above after the SPNavigationManager node updated in step 5

10.  Replace the value "WpNs0" with "Navigation".

10.  Save the master page

11.  Refresh the page created in step 1 from within the browser and the result should look like the following:

[Anonymous]

Hi Dan, thanks for this. Have you tried doing this with Design Manager and Code Snippets? Regards

[Anonymous]

Hi Dan, just looking at the Skins in the qCascadingMenu and the clean UI of 2013. Are any of these skins harmonised with 2013? We have found is hard to find a skin that looks right. Regards

[Anonymous]

Hi John,

Right now there is not an exact skin match for SP 2013.  There are a few that are close (like Metro).  Immediately after the 6.2 release we will be working on a SP 2013 skin that will be something you (and other customers) can use.

[Anonymous]

Hi Dan – Any update on that SP 2013 skin?  Thanks!

[Anonymous]

Hi ,

We plan to work on and deliver a new skin after the 6.2 release later this month.  The new skin will most likely be available sometime in August.  If you have any other questions please let us know.

[Author]

Posts