Skip to content

Studio language comparison view renders raw layout title keys instead of translated titles #410

Description

@GAL-CS

Affected Version

2026.2

Affected capability

Data Objects

Steps to reproduce

  1. In a DataObject class, set a layout container's (e.g. Panel) title to a translation key, e.g. Product.layout.general.
  2. Place a Localizedfields container with at least one field under that layout element.
  3. Add a studio-domain translation for the key (Product.layout.general → Allgemein) and rebuild the translation catalogue.
  4. Open an object of that class in Studio and open the language comparison ("Sprachvergleich") toolbar view.

Actual Behavior

The section header shows the raw key Product.layout.general. processNestedLayoutData builds the breadcrumb from the untranslated item.title (process-layout-data.ts, getBreadcrumbTitle(fieldBreadcrumbTitle, item.title ?? '')), and renderSectionTitle in language-comparison-content.tsx renders breadcrumbTitle.split('/') directly, without passing it through the translation function. The field labels in the same dialog are translated correctly, and the same layout title is translated in the normal object editor.

Image

Expected Behavior

The section header should display the translated layout title (Allgemein), consistent with field labels in the same dialog and with the layout title in the normal object editor.

Activity

  1. added theissue type on Aug 26, 2026
  2. updated Affected capability Assets and Platform Version 2026.2 on Aug 26, 2026
  3. jcPimcore commented on Aug 26, 2026

    @jcPimcore
    Contributor

    Hi @GAL-CS

    Thanks for the detailed report — this looks like a genuine display bug in the Studio language comparison ("Sprachvergleich") view.

    To confirm we're looking at the same thing and to rule out environment factors, could you please confirm the following:

    • Does the layout title translate correctly everywhere else (normal object editor tabs/panels) and only fail in the language comparison view? (Your report suggests yes — just confirming.)
    • Which translation domain holds the key — you mention studio. Can you confirm the same key resolves correctly when used as a field label vs. a layout container title?
    • Is the translation catalogue fully rebuilt and caches cleared after adding the key?

    Thanks in advance,

    Jochen

  4. GAL-CS commented on Aug 27, 2026

    @GAL-CS
    Author
    1. Only the language comparison view fails; the normal editor translates correctly.
    2. Domain is studio. The key resolves correctly in every place it is actually looked up; the comparison view just never looks it up.
    3. Catalogue rebuilt and caches cleared
  5. deleted a comment from github-actions on Sep 18, 2026
  6. added this to the 2026.3 milestone on Sep 18, 2026
  7. jcPimcore commented on Sep 18, 2026

    @jcPimcore
    Contributor

    Hi @GAL-CS
    Sorry for the delay. And much thanks for your answers!
    This will be investigated by our dev team now.

    Kind regards,

    Jochen

  8. modified the milestones: 2026.3, 2026.4 on Oct 2, 2026
  9. jcPimcore commented on Oct 7, 2026

    @jcPimcore
    Contributor

    Hi @GAL-CS

    A fix is up for review: pimcore/studio-ui-bundle#4170 (targets 2026.3, milestone 2026.3.1). The language comparison view now translates each layout title segment, as the versions view already does.

    Kind regards, Jochen

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Platform Version

2026.2

Affected capability

Assets

Galaxy

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions