Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Placing Sites under Sites (not Webs under Sites)

  Asked By: Bryon    Date: Sep 23    Category: Sharepoint    Views: 1274

Does anyone know if it’s possible to place sites (root webs) under other sites (root webs)? I want to be able to control what web parts the user sees in the list and ideally I’d do that with the web part gallery. Unfortunately, I need to be able to control this all the way down the hierarchy. Has anyone seen an approach to doing this that works?

Trying to do it from STSADM indicates that I have to go to Managed Paths – but it’s already setup in managed paths.



3 Answers Found

Answer #1    Answered By: Gregg Wilkinson     Answered On: Sep 23

Given the definition of "root" as a top-level site, no, you cannot setup  a
"root" underneath a "root". The path you would need to define using managed
paths has already been used and cannot be re-used for another path.

A top-level site is a site collection and the web  part gallery  defined there
would be available to sub-sites.

I believe that you would have to control  multiple web part  galleries to get your
scenario to work. Maybe the programmer types can come up with a work-around.

Answer #2    Answered By: Darrel Sexton     Answered On: Sep 23

Interesting question.

While building our Farm-wide User Manager Application we had to explore all
of these possibilities. Although you can't directly create a managed  path
inside of a managed path you can make it appear as if that is exactly what
you have done.

For instance, let's say that you created a top-level site in the root  as

No problem, you could then create a top-level sites  in a managed path called
Path1 as follows:

You could also create top-level sites in other managed paths  as follows:

The first challenge is creating top-level sites in a nested managed path
called Path2 as follows:

The interface doesn't provide the ability to create a managed path within a
managed path nor can you create a top-level site as a child of a top-level
site. It appears as if we are stuck. So, I asked one of my kids how they
would do it. They suggested that I create a managed path that included the
slash in the name: "Path1/Path2"

While it is true that Path2 is not a true child of first, you would be hard
pressed to convince an information office worker. Perception is reality.

The second and bigger challenge is creating multiple, named top-level sites
directly in the root as follows:

You can easily create a child site here or a document library that contains
Web Part Pages and behaves like a web  Site, but I don't think that you can
create a named top-level site directly in the root. To quote James Edelen,
"I'd love to be wrong, but I don't think so."

Answer #3    Answered By: Tory Sellers     Answered On: Sep 23

I'm OK w/o creating top level sites, I just need the hierarchy.

I had considered the approach  you outline here unfortunately, I don't think
it will scale to the size I need. I'll have 10,000 sites  for the first
release. Given that this information is in the registry, I'm concerned that
10,000 entries might make it perform poorly.

I guess I'll have to figure out another way to control  what web  parts get
added by web. I wasn't looking forward to replacing the gallery  view for
the sub-sites...

Didn't find what you were looking for? Find more on Placing Sites under Sites (not Webs under Sites) Or get search suggestion and latest updates.