Wekan dont Save Language

[EDV-Muencheberg]

Hello,

if you cahnge the Language to german or something else and reopen the Browser the Language changed back to the default (english)

Regards

[xet7]

@EDV-Muencheberg

What version of Wekan you have?

[xet7]

@EDV-Muencheberg

With newest Wekan, when I reload webbrowser page, after webpage is loaded it still has the same language I selected, in my case Finnish. While loading webpage, for a small time it shows English, because all translations have not been loaded yet, but after all translations have been loaded and Javascript code has run, it is still in Finnish.

[xet7]

@EDV-Muencheberg

I changed to Deutch, and after reloading webpage, it is still Deutch.

[xet7]

If still after updating to newest Wekan this happens, please comment on this issue, so I will then open this issue again.

[fcoufour]

@xet7 We found something strange relative to how user language is handle.

Without any language in user mongodb document:

• english (❌french expected) after login when french (France) is selected in Chrome settings, english (❌french expected) after refresh, english (❌french expected) selected in language menu
• english (❌french expected) after login when french is selected in Chrome settings, french (✅ok) after refresh, french (✅ok) selected in language menu

With "de" language in user mongodb document:

• english (❌german expected) after login when french (France) is selected in Chrome settings, german (✅ok) after refresh, german (✅ok) selected in language menu
• german (✅ok) after login when french is selected in Chrome settings, german (✅ok) after refresh, german (✅ok) selected in language menu

👉 the country language code (like fr-FR) seems to be ignored
👉 ths behaviour is not always as expected

Are you aware of this?

Tested with current last version of Chrome and with last version of Wekan (5.14.0)

[cosmoswafer]

Same here with latest version of Chrome and Wekan 5.14.

1. Wekan showed Traditional Chinese by default which is my default language in Google Chrome
2. I manually changed the language to English
3. Refresh, it was still showing English
4. Using Wekan for a while (about 1 hour?)
5. The UI was partially showing Traditional Chinese
6. Refresh, the entire UI became Traditional Chinese

Should we create another new issue or reopen this?

Edit: Just want to clarify that I mean the UI was partially changing back to the default language even the user manually changed the language.

[xet7]

For any translations that is only partially translated, please check that all are translated at:
https://www.transifex.com/wekan/wekan

[xet7]

Very often someone requests some language duplicate.
For example:

• Swedish (Sweden) is same as Swedish
• Chinese (China) is same as Chinese
• etc

So if there exists for example already either Language (Country) or Language, I have asked for confirmation is it different, and not added duplicate.

In addition of this bug, there are other translation bugs

[StefanNeubert]

Same here with 5.17. Reloading page or closing browser the language changes back to english.
Running on docker.

[EDV-Muencheberg]

Same Problem with version 5.15.0 with snap.

[StefanNeubert]

@EDV-Muencheberg are you running on a sublocation? Maybe this is an issue an related to #3384

[EDV-Muencheberg]

@StefanNeubert yes we run it on a sublocation.

[Meeques]

I've got this problem, too. Our WeKan instance is always the newest version (unbuntu snap). In Firefox, I don't have this issue, only in Chrome (Version 97.0.4692.99). A colleague of mine has the same problem. When reloading the page, it switches from german to english.

[xet7]

@Meeques

Try:

1. Clear Chrome history, everything but not cookies
2. Close Chrome
3. Open Chrome
4. Open WeKan board page
5. Reload page
6. Does it stay German?

[Meeques]

@xet7 Unfortunately the problem persists.
After doing all that (twice) WeKan still switches to english.

[cosmoswafer]

How is your Wekan instance running? Under a dedicated domain or sub-url? I found out that switching language won't work if your Wekan is running under sub-url. Not only this, many other features, such as create shortcut on mobile, are also not working. There are some static files not being resolved under the sub-url and the Wekan front-end still trying to fetch them from the root path (/).

I suggest you checking the browser console and network console form the developer tools, if there is any error.

[Meeques]

It is a dedicated domain. But the browser console does cast some errors. I will ask the data center for help. thank you!

[xet7]

@Meeques

If there are websockets or other errors, check webserver config. Examples for various webservers at right menu of page:
https://github.com/wekan/wekan/wiki

For example, there are Caddy, Nginx, Apache etc examples.

[xet7]

@Meeques

What errors there are at browser inspect console? Please copy them to text editor, anonymize it like replace your domains with example.com etc, and copy paste those errors to comment to this issue, if possible. Thanks!

[Meeques]

@xet7 Yes, there are websocket errors, I will check in with the server administrator. Thanks for the link.

Here is the requested output:
`persoenliches-kanban:1 Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('https://www.uni-example.de/') with script ('https://www.uni-example.de/pwa-service-worker.js'): A bad HTTP response code (404) was received when fetching the script.

/site.webmanifest:1 Failed to load resource: the server responded with a status of 404 (Not Found)

ebb61ec12b32fa847d2127e9f07f49439f92d685.js?meteor_js_resource=true:243 WebSocket connection to 'wss://www.uni-example.de/wekan/sockjs/462/xyw3oept/websocket' failed:

k.websocket @ ebb61ec12b32fa847d2127e9f07f49439f92d685.js?meteor_js_resource=true:243

/favicon-32x32.png:1 Failed to load resource: the server responded with a status of 404 (Not Found)

/site.webmanifest:1 Manifest: Line: 1, column: 1, Syntax error.

/site.webmanifest:1 Failed to load resource: the server responded with a status of 404 (Not Found)`

[xet7]

@Meeques

Current WeKan requires that websockets are configured to work.

In my install of WeKan using Caddy webserver, I don't have any of those errors.