Jun 06 2020 12:42 PM
Jun 06 2020 12:42 PM
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.
Jun 07 2020 04:52 AM
Jun 07 2020 11:28 AMSolution
@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.
Jun 07 2020 12:30 PM
Jun 07 2020 02:04 PM
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?
Jun 07 2020 02:20 PM
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?
Jun 07 2020 03:30 PM
Jun 07 2020 09:01 PM
@steve85 yes, but 3rd party product are outside the scope of this forum. You can message me.
May 21 2021 10:05 AM
@Susan Hanley I have a weird one...I just enabled the multilingual feature. The translate option on the Site Name, Description, and Navigation is missing... Did I miss something in my set up?
May 21 2021 12:02 PM - edited May 21 2021 12:02 PM
@rondharamdeolai I had that happen to me yesterday. I deactivated the feature and reactivated it, and it returned. It is rolled out to most Targeted Release tenants, but I'm not sure the rollout to other tenants is complete yet.
May 21 2021 12:24 PM
@rondharamdeolai I would try activating and deactivating the feature as Martin suggested. I haven't seen that before.