March 3, 2009 - 7:18pm
Taxonomy Access Control Lite
I'm pretty sure that you can do what you want with the Taxonomy Access Control Lite module. I usually use this module to control access using user roles but I'm pretty sure that you can also configure classes by individual users.
I wholeheartedly support the idea of not using the inherent Blog module.
Curt
March 3, 2009 - 7:39pm
TAC
I used TAC (or TAC Lite) once before, but as I recall, the focus was on using taxonomy terms to set permissions on pages. In my scenario, I'd want all blog contributors to be able to access the blog add/edit pages, but be able to select only certain taxonomy terms - so the permissions would be on the terms they could choose, not on pages (as set by terms).
March 4, 2009 - 12:04pm
A couple of thoughts
I just took a look at one of my sites where I'm using TAC Lite to control visibility of pages containing particular access tags. It looks to me like you can configure multiple "schemes" to control different access permissions, e.g., view, update, delete.
Brute force thought: How may different "blogs" are there? If the number is relatively small then you could create a different content type for each and control create authority that way. It's not very elegant, but it should work.
Curt
March 4, 2009 - 12:16pm
TAC
Hmmmm...
Here's the thing. As I am picturing it, I'm not wanting to control access to pages. I just want a contributor to only be able to see the taxonomy terms they are allowed to see in the "Which Blog?" pulldown. So the master vocab would have these terms:
Science Blog
Arts Blog
Business Blog
and user A would only see "Arts Blog" on the pulldown, since that's the only blog they have permissions to post to.
My guess is, there's no way to do exactly this. But I'm thinking there must be some way to do something similar - without resorting to different content types for each blog and managing permissions that way.
March 10, 2009 - 10:14pm
Darn good question
What I would do....
I would build it to show all taxonomy to everyone. Then I would go back with hook_form_alter and remove the ones a user shouldn't see by setting it's element in the form array call '#access' to FALSE. Does that make sense or is that too deep?
March 11, 2009 - 11:02am
get yer geek on
That sounds like a pretty coder-y (but flexible) solution. The mention of hook_form_alter makes my eyes glaze over a bit, though. I took a peek at Addison's tutorial at http://www.lullabot.com/articles/modifying-forms-5..., and it seems to make sense (I have to read slowly and put my concentration face on). It seems very similar to setting up preprocess variables - just stuff a new value in. The part I have no idea about would be how to remove entire choices (array indexes?) based on the user.
March 11, 2009 - 11:21am
March 11, 2009 - 11:33am
Term Permissions Module???
I am EXTREMELY interested in this too.
I found the Term Permissions module, and from the description, it looks like exactly what we are talking about!
BUT, I have not tried it out yet.
Also, I am not sure how active it is. There is only one -dev release back in 2009-Jan-18.
A couple of episodes back, Matt mentioned the idea of skipping the blog module and just creating a custom 'blog' content type. The idea was that you could let anyone post to any blog, and use a 'pulldown' to choose which blog the post goes to. I am assuming what he was referring to was having a taxonomy vocab whose terms are the different blogs on the site. Doing views based on these terms would split the blogs up nicely. My question is - how can I do a setup like this, but make it so that each user can only post to certain blogs? I want to keep everything separated. I know I could do this if I used a whole different content type for each blog, but that would be kind of kludgy, Using taxonomy (or even a CCK field) would be more elegant. Does anyone know?