Skip to main content

Minimize, Hide or remove the Quick Launch in Project Server 2010 or SharePoint

On a standard Project Server or SharePoint web page there is a quick launch in the left side of the screen. It is not always desirable to view this side bar to the user and sometimes you just want to hide it and let the user restore it when he needs it.

Remove Quick Launch
If you just want to remove the quick launch on a SharePoint web page you can add the following script in a content editor on the webpage (see how to add a content editor in the next section).

<style type="text/css">          
#s4-leftpanel
{
   display:none
}
.s4-ca
{
   margin-left:0px
}
</style>

But if you want to let the user be able to view it on command you can do it by adding Javascript to the content editor web part as described below.

Hide Quick Launch
This method only works for Project Server, SharePoint does not have the minimize button on the quick launch unfortunately.

If you go to the front page of Project Server you see that you can hide the quick launch by clicking the arrow button above it.



When the page is initially loaded the quick launch will be expanded. When you click the arrow then the following Javascript is executed: Shell_ExpandCollapseQuickLaunch
What we want to do is to execute the Javascript right after the page has been loaded.

Let’s start by adding a content editor web part to the front page so we have a place to add the code. Go to the front page of the PWA and click Site Settings in the top left corner and Edit Page.



Click Add web part and under Media and Content choose Content Editor. Click Add.

Click inside the web part to activate the ribbon. From the ribbon select HTML and Edit HTML Source.



In the text editor add the following code.

<style type="text/css"></style><script type="text/javascript">
    _spBodyOnLoadFunctionNames.push("Shell_ExpandCollapseQuickLaunch");
</script>

Click OK.

To hide the Content Editor web part select Edit Web Part and set the Title to a blank space and set the Chrome Type to None.

To exit the edit mode click on Page from the ribbon and Stop Editing.

When you go to the front page of the PWA now the Quick Launch will be hidden by default.










Comments

Popular posts from this blog

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Received this error today when trying to create a SharePoint solution against a newly created site.


My first problem was the site was configured to use a port which was already used by another web site. Therefore the site could not start at all.

In my case both Default Web Site and SharePoint - 2000 was both using port 2000. Changing the port of Default Web Site and I was able to start the site.

However now I still received the same error message. When browsing the site I realized I did not have access to the site.

Giving access to my user and I was able to deploy the solution.

To sum up this post:
 - Check the site can start
 - Check the site can be browsed
 - Check your user have access to the site

SharePoint 2013 : Cannot connect to the targeted site.

On my Contoso environment I was trying to create a sandboxed solution. I have already configured my app domain and app management services. But when I tried to validate the site I got the following error message.
Error

Cannot connect to the targeted site. This error can occur if the specified site is not hosted on the local system. SharePoint solutions work only with locally-installed versions of SharePoint Foundation or SharePoint Server. Remote development is supported only for apps for SharePoint 2013.
If you search around the internet you will find many people suggesting to change your host file from 127.0.0.1 to the actual IP.

Solution However the solution, at least on a Contoso environment, is to type in the actual IP address in the host file.
(the IP 192.168.150.1 is the special IP for Contoso, I have 2 network adapters)
And do not forget to clear/flush the DNS cache. Now the solution can be created and validates.


PowerShell results size unlimited/truncated - $FormatEnumerationLimit/Width

Ever experienced the problem where you run a Powershell command and you cannot see the whole result because the result is truncated.

Problem: If you for example run the Test-SPsite command you might see something like the following:


Site : SPSite Url=http://atlas/pwa Results : { SPSiteHealthResult Status=Passed RuleName="Conflicting Content Types" RuleId=befe203b-a8c0-48c2-b5f0-27c10f9e1622, SPSiteHealthResult Status=FailedWarning RuleName="Customized Files" RuleId=cd839b0d-9707-4950-8fac-f306cb920f6c, SPSiteHealthResult Status=Passed RuleName="Missing Galleries" RuleId=ee967197-ccbe-4c00-88e4-e6fab81145e1, SPSiteHealthResult Status=Passed RuleName="Missing Parent Content Types" RuleId=a9a6769f-7289-4b9f-ae7f-5db4b997d284, SPSiteHealthResult Status=FailedError RuleName="Missing Site Templates" RuleId=5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd, …