Node comments inherit parent node taxonomy term

Ok, here is what I think you have to do.

1) create a module weight a weight higher than nodecomment so it runs last.
2) create a form_alter on the node edit form. Look for $form['#node']->comment_target_nid -- if that exists, the form is a nodecomment and that nid is the original node.
3) Make sure your vocabulary is valid for your nodecomment node.
4) Using your form alter, change the #access on the select select for the vocabulary in question to hidden and place the terms from the parent node in the #value for that widget.
5) You may then need to manually edit and save existing nodecomments to get them categorized.

ACtually, in forums you specifically do *not* want the comments to inherit the terms, because then they will show up as top level forum posts. We call that bad.

Any word on this? It's been a few weeks. Kind of surprising that the concept of taxonomy inheritance was not one of the primary design goals of these two modules to begin with, since it is a built-in aspect of the default forum and comment Drupal modules.

Sorry, if my answers are not good enough, you're out of luck. I've answered more than adequately.

merlinofchaos, thanks for the quick reply. I'm not going to re-activate this issue, so hopefully you see this comment on a closed issue.

I believe I understand the rationale for not implementing this if one assumes post #7 is true. I don't understand why #7 is true, though, so perhaps I need to do more research. I would assume that the "top level forum posts" would be only forum nodes, not comment nodes, page nodes, or any other node type. The only way I could see #7 happening is if "top level forum posts" is defined as any node which has a forum taxonomy term selected. Is this the case?

Edit: I created a page with a forum taxonomy term. I didn't see the page included as a top-level forum topic, so I was not able to recreate the circumstances of post #7. I also tried it with a comment for completeness sake, with the same result.

That is, in fact, the case. Forums are not restricted to just the 'forum post' type.

Note that with nodecomment 2.x there is a relationship you can add, 'parent or self' or something like that, that you can use to get the right node to check terms against in a view.

Oops, I didn't expect you to reply so quickly so I edited post #13 with an update. So that I don't mess up the comment order logic, I'll repost my update here:

I created a page with a forum taxonomy term. I didn't see the page included as a top-level forum topic, so I was not able to recreate the circumstances of post #7. I also tried it with a comment for completeness sake, with the same result.

Yeah, that's a feature I may have to use. I was hoping to just use the base-drupal taxonomy system (e.g. taxonomy/term/1), which is simple. But I guess without nodecomment taxonomy inheritance, the views relationship method is the way to go, despite its complexity.

To make this there is a more easy way.

with hook_nodeapi:

<?php
 case 'comment':
      if($op == 'presave'){
        $node_father = node_load($node->comment_target_nid);
        $node->taxonomy = $node_father->taxonomy;
      }
    break;

?>

Only hidden the taxonomy as say merlinofchaos