Skip to content

Conversation

@engijlr
Copy link
Contributor

@engijlr engijlr commented Nov 21, 2025

Fixed: #20400

Problem

The umbContentName component in Block List labels always displayed content names in the default language, regardless of the currently active backoffice culture.

Solution

In content-name.element.ts, the code previously always accessed variants[0].name, which returned the first variant (typically the default language) regardless of the current backoffice culture. Now uses UmbDocumentItemDataResolver to get culture-aware content names for documents.

How to test

  1. Create a document with multiple language variants.
  2. Add a Block List with {umbContentName: combiGift} in the label
  3. Switch between languages in the backoffice
  4. Verify the block label updates to show the correct language variant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UFM: contentName component does not take current backoffice language into account

2 participants