Reviewed & tested by the community
Project:
Pathauto
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 Jul 2026 at 10:51 UTC
Updated:
31 Jul 2026 at 13:45 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
berdirComment #4
csakiistvanComment #5
csakiistvanEnvironment
Prerequisites
drupal/pathauto:1.15.0installed./forums/[term:name]./forums/general-discussion.Steps
drupal/forumdev requirement in favour of a version constraint, and drop forum coverage from the bulk update test.ddev drush cr/admin/config/search/path/patterns/add) and open the Pattern type select./admin/config/search/path/patternsand look at the existing forum pattern.Expected results
Actual results
Before the fix, pathauto provided the Forum alias type itself: Forum was listed in the Pattern type select, the forum pattern generated
/forums/general-discussionfor the default forum term, and that alias resolved in the browser. After applying MR !182, Forum was gone from the select, the pre-existing forum pattern was shown as Broken type, and re-saving the forum term produced no alias — as expected, since nothing provides the plugin at that point. After additionally applying forum MR !38, the pattern type read Forum again, the same pattern configuration was reused without any change, and re-saving the term regenerated/forums/general-discussionidentically to the pre-fix baseline. No errors were logged in any of the three states.Notes for the maintainer
drupal/forumconflict constraint) covers this.PathautoGenerator::updateEntityAlias()still contains forum-specific handling that readsforum.settingsand overrides$typetoforumfor terms in the forum vocabulary, together with a@todo Update and test forum related codecomment. It is harmless today because$typeis only used for the child-term recursion, but it is leftover forum coupling that this issue arguably should also remove.Testing produced with the assistance of an LLM.