Multiple web parts with different site collections?

May 29, 2014 at 8:16 AM
I've used the LynxTree navigation before but it would only display the sites within the site collection of where the web part is being displayed on the page.

I need to have for example 4 of these on one page but each web part be displaying a different site collection due to our structure - is this possible?

The page is basically a directory for all sites and it takes the need away from users having to remember site URLs.

Will the webpart only show sites that a user has access to or would it display all sites in a collection?

Jun 2, 2014 at 4:31 PM
Yes, should be no problem.

The web part have a web part property that allows you to set the root web site URL.

You should be able to set it to any site collection.

So, with 4 web parts you should be able to show all 4 site collections.
Jun 5, 2014 at 11:20 AM
Hi Shai

This is working great thanks! Just one question - can the filter be changed to work via managed paths?

For example say I want to display 2 sites and sub-sites on a page but they are both in the same site collection but split out via a managed path. Sites is the managed path in my example below.

http://projectsites/sites/globalsales http://projectsites/sites/localsales When i enter http://projectsites/sites/ into the webpart it displays everything at the http://projectsites/ level rather than http://projectsites/sites/ and below. Our structure is a mess so I'm basically trying to move sites from http://projectsites/ into a better structure.

Jun 13, 2014 at 1:27 PM
Hi Matt,

http://projectsites/sites/ is a bucket for site collections, it is not a site collection.

Meaning, it is a managed path that you create site collections under.

So for example your site collections would be:
http://projectsites http://projectsites/sites/siteA http://projectsites/sites/siteB You will need to add a web part for each site collection I'm afraid. If you would like to add multiple site collections in one web part that is a change I will have to make in the web part to support that.

Hope it makes sense now. I know SharePoint's site, web, site collection terminology is very confusing at times,