Closed (fixed)
Project:
Profile role
Version:
6.x-1.2
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
24 Jan 2009 at 00:45 UTC
Updated:
25 Mar 2009 at 22:20 UTC
I use this module and appreciate that user#1 can now view all fields.
On my site I have defined a role for admins, because we are three users different from user#1 administering the site.
Is ist possible to add an entry for the module in the Drupal pemission table, so that it can be selected which roles can acces and view all fields?
Comments
Comment #1
boombatower commentedSounds like dooable...I'll try and get on that within the next few days.
Comment #2
boombatower commentedSorry for delay in response. I've been swamped.
Are you referring to #362675: Fields not visible to admin user. Changed as that is not the intent of the module.
The module is intended to define what fields are applicable to a role, not be used as a permission system.
If you are looking for permissions trying profile_permission.
Comment #3
Cologner875 commentedI'll try to describe my feature request in other words:
A role that I use for all the admins of my homepage (not only user#1) has the permission in Drupal core to "administer users". But users with my admin role can only see the fields, that are also visible for a "normal" user, who ist not an admin.
You may now ask, why it is important for my admin role to see all fields. During the registration for new users, they have to fill out fields, that contain information, they are not supposed to change again later (e.g. their real name or birth date). I'm using profile role to make these fields invisible for the "normal" users. But the fields are important for my admins, because they need to see the real name and birth date of a "normal" user, e.g. to decide, if someone is allowed to register or not.
I hope this helps to understand why I would appreciate this feature :)
Comment #4
boombatower commentedThen I believe you are looking for profile_permission module.
It generates edit and few permissions for the specified profile fields. You can then give w/e role you want access to edit/view.
Profile role is intended to define a data structure, not permission system. For instance, my original use case was members/athlete. Where athletes had lots of athlete specific data fields and members had other fields. Each user role should never have fields of the other, unless they have both roles. Not even admin/registration can edit. (the idea - registration no restricted though)
Profile_permission should do what you want, let me know.
Comment #5
Cologner875 commentedok, thanks for your answer, I'll have a look at the module as soon as I've passed my exams :)
Comment #6
boombatower commentedPlease re-open if still have issue.