Incorrect alias for translated nodes in admin content overview

Is this only the case for the Title field? If you do the same thing for a field that was added through the UI and link that to the entity, does that work correctly?

@Lendude, this also happens on custom fields. So any untranslatable field with "Link to the Content" enabled always links to the alias of the default language.

For example;
I have one node with two translations ("English" is the original, "Dutch" is the translation) where the fields "Title" and "Identifier" are not translatable, but other fields can be translated.
I add "Identifier" to the admin view "Content" with "Link to the Content" enabled.
In the overview both fields of both translations refer to the English node.

Please note that if you create a node in "Dutch" and then translate it into "English" (so, the original language of the node is not the default language of the site), it will use the alias of the Dutch node. So links on untranslatable fields are always referring to the original translation.

If you put links on translatable fields, it is working as expected; the link is referring to the correct translation.

Aditi Saraf → made their first commit to this issue’s fork.