Unfortunately this issue has become a bit of a dumping ground for a variety of issues that people are seeing. I've made an attempt to answer some open questions and point folks to other issues that are likely related in comment 16: #1250760-16: Field permissions not working. If you find other things in this thread that seem to relate to an issue you're seeing, but don't see a related open ticket, please open a new one instead of adding more to this one.

With that, I'm closing this issue as cannot reproduce -- which is not to say that I don't believe these are real issues. This just isn't the place to solve them.

--- Begin original issue text ---

I've enabled field permissions and they are not working across the board. No matter what setting I make, users are restricted from editing fields. Users are also restricted from editing field even if I haven't activated field_permissions for that field yet.

#1246966: Untouched fields acting like they are enabled
#1250700: Field permissions not working for Video Embed Field


bryancasler’s picture

Status: Active » Postponed

This may be a D7 core issue. Postponing until I have more information.

RobLoach’s picture

Status: Postponed » Postponed (maintainer needs more info)

Update to 7.x-1.x-dev?

Michael-Inet’s picture

Not real sure where to add this, so adding more info here...

Drupal version: 7.9
Field Permissions: 7.x-1.0-beta1

I install Field Permissions, assign myself "Administer field permissions", and click Configure off the Module page (/admin/reports/fields/permissions)

- the standard "body" field across all content types becomes Private, and
- there is no way on that page to make anything Public.
- (besides which it's a reports page, so why is Configure going there?)

This image:


indicates a configuration path should be something like /admin/structure/fields/permissions, but there aren't any pages under Structure that look anything like that page.

So, 64-thousand dollar questions, where do I set the body field for all types to Public? Why did it default to Private? Also, can you please add how to do this to the documentation?


Edit: At the bottom of this page /admin/structure/types/manage/page/fields/body you can set "Body field settings", which, contrary to expectation, apply to all Body fields across all Content Types.

RobLoach’s picture

Priority: Critical » Major

Lowering priority as a somewhat related issue was just recently fixed. Again, mind updating to 7.x-1.x-dev and reporting back?

catya’s picture

Issue summary: View changes

Holy cow. Thanks Michael-Inet, I've been trying to figure this out for weeks, with crankier and crankier users.

RobLoach, it would be GREAT if this was something that could be at least noted someplace other than this thread... (and yes, I tried upgrading to the dev version first.)

Drupal lead learner’s picture

I am facing same problem for my drupal 7 site and have no idea how to resolve it?
Is there any need to update drupal version and field permission module ?

Leeteq’s picture

Leeteq’s picture

Status: Postponed (maintainer needs more info) » Active
chopper_elation’s picture

Version: 7.x-1.x-dev » 7.x-1.0-beta2

Installed the beta2 version last week. I am running this with RedHen. I created a custom text field that should be always be visible and editable by Admins. That works fine.

This same field should also be editable and viewable by another role.

This other role sees the field and can put data in it but after saving the node the author can no longer view or edit the field. Admins maintain the ability to view and edit this field.

The permissions for any role except Admin don't seem to be working properly.

ggevalt’s picture

I can report the same behavior as chopper_elation: Appropriate roles can view the field -- which is an entity reference tied to a Taxonomy Vocabulary -- in the content create area. They can select it, but once they do and once they save it, they cannot view the content -- "Access Denied."

We tried both the 7.x-1.0-beta2 version and the 7.x-1.x dev version. I wonder if the maintainers have any thoughts on this? And is this still being maintained? No responses in issue queue for a while and no changes since 2013.
We used this module extensively on our Drupal 6 sites with no problem. This is, for us, an important module. I hope someone can help.

FYI, we tried rebuilding permissions, tried giving EVERYONE access to the field and still only administrators can see the content created for this, that is, roles with complete node access. We have looked through configurations and permissions and everything appears to be set up properly. We are not using any other node access or content access module.

Thanks in advance to anyone who can help us with this. AND here's an overview on some of the issues with node access, perhaps this will help: https://www.drupal.org/node/270000 ... we will advise here if we have any luck resolving this.



Leeteq’s picture

Version: 7.x-1.0-beta2 » 7.x-1.x-dev
Göran’s picture

I have the similar problem as above. Tried the dev version without any changes.

My problem is detected to FILES, where 2 different Roles has permission to see the attached file, and the Roles can not.
The files is placed in field_collection fields, but I have tried to make a extra control-field directly in the content-type in a extra new field with same setting and with same failure result. I also use Content_Permission_module.
After second try, with backup DB and New unpatched dev version, the field from content-type show up. My problem seams to be related directly to the Field Collection Module.

I use DP 7.50, and before it was 7.41 AND 7.44 with same problem.
The old DP 7.34 did work well and some version before that.

I hope this problem could be detected and fixed because Drupal is of urgent need to be able to give information by files to defined roles. This is a MAJOR logical function in the "hart" of Drupal, so please we really need a patch solving this issue.

Here is a new issue who explain one precisely problem who is detected to the (different) settings under the "Manage Display" (in content types).

Göran’s picture

Maybe this issue explains some of the problem, especially related to fields for file (attachment)

Kris77’s picture

Version: 7.x-1.x-dev » 7.x-1.0-beta2

It is practically unusable. Does not work.

I made many tests but does not work.
When I set that a user can see the value of a field, that field will disappear from the content.

Kris77’s picture

I have installed RULES FORM module and now can disable each field in any content and any situation: Edit, Add, etc..

mariacha1’s picture

Issue summary: View changes
Status: Active » Closed (cannot reproduce)
112.55 KB
164.07 KB
128.74 KB

Existing questions:

No matter what setting I make, users are restricted from editing fields (initial comment)

This is likely fixed by #1246966: Untouched fields acting like they are enabled, given that this was reported 5 years ago.

How to edit the body field permissions, comment 3 #1250760-3: Field permissions not working

When Drupal core moved the body field to be a field proper, this issue resolved itself.

This other role sees the field and can put data in it but after saving the node the author can no longer view or edit the field. #1250760-9: Field permissions not working

Difficult to say what's happening here, but given that the role has the permission to create the value in the field but not edit it, I'll give a couple examples of when this might not work:

-- If you've given the new role the permission to "Create own value for field" but not the Edit own or View own permissions. See the "Content Creator" role here:

Create only selected

-- If you've given the new role the permissions to "Edit own value for field" and "View own value for field" but NOT the ability to Edit/View anyone's value for that field AND the field you're editing is part of a field collection. Like this:

Edit/View own selected

Field collection example

This issue is related to #1284016: field_collection integration -- add hook for defining entity's owner, which is fixed on the field permissions side, but not on the field collection side. I've added this issue as a list of things to fix before a 1.0 release: #2775787: Roadmap for 7.x-1.0

They can select it, but once they do and once they save it, they cannot view the content -- "Access Denied." #1250760-10: Field permissions not working

Field permissions should never make an entire page inaccessible -- we're not touching the permissions that do that. The worst you should ever get is the field disappearing, or showing up when it shouldn't. The situation described above mentions that another access control module is enabled. I would guess, given that there's an entity reference involved, that the entity being referred to is somehow restricting access to the page.

This looks like a promising place to keep talking about this issue: #1842580: Users cannot access term reference fields (edit or view)

Problems with file fields

Aside from the referenced issue here #2776087: Field for files module fail with fields permission, depending on settings. "Download files" is hidden for authorized roles there are many issues open for file fields:

It makes more sense to keep debugging in one or many of these issues, and not here.

Göran’s picture

OT - Note:
File field problems seams to be related to the "File_Entity" Module.
I found a work around (long shot) - see Bug Issue here https://www.drupal.org/node/2781275#comment-11519707

ibar’s picture


I had a similar problem with not being able to edit the name of a field.

The “problem” was an opening <b> and closing </b> tag in the Help text.

When I removed them everything worked fine! I think the same happens with every tag.