-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SitePages webparts and Navigation is always installed with english language in my env. #41
Comments
Can't seem to reproduce @tarjeieo |
Reason for error: I had no language set in O365, so it chose english language. We need to handle this in a more consistent way if possible. Discussing this a bit and will come back on what to do. |
@tarjeieo Update the installation documentation. |
Will either
|
Weird, Erwin says it's supposed to work like we want. If the web language is 1044 it should pick 1044..... |
Something wrong with your tenant @tarjeieo? |
I guess we can't do anything before 1.0.0 @tarjeieo? |
Current solution is to ignore english resx file... Don't need to solve this until the first version with english support |
Thank you for reporting an issue, suggesting an enhancement, or asking a question. We appreciate your feedback - to help the team understand your needs please complete the below template to ensure we have the details to help. Thanks!
Category
[ ] Enhancement
[X] Bug
[ ] Question
Environment
[X] SharePoint Online
[ ] SharePoint 2013
Summary
Navigation and web parts (and perhaps more) is always installed with english language.
Version
Please specify what version ou are using: [0.9.8 - latest]
If you are not using the latest release, please update and see if the issue is resolved before submitting an issue.
Expected / Desired Behavior / Question
Expect norwegian language as the site is in Norwegian (1044)
Observed Behavior
Navigation and SitePages/webparts are installed in english
Steps to Reproduce
Critical bug as I cannot dev, test or anything in my env.
Let's look at this monday @olemp
The text was updated successfully, but these errors were encountered: