Skip to content

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

@FrontisFrank

Description

@FrontisFrank

Which Umbraco version are you using?

16.2.0

Bug summary

We have setup a blocklist, where the blocklist element contains a content picker.
In the blocklist label we want to display the node name, using the recently added contentName component. Sadly the contentName component does not take into account the currently active backoffice culture.
When viewing the collapsed blocklist elements we see node names displayed in mixed up cultures:

Image

When opening a blocklist element and viewing the node name in the content picker, the currently active culture is used for the node name:

Image

In both cases the currently active culture is dutch., while we see one node name in french. Even though the dutch version is available.

Specifics

For blocklist elements the node name is displayed in the correct culture, but that seems to be coincidence. Probably the order in which node languages are created is responsible for this.

Steps to reproduce

  • Create a vary by culture doctype containing a block list
  • In the blocklist add an element containing content picker
  • For blocklist label use this label: {umbContentName: combiGift}
  • Setup the content
  • Make sure to create linked content first in a secondary culture (for us this is french)
  • Later on create the page in the primary culture
  • Use the content picker in the blocklist element
  • Regardless of the currently active culture, the displayed node name is always in the secondary culture

Expected result / actual result

In the blocklist preview when using the contentName component we expect the same node name is displayed as when the blocklist element is expanded and the node name is displayed using the content picker.


This item has been added to our backlog AB#57497

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions