Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.or have Automatic Alias set on a per node basis. Either way, it would be helpful to have some way to indicate that a set of nodes should be excepted from Pathauto aliasing. This problem occurs for me on sites where I have static pages that have unique URLs and other content types that are automatically generated. When the static pages are edited by a client, Pathauto kicks in and overrides the URL. Maybe this capability already exists, but I haven't seen it.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | path-auto-content-type.png | 84.07 KB | introfini |
Comments
Comment #1
gregglesAmanire - interesting idea - I like it.
For the record, I don't plan to work on this. I think it's an interesting idea but it would require 3-4 additional radio buttons per content type which would (further) clutter the settings page.
If someone wanted to do this but not provide a UI for it then that would be fine by me. By "not provide a UI" I mean "make it settable via the $conf array in settings.php".
Comment #2
introfini commentedVery useful idea.
@greggles: how about having a default update action on admin/build/path/pathauto and a fieldgroup in each content type administration form where we can change the defaults? (please see attached image)
introfini
Comment #3
gregglesNo.
My stance is that no new UI elements can be added to Pathauto unless we significantly simplify other parts of it.
Comment #4
dave reidI don't think this is a good idea at all, sorry. :/
Comment #5
gregglesAgreed.
Though it could be a candidate for something like #322320: create separate "pathauto advanced" module for the crazier settings ;)