8

When you create you're the second site collection in your fresh Web Application, it typically comes with additional sites in the URL. It doesn't affect the user unless she wants to type the URL directly. The reason for this as that we use a managed path of wildcard inclusion. With wildcard inclusion, you are able to have as many site collections you want (...


7

Figured it out, might be a Microsoft issue. For some reason, when you set a Navigation Term to "Simple Link or Header" and spell out the URL yourself, the navigation item is viewable to everyone. If you set the navigation term to "Term-Driven Page with Friendy URL" some sort of trimming happens, and only people with write access as well can view the Term. ...


7

Yes you can do that. Thank you to ASP.NET 4 and Managed Navigation this is very easy to do on SharePoint 2013. Please refer to these links: http://technet.microsoft.com/en-us/library/dn194310.aspx http://technet.microsoft.com/en-us/library/dn194311.aspx Note: The cross-site publishing feature is available only in SharePoint Server 2013 Enterprise. If ...


5

It could be achieved by creating a separate Term Set for Variation Navigation and configuring Navigation settings for a Variation sub site How to configure Managed Navigation for a a Variation sub site Assume we have Variation sub site named News for which we need to specify custom Global Navigation (Managed Navigation). Steps: Go to Term Store ...


5

The logic is contained in VariationRoot.aspx which by default redirects users according to language and cookie settings by means of a custom control in the page layout (VariationRootPageLayout.aspx). You have a number of options for customising this logic if required, including replacing the custom control or adding some client-side logic using JavaScript, ...


5

You could use _spFriendlyUrlPageContextInfo.termId to get the Term information(GUID) for the current page.


4

If you have a page, "page1.aspx" in the pages library, it can be accessed via: http://site/pages/page1.aspx. But, perhaps you would rather be able to access it via: http://site/page1 The above would require some sort of routing table. This routing table could have been implemented in a variety of ways, but they happened to decide to use a term set for ...


4

Structural navigation is tightly coupled with the content and therefore it is hard to create friendly URLs. However, managed metadata navigation addresses this issue by providing central way to manage navigation, irrespective of location of content, which makes it easy to create friendly URLs. The only con, navigation will be managed by term store. You can ...


3

Have you tried to use managed metadata. 1. create a new Global Term Group called Global Navigation. 2. Createjavascript and placed inside Style library folder Function.registerNamespace('Mavention.GlobalNavigation');   Mavention.GlobalNavigation.MenuItem = function(title, url) {     this.title = title;     this.url = url; };   Mavention.GlobalNavigation....


3

Solved the performance issue with the help of Robert as well as came up with an optimised solution by using getTerms() to search the entire Term Store for required Term: // Get SP Context var context = SP.ClientContext.get_current(); // Get the default Term Store for context var session = SP.Taxonomy.TaxonomySession.getTaxonomySession(context); var ...


3

Ensure you run this call GetWebRelativeFriendlyUrl such as below: var friendlyUrl = term.GetWebRelativeFriendlyUrl(); Before your call to: clientContext.ExecuteQuery(); Then use the friendlyUrl in your output: Console.WriteLine(" --- " + childTerm.TaxonomyName + " - " + friendlyUrl); Small side note: The method GetWebRelativeFriendlyUrl returns a type ...


3

Alright, so after peering into the inner workings of the code behind for those settings pages, I've found that you can detect the source of the publishing site's navigation by using the WebNavigationSettings class and reading its GlobalNavigation.Source property (a StandardNavigationSource enum) like such: if (PublishingWeb.IsPublishingWeb(web)) { ...


3

I think the friendly URL is stored in the catalog, not the page itself. You'd probably be better off using a Content Search Web Part (in most cases). It's the "new" way to do DVWP-like stuff, but it's also different tech than you are used to. You can build your own Display Template that sits underneath the CSWP to display the data.


3

Managed Metadata term set not support use Target Audience. At the term set level, you have owner and stakeholders but these are 'administrative' roles or care takers, not security. you can not set group in term set for target audience.Please check this link for more detail.


3

If you want to do it out of the box, you can do an update to the TopNavigationMenu control and set the MaximumDynamicDisplayLevels to 3 from 1(default). The disadvantage is you can have only maximum 3 nested levels. Static Display Levels In case you want to have N levels of navigation menu and want to create it dynamically from a SharePoint List, I have ...


3

You can do this by creating managed paths, specifically an Explicit inclusion. You would first need to define this managed path using central administration, then create a site collection using this. This would give your site the url https://xyz.com/testpage, and the home page of that site would be accessible using that url directly. If you just want a ...


2

There isn't an "out-of-the-box" way to accomplish this. However, you could create your own custom Site Map Provider and in your code get the data from the Managed Metadata Service. Then you can modify the information however you need to. Here is some info to get you started: TaxonomySession (How you get the metadata): http://msdn.microsoft.com/en-us/...


2

I have used the "reuse terms" feature on a site I've done. I think that is the better way if you want the links to remain the same. The other option seems to be Pinning, which keeps the structure but apparently does not keep any of the links.


2

You can follow the below link to create managed metadata terms for navigation and link it with your wiki pages.https://www.nothingbutsharepoint.com/sites/eusp/Pages/SharePoint-2013-Navigation-using-Managed-Metadata-Term-Store.aspx Once done go to Site Settings, under Look and Feel click on Navigation. Select "Managed Navigation" for "Current Navigation" ...


2

I know its been so long but for someone in the future who has issues make sure you have below: If you use the Term-Driven Page with "Friendy" URL (MS's typo, not mine), there are a couple things that must also be in place for it to show on the navigation for Users with just visitors rights: In the Term Driven Pages tab of the Term Store Manager, you must ...


2

Unfortunately there is no direct way to do this. PowerShell should be used or you should us custom code. This article give you step by step instruction to export managed terms. This article give you step by step instruction to import managed terms.


2

The navigation options which you have set tries to pulls the items from managed metadata term sets. Change the Global and Current Navigation settings as below to display the pages as navigation items. The folders will not be displayed as navigation items. But you can still add the folders manually and move the pages accordingly under the same navigation ...


2

There is a button under the Page tab of the Ribbon labeled "Page URLs", which is where you go to specify which term(s) point(s) to a given page. In order to use this, you must first set up the following: Have a Managed Metadata service running in the farm Create a term set for Site Navigation in the MM Term Store Configure the Intended Use setting of the ...


2

I tried to edit the page layout and the master page in order to change the behavior of the menu but nothing helped. Then I found a blog post about an xml-file on the server that had the same settings. When I made changes to that file the menu worked as I wanted. It is probably not the best practice way because it involves editing a standard SharePoint file ...


2

To retrieve navigation behavior and properties for a SP.Taxonomy.Term object the SP.Publishing.Navigation.NavigationTerm object is intended, the following example demonstrates how to retrieve those properties by Term Id: var scriptbase = _spPageContextInfo.webAbsoluteUrl+"/_layouts/15"; $.getScript(scriptbase +"/sp.runtime.js",function(){ $....


2

Try this code: <script src="https://code.jquery.com/jquery-2.2.4.min.js"></script> <script> var $j = jQuery.noConflict(); $j(document).ready(function() { var select = $j("#ctl00_m_g_7bb989f2_7ca9_456f_b0be_ee0996c38db1_ctl00_ctl05_ctl03_ctl00_ctl00_ctl04_ctl00_Lookup") select.on("change", function() { if (select.find("...


2

You can alter the navigation items from the site settings page: {yoursite}/_layouts/15/settings.aspx You can access this section from the Settings cog too: On the site settings page you should have a Look and Feel section. Check for a Navigation option in this section: If you don't see this option, you may first need to enable the site publishing ...


2

As per MSDN official article metadata navigation will be available in both standard and enterprise but foundation doesn`t. Here is the article https://blogs.msdn.microsoft.com/sharepoint__cloud/2013/01/09/sharepoint-2013-onpremise-edition-comparison-chart/


2

I have tested in SharePoint RTM and SharePoint with July 2017 CU (15.0.4945.1000), but cannot reproduce your issue. Here are my test steps and results: Open an Enterprise wiki site and create a term set using “Create Term Set” option in the navigation settings page. Open Term Store Management Tool to check the term set. The “Available for Tagging” option ...


2

I would suggest looking at PnP PowerShell. This is a collection of commandlets that extend the capability of PowerShell. This article explains several capabilities PnP PowerShell provides for managing the Term Store: https://medium.com/rapidcircle/pnp-powershell-maintain-all-your-termset-data-across-tenants-86ee26623097


Only top voted, non community-wiki answers of a minimum length are eligible