If the Update action is "do nothing" then aliases cannot be auto generated. If the Update action is anything else then aliases are forcibly changed. I needed a way to define aliases, have them stick, but also allow them to be auto generated. The settings help text indicates that the rule should NOT apply if there is NOT an alias but the code does not match that description. The attached patch aligns the code and the description.

While this resolves my problem I am not entirely happy with the solution. It is NOT backwards compatible and it is confusing. I am posting this here just in case someone else finds it useful. A potentially better solution is a hook that enables a 'maintain pathauto' option that self-manages paths that need to be and ignore those that must have a consistent URL.

CommentFileSizeAuthor
pathauto.inc_.patch745 bytesrobb

Comments

greggles’s picture

Status: Active » Closed (duplicate)

Thanks for providing this patch.

I believe this is a duplicate of the ideas expressed in #228762: Un-aliased nodes should still get an alias generated even if the update action is 'Do nothing with existing aliases'.

Can you perhaps join the effort there and update the patch for 6.x-2.x? I would like to see this fixed in that version.

robb’s picture

Sounds good, I will post my latest patch there.