Closed (won't fix)
Project:
Content Construction Kit (CCK)
Version:
6.x-2.2
Component:
General
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
3 Jun 2009 at 18:55 UTC
Updated:
29 Jun 2009 at 02:54 UTC
Is it possible to administrate field permissions so that roles can only edit/view fields based on whether or not they are their own content? For example:
Role 1 can:
Edit own field_a = yes
Edit any field_a = no
View own field_a = yes
View any field_a = yes
I think it is more important for the edit field permission to be based on "own" or "any", but if both are possible that would be good too.
Comments
Comment #1
ballerjones commentedmaybe there is already a patch available for this? After looking around, it seems like the old Field Permissions module (before CCK integrated) had this capability. Any word on this?
Comment #2
ballerjones commentedBump - anyone?
Seems like a pretty useful feature. Maybe it already exists in some way? They did it here: http://drupal.org/node/368161
Comment #3
ballerjones commentedThe reason, in my case, this would be useful is form authorization. Say Form A has field_A and field_B. Field_b is the approval field that can only be edited by the Approver role. But, to simplify the process, when the Approver goes to edit the form, all he can see is the field_A.
The problem, therefore, is when an Approver tries to create a Form A (would, in this case, be sent to another approver). Approver needs to be able to see field_a and not field_b. But the way CCK Field permissions is currently set up, the Approver only sees field_b.
Thus, the need for field permissions based on an own-any dichotomy.
Comment #4
karens commentedThe number of permission elements is already huge and overwhelming, we probably won't add any more in the core module. There is nothing to prevent anyone who wants to create a separate Content Permissions Plus module from doing so and adding additional features in. You can also use the Permissions API with the new module I just contributed at #503118: Add easy reset form to user permission page, which makes it easy to do mass changes to all those field permissions on the permissions screen.