Hello,

I need some help here. I have a bool field called "approve" in a content type. I do not want that the author of new content ticks the "approved" box and it should not even be visible on creation or edit of the content. No matter what I tick, I don't get it to work. Currently it is ticked as follows:

N Create field_approved (edit on content creation).
N Edit field_approved, regardless of content author.
N Edit own field_approved on content created by the user.
Y View field_approved, regardless of content author.
Y View own field_approved on content created by the user.

In my understanding everbody should be able to see the field. But no one should be able to see it when creating or editing. But you can see and change the value of the field when creating or editing.

Comments

Danic’s picture

Category: support » bug
Priority: Normal » Major

This is very confusing. I finally got it working, but it just does not seem like correct behaviour. My field settings are as follows:

- Y Create field_approved (edit on content creation).
- N Edit field_approved, regardless of content author.
- N Edit own field_approved on content created by the user.
- N View field_approved, regardless of content author.
- N View own field_approved on content created by the user.
------------
- When the user creates content, he does not see the field.
- When the user edits own content, he does see the field.
- When the views any content, he does see the field.

Shouldn't it be exactly the opposite? The user was granted the permission to create the field, but not see or edit it.

I will change the category to bug report.

Danic’s picture

Title: Field only editable by members of certain group. » Field permissions are broken

I changed the title to a more exact description.

BenK’s picture

Subscribing

Danic’s picture

Component: User interface » Code
calefilm’s picture

Yes this makes total sense. You are simply enabling this feature so it is now visible at admin/user/permissions. So now, your next step would be to obviously check the corresponding role -- with the ability to either create this field or not to create this field (at permissoins). Seems confusing but it really makes sense.

RobLoach’s picture

Title: Field permissions are broken » Better documentation on how to use Field Permissions
Component: Code » Documentation
Category: bug » feature
Priority: Major » Minor

Yeah, enabling the Field Permissions on a field just exposes the field to the Permissions page. Maybe there needs to be better documentation on how to use this? If you write something up, I could translate it to a patch. Thanks!

calefilm’s picture

I don't know anything about creating patches--and am still on version 6 but I've written up a little "how to" that I can refer back to the next time i get confused: http://drupal.org/node/1084688#comment-4284504

RobLoach’s picture

Version: 7.x-1.x-dev » 6.x-1.x-dev

There's a whole new UI with a bunch of new documentation in there for 7.x. So this is only on 6.x now.

hass’s picture

I was also confused by the Create permissions. Looks not very intuitive and self explanatory to me. Thanks for writing this up.

mariacha1’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

D6 version is no longer supported.