Closed 1yuv closed 1 hour ago
Update:
This could be not an issue with CHT itself. Looks like the instance with issue has translations like this, where a translation was explicitely specified previoulsy when we had missing translation keys.
configuration.sms.settings = configuration.sms.settings
configuration.sms.test.description = configuration.sms.test.description
configuration.sms.test.message.description = configuration.sms.test.message.description
configuration.sms.test.number.validation.description = configuration.sms.test.number.validation.description
Describe the bug On 4.12.0, we added Nepali translations for missing keys and it was expected those keys to be translated to Nepali language after upgrade. However, even after upgrading an instance to 4.12.0, there are many translation keys that are not showing the translated text.
To Reproduce Steps to reproduce the behavior:
Expected behavior All translation keys, that have the translation available should display the label on the properly translated text.
Screenshots
Environment
Additional context