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

Display of a value from controlled vocabulary is not translated on the itempage #310

Open
olli-gold opened this issue Jan 26, 2023 · 0 comments
Labels

Comments

@olli-gold
Copy link

olli-gold commented Jan 26, 2023

Describe the bug
Translation does not work on item pages for values taken from Controlled vocabularies. On Slack Corrado Lombardi said, that "valuepair.<name of controlled vocabulary> rendering in cris layout configuration should display the value according to language". But in fact that does not work. If I create a language version of the controlled vocabulary by creating a file <name of controlled vocabulary>_<language>.xml, the values in the dropdown list in the submission form is displayed in the language chosen by the user, who uses the submission form. The value in the field is stored in the language of the submission form and it's not translated on item pages, if the user of the item page has set a different language.

To Reproduce
Steps to reproduce the behavior:

  1. Create a language specific version of a controlled vocabulary (for instance types_de.xml)
  2. Use this controlled vocabulary in the submission form (for instance for the field dc.type)
  3. Use the submission form (or an edit form using this field) to set the type of a publication
  4. Set valuepair.<name of controlled vocabulary> in the cris layout configuration for the item page (for instance rendering=valuepair.types for the dc.type field of the Publication entity)
  5. Process the cris layout configuration
  6. Call the publication you have edited and switch languages.

Expected behavior
On the itempage the display of the type field should be in the language the user has actually selected.

Related work
I'm not aware of any related tickets or PRs.

@olli-gold olli-gold added the bug label Jan 26, 2023
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