By spanders on
I'm setting up a permissions system on my site using Taxonomy Role, and I feel like I'm starting to get a lot of roles in my database. I'm at 12 I think.
How many roles is too many? What if I need 100 or 1000 to setup my permissions correctly? Is that okay, or should I try to find another solution now before I get too far along in the process?
Comments
You do not say how many
You do not say how many users you have but 1000 sounds like too many and a 100 if not too many it would be hard to manage. You might want to explain what you are trying to do (ie limit permissions in what way) and someone might have a different approach.
what I'm trying to do
I'm trying to use "Taxonomy Roles" to implement multiple different blog rolls on my site. Every user has their own blog, but when making a post, I'd like people to be able to select "Additional Blogs" to submit the post to using Taxonomy. Then use Views to display the additional blog rolls.
http://mysite.com/blog/DailyPhoto
http://mysite.com/blog/DailyTip
For instance, if I add a blog post, I might want to include my blog post in a a blog roll called "Photo of the Day". A different user on my site could submit their blog entry to "Tip of the Day" but not "Photo of the Day"
So I think I need to have one category for each blog (with terms 'Yes' & 'No'), and then one matching role for each blog roll, so I can use taxonomy roles to control who can post where.
I don't think I'll have 1000 different blog rolls, but I might, you never know.
I find this an interesting question
I wonder how much overhead adding a role contributes to an overall drupal installation? How would one test this in a "real world" type situation?
Is 10 roles excessive?
--
Veneer | Crack-proof Creative
http://www.veneerstudio.com
Civicsolar
http://www.civicsolar.com
too many roles
I have a comparable problem: I'm thinking out a way to let somewehere between 60 to 300 groups of users (a group may consist of one to aprox. 12 persons) to edit a page (in fact I want them to be able to edit a group of pages, but for the sake of argument I am first trying to tackle the simple proposition.)
I can do so making 300 roles and then constrain the access to the mentioned pages by taxonomy access.
But this will become unmaintainable, let alone the image of the oversized acces table in admin on adding a new module.....
To answer your question: I think 12 's already quite a lot to handle. With something like 100 roles you would need an extra rolemanager module simply to keep track of that lot.
I am now contemplating family relations between users. I want to be able to define users as siblings, or give them mother child relations. And then I can regulate access by simply tracking the relation between the current users and the user who owns a certain page. Anyone found a solution for this kind of problem?
Egbert - webdevelopment and implementation - www.overboord.nl
organic groups?
spanders,
I wonder if the Organic groups module would do the trick for you. You could create a custom node type (which you can even call "blogroll") to use as your group nodes. One would be "Photo of the Day," one "Tip of the Day," etc. You can enroll individual users in just the "blogroll groups" to which you want them to be able to post, and for each blog post that they write, they can decide which "blogroll groups" to post to.
Thanx grobemo. Am right in de
Thanx grobemo. Am right in de middle of the OG modules now. Seems to be exactly what I need.
Now I want to change the permissions of all members of a group in one action. For instance: I would like to change a taxonomy of the group node, and by that change the permissions of all group memebrs.
Egbert - webdevelopment and implementation - www.overboord.nl
Check out the access control modules
There are lots of access control modules out there. I haven't used many of them, but here are two that seem promising: Taxonomy Access Control and Taxonomy Access Control Lite.
Thanx for your comment, we
Thanx for your comment, we use them a lot, but for this implementation I do not have to change or control the access to the nodes, but merely open up a lot of extra functionalities to all members of a group. The logical way to do this is by changing role settings. This would greatly simplify the construction of this community site we're building. Simple is Wise, is my motto.
The problem is, as most of the time, the webmaster. He/She needs a simple interaction, not a long protocol like: 'on changing the status taxonomy of a group node to "member" go to this view, select al members there and go to the user panel and change all of their roles from "aspirant" to "member"'
Would be nice to have some jquery widgets that would like hover over the site and could be configured to perform complex maintenance tasks. Drupal maintenance helper bots :-)
Or maybe that's a crappy thought.....
Egbert - webdevelopment and implementation - www.overboord.nl
I'm curious what you decided on
I have a similar problem where I have to find a way to sync hundreds of roles from our agency's network and multiple databases' roles with a drupal site which will be serving as an extranet. I'm going with a single-signon type approach, but I fear simply copying this many roles over is a scalability mistake and am looking for a better way to go about this. It looks like Organic Groups and OG Access may be the answer. Am I on the right track?