First: thanks for the awesome module.

This patch makes community tags support more than one vocabulary per node type.

Changes:

* Support of multiple vids in form building, js, term saving and term display
* Use vocabulary name as label for forms
* Adjust settings page
* Implement nodeapi(delete, ...) operation (OT, slipped in)

I tested with 2 different vocabularies on 2 different node types with different user permissions. Seems to work fine. We will use this patch in a production grade site from the beginning of January on.

If you review this code, please cast your critical eye on the lines following the comment "// Re-insert the existing tags we haven't already added back in (incl. other users' tags).". I am not sure whether I'm not missing sth there.

This patch doesn't change much when you use only one community tags vocabulary per node type. For our current project this feature is vital though, as it allows us to track all different kinds of tags on a per user basis. This patch will essentially allow us to switch over from taxonomy_user - I plan to abandon this module in favor of community_tags.

Alex

Comments

alex_b’s picture

any news on this?

alex_b’s picture

news?

owahab’s picture

Alex,
I have been busy the past time.

I am reviewing and testing this patch and will update this ASAP.

dropcube’s picture

Version: 5.x-1.x-dev » 6.x-1.x-dev
Assigned: Unassigned » dropcube
Category: task » feature

Assigned to myself remembering to review this patch.

alex_b’s picture

We've been working with a version with this patch for a while in production and everything seems to be smooth. Didn't do specific testing though.

rssfrrst’s picture

I'm working on a project that needs this feature - my users need to be able to tag everyone's images under multiple categories. I've looked at other free tagging modules but none come close to being as good as community tags.

I'm pretty new to drupal - I attempted to patch my module but it didn't work, possibly due to the patch being for an older version?

Any help would be appreciated!

henrijs.seso’s picture

subsr. need to use 2 dictionaries of LIKE and DON'T LIKE on user profile nodes. Only profile author could add tags.

chrisirhc’s picture

Version: 6.x-1.x-dev » master
StatusFileSize
new11.32 KB

I've made some adjustments, while working with the code from HEAD (so there is a minor change to make it work with the regular vocabularies).
Hopefully, this will raise some interest in this.

Next I'm going to work on making it work with regular vocabularies properly, by respecting the taxonomy settings, i.e. not adding any terms. (I'm thinking of using Radio options instead of a text field for those disallowing multiple selection)

I believe that the non-AJAX form submission is broken after this change. More work has to be done on that part.

entrigan’s picture

I applied the patch but it seemed to break the ctags form. I think this functionality is important, and it would be great if we could also support all types of vocabularies.

I just synced 2.x and HEAD so maybe that changed some small things.

entrigan’s picture

Version: master » 6.x-2.x-dev
Assigned: dropcube » Unassigned
Status: Needs review » Needs work

Can we work on this against 6.x-2.x? since it is easier to do all of the committing there and then sync HEAD only when needed.

chrisirhc’s picture

StatusFileSize
new8.99 KB

Sure, I've made some modifications to make it work (unbreak) with the form validation.

Here's the patch to use with the current 6.x-2.x sync.
Let me know if there are any problems. I haven't done extensive testing of it as of yet.

After this, I went on to add radio buttons as a widget to pick to taxonomy (for regular and non-multiple vocabularies). I'm not sure if there's a shortcut to creating those kind of forms and, if possible, I think the best way is to allow any Content_Taxonomy (CCK) widget to be used when choosing the tags. What do you think?

I haven't looked much into it yet except for a thread and the Computed Field module which I'm not sure if it's what I'm looking for.

entrigan’s picture

So I apply the patch on a fresh 6.x-2.x ctags and I am getting some very strange behaivor. I create a few vocabularies, and mark them as ctag vocabs. Then I go to tag a node, and the ctag form submit buttons all say undefined, and no tags are listed (in the ctags form that is).

So I unmark for ctags all of the non-free-tagging vocabs, and the ctags form now properly displays, but the tags disappear after any ajax action, giving the message: warning: Missing argument 3 for community_tags_get_user_node_tags(), called in /Applications/MAMP/htdocs/repo/ctags/sites/all/modules/community_tags/community_tags.ajax.inc on line 29 and defined in /Applications/MAMP/htdocs/repo/ctags/sites/all/modules/community_tags/community_tags.module on line 250.

entrigan’s picture

StatusFileSize
new10.39 KB

Updated community_tags.ajax.inc and I rerolled the patch with the changes. This patch includes the patch from #11.

This patch fixes the ajax form functionality (or at least partly)

chrisirhc’s picture

Sorry about that. I missed out the ajax file while I was posting the patch.
The changes you made are pretty much the same as what I have on my side.

chaps2’s picture

Status: Needs work » Fixed

Thanks for all patches and contributions! This is now fixed in 6.x-1.x-beta4.

chaps2’s picture

Version: 6.x-2.x-dev » 6.x-1.0-beta4

Status: Fixed » Closed (fixed)

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