Autocatagorise seems to interfere with forum module.

Have Blogs (with one vocab + autocatagorise) and Fourm (with second vocab w/o autocat). Create/update nodes of type blog work fine. The Taxonomy selector appears, even though this will evidently be overridden by the modules function.

Forum Topic nodes do not exhibit the "Forums" selection list (i.e. the taxonomy selection). This is true for the Create and Update actions. One simply cannot assign a forum topic (i.e. taxonomy) to these nodes.

Disable the autocatagorise module and normal function of the forum module returns.

If autocatagorise is not selected for a given vocabulary, it appears to leave the core taxonomy intact - except for the forum module and/or the forum topic node type.

Comments

matslats’s picture

Autocategorise removes the taxonomy select widget from the node form for all nodetypes to which the autovocabulary is assigned.
What you describe here could be accounted for if you had checked the wrong content type on the vocabulary properties page.
If that's not the case can you let me log in and see?

matslats’s picture

Status: Active » Fixed
wtopper’s picture

Status: Fixed » Active

Forums module (core) uses a distinct vocabulary. Autocatagorise was not enabled for this vocabulary.

No other vocabulary was assigned for the node type "Forum topic".

I have the version installed on a development instance. Access credentials were sent via contact email.

wtopper’s picture

Good progress working with matslats. I think he's got it sorted out and an update is pending.

Thanks again for the hard work and a fine module!

ManyNancy’s picture

Doesn't seem fixed yet.

To decrease the chances of someone breaking things by turning it on for forums, if this isn't fixable can you disable the button for forum?

Thanks.

wtopper’s picture

Error still exists in 1.3 - agreed. I had been using a DEV version that was working. Fix must had been lost in the CVS updates.

matslats’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.