Every node is assigned the category of the last term
a great place f... - September 25, 2008 - 12:45
| Project: | autocategorise |
| Version: | 6.x-1.2 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Description
I created a test category with a stack of terms in it then go back to edit the vocab and hit autocategorize.
I get a stack of Invalid argument supplied for foreach() ....line 114 errors and every node is assigned to whatever is the last term in the vocabulary. If I change the order of the terms it is still whichever term is the last one.
I'm running D6.4 and all the modules are up to date, I disabled the vocab index module.
#1
This goes for 6.x-1.1 to, this bug is really making things not working at all.
#2
I have the same problem. Using Drupal 6.6....
I created a new taxonomy with a couple of terms... however, no matter what text I use, last term always gets published/selected as the tag.
Anyway, ideas how to fix it?
Thanks!
#3
I'm experiencing the exact same problems on Drupal 6.6
Aside from that, the module works great. I too would like to see this fixed.
Thanks for your work.
#4
Sorry about the delay in replying. The rss notification stopped working...
I think this happened because you didn't read the instructions. The matching happened not against the term name but against all the synonyms of a term.
As of now, the term name is included in the list of synonyms,
Coming soon... regular expression matching!
Matthew
#5
The module "assumes the last term is a 'misc' ". I commented it out here.
**From**
$matches[]=$catch_all_tid;**To**
//$matches[]=$catch_all_tid;#6
It only assumes last category is misc if the vocabulary is 'required' on the vocabulary settings page
#7
This appears to not be the case - I have made the vocabulary not "Required" and it still applies the last term to every item...
#8
Like #7. Using autocategorise.info,v 1.2 2009/05/14 18:51:04. Everything gets into that last term bucket.