I have a special use case for your realname module. We connected a vBulletin forum with a Drupal 5 website. Both Systems have a bunch of existing users. Some have an account in Drupal and in vBulletin as well, but with differen user names. To match the vBulletin accounts with the drupal accounts, we implemented a new profile field "forum name" and filled it with the vBulletin user names. With profile privacy we prevent users from changing this field, because this would be a security issue and would breal the connection. During the tests we found, that some user did show their forum name (taken from the corresponding profile field) on the drupal site but connected to vBulletin with their original drupal user name. Thus vBulletin created a new account instead of connecting to the user's existing account.

To solve the problem I changed the function realname_make_name in realname.module

Line 264 from
if (isset($account->$name) && !$private_field) {
to
if (isset($account->$name)) {

Now Realname does not longer check the privacy settings from Profile Privacy. It would be great if you could implemen a checkbox for this behavior.

Comments

nancydru’s picture

Status: Active » Postponed (maintainer needs more info)

What's the point of using PP if you bypass it?

nancydru’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

No further update