Category Archives: SharePoint 2013

Hide Current Navigation Panel in SharePoint 2013

Create your own css file and add to the site collection’s Style Library.

The css should contain:

<style>

.ms-core-navigation { DISPLAY: none }

#contentBox { margin-left: 0px }

</style>

Now goto the site collection’s Site Settings page. Click on the ‘Master page’ link under ‘Look and Feel’, expand the Alternate CSS URL section and select the css file.

The Focus on Content button (top right) also exhibits similar behaviour – see http://www.learningsharepoint.com/2012/12/03/hide-quick-launchleft-nav-using-focus-on-content-in-sharepoint-2013/

Re-instating the Navigate Up function on SharePoint 2013

For some reason SharePoint 2013 doesn’t include the Navigate Up function previously available to SharePoint 2010. This function is important when navigating up a site hierarchy. To get it back you must open SharePoint Designer 2013.

1. Click on Master Pages and create a copy of the seattle.master (the new default master page).

2. Right click on the seattle_copy(1).master and select Open. Search for:

class=”ms-breadcrumb-dropdownBox” – it should be on line 369.

3. Delete the style=”display:none;” at the end of the line.

4.Delete the Visible=”false” a couple of lines underneath.

5. Save the seattle_copy(1).master.

6. On the Master Pages list, right-click on the seattle_copy(1).master and select Set as Default Master Page.

7. Check that the seattle_copy(1).master is applied to the site collection as the default Site Master Page by clicking on Master Page (under Look and Feel) in Site Settings.

8. Refresh the sub-site to see the Navigate Up icon to the left of the global navigation menus.

.

Importing Profile Pictures from Active Directory to SharePoint 2010 or 2013

This link explains how to add profile pictures to Active Directory using PowerShell, and how you can import these pictures into user profiles in SharePoint 2010 or 2013:

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=253

You can get sample contoso user accounts and images from the Codeplex site here: http://sharepointdemobuilds.codeplex.com/releases/view/101674

Can’t sign in as a different user in SharePoint 2013

This Microsoft Knowledgebase article explains how you can sign in to Internet Explorer as a different user to get round this omission: http://support.microsoft.com/kb/2752600

Extract here:

1. Start Internet Explorer by using the Run as different user option, and then go to the SharePoint site.

Note: The Run as different user option is visible if you hold the Shift key when you right-click a program icon.

2. Access the SharePoint site by using the URL as http://siteurl/_layouts/closeConnection.aspx?loginasanotheruser=true

Important:

This option uses an unsupported browser feature which is unreliable and causes other issues. Currently this option does not work in IE 10 and Safari.

Why does /_layouts/15/start.aspx appear as part of my SharePoint 2013 Site URL?

The URL path of a newly created site collection will include “/_layouts/15/start.aspx” To avoid this it is necessary to deactivate the following site feature:

1. Go to Site Settings – Site Features page.

2. Deactivate the “Minimal Download Strategy” feature.

Why is the Minimal Download Strategy available by default on various site collection templates including the Team Site? This is a new feature for SharePoint 2013 that is designed to increase the performance of the SharePoint site.

The start.aspx page has a specific JavaScript object asyncDeltaManager (defined in start.js). This parses the URL, looks for the # sign and takes the path following that and dynamically loads that page.

Subsequent requests to pages are dynamically loaded through the asyncDeltaManager object. Once a link is clicked it will invoke a method in the JavaScript object which creates the MDS URL and appends the query string parameter AjaxDelta=1. A request is created and downloaded asynchronously and only the “delta” is returned to the client and assembled and rendered using JavaScript.

For a full explanation please read Wictor Wilen’s Blog post here: http://www.wictorwilen.se/sharepoint-2013—introduction-to-the-minimal-download-strategy-mds

Common PowerShell commands

Here are some commonly used PowerShell commands:

1. Add-SPSolution “<file location\Name.wsp>”

e.g. Add-SPSolution “c:\customsolution.wsp”

2. Install-SPSolution -Identity <Name.wsp> -WebApplication http://name -GACDeployment

e.g. Install-SPSolution -Identity customsolution.wsp -WebApplication http://sp10/sites/finance -GACDeployment

3. Uninstall-SPSolution -Identity <Name.wsp> -WebApplication http://name

e.g. Uninstall-SPSolution -Identity customsolution.wsp -WebApplication http://sp13/sites/hr

4. Remove-SPSolution -Identity <Name.wsp>

e.g. Remove-SPSolution -Identity customsolution.wsp

How to change a site collection’s URL

1. Backup the site collection using PowerShell or the menu option available in Central Admin.

2. To restore, use PowerShell. Here is an example:

Restore-SPSite -Identity http://thehub.harrogate.local/bussupport/procurement -Path c:\backup\SharePoint\[BackupFileName.bak] -DatabaseServer [DatabaseServerName] -DatabaseName [ContentDatabaseName] -Force

How to create a new site collection assigned to a new content database

$db=New-spcontentdatabase –name “Marketing_ContentDB01” –webapplication http://sp10; new-spsite –url http://sp10/sites/marketing -name “Marketing Site” –description “Welcome to the Marketing Site” –owneralias “contoso\driscollm” –contentdatabase $db –template “STS#0”

SharePoint 2013 – “Sorry, this site hasn’t been shared with you.”

“Sorry, this site hasn’t been shared with you.” This seems to be a common message SharePoint 2013 users are seeing if things aren’t configured correctly. There may be a variety of reasons why you are seeing this message. In my case it was happening when I tried to go to particular site admin (_layouts) pages and seemed to be caused by the site collection not being correctly provisioned. To overcome the problem it was necessary to do the following:

1. Go to Central Admin. Click on the “Application Management” heading.

2. Click on “Manage services on server”.

3. Stop the service “Microsoft SharePoint Foundation Web Application”. This will take a little while to stop.

4. Start the above service again.

 

This should resolve the problem.