We are using field_permissions to restrict access on fields associated with user accounts.

The module appears to work as expected, but the description shown on the permissions screen seems a little confusing, as the user account isn't really considered "content". (OK, we're all just content, move along. Hopefully you know what I mean though.)

If the descriptive text on the permission was "Edit own field_foo on field contents belonging to the user." then I think it would make sense both in the context of node and user -associated fields. I'm unsure about other use cases (comments, taxonomy terms).

CommentFileSizeAuthor
#1 blah.patch649 bytesrobloach

Comments

robloach’s picture

Status: Active » Needs review
StatusFileSize
new649 bytes

How about........

Edit own @field
Edit own @field when the field's parenting content belongs to the user.

robloach’s picture

Component: User interface » Documentation
Category: feature » bug
Priority: Normal » Minor
robloach’s picture

Status: Needs review » Fixed

'title' => t('Edit own value for field %field', array('%field' => $field_label)),

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.