10

The recommended way to do this is to use PropertyBag (key/value pairs) through the Properties of SPFarm, SPSite.RootWeb (for root site of site collections), SPWeb, SPList etc (depending upon the scope that you need). Managing Custom Configuration Options for a SharePoint Application Update code example: // ...inside web app feature ...


7

I achieved this in a much more simple way. Follow this link - really easy for beginers linke me... http://blog.incworx.com/blog/sharepoint-administrators-blog/hide-recently-modified-from-the-quick-launch Edit page, insert content editor web part, edit source HTML of web part, paste in this HTML: <style type="text/css"> .s4-recentchanges { ...


7

There's a property for the list instance called something like ShowOnQuickLaunch, and you want to set that to false.


7

Like Amal said, it's not easy with CSS, because FontAwesome already uses :before and :after. One possibility is to solve this with JavaScript on runtime. Try something like this: function AppendMenuFontAwesomeIcons() { var elements = document.querySelectorAll('ul[id^=zz][id$=_RootAspMenu] li span.menu-item-text'); for (var i = 0; i < elements....


6

Using developer tools in IE, use the 'select element' tool to pick out a link that should be styled, and look at the Trace Styles tool to have a look and see what CSS is being applied. Use this to see if your style is being overridden by the corev4.css. If it is, make your CSS selectors more specific. If you can't see your selectors at all, use the source ...


6

You could wrap the Quick Launch with the SPSecurityTrimmedControl and configure Permissions so that the Quick Launch is visible only to users with Edit Permissions.


6

Try the below CSS in Script Editor Web Part <style> .ms-core-listMenu-verticalBox > .ms-core-listMenu-root > LI > .ms-core-listMenu-item { font-weight:bold; } </style> [OutPut] By the way, the Content/Script Editor Web Part is not a solution to apply your CSS on all quick launch headers for all pages. It will be applied only on the ...


5

I figure your problem is that you have not specified URL for MainMenu. As you notice all links in QuickLaunch has link associated with it. Specify a Url and it should work (I tested that locally).


5

If you can drop a Content Editor web part into the page you can add an anchor and some javascript into the web part that looks like this: <a href="javascript:history.length&gt;0?history.back(): window.location = &#39;http://yoursitehere.com&#39;;">Go back to previous page.</a> Just replace "yoursitehere.com" with your own site page ...


5

