Since upgrading to the latest beta we’ve noticed some very annoying translation issues. How can I fix this immediately?
Someone at Discourse should make sure, that changing those name conventions also need a response from the translators. It’s kind of unprofessional to ignore existing strings with the same meaning and than overwrite it with placeholders like “[object Object]”. Especially at the main menu. There was already a valid translation.
Best,
M
I can’t confirm this:
Which version are you on, exactly? I’m on Discourse 1.5.0.beta5 - https://github.com/discourse/discourse version 50da33eee1b656f8370045d720adb601e575be0c a.k.a. v1.5.0.beta5 +128.
Latest github commit: (1be4b6a) – status: up to date
v1.5.0.beta5 +9 … I will try a complete rebuild via SSH.
Okay, so you’re a few commits ahead of beta. Looks like this commit is the culprit:
https://github.com/discourse/discourse/commit/bb76c389fda4349abdb0f8b54b0618a66186b018
This should be fixed as soon as the translations are updated. You might want to switch to the beta channel to decrease the risk of this happening.
But I agree that the current handling is suboptimal. Discourse should at least show the English original text if the translation is unavailable…
As @fefrei said, you are not on beta, so you should expect certain things to break now and then.
The locale files still contain obsolete translations which are causing this glitch.
This will fix itself within the next few days. It needs a complete translation round-trip:
That’s how it usually works. But in this case the existing translations are wrong and the code responsible for showing those labels can’t handle that.
Hopefully a fix will roll out very soon.