Open chjohan opened 3 years ago
Are anyone else experiencing this issue?
@chjohan did you ever find any workarounds? Experiencing the same issue (a year later) with 1.11.0 and 2021/03
@chjohan And here I am another year later with the exact same issue looking for an answer. :)
I did not find a solution to the problem. Unfortunately :(
tor. 14. sep. 2023, 21:42 skrev oliver-tbs @.***>:
@chjohan https://github.com/chjohan And here I am another year later with the exact same issue looking for an answer. :)
— Reply to this email directly, view it on GitHub https://github.com/pnp/PnP-Provisioning-Schema/issues/554#issuecomment-1720039768, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5KYEC7VA6Q4H4YS5LBI5LX2NM2BANCNFSM47DDENHQ . You are receiving this because you were mentioned.Message ID: @.***>
I'm using schema https://github.com/pnp/PnP-Provisioning-Schema/blob/master/ProvisioningSchema-2020-02.md.
Localization suddenly stopped working for LCID 1033 a week ago in structural navigation on a Communication site. Only localization values for the default site language (1044) is successfully set in structural navigation after provisioning.
Localization works everywhere else in my solution for both languages. I have "Enable pages and news to be translated into multiple languages" enabled on on my Site collection.
I get no warnings or errors while applying the template.
I have the following localizations:
I have the following structural navigation: