I have a SharePoint Site called ProxymGroup which has multiple affiliates and departments.
I created the webApplication and added 2 managed Paths of type WildCard called Affiliates and Departments.
Under affiliates i needed to create 3 site collections and under departments 2 other SiteCollections. So, here i have the links for the siteCollections:
http://MyHostName/affiliates/SiteCol1 ... and http://MyHostName/departments/SiteCol1 ... etc.
My goal is to display all that hierarchy in theTopNavigationBar menu of the siteCollection because when i activated SharePoint server publishing feature and checked Show SubSites in navigation tab under site sittings it only showed me the subsites, not the siteCollections created under this site.
How can i do please to get that hierachy shown in my TopNavigationBar menu???
Thanks in advance
as far as I know there is no ootb way to show information in the navigation shared among site collections. each site has its own master page and can only display subsites, not other site collections.
alternatively, you can create a powershell script that sets the same navigational items for all the existing site collections, adding links for all the existing sites in all menus of all sites
...or just create subsites
Go to Site settings -> Look and Feel -> Navigation and you can add links manually and change the hierarchy as you want , Please check below image for same.
Related
we have created a new site and we want to move our team's wiki to the new site.
is there a nice and easy way to do it? we've tried the tree view with drag and drop but it won't work.
Thank you.
Ok so after a number of dead ends, I found a quick and easy solution:
Navigate to the physical folder location for your Sharepoint docs.
[Do this by selecting documents in the menu list, select the library tab and then open with explorer]
Once there navigate to the folder containing your wiki site/s.
They will have a .aspx extension usually
You can then move them to the folder you like.
Note: The site needs to be checked in or the move process will moan
One of the options could be to save a Wiki site as a site template. Then deploy it in a site collection and to create new sites from it. But unfortunately since Wiki site is Publishing based site, it is not supported to Save Site as Template.
But there is another option - moving sites via Site Content and Structure:
You can move individual list items or entire subsites to another
subsite within the site collection. A subsite can be moved to be
directly under the top level in the site collection hierarchy or under
another subsite in the site collection hierarchy. When you move a
subsite, all of the content in the subsite is moved
Steps:
Go to Site Settings, then Content and structure (under Site
Administration)
Select site you would like to move and Move action in the context menu
as shown below on picture
In the Move dialog select a destination (parent site) and
then click OK as shown below on picture
That's it.
you can try opening both sites/libraries in explorer view, side by side, and copy paste them from one to the other
you can also try to save a template out of the wiki including content and then import it
I have to create a team site with Sharepoint 2010 for a company that has several departments.
Requirements (simplified) are:
Top Menu: company / department-A / department-B
Main-page (default, home page):
company news
department-A tasks
department-B tasks
company quick launch menu (on the left)
Department-A-page
department-A news
department-A tasks
department-A quick launch menu (on the left)
Department-B-page
department-B news
department-B tasks
department-B quick launch menu (on the left)
So I have 2 lists of departments tasks to share between pages. I have to create personalized quick launch menu per each page (home, department-A, department-B) also.
How can I do this?
If I create several site pages (one page per department) and customize top level menu, then I can't customize quick launch menu per page. Because it seems to be the only one for the whole site.
If I create nested team sites (one site per department) I can't share task lists anymore?
What are the ways to customize quick launch menu per every page or share lists between sites?
Thank you in advance!
I recommend you to create sub-sites for each department and store department-specific data under them. It will help you in future (when sites will grow) to:
not have mess of lists in home site
create department site template (to create site for department "C" in few clicks)
sitemap and navigation controls will be automatically populated
easier to configure permissions (no need to set-up permissions for each departmental list)
The only disadvantage of this approach is that it will be more complex to show task from child site on the home site (do you really need it?). However this can be achieved by implemented custom webpart or using dataview webpart (xslt).
QuickLaunch can be customized from site settings or from code (for example via features).
Let me know if you have any other questions.
How can we restrict a site collection and its subsites to a particular site theme or set of themes?
If you have the Publishing enabled, you have a Master Page link in the Look and Feel section in Site Settings. You can force all subsites to inherit the masterpage from the top site, making the theme applied to that master page the one to show on all subsites, no matter what theme they have.
Also http://stsadm.blogspot.com/ has an extra option to stsadm that lets you apply a theme recursively.
I have a site collection with the following structure:
Sales Dept Site (site collection top-level site)
Sales Dept Sub-Site 1
Sales Dept Sub-Site 2
We now have a need to insert a new top-level site so that the new structure will look like the following:
Sales Public Site (site collection top-level site)
Sales Dept Site
Sales Dept Sub-Site 1
Sales Dept Sub-Site 2
So, I need to shove all the existing content down a level and insert a new content at the site collecteion top-level site.
What is the best approach to accomplish this? My thought is to create a new site collection with the top-level site created as I need it (Sales Public Site). I can then export the content of the Sales Dept Site and import it into the new site collection as a sub-site.
You can move entire sites via the 'Manage Content And Structure' from the 'Site Actions' menu on the top level site, so there is no need to export and import sites.
Follow this guide for getting access to the 'Manage Content And Structure' if it doesn't exist in the 'Site Actions' menu.
That approach should work. The easiest method is to export a site template, but that does have a fairly small size limit. For larger sites you may be able to get something working with the content deployment wizard.
Of course any customization of the site that assumes the current structure can't be guaranteed to continue to work. Is it an option to simply change the url and navigation to look like a part of the main site?
You approach is the right one. However if you are using MOSS you should use use Manage Content and structure feature instead of exporting sites. This feature allows you to move your sites and restructure your collection. Learn more...
If you created your site collection as pure collaboration site you will have to activate SharePoint standard Publishing features on the top level site to enable this option.
Please note: This feature is not available in WSS.
I am a beginner in SharePoint and I need to create publishing site that will have multilevel menu. Requirement is that levels will not be fixed and that client should be able to add pages and customize menu.
If I am not mistaken pages can be created only in the first level under the site. I don't see something like folders concept. For the navigation purposes I can add heading and it will be shown as another level. If I need more levels I need to create sub sites.
Site
Page1
Page2
Heading
Page3
Is this correct?
Site
Page1
Page2
Sublevel_1
Page1_1
Sublevel_2
Page2_1
Sublevel_3
Page3_1
...
Can I do something like this without creating SharePoint sub sites ?
If I don't need I will skip writing some custom menu control or write custom SiteMapProvider. I will than need to write UI for managing navigation also.
EDIT:
I have managed to create Folder in Pages list and create (actually move) pages to that folder and even create sub folder but they are not showing on the menu not even in the navigation settings page. I can't approve folder, it is in pending status what ever I try.
I looks like this is not possible by the Andrew Connell: Subfolders are not Supported in the Pages Library in MOSS Publishing Sites
Out of the box, you can modify the navigation for a Publishing site manually.
I assume that you are after a more automated way to do this. Unfortunately, the way to modify the navigation for a PublishingWeb is through the object model and the PublishingWeb.CurrentNavigationNodes object, which would require a timer job or some other method to update as pages are edited/added/deleted.
This is non-trivial and you will still need to create a solution/feature package.
The other way is to create a custom navigation provider.
The issue with both of these options (aside from the actual coding and release) is caching the navigation structure. We have used the standard web cache for the object holding the navigation structure, but using the standard user browsing (i.e. the menu code itself) to kick of a refresh of the navigation is fraught with threading issues.
You can create multiple document libraries in a site and then put the pages in the various libraries. That way you wouldn't need to create sub-sites