Hello,
Thank you for a very powerful and feature rich program. While I am deriving much benefit from Drupal, I find that the one layer of administration is a bit of a limitation. By this I mean that if a user has Administer Node access, then they can administer ALL nodes. Also, only roles with Administer Nodes can publish/approve content.
What I would like to see is a second level of administration that would allow another role to administer content based on the Taxonomy_access. By this I mean that is Role 1 is permission assigned to Taxonomy 1, and Role 2 is assigned permission to taxonomy 2, then Role 1 could approve content submitted for taxonomy 1 but not taxonomy 2, and Role 2 could approve content submitted to taxonomy 2 but not to taxonomy 1. My understanding is that only the over-all Administer Nodes role could approve content equally to both these taxonomies.
If this has already been done, then please direct me to the appropriate module or instructions on how to achieve it.
I am using 4.7.0 and Taxonomy Access. I will also try OG to see if that provides what I am looking for.
Thanks in advance.
Comments
Comment #1
magico commentedComment #2
Kieg Khan commentedHello Magico,
I am not sure what your post is trying to tell me. Does 4.7.0 allow this, or is it being considered for 4.7.0?
Thanks.
Comment #3
magico commented@Kieg Khan: sorry for not being more explicit. Whenever a feature request is made, it must be against HEAD branch. This happens, because new features are only developed on HEAD and never on stable releases (like 4.7).
Comment #4
Kieg Khan commentedThanks,
So does this mean that the feature is available in CVS, or does it just mean you will suggest it for CVS? If it is available then I will take a look at CVS and see how it is going.
Bye.
Comment #5
magico commentedThis means that the feature was suggested for future development on HEAD.
See http://drupal.org/handbook/version-info
Comment #6
LAsan commentedComment #7
marcingy commentedBumping to d8
Comment #8
rfayI have no idea what this is about, but it was misclassified.
Please close or put it in the right place or something. Looks to me like it's dead.
Comment #9
xjmI believe the user is requesting some sort of bridge module between TAC and some other module. Closing since there has not been any action on it since 2006.