Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It would be useful to have some roles be able to see the fields that would normally be hidden.
Not sure whether this should be a new permission or the existing 'administer conditional fields'...
Comments
Comment #1
peterpoe CreditAttribution: peterpoe commentedComment #2
yched CreditAttribution: yched commentedWhoa, *that* was fast :-) Thx !
Comment #3
nathanraft CreditAttribution: nathanraft commentedGreat idea! This could be extended to include a role visibility setting for displaying fields. Thus, if someone has a given role then the questions would show.
Is this worth putting in as a feature request or is this beyond the scope?
Comment #4
peterpoe CreditAttribution: peterpoe commentedSo we could do one or more of the following:
- we could add an option for each controlled field, to let the admin decide if the controlled field should be hidden or visible WHEN the controlling field is not present
- we could add a 'view controlled fields' role
- we could add a 'view controlling fields' role
The problem is that we would add an additional layer of permission control to the fields which is usually already a mess (in my site, for example, I have field visibility controlled by workflow (with workflow_fields.module) and by group (with og_user_roles.module), and it's already tricky to make them play nice together).
Probably we should now concentrate on making the core system more stable (e.g.: work with more field types, with multiple controlling fields), and add a permission system layer. What do you think?
Comment #5
nathanraft CreditAttribution: nathanraft commentedI think that to make it most flexible, it would ideally need all three options, as long as it applied to groups as well. Just so you understand, my main need is to show a group/tab and all thus all its fields only if the person has a specific role.
I do understand the mess issue through but think that this is a really slick option. As far as when to add these features...while I would really like these options, I have to agree with you that the core functionality should be built up a bit more first. (Yet, you never know how many others will start contributing if there are more options to work on.) I will try and focus on these more pressing issues for now but if you were to get to the tabs and this feature sooner I would be even more happy!
Comment #6
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
bendev CreditAttribution: bendev commented"show only if triggered" option doesn't work... on my D6 installation
Do I understand correctly that if the controlled field is hidden (due to permission settings) but assigned to the triggered value for the controlled field, the controlled field should be visible ....
It doesn't work...
If I change the permission to visible, it works like intended... so this option for orphaned controlled field doesn't seem to work
thanks
Comment #8
peterpoe CreditAttribution: peterpoe commentedFixed here: #611230: Orphaned fields don't show when triggered.