Forum Discussion
Solved
How to provision web part titles in multiple languages using Office Dev PnP Provisioning?
Using the Office Dev PnP provisioning engine I've managed to deploy a site in multiple languages. We managed to localize just a few of the web part titles shown on the welcome page of our site: The...
Hi Harold,
I did a big multi langual project and managed to get it working for all my webparts. In my experience your need to put the language tokens in bot the pnp:webpart title attribute as in the webpart xml title property. Both needs to be the same. All localization files needs to be refered to in your template and als the supported languages needs to be set. This way it works in my opinion.
One thing to note here: The webparts only show in the language of the site and does not follow the users language. So if a German user visits a French site, the webpart titles are shown in German. Not in French. I would have expected that the users language would be leading here, but haven't seen it work like that.
Hi Harold,
I have currently a very similar problem: Some webpart titles "accept" the ressource-string others just always display their english title.
I'm using SharePpoint 2016 with PnP Partner Pack to provision the webparts.
For me the CSWP is translated correctly.
Not translated: Script-Editor-Webpart and Project Summary Webpart.
Did you ever find out what the problem was? Currently I guess that some webparts render server-side and some render client-side. Depending on the render mode it fails or it works - but till now I couldn't test it.
Hi,
I just figured out the behavior in my case: It is not related to the type of webpart but to the order the webparts are provisioned. Only the last Webpart in my PnP-Template-XML will get a translated title.
More testing is in progress.
