Canonical taxonomy term link for forum vocabulary is broken

Forum is approved for removal. See #1898812: [policy] Deprecate forum module for removal in Drupal 11 →

This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

It will be moved to the contributed extension → once the Drupal 11 branch is open.

Hey @ravi.shankar The is not working with drupal 10.2
it patched the still facing the same issue with "forum/13" instead of "forum/all-discussion"
I see in the alias list, the alias is there for taxonomy but it redirects to "forum/13"
ANy solution to this?

Any Solutions for Drupal 10?

I am also encountering this issue in Drupal 10. For example, I am seeing "forum/1" instead of "forum/sports".

This is my path alias pattern:

forum/[term:parents]/[term:name]

Turned patch #150 into a merge request for the new module (had to do a little convincing to get the patch to apply to the standalone module). Also, updated the deprecation info (I missedn #154, but the updates in there are obsolete anyway; I take it Forum will be doing its own deprecations, independently from core).

Still need to actually tests whether it (still) resolves the problem, although I suspect the latest reports of it not working are running into the standalone module being installed, while the patch applies to the core version.

OK, seems to still work.

Thanks everyone for working on this, the MR works well, and I get the desired paths, after patching the Forum module.

Where URL aliases were previously ignored for Containers and Forums, and "forum/1" used instead of "forum/sports/badminton", with the patch and the Pathauto alias pattern forum/[term:parents]/[term:name], the correct alias is generated.

Hi, i too applied the patch: 2010132-154.patch - and add this two pathauto field:

Seems to work as expected now :)

Looks great @salvatoren, thanks for confirming!

Hopefully, since Forum is now a contrib module, this great update can get committed before too long. It would be epic to land this 12 year old issue, way back from June 2013 :)