- Nope
1 week 6 days ago - do you have any other blog or
1 week 6 days ago - Corsix is in the back row,
6 weeks 2 hours ago - Wow, awesome write-up!
6 weeks 2 hours ago - any other place?
8 weeks 2 days ago - Maybe, but I'm not sure
27 weeks 3 days ago - Was already possible with comment_cck + content_taxonomy
27 weeks 3 days ago
Recent comments
Comment alter taxonomy module: One step closer to issue tagging on d.o
Sun, 02/17/2008 - 20:20 — aclight
I've just committed the first code for the new comment alter taxonomy module. This module will allow users with certain permissions to change taxonomy terms associated with a node from comments on that node. The main motivation behind this module was to make it possible to have labels/tags on project issues like "needs doxygen", "benchmark", and "newbie", etc. Instead of just adding this functionality to the project issue tracking module itself, I thought it would make more sense to create a generalized module that works for all node types, not just project issue nodes.
I've written this up in a bit more detail at http://groups.drupal.org/node/8968. I'd love to get some feedback on potential use cases for this module as well as feedback on certain design decisions I made.
Here's a screenshot of an example issue where a term has been altered via a comment.
| Attachment | Size |
|---|---|
| cat_example1.png | 56.81 KB |
Comments
do you have any other blog or
do you have any other blog or place where you share more about this module and other drupal experiences, like your stage at Drupalcon?
Nope
No, for the moment this is it. What specifically would you like to know?
any other place?
sorry for commenting here... do you have any other blog or place where you share more about this module and other drupal experiences, like your stage at Drupalcon? the topic is promising, but the place looks a bit empty...
Was already possible with comment_cck + content_taxonomy
This was already possible with comment_cck and content_taxonomy!
Maybe, but I'm not sure
I myself did not go through all the available modules before writing this, but I have a feeling that comment_cck and content_taxonomy would not quite be acceptable alternatives here. If you want to start reading the original free tagging on issues feature request at http://drupal.org/node/187480#comment-626854, several possible modules that already existed were discussed, but each of them had problems that would keep them from being right for the task. Furthermore, the plan is to deploy this on d.o once it's finished, and I get the feeling that those in charge are not ready for a full on CCK deployment on d.o yet. Assuming that's the case, that would eliminate comment_cck and content_taxonomy from solving this problem on d.o.
The other thing is that as far as I know, comment_cck does not store each change made in a comment so that each comment can show changes made in that comment. So, with project issue, if you change the status in a comment, that change is shown in your comment and also shown in the main metadata table at the top of an issue. AFAIK, comment_cck would show that change at the top of the issue, but it would not be clear which comment actually changed a term of the issue.
Lastly, a good bit of the module is implementing new project_issue hooks that allow modules to indicate their own changes so that they are displayed in the metadata tables. Regardless of what module ended up getting used to solve this problem, it would need these hook implementations, so my new module isn't that much duplicated code, if you want to look at it in that way. :)