Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content Localization Autoroute problem with culture name in path #15805

Open
MichaelPetrinolis opened this issue Apr 22, 2024 · 2 comments · May be fixed by #15810
Open

Content Localization Autoroute problem with culture name in path #15805

MichaelPetrinolis opened this issue Apr 22, 2024 · 2 comments · May be fixed by #15810
Assignees
Labels
Milestone

Comments

@MichaelPetrinolis
Copy link
Contributor

Describe the bug

There is an issue when you create multilingual content with the {{ Model.ContentItem.Content.LocalizationPart.Culture }} in the autoroute path pattern.

If you try to create a localized version of a content item, the pattern is not taken into account. The handler calls the GenerateUniqueAbsolutePathAsync to create a unique autoroute path by appending an integer to the original path to make it unique.

To Reproduce

Steps to reproduce the behavior:

  1. Create a Localizable Content Type with Autoroute part attached and {{ Model.ContentItem.Content.LocalizationPart.Culture }}/{{ Model.ContentItem | display_text | slugify }} as the pattern.
  2. Configure two languages in the admin settings
  3. Create a new Content Item.
  4. Add a new localizable version

Expected behavior

The Localized version should reevaluate the autoroute pattern when publishing to take into account the translations made.

@Piedone
Copy link
Member

Piedone commented Apr 22, 2024

The issue is that the original content item is completely copied, including its permalink.

@Piedone Piedone added this to the 1.x milestone Apr 22, 2024
@hishamco
Copy link
Member

Ya because it's cloned, I will have a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants