This may actually not be an issue, so forgive me if I've just misunderstood.

I set up CCK field perms so that a particular user role (called "Full Listing") can "create" and "edit own" on the field "Listing Description".

This allows "Full Listing" users to create CCK nodes with the field "Listing Description". However, when they edit the node, they don't have access to the "Listing Description" field, unless I ALSO give them "edit" permission.

Doesn't "edit own" imply that "edit" permission is also being given, without "edit" being required?

At the moment it's not a big deal for me, as I am using the content module permissions to stop users editing other users' nodes, but I can envisage a situation where you'd want to allow users to edit other users' nodes, but just want to restrict them from that field - and you wouldn't be able to.

Comments

mrtoner’s picture

mrtoner CreditAttribution: mrtoner commented

I was frustrated by this as well. Actually, a user cannot edit a protected CCK field unless "Edit <field>" is checked, regardless of the setting of "Edit own <field>."

arthurf’s picture

arthurf CreditAttribution: arthurf commented
Status: Active » Patch (to be ported)

This is now fixed in the 5.0 branch. It needs to be ported to 4.7