Hot answers tagged quick-launch
14
Here is a post that shows how to do this. Link The following jQuery can be placed in a content editor webpart or on the masterpage, which is how I implemented it.
function makeHeaderCollapsible() {
$("div.menu-vertical>ul.root>li.static>ul.static").css("display", "none");
$("div.menu-vertical>ul.root>li.static>span.static").toggle
(
...
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 ...
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 ...
5
You certainly can; Rich's approach will work (and is probably the way I'd do it), you also have the option of porting the quick launch into an accordion control (there's a few plugins out there, or you can utilize jQuery UI). The nice thing about Rich's method is that it doesn't require re-rendering the quick launch--it's simply hiding or showing the ...
5
I think here is the answer to your question:
Security Trim "View All Site Content"
It involves wrapping the View All Site Content link in a SecurityTrimmedControl (out of the box control) in the master page and setting the PermissionsString property with the appropriate value.
4
You can modify the navigation on this page:
http://<server>/_layouts/AreaNavigationSettings.aspx
In WSS3.0 this is under Site Actions > Site Settings > (Look and Feel) Quick Launch
Then, you can delete the link.
4
I accomplished this by using the steps outlined here.
Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\DocumentTemplates\
Open wkpstd.aspx in a text editor.
Find <SharePoint:RecentChangesMenu runat="server" id="RecentChanges"/> and replace with <SharePoint:RecentChangesMenu runat="server" ...
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 ...
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 ...
3
Do you use Publishing features? Normally you can changer order in Quick Launch settins from Site settings, Look and Feel column. You can find step by step guide here http://support.sherweb.com/Faqs/Show/how-to-change-the-order-of-the-items-in-the-quick-launch-of-sharepoint-sharepoint-2007 for example.
3
There's an extra class added to 'selected' menu nodes in the quick launch. That's used to style the current selected node in there. Use FireBug or Internet Explorer Dev Tools to locate it.
The /_layouts folder is in SharePoint Root on the server file system, so you will need a feature to deploy files to that location.
If you want only to change this for a ...
3
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)
{
...
2
Bob - This is not so much an answer as a point in the right direction. I don't have the menus enabled so cannot tell you exactly what tags to look for. What you need to do is use the IE Developers Toolbar or a similar tool to identify the style associated with the background color on the menu. Then using jQuery, you can write a few lines of javascript to ...
2
Yea, you are on the right path but unfortunately the ootb pages for generating the quicklaunch or top nav structures only allow 1 or 2 levels of depth. I had to write my own application pages that allow me to have unlimited levels of depth.
In addition, the default SPNavigationProvider doesn't seem to allow navigation items that don't have a url or if ...
2
If publishing feature is enabled or you created site using publishing template, http://office.microsoft.com/en-us/sharepoint-server-help/customize-navigation-links-on-the-quick-launch-HA010255192.aspx#BM10
If not, you have to use code to sort it...Example here
...
2
Here is the script is working fine for me I found it from below link and did some modification. http://social.technet.microsoft.com/Forums/en-US/sharepoint2010customization/thread/02f1d451-aaca-4708-8171-fc6e4d24d7d6
$(document).ready(function() {
// do stuff when DOM is ready
$("#s4-leftpanel-content ...
2
You already answered half of your question. You cannot customize Quick Launch by changing SPNavigationNodeCollection on server side because your changes are then applied globally.
So you are left with one reasonable option - to do it on client side with some javascript. I would suggest that you use jQuery for the sake of simplicity. To hide Libraries ...
2
You dont have to use code behind if you could use SPServices Jquery from CodePlex.
Do the necessary steps:
Download the jquery.SPServices-0.6.2.js from SPServices Jquery.
Upload the minnified js file - 'jquery.SPServices-0.6.2.min.js' to the style library of your site.
Add the script link <script type="text/javascript" src="Path of the JS file"> ...
2
Use codebehind in the master page to check if the current user is a member of the group (or not), then use the Visible property on the Quick Launch web control to hide it.
Control:
<Sharepoint:SPNavigationManager
id="QuickLaunchNavigationManager"
runat="server" ...
Code behind (eg on Page_Load)
...
2
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 ...
2
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" ...
2
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 ...
2
You can use the following in your master page to only show the default quicklaunch to Contributors (Users who can add list items)
<SharePoint:UIVersionedContent UIVersion="4" runat="server">
<ContentTemplate>
<Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="AddListItems">
<SharePoint:AspMenu
...
2
Instead of using $(document).ready() try using the SP function for this:
_spBodyOnLoadFunctionNames.push("FunctionName");
See: http://www.stephanrocks.com/2011/10/05/_spbodyonloadfunctionnames-in-sharepoint-vs-jquerys-document-ready/
Also see: Risk of conflict between jQuery document ready and _spBodyOnLoadFunctionNames?
2
If you have jQuery, why not go full jQuery? :)
Try this code:
jQuery(document).ready(function () {
if(window.location.href.indexOf("_layouts") != -1) {
jQuery("#v5-page-column-sidebar").hide();
jQuery("#v5-page-column-main").css({"width","100%"});
}
});
1
QuickLaunch items could be linked only to separate lists and pages, not to their groups. Heading items, which reference your Discussions "groups", are not more than simple links with some custom anchor text. So don't expect any intelligent behavour from them.
OOTB viewlsts.aspx page presents some functionality for filtering by type of list and by list ...
1
Here is article with everything about quick launch menu and items inside: http://www.endusersharepoint.com/EUSP2010/2010/06/04/navigating-sharepoint-2010-part-2-the-quick-launch/ (...maybe with more information then you need). Do you have enabled Publishing features on your site?
1
Link in your question is refering MOSS 2007. It can be ported Sharepoint 2010, check link below:
https://www.nothingbutsharepoint.com/sites/eusp/Pages/Accordion-Style-Quick-Launch-in-SharePoint-2010.aspx
1
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 ...
1
As I understand your question, all these functions could be implemented with no problems.
Though, I recommend you to use not a webpart, but a user control, and attach it to your pages using Delegate Control approach.
Inside your control, you can check Request.RawUrl or enumerate webparts on the page using SPLimitedWebPartManager, or whatever.. - to ...
Only top voted, non community-wiki answers of a minimum length are eligible