That JSOM API only accepts local references or full URI external references So one option is to create a distinct URI that is accepted: function addNavigation(title,url) { var clientContext = new SP.ClientContext(); var oQuickLaunchColl = clientContext.get_web().get_navigation().get_quickLaunch(); var oNavigation = new SP....


5

This is as per the design. By default, links in quick launch does not accept query string parameters. when applying the 'selected' style it matches only the url component without parameters. So all your links will be defaulted to "/Lists/Management/NewForm.aspx" when applying the style and last navigation item will be selected. As a workaround you can ...


4

By default, sharepoint uses AspMenu as control that renders top nav and quick lunch. Something interesting you can find using reflector in this control. Consider method OnMenuItemDataBound (some code omitted for clarity): if (bool.TryParse(dataItem["AllowScriptUrl"], out result) && result) { if (this.allowScriptUrlItems == null) { ...


4

You can accomplish this easily using SPServices and CSS. Add the script for including the Jquery file in your master page and include the following code to get the group name of the person logged in. <script type="text/javascript" src="/Jquery/jquery-1.6.2.min.js"></script> <script type="text/javascript" src="/Jquery/jquery.SPServices-0.6.2....


4

Untested across the whole gamut of browsers, but if you're using the OOTB DOM, you have to do much more than just set the quick launch height. The #s4-leftpanel-content div contains the content and background color of the quick launch, so this has to be given a height of 100% (which sizes it to the height of the #s4-leftpanel div. #s4-leftpanel needs to be ...


4

In the SPNavigationNode make the isExternal variable as true . Check this article Link


4

The answer is quite simple. Open the Master Page (Normally V4) Find the following control : <SharePoint:ClusteredSPLinkButton id="idNavLinkViewAllV4" runat="server" PermissionsString="ViewFormPages" NavigateUrl=...


4

You can create a custom css style and reference it through master page. For styling quick launch you can use following styles .ms-core-listMenu-verticalBox UL.root > LI > .menu-item { /*Style each menu item*/ } .ms-core-listMenu-verticalBox > ul.root > li.static > ul.static > li.static > a:hover { /*Style on hove sub items*/ } ...


3

The accepted answer is an answer yes but this is really not a recommended way! The best way would be to place the CSS from the other answer in you master page! <style type="text/css"> .s4-recentchanges { display:none; } </style> This protects you from the setting beeing removed trough updates etc.


3

The answer to this lies in the blog site definition. Open this file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\Blog\Xml\onet.xml This file is what deploys all the lists and each of their associated views or pages. If you scroll down to the Modules section, you'll see all the web parts being added to ...


3

I'd do this with CSS or script. In my experience, this is the type of critical requirement that is usually reversed, as users find the groupings useful once they aren't there any more. In other words, do it the "cheapest" way, then maybe instantiate it more "expensively" later if need be. The CSS or script route is totally acceptable technically, as long as ...


3

If this is something you need to fit into a feature, you can use the following code within a feature receiver. using (SPWeb web = properties.Feature.Parent as SPWeb) { SPNavigationNodeCollection nodeCol = web.Navigation.QuickLaunch; foreach (SPNavigationNode node in nodeCol) { if ((node....


3

Another option is to use Chris O'Brien Config Store (in CodePlex). Essentially it is a SharePoint list that contains your variables and values that can be accessed programatically. It also deals with caching so it doesn't have to retrieve the value every time. There's some installation and configuration hassles to be aware of (like modifying web.config ) but ...


3

To offer an alternative, just use a Links list and put the Links web part on your page. You can remove the Category and Archive web parts if you want, and just have your custom links showing in the left-hand column.


3

What you could probably do is open the blog page in sp designer and then remove the whole div element named something like PlaceHolderLeft. (I don't have access to Sharepoint right now) When this element is on the page, the page will use the LeftNavBar and thereby quicklaunch from the masterpage. Otherwise the element on your page will overwrite the on in ...


3

Go to Site Settings . Under Web Designer Galleries click master pages and page layouts. Look for your master pages version history. Then reload to the which version you want.


3

Lists When you create a List it has an option whether to show that list in Quick Launch or not, you can uncheck the checkbox, as shown below: If you are making the list via code, you have SPList.OnQuickLaunch property, which you can set to false! Subsites You can activate Publishing feature for your Site and once your Web is Publishing.. In Site Settings ...


3

I did it with the following code, Add-PSSnapin Microsoft.Sharepoint.Powershell $FindString = “something” Get-SPSite http:/sitecollectionurl/ | get-spweb -limit all | foreach-object{ $web = $_ $_.Navigation.QuickLaunch | ForEach-Object { $_.Children | ForEach-Object { if($_.title -eq $FindString){ $node = $_ ...


3

Some things to check: Ensure Managed Metadata Service / Connections are functioning without problems If recent changes were made to terms, these changes may impact your navigation. Consider rolling back changes temporarily so you can access your site's Navigation Settings. Ensure that sites/lists/pages etc. referenced by your site's navigation were not ...


3

In reality what happens if you create for instance a list named Tasks, is that two extra navigation items are added to quick launch navigation: a header labeled Lists, and a child of it named Tasks. To answer your points Is it possible to set default No using OOTB? If you're in control of the list template used for the list (so it's a custom ...


3

That is possible but you will have to use a trim control and custom script in the master page to append the recycle bin to the menu. Something like this will do the trick <SharePoint:SPSecurityTrimmedControl PermissionsString="ManageWeb" runat="server"> <script type="text/javascript"> document.getElementsByClassName('root ms-core-...


Only top voted, non community-wiki answers of a minimum length are eligible