- π©πͺGermany hchonov πͺπΊπ©πͺπ§π¬
Our use case is like this that we have a content type that is not translatable, but the site has multiple languages enabled without language detection enabled and it is possible to create content in that content type for different languages. However since pathauto automatically creates the aliases with the language of the entity if we would create content in a non-default site language then we cannot visit the url of the page. I think that we need an approach similar to π If you don't want to translate your URL alias, the original URL alias won't work with your translations Needs work that will set the language to undefined in case the entity is not translatable. The only issue I can think of is though what should happen if the content type is made translatable at a later point, so this needs to be defined and tested how the aliases old and new will behave.
- π©πͺGermany geek-merlin Freiburg, Germany
@hchonov: Nice to meet you again here. We face a similar problem and your approach pointed me in the right direction.
Made an overview π± Overview of Pathauto language problems and approaches Active with some more pointers and what core does ("und if entity OR path field is untranslatable"). HTH!