Problem/Motivation

Default content exports aliases with an explicit language, e.g. path: [{alias: /home, langcode: en}]. The core importer imports the entity in the site language (Importer::verifyNormalizedLanguage()), but the alias keeps langcode: en. On a site without English, these aliases never match: the front page (/home) and other pages return 404.

Steps to reproduce

  1. Install Drupal CMS in German with Haven (English removed at the end of the installer).
  2. Visit / → 404; path_alias shows /home with langcode = en.

Proposed resolution

When the importer changes the entity language, move the entity's aliases to the same language – or templates should export aliases without a fixed langcode.

Additional information

Workaround in dcle (AliasLanguageNormalizer, also applied before import so Pathauto patterns built from a parent alias work).

CommentFileSizeAuthor
#4 3629564-after-front.png896.62 KBchaitanyadessai
#4 3629564-before-front.png78.92 KBchaitanyadessai

Issue fork drupal-3629564

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

joachim namyslo created an issue. See original summary.

chaitanyadessai made their first commit to this issue’s fork.

chaitanyadessai opened merge request !17392

chaitanyadessai’s picture

chaitanyadessai commented
Status: Active » Needs review
StatusFileSize
new 3629564-before-front.png78.92 KB
new 3629564-after-front.png896.62 KB

Please review MR.