Incorrect alias for translated nodes in admin content overview

Created on 22 February 2023, over 1 year ago
Updated 21 September 2023, 9 months ago

Problem/Motivation

In the overview of all content in the admin, the alias of the original translation is used for the translations in particular situations. It should be the alias of the translation, not of the original node.

Steps to reproduce

  1. Add a new content type
  2. Add a custom field which can be translated
  3. Set the "title" to be untranslatable
  4. Add a node in the original language (e.g. English) and fill in the title and custom field (e.g. "EN") and give it an alias (e.g. "/foo")
  5. Add a translation of the node in a second language (e.g. Dutch) and change the custom field (e.g. "NL") and give it an alias (e.g. "/bar")
  6. Go to the admin overview: /admin/content
  7. See that both the original as the translation have the same alias ("/foo") => this is incorrect
  8. Change the title of the content type to be translatable
  9. See that both the original as the translation have its correct alias ("/foo" for English and "/nl/bar" for Dutch) => this is correct

Proposed resolution

Even if the title is not translatable, it should link to the correct alias.

๐Ÿ› Bug report
Status

Active

Version

9.5

Component
Viewsย  โ†’

Last updated about 2 hours ago

Created by

๐Ÿ‡ณ๐Ÿ‡ฑNetherlands Rik Wijnen

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Rik Wijnen
  • ๐Ÿ‡ณ๐Ÿ‡ฑNetherlands Lendude Amsterdam

    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?

  • ๐Ÿ‡ณ๐Ÿ‡ฑNetherlands Rik Wijnen

    @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.

  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia AditiVB

    Aditi Saraf โ†’ made their first commit to this issueโ€™s fork.

Production build 0.69.0 2024