I've found that using a vocabulary that applies to more than 1 content type makes all of those content type's nodes editable. Is there a way around this, or another module that works in conjunction with tac_lite to make it so that I can choose the content types allowed to be edited as well?

I've attached a comp of what I think the UI could look like if tac_lite did this. This may go against the philosophy of keeping this module 'lite' but it'd be a really useful feature (in cases where vocabularies go across 30+ node types and users shouldn't be able to edit each content type when they can't even create them).

CommentFileSizeAuthor
tac_lite_by_content_type.gif10.71 KBbsuttis
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Dave Cohen’s picture

Dave Cohen CreditAttribution: Dave Cohen commented
Title: Restrict by node type » Restrict node_access by node type (tac_lite)
Status: Active » Closed (won't fix)

I'm 99% certain this is "won't fix". As you said, it conflicts with the lite philosophy. It's a good candidate for a helper module. See #309007: Add drupal_alter() after hook_node_access_records(), which will make such things possible, but not in Drupal 5.x.

Have you thought about using multiple vocabularies? If you're defining custom node types in modules, you can write more complicated logic into hook_access.