Closed (duplicate)
Project:
Field Permissions
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
21 Jun 2011 at 13:04 UTC
Updated:
15 Oct 2016 at 17:41 UTC
Jump to comment: Most recent
Comments
Comment #1
tomhung commentedI too would like this option... it would make nodes with LOTS of fields easier to manage.
G
Comment #2
t-dub commented+1
It would be exceedingly convenient to manage permissions on entire groups of fields at once (if nothing else, it would make admin/people/permissions *slightly* less imposing :)
Comment #3
robloachThe new UI makes the access control much easier. Not sure if we should add the permission check on the group itself though. The group will only appear if you have access to something within the group. I think having individual control over the fields is something we want.
Just tested with 1.x-dev and it work fine. The new UI will really help with managing this. I'm inclined to set this to fixed as it's much easier to maintain.
Comment #4
allio_froggio commentedThis works when the fields are contained within a fieldset (the fieldset does not show if the logged in user has no permisions to edit a field contained within that fieldset), but not when the fields are contained within a vertical tab (the tab still shows even when the logged in user has no editable fields). Obviously this is a minor issue, but, if the show/hide was expanded to the tab groups, that would be awesome!
Comment #5
carcinovich commentedI agree with adding fieldset permissions -- it would be nice, because the fieldset shows up regardless of the status of the fields within in. It makes it difficult to hide in the even that its contents are missing.
Comment #6
aitala commentedHi,
I would find it useful for fieldsets to be hidden if all the content within is not visible to the role of the user viewing the node..
Eric
Comment #7
marleo commented+1
If you can't see anything in the fieldset, it should behave like an empty fieldset normally does.
Looks like someone's already asked for this: https://www.drupal.org/node/1417008
Comment #8
mariacha1 commentedComment #9
mariacha1 commentedLooks like this was fixed at the Field Group level:
https://www.drupal.org/node/2081217