#522 Privacy for single person name

[Borksoft]

I came across a problem, where I had to hide a name of
a single person. The standard setting of my system is
to show names of living persons to unauthorised users,
so I had a problem there.
When changing the privacy setting of the person
(using "1 RESN privacy" as first line in GEDCOM data)
did not help, nor did adding the person to the
person_privacy array.

To get this to work I made the following change to
function showLivingNameByID in the file
functions_privacy.php:

if (displayDetailsById($pid)) return true;

if (isset($person_privacy[$pid])) {
if ($person_privacy[$pid] < $PRIV_USER) return
false;
}

if ($SHOW_LIVING_NAMES>=getUserAccessLevel())
return true;

return false;

I could have enabled the code that was commented out
(where I copied the part I added from), but I don't
know why this was disabled.
If this change is not possible, is it possible to
implement another way to disable showing the name of a
single person to unauthorised users?

(phpGedView version 3.3.8, functions_privacy.php,v 1.5
2005/04/08)

[Laie Techie]

Logged In: YES
user_id=1278885

Inside the mygedcom.ged_priv.php file is the following:

/**
* Check for RESN privacy restrictions
*
* This setting tells the privacy functions to look inside
the gedcom record for a RESN restriction tag.
* The RESN tag was used by Ancestral File as a way of
marking a record as private.
* @global boolean $PRIVACY_BY_RESN
*/
$PRIVACY_BY_RESN = false;

I think the privacy functions already (or should!) take this
into consideration.

[Borksoft]

Logged In: YES
user_id=1430243

I tried that setting, but it does not work like this.

As far as I can see the RESN setting only works for the
details and not for the names of the person. In the
function showLivingNameByID the function displayDetailsById
is called (returns FALSE, as RESN is set), but then
$SHOW_LIVING_NAMES is checked, and this one is also set, as
I want to show (most of the) names of the people. So the
result is TRUE which displays the name.

[Laie Techie]

Logged In: YES
user_id=1278885

One other quick note: RESN can be locked or privacy. With
a value of locked, that record should still be public, just
not editable.

[Borksoft]

Logged In: YES
user_id=1430243

The restriction should be privacy, as the details
(including the name) should not be visible to other users.

[Borksoft]

Logged In: YES
user_id=1430243

The restriction should be privacy, as the details
(including the name) should not be visible to other users.

[KosherJava]

Logged In: YES
user_id=634811

Has this ever been implemented?

[Borksoft]

Logged In: YES
user_id=1430243

It works when using the person_privacy array, but it still
does not when using the "1 RESN privacy" line.