Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document Type Field Names in Umbraco Backoffice Do Not Switch Based on Selected Culture Despite Added Translations #17450

Open
jerin-ose opened this issue Nov 7, 2024 · 1 comment
Labels

Comments

@jerin-ose
Copy link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

Umbraco 13.5.1

Bug summary

In Umbraco, even when translations are added for document type field names, these labels in the backoffice do not switch according to the selected culture. Field names remain in the default language, regardless of the selected culture in the content editor.

Specifics

No response

Steps to reproduce

In Umbraco, go to the Translation tab and add a translation with two languages. Next, go to any Document Type and set a field label and alias to match the translation name. Then, go to Content, select a node using this document type, and switch cultures. The field label always displays in the default culture’s language, ignoring the selected culture’s translation.
Screenshot 2024-11-07 162214
Screenshot 2024-11-07 162718

Screenshot 2024-11-07 162229
Screenshot 2024-11-07 162237

Expected result / actual result

When switching cultures in the Content section, field labels should display in the selected culture’s language, reflecting the translations set for each language.
Screenshot 2024-11-07 162951
Screenshot 2024-11-07 163013

Copy link

github-actions bot commented Nov 7, 2024

Hi there @jerin-ose!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant