The CCK boards won't reply, so I thought I'd try you guys (who seem to always be far more prompt). This is in regards to CCK fields, something I think most people are familiar with.
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.
The 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.
