Skip to end of metadata
Go to start of metadata


Sadly, we aren't perfect. But we are trying to get there! Some bugs might appear when using Linchpin Translations. We are actively working on the bugs listed here.

General issues

SOLVED IN LISU 4.1.2 & LESS 1.5.2

The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite.

For more information, follow the link below:

Knowledge Base: "Atlassian Troubleshooting and Support Tools" app causes health checks to freeze and blocks the creation of support zips



Usability issues

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.



User experience

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.

Workaround: Knowledge Base - Outdated translations due to duplicate language pack installations

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.

This content was last updated on 04/01/2021.

This content hasn't been updated in a while. That doesn't have to be a problem. Some of our pages live for years without becoming obsolete. Please click this link if you want us to update this page. Old content can be incorrect, misleading or outdated. Please get in contact with us via a form on this page, our live chat or via email with content@seibert-media.net if you are in doubt, have a question, suggestion, or want changes from us.