You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behaviour
On a multilingual site, when using Invoke-PnPSiteTemplate all translatable elements from the resx resource files should be applied, including the navigation nodes.
Actual behaviour
All translations are applied except for the navigation nodes, these are only applied in the sites default language.
Steps to reproduce behaviour
Create a team site without M365 group with default language Dutch
Connect to the new site with PnP.PowerShell
Execute Invoke-PnPSiteTemplate with nav.xml
Go to the site using a browser that is in English, the navigation will be in Dutch
Which operating system/environment are you running PnP PowerShell on?
We experience this bug in 2 environments
On Azure in a C# project using PnP.Framework version 1.13.0
Locally using PowerShell 7 and PnP PowerShell 2.5.0; I tried downgrading to 2.4.0 and 2.3.0 but the bug persists.
Extra Info
We have 3 tenants, in our test tenant the navigation nodes are created as expected... But in our quality assurance
and production tenants they are not.
Expected behaviour
On a multilingual site, when using Invoke-PnPSiteTemplate all translatable elements from the resx resource files should be applied, including the navigation nodes.
Actual behaviour
All translations are applied except for the navigation nodes, these are only applied in the sites default language.
Steps to reproduce behaviour
Which operating system/environment are you running PnP PowerShell on?
We experience this bug in 2 environments
Extra Info
We have 3 tenants, in our test tenant the navigation nodes are created as expected... But in our quality assurance
and production tenants they are not.
Files (added .txt to be able to upload them, remove this when executing)
nav.xml.txt
NAV.nl-NL.resx.txt
NAV.en-US.resx.txt
The text was updated successfully, but these errors were encountered: