Tag Info

New answers tagged

0

Pages will always inherit the master page from the parent site, if you set a master page with a side bar in the top site all the sub pages will have the menu. You can remove it page by page using a javascript, you just need to add a content editor webpart to the pages where you don't want the vertical menu and add the script inside of it. For the settle ...


0

Dirty way of doing it but, create and add a user control to all pages, in user control's on load method, check if web has any pages in pages library or other possible ways, if it does then change the master page url for the web. Get count of publishing Pages SharePoint: Dynamically Change Master Page OR if i didn't understood you properly then, Using a ...


0

if i get you right you want the same menu displayed on all site collections.... just like a website? if so goto your root site collection homepage, site actions site settings -> click on navigation under look and feel -> make sure global navigation "show subsites" is checked. Make sure it looks correct under navigation editiing and sorting. Once that is ...


0

If you use SharePoint 2013 you can use Managed metadata navigation to create custom navigation for your site collections. Read this blog post for details.


1

You may define New Heading (Site Settings -> Look and Feel -> Quick Launch) with the required URL for other site collections URLs to be added to the quick launch menu.


0

I'm not sure how much of a hack this is, but we got tired of the HostWebUrl; So we edited the SharePointContext.cs: On Home controller we save the SPHostUrl if provided. Where SharePointContext.cs tries to resolve the host url from HttpContext.Request.QueryString, if the QueryString does not contain the SPHostUrl we simply read it from the cookie. We ...


0

You can achieve this by using CSS ':after' selector and 'content' property. #DeltaTopNavigation ul#zz10_RootAspMenu > li.static > a > span > span:after { content: "Home"; font-family: inherit; font-size: 14px; } #DeltaTopNavigation ul#zz10_RootAspMenu > li.static > a > span > span { font-size: 0; } In the above image, you ...


0

First you will have to set up the lists with the different permissions to lock down what the users have access to. You could then use a content search webpart to return only lists. This should run the query using the authenticated user so they will only be able to see the lists that they have permissions for.


0

I'm not sure I understand the question exactly, but if you mean showing a different top nav, left nav, and web parts per user it's probably easiest to use the "Target Audience" functionality on the individual navigation links & web parts. With that, you can use AD groups, SharePoint groups, or even individual usernames to show different content on the ...


0

I see two ways: 1. Use PowerShell and this arcticle. Preffered. 2. Edit url's in content DB. Not preffered.


0

Everything is possible! If you have a custom master page you can move around the ContentPlaceHolders as you wish (even empty some of them). But, you will probably need to write a lot of css to make it look good, and also, the left navigation can be overwritten by page layouts so if you choose this path you should probably make your own page layouts as well ...


1

Regarding your first question: you can also use PowerShell to accomplish this. Powershell has built in cmdlets to open and process XML and the SharePoint cmdlets will allow you to easily insert this data into a list. This snippet shows how easy it can be: Use the [XML] type accelerator to convert results from Get-Content into an XML document, and then ...


0

There is not a way to do this out of the box. You will need to do this using the API or Web Services. Your code would parse the XML and then create a list with the required columns based off of the nodes in your file. OR you can open the excel file with your xml content,then you can import the same excel sheet to sharepoint list as well. Source


1

I think this is what you are looking for: // Web Navigation using (var site = new SPSite("http://yoursite/")) { using (var web= site.OpenWeb()) {   // PublishingWeb Navigation var pubWeb = PublishingWeb.GetPublishingWeb(web); // Exclude subsites to appear in navigation pubWeb.Navigation.CurrentIncludeSubSites = false; // Exclude new ...


0

It's using the SPWeb.Navigation.TopNavigationBar Excerpt from MSDN: using (SPSite site = new SPSite("http://localhost")) using (SPWeb web = site.OpenWeb()) { if (web.Navigation.UseShared) return; // Get the top link bar. SPNavigationNodeCollection topnav = ...


1

This blog post might answer your question (if I interpret it correctly): Query String URLs are Magical (Part 2 of 4) It uses Query Strings in the URL to pass in the project ID as a parameter to another page and uses the query string filter web part to parse that parameter out of the URL. I think this is what you mean by "defined by a link from a previous ...


0

I would see about using the Managed Metadata Navigation feature in SharePoint 2013. It might require a custom server control or web part to accomplish but that would be about the only way I can think of to make them all the same without manually maintaining them on an individual basis. You might be able to accomplish the separate sites with "pinning" or ...



Top 50 recent answers are included