I'm new here. I'm working on a SharePoint website and I want to create a different navigation bar for a part of pages while others use the global navigation bar. It is like they are different websites but actually they are not. I wonder is that possible? If it is, how can I make it?
In addition, according to my research, it's possible to have a different navigation bar if I create a subsite, right?
The problem now is that I don't have the permission to create a subsite, that's why I'm asking if I can create a different navigation bar for a set of pages.
Thank you!
For a SharePoint site, there are two sets of navigation.
One: Global Navigation. Two: Site Navigation (Which is mostly the sites Left side navigation)
These articles describes more about having multiple navigation elements in a site: https://technet.microsoft.com/en-us/library/ee695757.aspx
https://support.office.com/en-us/article/customize-the-navigation-on-your-sharepoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca
Note: Instructions vary based on your SharePoint environment and setup. For better understanding if you can share which version of SharePoint you are working on. can give more insights. Hope this helps!
Related
I have a portal in Liferay 6.2, and need to design the velocity template of a web content that must have a menu listing the pages (linked names) of the site where is present.
My questions are:
Is this possible?
What would be the correct way to do this?
Would it be better to make a portlet instead of a web content for this purpose?
Thanks for the help.
It feels a bit like you are trying to solve many problems in a single template - consider to compose the UI from many different elements (e.g. custom portlets) rather than building the one structure/template that fits all requirements.
That being said, as there's also the chance that your template doesn't do more than just displaying the current navigation: You have two options: The out-of-the-box Navigation portlet is quite configurable, you might be able to utilize that one instead of implementing anything yourself (check the configuration options).
And lastly, if you want to implement for yourself: Get hold of the themeDisplay object. With getLayout() you'll get the current page, while getLayouts() you'll get all pages of the current site and can enumerate them. However, there's one problem: You typically don't have access to the themeDisplay object from a CMS template. But there are several ways to still get to the data (search the Liferay forums for cms template themedisplay). Also, an Application Display Template will be a lot more powerful - and you can also check how the layouts collection is built - just search for usage of ThemeDisplay.setLayouts in Liferay's source code. But with ADT we're diverting from your original question.
Liferay offers a sitemap portlet out-of-the-box which lists pages of a site. You can configure it and define your own application display template (ADT).
I was wondering if someone has had a similar requirement before. What they want is a link that on the main site that would point to a different document contained within a document library every week. So week one it would be "document1.pdf" and week two it would be "document2.pdf" and so on. Is this possible for the navigation that is contained in the left hand side of a sharepoint site? Can a link be tied to a lookup? Any help would be appreciated!
You can create some redirect javascript within the Content Editor webpart. host it on a page and add a link to the page on the navigation.
This is by far the fastest way to get what you want.
Make sure to follow the advice here to be able to edit the page once you set the redirect.
How do I configure the Site Hierarchy on the left hand side of a SharePoint Services 3.0 site to NOT show folders?
We have thousands of folders and it takes ages to load the page!
Thanks
Go to Site Actions, Site Settings, Modify All.
In 'Look and Feel' click on 'Tree View'.
In 'Tree View' uncheck Enable Tree View.
I'm going to assume you mean the Quick Launch bar. If not then just leave me a comment so I can update the answer.
In a nutshell you want to configure navigation from the site settings page. You an quickly go in and tell it to NOT display any child sites. For detail instructions checkout this page.
One way would be to use the SPWeb.Navigation class to remove all the undesired items from the quick launch bar. For more information check these classes:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.navigation.spnavigation.aspx
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.navigation.spnavigation_members.aspx
Good luck.
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
I have a feature that deploys a few site columns, a content type (inheriting from Page Publishing Content Type) and a page layout based on my content type.
Everything is fine on two tests, performed on different servers, but on the third server, although the feature is being activated correctly and I can see the site columns, content types and the page layout in the galleries, I cannot create a new page based on my page layout because the page layout does not appear in the list of available page layouts.
On all tests I have used the administrator account.
Does anybody have any thoughts on possible reasons for this?
Thanks.
Did you have a look at the "Page layouts and site templates" page under Site Settings? On this page you can enable an option that limits the available page layouts to a specified list of page layouts.
I have worked on a project where we needed to limit the page layouts available on a custom site definition. We implemented this in a feature, that enabled the "limited page layouts" option and populated the list of available page layouts upon activation.
If this is the issue you are having you could simply turn off this option in the web interface or add the new page layouts manually, but you could also consider implementing a feature receiver that automatically adds your custom page layouts to the list of available layouts.
Thank you all for your answers.
What actually happened is that the page layout was, for some reason, deployed as a Master page and not as a Page Layout. The admin has manually changed this and now it works.
This is just an educated guess but check to see if the Page Layout is waiting to be checked-in or approved.
In my case the path for the layout was wrong so the layout itself ended up in a different location, when I corrected that i was able to see the results.
I had added files manually and it did not appear.
When I edited properties of that layout page from UI and saved it, it appeared.