Closed (fixed)
Project:
node privacy byrole
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Reporter:
Created:
11 Jan 2005 at 02:05 UTC
Updated:
21 Apr 2005 at 03:15 UTC
I like having node privacy for myself and a small group of editors, but I don't want regular authenticated users to see this module when creating content. Is this possible already and I'm just missing it? Can it be added if not?
thank you.
Comments
Comment #1
shane birley commentedYes, I would very much like only certain roles to use this feature. For example, if I have ten million bloggers on a site, I don't want them selecting permissions. It's a blog, for crying out loud! ;-)
Comment #2
ankur commentedThis feature can be added, but we were thinking of doing something with it that is halfway there:
We were thinking of changing the module so that each node is assigned with default permissions and if the owner of the node feels that the permissions should be different, they can click on a "security" tab when editing the node....
-Ankur
Comment #3
javanaut commented+1 for the security tab idea.
I did a quick hack such that a user only sees the various permissions settings if they have more than one role. Otherwise, whatever the existing/default permissions apply.
Comment #4
jasonwhat commentedSecurity tab could work. I'd just like to declutter these pages as best I can for users. Most of them only need to see the title field and text area.
When will this be added?
Comment #5
ankur commentedAt present, the module is being maintained by someone that was going to add more configurability. His plan includes being able to turn this off/on for different node types. He may include the idea of meta-permissions, being able to decide which users can set permissions for which node types.
When maintenance comes back to, I will look into making the other commonly requested changes.
For the changes I'm waiting on, I see something coming back in two or three weeks. Changes that I plan on putting into the modules will be an ongoing thing. As for everything mentioned here, I can't say for sure.
But the module does have a clean interaction with the node access system, though it is missing some things you would expect to see in terms of other interactions with Drupal core.
-Ankur
Comment #6
jasonwhat commentedjavanaut: could you share your hack?
I like the security tab, but that should still have a permission. It seems clear to me that some people will want to use the module to control showing of content on their site, but not let regular users do this. I have board members and editors as roles, there is special content I create just for them and this module really helps, but nobody besides me needs this function. It just confuses most of them.
Comment #7
ankur commentedThis is a feature request that has been a while in coming. I'm looking to implement the "permissions to set permissions" feature when I port this module to 4.6 in the coming weeks.
-Ankur
Comment #8
ankur commentedComment #9
ankur commentedpatched:
http://cvs.drupal.org/viewcvs/drupal/contributions/modules/node_privacy_...
Comment #10
(not verified) commented