Publish Settings, a permission?
| Project: | Content Management Filter |
| Version: | 6.x-1.4 |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
issue: removing 'administer nodes' permission also removes 'publish settings' options when creating new content (page, story). This is a side effect of removing the permission. Users can use CMF to change publish settings after publishing the content, but this is obviously not the way it should be. That's a real issue when using this module, because otherwise this module is filling a huge hole in the Drupal system (e.g. having multiple users manage their own content effectively).
Really, the core 'administer nodes' permission needs to be disambiguated into several permissions, but this is the Drupal we have!
solution: User should be able to set publish settings when creating a new node of a content type. The most simple would be to add an "access publish settings on create/edit" permission to CMF.
#1
The "administer nodes" permission issue has spawned several core issues; I suggest you search for them and participate.
+1 for adding a "publish" permission. This is the most common "moderation" mechanism right now and should be up to the admin as to whether it can be circumvented.
BTW, CMF is not in the picture at "create" time, therefore we cannot access the permission then.
#2
Looking at the various operations, I think 'allow publishing options' is more appropriate. This would restrict all the standard mass node operations (publish, promote, sticky, delete). So now the question is: Other modules, for example, Image and Pathauto, also provide mass node operations, should they also be restricted ('allow mass operations')?
Should we also restrict comment operations?
#3
Other modules also enable publishing of nodes for users without the administer nodes permission.
For example: http://drupal.org/project/override_node_options
#4
Thanks. That takes care of create time settings.
#5
No further update.