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
{{ message }}
Repository navigation
Missing translation: en| - Unable to set language on Firefox #9422
Recently I've seen lots of people reporting that they are seeing missing strings for languages that are properly translated. I've also gotten bit by this a few times. The console error that looks relavent is
Unable to set language
Object { err: null, response: XMLHttpRequest }
rageshake.js:61:8
I got it on /develop, other people on /app have reported the same issue.
This is happening for me and other people using the Riot that I host since I upgraded. The thing is, reload doesn't help. The error message is the same. Is there a header I can set with nginx to kill the caching?
I got this issue many times per week as well, for the last 2 months, a popup telling me "missing translation". But it was only a single popup. Not more.
But since yesterday, it all strings provided by Element which are pre-fixed by "Missing translation" as you can see on the screenshot
Yeah, this is still present. I got it and pressed "send feedback". Hope that's equivalent to rage shaking. I tried rage shaking my laptop, but nothing happened...
Yeah, this is still present. I got it and pressed "send feedback". Hope that's equivalent to rage shaking. I tried rage shaking my laptop, but nothing happened...
Unfortunately feedback doesn't include logs for privacy reasons, please send logs from Settings > Help & About
Yeah, this is still present. I got it and pressed "send feedback". Hope that's equivalent to rage shaking. I tried rage shaking my laptop, but nothing happened...
It's happened to me again this morning, except this time it seemed to prevent Element to load (I got an infinite spinner until I reloaded the tab), so I couldn't rageshake.
Content Security Policy: The page's settings blocked the loading of a resource at inline ("script-src"). moz-extension:33:9
Unable to set language Error: Failed to load i18n/languages.630445c.json, got 404
getLangsJson languageHandler.tsx:533
on_end index.js:294
on_state_change index.js:244
rageshake.ts:72:27
Loading Worker from “https://develop.element.io/ad35579c7db15f5fe93e.worker.js” was blocked because of a disallowed MIME type (“text/html”). develop.element.io
Activity
aaronraimist commentedon Apr 10, 2019
Possibly related: #4136 / #8710
#8879
#7847
turt2live commentedon Apr 10, 2019
Looks like we might be eagerly deleting files which causes 404s later on. Might need a different cache strategy
lampholder commentedon Apr 29, 2019
@turt2live - eagerly deleting when? When we redeploy?
turt2live commentedon Apr 29, 2019
yes, it seems like we're blowing away the old build when we deploy a new build, which means that people who are unlucky will have missed the bundle.
bwindels commentedon Oct 11, 2019
We could solve this by adding a service worker that adds the language files (and others) to the cache and falls back to it on a 404
kixiQu commentedon May 8, 2020
This is happening for me and other people using the Riot that I host since I upgraded. The thing is, reload doesn't help. The error message is the same. Is there a header I can set with nginx to kill the caching?
Yoric commentedon Dec 23, 2020
I keep being bitten by it several times per week, so I'd be happy if we could fix this 👍
Relevant console message seems to have changed:
Could we possibly init an auto-reload when we detect the issue?
Gustry commentedon Jan 19, 2021
I got this issue many times per week as well, for the last 2 months, a popup telling me "missing translation". But it was only a single popup. Not more.
But since yesterday, it all strings provided by Element which are pre-fixed by "Missing translation" as you can see on the screenshot
t3chguy commentedon Jan 19, 2021
Clear your browser cache.
Gustry commentedon Jan 20, 2021
Thanks, it worked.
127 remaining items
lindhe commentedon Apr 28, 2022
Yeah, this is still present. I got it and pressed "send feedback". Hope that's equivalent to rage shaking. I tried rage shaking my laptop, but nothing happened...
t3chguy commentedon Apr 28, 2022
Unfortunately feedback doesn't include logs for privacy reasons, please send logs from Settings > Help & About
novocaine commentedon Apr 29, 2022
Element
1.10.11was created on April 19, so doesn't have the most recent attempt to fix the issuebabolivier commentedon Apr 29, 2022
I saw it again this morning on develop, I've rageshaken ^
babolivier commentedon May 3, 2022
It's happened to me again this morning, except this time it seemed to prevent Element to load (I got an infinite spinner until I reloaded the tab), so I couldn't rageshake.
andybalaam commentedon May 4, 2022
I got the infinite spinner this morning. Console:
Address bar:
The screen is blank except for "missing translation: en|Logout" at the bottom, and a spinner in the middle.
babolivier commentedon May 4, 2022
I got it again this morning. I managed to rageshake through the console ^
andybalaam commentedon May 5, 2022
I got it again today (not the freeze), rageshake ^, URL: https://develop.element.io/?updated=850a250cea91-react-1c70696b1020-js-d190cdc307f1#/room/!HtSAtjJmFcbeysRBii:envs.net
babolivier commentedon May 13, 2022
Also had one just now (not the freeze), rageshaken ^
babolivier commentedon May 16, 2022
Again ^
turt2live commentedon Jul 4, 2022
It's unclear what this was blocked on, but it's certainly worthy of picking up.
I believe at this point we know what causes it, we just need to figure out how to fix it.
richvdh commentedon Aug 30, 2023
Is this still happening? I don't remember seeing it recently.
andybalaam commentedon Aug 30, 2023
I haven't seen it for ages. Closing. If it re-occurs please re-open. (Thanks Rich for pointing this out.)