I have a vocabulary of university name abbreviations, many of which are 3 letters long. My users tend to use these abbreviations quite frequently, and I want to automatically tag forum posts with them.

However, the _autotag_search_field function has a line of code the purposely ignores any words less than 4 letters long, so none of the 3 letter abbreviations are getting tagged. I'm referring in particular to the "if" statement on line 44 of autotag.functions.inc

I would suggest either eliminating this restriction all together, or at least adding a user setting that allows the admin to specify what minimum word length is going to be enforced. Or perhaps another option is to scan the vocabularies, see what the smallest term is, and use that as the cutoff.

For the time being I've hacked my version to eliminate the minimum, but would be nice to not need to hack it.

In any event, thanks for a very useful module.

Comments

sdrycroft’s picture

sdrycroft commented
Version: 6.x-1.27 » 6.x-2.0

This definitely makes sense - I like the idea of checking for the minimum length of words in the taxonomy/synonyms table first, and using that. I'll see if I can get this into v2 of the module.

protoplasm’s picture

protoplasm commented

Agreed. A highly useful module and thanks for it. I have made a similar hack because my vocabularies include names like some company names for example, W. S. George. Using George without the W. S. is too generic and creates a non-specific feed. Looking forward to eliminating the hack.

iantresman’s picture

iantresman commented

It does seem odd to check for taxonomy term length; if a tag is 2 or 3 letters, then so be it! So yes please, can we have the option to specify the minimum term length (eg. 1, 2, 3 or more letters).

solidad’s picture

solidad commented

I am guessing this was never addressed or fixed? I have 3 character terms like "red" that I need to have auto-tagged.

sdrycroft’s picture

sdrycroft commented
Issue summary: View changes
Status: Active » Closed (won't fix)

This was fixed in the 7.x version of the module. I'm afraid no further development will be carried out on the 6.x version of the module.