Problem/Motivation

I want to be able to control what strings and punctuation are filtered/removed by pattern type.

For example, with user profiles someone's name may be Jane A. Doë and their profile url alias could be a combination of

  • jane-.-doe
  • jane-doe (which then could be jane-doe-1, jane-doe-2, etc. for common names)
  • jane-a.-doe

when I actually want the alias to be:

jane-a-doë

Other common use case is also legal decisions and e-commerce where you may want a url to be

legal
Lawsuit Jane Doe vs. Bradley Smith, Jr.

docket-jane-doe-vs-bradley-smith-jr vs. docket-jane-doe-bradely-smithjr

e-commerce/policy
Per Diem, Travel and Transportation Allowance Rules

diem-travel-transportation-allowance-rules vs. per-diem-travel-transportation-allowance-rules

However, since punctuation and strings are controlled at a global level it's hard to specify exactly how an alias should be when considering names, places, or legal information.

Proposed resolution

Allow strings, punctuation, and special characters to be controlled by pattern type when creating a new pattauto pattern.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

laura.gates created an issue. See original summary.

laura.gates’s picture

Issue summary: View changes
laura.gates’s picture

Title: Allow strings and puncuation to be controlled by content type » Allow strings and puncuation to be controlled by pathauto pattern
Issue tags: +pattern, +special characters