Linchpin Translations 1.6.5 duplicates a language pack instead of replacing/updating it.
We introduced a new formatting for the plugin key. It uses the kebab case style. This leads to the issue that existing projects (which don't use the kebab case style in their plugin keys) won't be simply updated but receive a new, duplicate installation which matches the new styling. This can lead to outdated translations being displayed to users.
It is possible that this issue affects the whole app (and not only profile fields). We are investigating this behavior.
Until then we recommend to avoid using the same values for the translation key and the translation itself.
Other known issues
Issue Type
Description of the Issue
Usability issue
User profiles: Field labels can't have the same value as translations keys. If they do, the translations won't work.
Let's say your profile field is called "Street" (=field label). Now, you want to create several translations for this field label. If one of those translations is also called "Street", it won't be displayed to the user in their language. Instead, the default value will be displayed.
Have you found another issue or do you have a stronger need to fix one of these issues? Tell us here.
Simplyvisit our feedback board in Cannyand create a feature idea, vote for existing posts or discuss your ideas with other customers.
