PnP Provisioning composed look element not included in non-english sites

%3CLINGO-SUB%20id%3D%22lingo-sub-13564%22%20slang%3D%22en-US%22%3EPnP%20Provisioning%20composed%20look%20element%20not%20included%20in%20non-english%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-13564%22%20slang%3D%22en-US%22%3E%3CP%3EWe%26nbsp%3Bhave%20just%20started%20using%20the%20OfficeDevPnP%20provisioning%20engine%20(Nuget%26nbsp%3BSharePointPnPCoreOnline%20ver.%26nbsp%3B2.7.1609.3).%20Our%20solution%20is%20intented%20to%26nbsp%3Bwork%20in%20a%20hybrid%20scenario%20(templates%20edited%20in%20SharePoint%20Online%20and%20applied%20to%20both%20Online%20as%20well%20as%20OnPrem%20sites).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEverything%20works%20fine%20except%20Composed%20looks%3A%3C%2FP%3E%3CP%3EIf%20extracting%20a%20template%20from%20an%20english%20site%20(lcid%3A%26nbsp%3B1033)%20and%20applying%20to%20an%20empty%20site%20(also%20lcid%3A%201033)%20then%20the%20composed%20look%20selected%20in%20the%20template%20is%20applied.%3C%2FP%3E%3CP%3EHowever%20if%20the%20template%20is%20a%20Danish%20site%20(lcid%3A%201030)%20and%20applying%20to%20an%20empty%20danish%20site%2C%20then%20the%20Composed%20look%20information%20is%20NOT%20applied.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20using%20the%20new%20pnp%20file%20format%20for%20persisting%20extracted%20template.%20When%20inspecting%20the%20pnp%20file%2C%20we%20can%20see%2C%20that%20extract%20from%20an%20english%20site%20with%20updated%20composed%20look%20has%20an%20element%20like%20the%20following%3A%3C%2FP%3E%3CPRE%3E%26lt%3Bpnp%3AComposedLook%20Name%3D%22Breeze%22%20ColorFile%3D%22%22%20FontFile%3D%22%22%20BackgroundFile%3D%22%22%20Version%3D%220%22%20%2F%26gt%3B%3C%2FPRE%3E%3CP%3EThis%20element%20is%20however%20not%20present%20in%20a%20template%20extracted%20from%20a%20Danish%20site.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20we%20missing%26nbsp%3Bsomething%20in%20the%20way%20we%20use%20the%20framework%3F%20-%20or%20is%20there%20some%20localization%20missing%20in%20the%20OfficeDevPnP.Core%20preventing%20the%20framework%20to%20be%20used%20in%20non-english%20sites%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3EThomas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-13564%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EPnP%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

We have just started using the OfficeDevPnP provisioning engine (Nuget SharePointPnPCoreOnline ver. 2.7.1609.3). Our solution is intented to work in a hybrid scenario (templates edited in SharePoint Online and applied to both Online as well as OnPrem sites). 

 

Everything works fine except Composed looks:

If extracting a template from an english site (lcid: 1033) and applying to an empty site (also lcid: 1033) then the composed look selected in the template is applied.

However if the template is a Danish site (lcid: 1030) and applying to an empty danish site, then the Composed look information is NOT applied. 

 

We are using the new pnp file format for persisting extracted template. When inspecting the pnp file, we can see, that extract from an english site with updated composed look has an element like the following:

<pnp:ComposedLook Name="Breeze" ColorFile="" FontFile="" BackgroundFile="" Version="0" />

This element is however not present in a template extracted from a Danish site. 

 

Are we missing something in the way we use the framework? - or is there some localization missing in the OfficeDevPnP.Core preventing the framework to be used in non-english sites?

 

Best regards,

Thomas

0 Replies