4

When using Metadata Navigation with Variations enabled, the default is the following (assuming languages EN-US and DE-DE):

Also the default for a publishing portal is to use the metadata navigation. SharePoint creates one term set per site (i.e. one navigation term set for the site collection, one for each new variation site).

So, right now I have three term sets:

  • Site Navigation
  • Variation Navigation
  • Variation Navigation (EN-US)

By default the variation sites do not inherit the navigation from the site collection. That means if I create a new page within the source variation (de-de) and assign it a navigation metadata term, that term is automatically copied to the other's variation term set (so the term is copied from "Variation Navigation" to "Variation Navigation (EN-US)").


Here comes my question: By doing so the "friendly URLs" are like so for the same page:

What I would like is to strip out the language part (de/en) and I would like the URL to be the following:

With the automatically generated term sets (per variation site) this doesn't seem possible, or is it? Would I have to inherit the navigation for all variation sites from the site collection and create the terms there manually - I mean I would lose all the "automatic copying of source variation to destination variation term set" functionality?

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/library/microsoft.sharepoint.taxonomy.taxonomysession(v=office.14).aspx

Sample custom site map provider: http://msdn.microsoft.com/en-us/library/cc789625(v=office.14).aspx

  • So OOTB I will be stuck with the language identifiers in the URLs? Could I not simply choose the site collections' navigation term set as the navigation term set for all variations? When I tried using the site collections term set I could only have one URL per term (multiple languages, but one URL). – Dennis G Nov 6 '13 at 17:03
  • 1
    That is correct. What you are experiencing is the designed behavior (adding the identifier in the URLs, etc.). Anything outside of this behavior you would need to accomplish using custom code. – John Chapman Nov 6 '13 at 17:58
  • Understood. Perfect answer then! One more limitation of the metadata navigation, I just hate that it only works with publishing pages and not with team sites. – Dennis G Nov 6 '13 at 18:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.