Problem/Motivation

Default content gets path alias language exported.

When default content is imported, if the language of the entity does not exist on the site that gets normalized to the site default language. But the path language remains as-is in the import, even if such language did not exist on the site.

Steps to reproduce

Proposed resolution

Do not include the path language if it was the same as the entity language. This at least resolves getting invalid language for the base use case. When multilingual path aliases are exported that could still end up with invalid language but the basic Drupal CMS site template scenario is resolved this way.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3616015

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

gábor hojtsy created an issue.

gábor hojtsy opened merge request !16650

rodrigoaguilera’s picture

rodrigoaguilera
Primary language Spanish
Location Madrid
commented

I'm experiencing that path aliases for node translations don't get imported on recipe apply. Can this be related?
You seem to have aliases for translations working as expected, should I file a different issue?
I proposed exporting aliases as a workaround:
#3612967: Use uuid when exporting a path_alias in its canonical path