Is it possible to make transliteration functionality more selective? Is it possible to turn off transliteration on some patterns or/and node types or/and taxonomy?

For example, "Pattern for blog page paths" and "Pattern for all story paths" using [user-raw] with transliteration option on, but "Pattern for all vocab-name paths" using [cat-raw] with transliteration option off.

When transliteration option is enabled, I see two ways to make this functionality:
1. Add additional tokens with transliteration (for example, [user-raw-translit])
2. Add additional options on Pathauto setting page on every pattern.

Thanks for help.

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Make transliteration more selective » Make all pathauto variables overridable at the beginning of cleanstring
Version: 6.x-1.x-dev » 7.x-1.x-dev
Component: Miscellaneous » Code

This is not currently possible and neither of those solutions seems like a workable solution to me.

That said...we do need to make pathauto more extensible so that the extreme things like this are possible...

New title/version to reflect this.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (duplicate)

This will be possible with #686234: Re-architect alias transformations, so merging this issue into that one.

ludo.r’s picture

ludo.r
Location Brussels
commented
Version: 7.x-1.x-dev » 8.x-1.x-dev
Issue summary: View changes
Status: Closed (duplicate) » Active

I'm re-opening this 11 years old issue cause I'm facing this exact issue now.

I'd need to have custom settings depending on the entity type - in my case I need a different max_component_length value - for now I'm overriding the AliasCleaner service, especially the cleanString() method, but even there I think the way to populate the cleanStringCache property should be in a dedicated function.

If needed I can provide an example.