Closed (fixed)
Project:
Taxonomy Term Permissions
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Oct 2010 at 02:53 UTC
Updated:
3 Nov 2010 at 06:31 UTC
It looks like we can not use this module, although we want the same result.
Planning to implement a simple role to term table, that defaults to having roles 1 & 2 added for every term. Then using rewrite_sql, filter the results on all term queries.
If this works, would you want to implement this in this module or should I look at another project for it?
I do not plan to create the batch process that will be required to generate the initial term - role relationships post install, (no time), simply doing this step with a long timeout.
Comments
Comment #1
alan d. commentedThis falls down on one of the requirements that the client has sadly. I will not be pursuing this any further.
It would be great to completely allow or block access via a role however :)
Comment #2
alan d. commentedIn case someone whats a head start, here was the code: It was never even run.
The core rewrite is not completed, and was where I discovered that this would not work as there is no way to determine where the query is generated from. The base table is also not populated with default term role values.
Queries in Drupal 7 are tagged, so this approach may work on this system.
File: term_roles.info
File: term_roles.install
File: term_roles.module
Comment #3
deviantintegral commentedThanks for at least considering to contribute your work! I'm not a huge fan of db_rewrite_sql(), but for D7 I could see adding WHERE clauses as being a much saner design. If you end up being able to work on this, feel free to reopen this issue.