Taxonomy Role module is obsolete in Drupal 7

I'd like to see this in D7 as well. I have a use for it right now. :D

Ditto. I have an excellent use case for this module and have it in productions sites right now. It's great for restricting access to taxonomy trees based on role, almost a critical tool for managing small publishing workflows.

How can I help with the port?

I recently found the Field Permissions module that does pretty much what this does, just you can apply it to any field.

Good point. Since taxonomies are stored in fields, and the D7 Fields API has a field permissions module that controls who can access a field based on role, then this module does not need to port to Drupal 7.

Unless someone wants to build a migration path for elaborate taxonomy role implementations. If so, go ahead and reopen this thread.

Terms reference field attached to hierarchical select, we have a requirement for to select a role though Hierarchical select, I think this module will help us in our scenario.
If some one could port is please?

I'm porting my site to D7 and my site relies heavily on this module to publish and place nodes.

What happens when this isn't available?

I'm closing this issue again. The Taxonomy Role module is obsolete in Drupal 7.

If you are looking for a D7 port then follow along here, this is the answer. Taxonomy terms are now stored in Drupal 7 core fields. The D7 Field Permissions module allows you to control access to those fields based on roles. Make a new taxonomy vocabulary, create a field on your content type, then set the field permissions to your liking. Be sure you don't create a required taxonomy field that is not accessible to your content creators - that will prevent them from submitting new nodes.

The comment on #6 is unrelated. Hierarchical Select is a different module that is only an input method for selecting taxonomy terms. It has nothing to do with granting permissions to fields.

The Field Permissions module misses an essential part: it does not hide the taxonomy/term/TID pages, which show teasers of the nodes that are tagged with the given term.

@salvis The scope of this Taxonomy Role module is to prevent users from seeing certain taxonomy fields on the node creation pages. It sounds like you are having problems with making nodes private based on a taxonomy field, and that is not the function of this module.

If I am mistaken, then you should open a new ticket for this issue anyway.

From the front page:

The purpose of this module is to provide a way to restrict which vocabularies show up on the node forms. This allows you to do things like setup vocabularies for administrator-only use or for any other purpose where you want only certain roles to see or set vocabulary terms on the nodes.

This is more than what you write in #10 above.

To me this reads as "hide a vocabulary and its terms from non-administrators", which is what I'm looking for. Field access only hides the terms on the node pages, but it does not hide the term pages themselves, so the terms (and which nodes are assigned to them) are visible for anyone who bothers to enumerate the TIDs.

(Not sure under which title to open a new ticket if not under "D7 Port", which was the title of this thread before you changed it under an erroneous assumption.)

This module won't be ported over to D7 because its handled in core now. Since this module has not been updated since 2011, I bet that you're not going to get any solution on this module issue queue.

I suppose you are welcome to keep this issue open, but maybe you would have better luck meeting your goals if you look to the Views module to override and restrict access to the taxonomy term pages you're concerned about in D6.