Respekt the visibiity setting of the linked field [#1541782]

Hello,

at first..Thanks for this really useful module. I have one feature request.
It would be really nice if the module respect the visibility settings of a field. For example a site uses the Profile2 or Profile2Privacy Module. If the user had the right to see the field witch is associate with the Realname-Module he will see the realname in the Profile,Forum etc.. Other people see the account name.
This would be a really nice feature..

Best regards
Frank

Comments

Comment #1

Dave Reid

he/him

English

Nebraska USA

CreditAttribution: Dave Reid commented 14 May 2012 at 00:09

Status:

Active

» Postponed (maintainer needs more info)

If the module implements hook_field_access() then it should be automatically respected in the generated real name. I'm not sure what more we can do.

Comment #2

fraweg CreditAttribution: fraweg commented 14 May 2012 at 06:30

Hello,

thank you for your effort. My English is a little bit poor so maybe we misunderstood each other. I will explain it a little bit more.
For example:
I create/use a field "name" in the profile (in my system I use the module profile2) where the user can fill in his Name. Now I can use your Realname-module and use this name instead of Login-Username. After that the name is shown at the top of the profile, in forum topics etc. So far, so good...
When I use a field in my profile (for example the "name" filed) there a several ways to set the visibility
for other users. For example Profile Privacy,Field Permissions,Profile2 Privacy. When I set the visibility settings with one this Modules (for example for the field name) the field is not visible,so this modules work as they should. But the realname-name is still shown as a top of the user profile in the forum etc.
It would be very nice if the Realname-module respect this visibility settings. So when I set this field "name" invisible for some user, roles, etc. the name is also unused by the Realname-module. I have test it with the Profile2privacy-Module "http://drupal.org/project/profile2_privacy".
So this would be a very useful feature.

Best regards
Frank

Comment #3

sry CreditAttribution: sry commented 12 July 2012 at 21:48

Hello,

as I have a similar (if not same) request as Frank and as the issue is marked as "postponed (maintainer needs more info)" I try to explain it in an other way: RealName replaces Username as soon as configured, any where, any time, that's great. But there may be situations (in my case a specific community), where you don't want real names to be visible for everybody (=anonymous users) for privacy reasons.

Frank's approach (if I understand him correctly): Profile field(s) containing real names is/are configured as invisible for anonymous users, but visible for e. g. authenticated user via Profile2Privacy. RealName could (at least in theory) work like this: RealName "knows" the role of the site visitor and checks if this roles entitled to see the content of the respective profile field(s). If yes, RealName displays, well, the real name. If not, it leaves the username unchanged.

Alternative: Maybe it is possible to add a role permission for RealName, means the execution of RealName module must be set in the role permissions. If checked, RealName module works for visitors of that respective role , means displays the real name info, all others see the username.

What confuses me: Documentation says

Permissions

There is one new permission, "use realname." This allows you to control which roles see the realname and which don't. Additionally, if you want the Real Name to show up as a link to the user profile or homepage, the role must also have the "access user profiles" permission.

Sounds like this is it. But I cannot find "use realname" in permissions (D 7.14, RealName 7 1.0), just "Administer Real Name configuration". Is this the solution, and if, can someone give me a hint why it is invisible for me?

Hoping that this brings rather information than misinformation ;-)

Sándor