SOLVED

Hub Site Navigation Address Field Behaviour Multilingual

%3CLINGO-SUB%20id%3D%22lingo-sub-1445607%22%20slang%3D%22en-US%22%3EHub%20Site%20Navigation%20Address%20Field%20Behaviour%20Multilingual%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1445607%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20SharePoint%20hub%20site%20which%20requires%20translation%20of%20its%20navigation%20links%20display%20names%20and%20address%20fields%20-%20default%20is%20English%20and%20users%20with%20Spanish%20language%20settings%20should%20see%20Spanish%20navigation%20titles%20and%20address%20field%20links.%26nbsp%3B%3CBR%20%2F%3EI%20followed%20the%20instructions%20from%20here%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fcreate-multilingual-communication-sites-pages-and-news-2bb7d610-5453-41c6-a0e8-6f40b3ed750c%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fcreate-multilingual-communication-sites-pages-and-news-2bb7d610-5453-41c6-a0e8-6f40b3ed750c%3C%2FA%3E%26nbsp%3B-%20specifically%3A%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3E%22After%20the%20site%20is%20set%20up%20in%26nbsp%3BEnglish%2C%26nbsp%3Ba%20user%20with%20Spanish%20as%20their%20preferred%20personal%20language%20manually%20edits%20and%20translates%20the%20title%2C%20description%2C%20navigation%20and%20footer%20content%26nbsp%3Binto%20Spanish%22.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSPAN%3EThis%20has%20worked%20correctly%20for%20the%20navigation%20link%20and%20label%20display%20name%20fields.%20A%20user%20with%20Spanish%20language%20settings%20see's%20the%20Spanish%20display%20name%20and%20non-Spanish%20users%20see%20the%20Default%20(English).%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20found%20that%20this%20does%20not%20work%20the%20same%20if%20the%20Address%20field%20for%20a%20link%20is%20changed.%20For%20example%2C%20we%20have%20Spanish%20versions%20of%20pages%20we%20would%20like%20the%20navigation%20to%20link%20to%20for%20Spanish%20users.%20I%20find%20when%20I%20amend%20the%20Address%20field%20with%20Spanish%20language%20settings%2C%20it%20also%20changes%20the%20Address%20field%20URL%20for%20the%20Default%20language%20navigation.%26nbsp%3B%20Is%20this%20expected%20behaviour%3F%20I%20cannot%20see%20anything%20regarding%20this%20either%20way%20in%20the%20documentation%20linked%20above.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1445607%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHub%20Site%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMultilingual%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENavigation%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1446151%22%20slang%3D%22en-US%22%3ERe%3A%20Hub%20Site%20Navigation%20Address%20Field%20Behaviour%20Multilingual%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1446151%22%20slang%3D%22en-US%22%3EYou%20shouldn%E2%80%99t%20need%20to%20change%20the%20link%2C%20just%20the%20label.%20When%20a%20user%20with%20the%20Spanish%20language%20setting%20clicks%20the%20link%2C%20the%20URL%20in%20the%20default%20language%20will%20automatically%20redirect%20to%20the%20Spanish%20page.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1447021%22%20slang%3D%22en-US%22%3ERe%3A%20Hub%20Site%20Navigation%20Address%20Field%20Behaviour%20Multilingual%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1447021%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F690047%22%20target%3D%22_blank%22%3E%40steve85%3C%2FA%3E%26nbsp%3BNavigation%20node%20text%20is%20MUI-enabled%2C%20but%20the%20URLs%20are%20not.%26nbsp%3B%20That%20is%20the%20case%20whether%20the%20hub%20site%20navigation%20is%20modern%20or%20classic%20and%20has%20MLP%20enabled%20or%20not.%26nbsp%3B%20For%20certain%20types%20of%20target%20pages%2C%20there%20is%20redirection%20according%20to%20the%20user's%20language%2C%20if%20the%20target%20is%20on%20an%20MLP-enabled%20Communication%20site%20or%20a%20variations%20site%20collection.%26nbsp%3B%20This%20redirection%20does%20not%20apply%20in%20all%20cases%2C%20but%20in%20most%20common%20scenarios.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20want%20it%20to%20work%20for%20other%20types%20of%20target%20pages%2C%20you%20can%20do%20it%20with%20a%20third-party%20product.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1447050%22%20slang%3D%22en-US%22%3ERe%3A%20Hub%20Site%20Navigation%20Address%20Field%20Behaviour%20Multilingual%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1447050%22%20slang%3D%22en-US%22%3EBTW%2C%20I%20am%20assuming%20that%20you%20have%20implemented%20multi-lingual%20pages%20for%20modern%20comm%20sites.%20If%20you%20do%20that%20AND%20use%20the%20MUI%20links%20as%20you%20describe%20the%20pages%20should%20re-direct%20to%20the%20appropriate%20language.%20See%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fcreate-multilingual-communication-sites-pages-and-news-2bb7d610-5453-41c6-a0e8-6f40b3ed750c%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fcreate-multilingual-communication-sites-pages-and-news-2bb7d610-5453-41c6-a0e8-6f40b3ed750c%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1447119%22%20slang%3D%22en-US%22%3ERe%3A%20Hub%20Site%20Navigation%20Address%20Field%20Behaviour%20Multilingual%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1447119%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20response%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F73026%22%20target%3D%22_blank%22%3E%40Martin%20Laplante%3C%2FA%3E.%26nbsp%3BIn%20my%20scenario%2C%20we%20have%20not%20used%20the%20translation%20feature%20to%20translate%20the%20pages%20to%20Spanish.%20They%20exist%20with%20their%20own%20URLs%20with%20reference%20to%20the%20page%20in%20Spanish.%20The%20hope%20was%20the%20Address%20field%20was%20unique%20for%20each%20language%20once%20MUI%20was%20enabled%20and%20therefore%20I%20could%20add%20the%20English%20page%20URL%20for%20default%20and%20the%20Spanish%20URL%20when%20using%20Spanish%20language%20settings.%20I%20guess%20not.%20Would%20the%203rd%20party%20tool%20you%20mention%20enable%20this%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1447129%22%20slang%3D%22en-US%22%3ERe%3A%20Hub%20Site%20Navigation%20Address%20Field%20Behaviour%20Multilingual%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1447129%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20response%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F38%22%20target%3D%22_blank%22%3E%40Susan%20Hanley%3C%2FA%3E.%26nbsp%3BIn%20my%20scenario%2C%20we%20have%20not%20used%20the%20translation%20feature%20to%20translate%20the%20pages%20to%20Spanish.%20They%20exist%20with%20their%20own%20URLs%20with%20reference%20to%20the%20page%20in%20Spanish.%20The%20reason%20for%20this%20is%20originally%20a%20custom%20navigation%20was%20being%20used%20but%20now%20we%20have%20pivoted%20to%20the%20OOTB%20hub%20navigation%20and%20hoped%20to%20keep%20the%20Spanish%20URLs%20if%20possible%20just%20for%20consistency%20of%20user%20experience%20(I%20realise%20the%20irony%20of%20having%20just%20mentioned%20we've%20changed%20an%20entire%20nav%20menu%20experience).%20I%20assume%20if%20I%20was%20to%20use%20the%20translation%20feature%20instead%2C%20I%20would%20have%20to%20use%20the%20default%20language%20URL%20for%20the%20page%20for%20both%20default%20and%20Spanish%20language%20users%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1447151%22%20slang%3D%22en-US%22%3ERe%3A%20Hub%20Site%20Navigation%20Address%20Field%20Behaviour%20Multilingual%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1447151%22%20slang%3D%22en-US%22%3EIf%20you%20use%20the%20multilingual%20feature%20for%20modern%20comm%20sites%2C%20your%20link%20URL%20will%20be%20the%20one%20in%20the%20default%20language%20-%20and%20the%20user%20will%20automatically%20be%20re-directed%20to%20the%20corresponding%20page%20in%20their%20language.%20You%20can%20learn%20more%20at%20the%20link%20I%20provided%20earlier.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1447420%22%20slang%3D%22en-US%22%3ERe%3A%20Hub%20Site%20Navigation%20Address%20Field%20Behaviour%20Multilingual%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1447420%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F690047%22%20target%3D%22_blank%22%3E%40steve85%3C%2FA%3E%26nbsp%3Byes%2C%20but%203rd%20party%20product%20are%20outside%20the%20scope%20of%20this%20forum.%26nbsp%3B%20You%20can%20message%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We have a SharePoint hub site which requires translation of its navigation links display names and address fields - default is English and users with Spanish language settings should see Spanish navigation titles and address field links. 
I followed the instructions from here - https://support.office.com/en-us/article/create-multilingual-communication-sites-pages-and-news-2bb7... - specifically: 

"After the site is set up in English, a user with Spanish as their preferred personal language manually edits and translates the title, description, navigation and footer content into Spanish". 

This has worked correctly for the navigation link and label display name fields. A user with Spanish language settings see's the Spanish display name and non-Spanish users see the Default (English). 

I have found that this does not work the same if the Address field for a link is changed. For example, we have Spanish versions of pages we would like the navigation to link to for Spanish users. I find when I amend the Address field with Spanish language settings, it also changes the Address field URL for the Default language navigation.  Is this expected behaviour? I cannot see anything regarding this either way in the documentation linked above. 

7 Replies
Highlighted
You shouldn’t need to change the link, just the label. When a user with the Spanish language setting clicks the link, the URL in the default language will automatically redirect to the Spanish page.
Highlighted
Solution

@steve85 Navigation node text is MUI-enabled, but the URLs are not.  That is the case whether the hub site navigation is modern or classic and has MLP enabled or not.  For certain types of target pages, there is redirection according to the user's language, if the target is on an MLP-enabled Communication site or a variations site collection.  This redirection does not apply in all cases, but in most common scenarios.

 

If you want it to work for other types of target pages, you can do it with a third-party product.

Highlighted
BTW, I am assuming that you have implemented multi-lingual pages for modern comm sites. If you do that AND use the MUI links as you describe the pages should re-direct to the appropriate language. See: https://support.office.com/en-us/article/create-multilingual-communication-sites-pages-and-news-2bb7...
Highlighted

Thanks for your response @Martin Laplante. In my scenario, we have not used the translation feature to translate the pages to Spanish. They exist with their own URLs with reference to the page in Spanish. The hope was the Address field was unique for each language once MUI was enabled and therefore I could add the English page URL for default and the Spanish URL when using Spanish language settings. I guess not. Would the 3rd party tool you mention enable this? 

Highlighted

Thanks for your response, @Susan Hanley. In my scenario, we have not used the translation feature to translate the pages to Spanish. They exist with their own URLs with reference to the page in Spanish. The reason for this is originally a custom navigation was being used but now we have pivoted to the OOTB hub navigation and hoped to keep the Spanish URLs if possible just for consistency of user experience (I realise the irony of having just mentioned we've changed an entire nav menu experience). I assume if I was to use the translation feature instead, I would have to use the default language URL for the page for both default and Spanish language users?

Highlighted
If you use the multilingual feature for modern comm sites, your link URL will be the one in the default language - and the user will automatically be re-directed to the corresponding page in their language. You can learn more at the link I provided earlier.
Highlighted

@steve85 yes, but 3rd party product are outside the scope of this forum.  You can message me.