I'm running a site that has *mostly* restricted content that anonymous users should not see. Yet, everytime a new category is created, they are able to view it unless I remember to change the new category's "view" permissions for anonymous users.

This is a problem. Not only is it a pain to have to change these permissions each time a category is created, it is a big security hole because it's very easy to forget to change the permissions.

I'd like to see the "default" permissions feature re-introduced back into the module. I'm willing to pitch in and help.

Comments

pyromanfo’s picture

pyromanfo commented

I think it'd be fine as long as two things are kept in mind
1) the original way it worked, with default being applied along with specific permissions for each node is bad. Default should be what a category gets when it is first created, this should be pretty easy
2) The UI is clear and explains this

I think if implemented that way it'd be much less confusing than before, and a whole lot easier too. Let me know what you think. It could probably be done in a variable_set/get command so there wouldn't need to be any database changes.

nazadus’s picture

nazadus commented

I'm going to have to say that I absolutely hate updating my taxonomoy_access module becuase I have to recreate the permissions which takes forever. Most of my stuff is public accessible except for a few sections and misc create permissions are granted to certain groups.
This makes it very painful for me.

I would *love* to have a default permissions -- or a way to mass select categories. For example, I check the tier1 in a tree, all tiers below it get the same permission, by default. OR if I uncheck it,m all get unchecked. Although I think doing this would be excruciatingly painful to code.

I'd have to agree with pyromanfo that the default permissions need not be "in addition to". They should just be permissions selected when you go to change them.

Perhaps a better name than 'default permissions'. Perhaps, 'permission template'?

pyromanfo’s picture

pyromanfo commented

Something that might help you nazadus, I just checked per-vocabulary permissions into CVS. So you can select "view and create" for a vocabulary and when you save the permissions those are added to all categories in the vocabulary.

nazadus’s picture

nazadus commented

Excellent!
for what it's worth, nice job on all your work!

pyromanfo’s picture

pyromanfo commented

I just added default permissions as we discussed into CVS. Let me know how well it works.

I also updated the vocabulary wide settings to be a dropdown for adding or removing that permission from all categories in the vocabulary. Those two settings combined should remove most of the tedium from the permission modification process.

Anonymous’s picture

(not verified) commented