Because we needed such functionality we've custom wrote a little piece of code that actually let's you choose to limit the autocomplete results to leaf tags only, and another one that lets you limit the tags to existing tags only.

Because we are having a hard time patching the module with every new version that comes out we were thinking to ask you if this sounds interesting enough to include it in the next version of the module.

I can upload a patch for the current version if you want to take a look first.

Thanks, Mihai Fratu

Comments

dragonwize’s picture

dragonwize commented
Status: Active » Closed (works as designed)

Read over the project page on what AT is and is not. This feature request should be directed to the taxonomy module you are using. I believe content_taxonomy already has all of those features.

kerberos’s picture

kerberos commented

Hi Dragonwize.

Content_taxonomy uses CCK for storage. Our patch does not alter storage or performance in any way. We have three changes that simply add more versatility to ActiveTags and were wondering if you are interested in incorporating any of these into Active Tags. In theory, we could branch our own module, but I don't think that would serve anyone's interests. The three changes are:

1) On the autocomplete (AT uses the Drupal built-in auto-complete, we expanded it to use a modified version thereof) we also show the parent categories (if any) of a tag. This helps users to see how an existing tag fits into the taxonomy if there is an existing hierarchy.

2) Option in the taxonomy admin interface to prevent creation of new tags (so ActiveTags becomes a selection-only tool). We think it's the best selection tool out there, but we don't want to allow the creation of new tags in all circumstances. This is merely an option, so can be turned on and off depending on vocabulary.

3) Option to allow selection of leave-only tags (tags with no children). In the same vein as the options before, if you have a hierarchical taxonomy, sometimes you only want child tags to be selectable, not parents. Again, this is a per-taxonomy admin option.

We feel there may be other users out there that could benefit from these fully optional additions and we did not want to create yet another taxonomy select module. Please let us know what you think. We will use the module on several production sites and are willing to assist in the maintenance of this side features if you are worried about that.

-Daniel
Adulmec

dragonwize’s picture

dragonwize commented

As stated on the project page, AT is designed to be a light weight javascript widget that does not touch the backend of the taxonomy system in place. There are many, many modules that affect how both the core taxonomy module as well as content_taxonomy work. BTW content_taxonomy saves both in CCK and in the core taxonomy tables.

My suggestion to you is that if you can not find a module to do what you want to the core taxonomy module or content taxonomy module, to build a module that affects the backend for the functions you desire and let AT handle the display so you do not have to duplicate that work. Ultimately the best way is to submit your patch to the appropriate issue queue to get your feature included in the proper taxonomy backend module.

mpavankumar’s picture

mpavankumar commented

Hi Daniel,

I am looking for a similar functionality relating to hierarchial taxonomy autocomplete which you have mentioned. It it possible for you to upload the patch/module you have created.

Thanks,
Pavan