Now that we have #841804: entity_uri() should be used wherever possible committed and am very close on #288639: Taxonomy term aliases are build against incorrect source paths there should actually be no reason to special case the handling of forum module. Since we will be using taxonomy_term_path/entity_uri everywhere, we can just re-use the existing taxonomy pathauto support. Yay for more simple code!

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Dave Reid’s picture

Priority: Normal » Major
Dave Reid’s picture

Status: Active » Needs work
FileSize
7.16 KB

Hrmf, the taxonomy and forum modules keep separate UIs, so I'm not sure how much of this makes sense to do. This definitely makes things a little more difficult if we want to generalize with entity information.

...

Dave Reid’s picture

Assigned: Dave Reid » Unassigned
Priority: Major » Normal

Bumping down in priority

Dave Reid’s picture

Assigned: Unassigned » Dave Reid
Priority: Normal » Major

Bumping back to major as I would really like this solved before 7.0.

Dave Reid’s picture

Status: Needs work » Needs review
FileSize
8 KB

And now here's the working patch with update function. This is ready to roll for me.

Dave Reid’s picture

Without setting a forum variable this time.

Dave Reid’s picture

Dave Reid’s picture

Dave Reid’s picture

Priority: Major » Normal

This can wait until after a 7.0 release.

Scott J’s picture

OT:
What would be really good, is for Drupal core to stop special-casing Forum module (and Blog for that matter), and just make their functionality available to ALL content and taxonomy types.