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.