You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create a Localizable Content Type with Autoroute part attached and {{ Model.ContentItem.Content.LocalizationPart.Culture }}/{{ Model.ContentItem | display_text | slugify }} as the pattern.
Configure two languages in the admin settings
Create a new Content Item.
Add a new localizable version
Expected behavior
The Localized version should reevaluate the autoroute pattern when publishing to take into account the translations made.
The text was updated successfully, but these errors were encountered:
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:
Expected behavior
The Localized version should reevaluate the autoroute pattern when publishing to take into account the translations made.
The text was updated successfully, but these errors were encountered: