On the hub site top navigation, I cannot find a way to add a menu item without a link.
On all of the other SharePoint online menu editors, you can leave the URL blank and it will make the new item a label without a hyperlink. However, in the hub sites top navigation, if you leave the URL blank, the "OK" button is disabled. If you add "#" in the URL, it links to the site home page. This is a problem because users automatically click on a menu item when they want to see the children, resulting in a page reload.
More details here: https://techcommunity.microsoft.com/t5/SharePoint/Hub-site-navigation-top-level-requires-URL/m-p/226427#M20428
Has anyone been able to successfully add a menu to their hub site with top level navigation items not linking to anywhere?
Yes, that is not supported OOTB. A valid URL seems like a must.
To get around this issue, you can make use of SPFx extensions based on links in term store.
After that, you can delete all the links in your hub site and then deploy this extension to sites associated to your hub. This will provide you will a consistent top navigation across site collections.
GitHub Link - Tenant Global NavBar Application Customizer
Use PS script from - Apply SPFx extensions to SharePoint Hub Sites using PnP PowerShell
When you deploy this extension, if the term has no link it acts like a label.
If the term has child links, it will open a dropdown showing those child links which can then be clicked.
Seems like an overkill but there seems to be no other option.
You can always guide and train your end users or content owners to hover the links and the dropdown for child links besides it before clicking, but it will require a mentality change on their part !
Related
I am trying to integrate the SharePoint extension in Teams and can't find a solution, to add a Label, Button or other type of Link to the NavBar.
The list i used was a generated with a template.
I tried to connect the different types of lists, with a homepage which is automatically generated in SharePoint.
After i redesigned the homepage, added the different links in a hero and connected the SharePoint site to Teams, i saw that that after clicking the link which led me to the list i could not go back to the homepage anymore.
The only way to access the homepage again was via dropdown on IT-Tickets and reload tab or closing it entirely.
The question is, how can i add an Element, after Open in SharePoint which links me back to the homepage ?
You cannot add a link to SharePoint list command bar using SharePoint out of the box capabilities.
You have to develop a SPFx ListView Command Set extension to add a link or button to SharePoint list command bar:
Documentation: Build your first ListView Command Set extension
I have just edited my publishing site home page in SharePoint Designer. The page originally contains some web parts.
I am a newbie as far as SharePoint branding is concerned. I did the editing in Advance Mode when I realized that I couldn't edit areas outside my Web Part Zones and since I need to do that, I tried it using the advance mode. I edited the page adding some inline CSS styling and even added some additional Web Part Zones. Everything looked good when I previewed so I saved and thought all was okay. But to my surprise, Only my account (System Account) can see the changes I made. Every other user on the domain are still see the original page without any of my recent changes.
I have done the Check-In and Publish circle over and over again but no luck.
Does any one have any idea as to what I might have done wrong here and what I can do to fix the issue.
Follow below steps for publishing:
Select “Publish a major version,”. When
prompted to approve the master page, click Yes. This automatically
invokes a SharePoint master page approval page, where you
will find your new master page listed at the top of the page.
Click the drop-down menu beside the master page. Select
Approve and select the Approved radio button. Click OK. Your
master page is now saved and approved in SharePoint.
Navigate to your top-level site collection, and click Site Actions -> Site Settings
Under Look and Feel, select the Master Pages link. For both the
Site and System Master Page settings, select your new master
page from the drop-down menu.
Once you click OK, your changes should be available to all users
I'd like to ask if you came up with a solution that will allow for subsites to access a centralized document library at the parent level. I'm still trying to no avail. I've tried doc library templates, views, Doc Center and the best method i have OOTB is a page view web part on the subsites page display a view from the parents library. (by the way to remove the ribbon, append ?IsDlg=1 to the url and the ribbons hidden) cool tip. Say will you give be a Y/N on a solution that will allow one to keep a set of documents in the doc center and surface them in the sub-site.
There are another option without such hard coding. You can open any view of your document library, as mentioned earlier AllItems.aspx for example with SharePoint Designer. Open it for editing in advanced mode (there are option when you click right mouse button on file in SP Designer). Then just point mouse cursor inside web part and chose in ribbon web parts, Add to Site gallery, see the picture. Fill in name of new web part. That is all, now you can add this web part on any page on any web site from webpart gallery through the user interface or through the SP Designer by clicking Insert, Web Part in the ribbon on any page.
You can do this by editing the AllItems.aspx (or other view page) and scraping off the WebPartPages:ListViewWebPart and pasting it into a page on the subsite.
This will give you an error "List does not exits The page you selected contains a list that does not exist."
Then you need to get the WebID for the root site (where you took the ListViewWebpart from and replace the part of the webpart that looks like this:
<WebId xmlns="http://schemas.microsoft.com/WebPart/v2/ListView">00000000-0000-0000-0000-000000000000</WebId>
with (for example)
<WebId xmlns="http://schemas.microsoft.com/WebPart/v2/ListView">7b04dee8-b120-4dee-abea-28b77316ec7d</WebId>
My site structure looks like this:
- top-level site
--sub-site
---page
---page
--sub-site
---page
I want to disable the link on the tab of each sub-site that currently links to default.aspx so that it acts as a heading to the pages only and not a url that can be clicked. When users navigate over the sub-site tab, the pages drop down menu displays.
Would I need to code this?
Coding it would make it easier as it would give you more control over the html. It is not a massive job to create a custom navigation provider and include it in your masterpage/page layouts.
This is a reasonable introduction to your options.
I personally have found the code released here by the SharePoint team to have been very useful.
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