I have a content type with terms from two vocabularies (Alfa and Beta). With autocategorisation turned off, the links for terms from both vocabularies show up regularly at the bottom of the node display. However, as soon as I turn on autocategorisation for vocabulary Beta, the links for vocabulary Alfa disappear from node display. I believe this is not a duplicate of http://drupal.org/node/444124, as I am not trying to use autocategorization on both vocabularies.

CommentFileSizeAuthor
#6 termreplacement-457316-5.patch1.09 KBbrycesenz

Comments

skizzo’s picture

Title: Existing taxonomy link disappears when adding autocategorised vocabulary » Existing term (vocab X) removed when adding autocategorised term (vocab Y)
Priority: Normal » Critical

Apparently when the Beta term is applied to a node all existing terms from other vocabularies are deleted.
Marking as critical, as it can result in data loss for existing installations.
Rewording title to better describe the problem.

skizzo’s picture

Status: Active » Needs review

Big thanks to matslats for fixing this issue in 6.x-1.4. I could only test it functionally and it seems ok. Changing status to needs review in case someone else is willing to carry out further testing, or review code.
Note: warning on update.php from 6.x-1.3 to 6.x-1.4 can be ignored.

mkinnan’s picture

Version: 6.x-1.3 » 6.x-1.4
Status: Needs review » Active

I am experiencing this problem as well. All the terms in my taxonomy categories (except 1) get erased for a node when I have one category as autocategorized.

I changed the Version to reflect that this issue does not appear to be fixed in 6.x-1.4.

szy’s picture

It still active in DEV from 2009-Aug-29.

If modules developer doesn't care about critical issues
for months, I don't think it is safe using it... :/

Szy.

brycesenz’s picture

subscribing. This is still a major problem for me.

brycesenz’s picture

Status: Active » Needs review
StatusFileSize
new1.09 KB

Ok, I think I've got a solution for this. The attached patch is against the latest -dev version. It seems to be working fine for me.

brycesenz’s picture

Status: Needs review » Fixed

This is fixed in the latest dev version (September 17th release).

Status: Fixed » Closed (fixed)

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