user cannot edit his own data, only others
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
Assigning a person his ID causes his data to be listed as private, while his siblings and their info is viewable. Using 4.2
Tried deleting him and adding him again, no change.
Set various privacy settings on and off to no avail.
Thoughts?
"Assigning a person his ID causes his data to be listed as private"
We'll need a lot more detail than that. What EXACTLY did you do? Its definitely not a standard outcome. What does "assigning a person his ID" actually mean, interns of the actions you took?
Is this a living person, ore deceased? What privacy settings do you have overall?
Do you really mean version 4.2? Is that 4.2.0, or 4.2.1, or 4.2.2?
In most cases privacy is determined by alive or dead, or age.
Or do you have his ID set individually in Privacy config to hide him?
On creating his user account, I assigned him his I-number for GEDCOM INDI record ID and Pedigree Chart Root Person.
Max relationship privacy path length = 5.
Access level = edit.
This person is living and wants to edit his immediate family.
version is 4.2.1
Privacy settings on the gedcom are:
Show dead people Show only to auth users
Show living names Show only to auth users
Show sources Show only to admin users
Enable Clippings Cart Show only to admin users
Show Research Assistant Show only to auth users
Show Multi-Site Search Show only to admin users
Limit Privacy by age of event NO
Use GEDCOM (RESN) Privacy restriction NO
Show private relationships YES
Use relationship privacy YES
Max. relation path length 6
Check marriage relations YES
Age at which to assume a person is dead 120
No other settings are set on this page
There are no privacy setting in the GED for him.
As I said he can see all his siblings and their families, but his is private.
Hmm, those settings all seem fine.
I don't recall any bug that would cause that, and its not an issue I've seen reported before. That all points to something unique about your data.
I'm sure this is OK, but double check that you entered the correct I-number in his user account settings, and didn't accidentally use lower case or anything like that.
Is there anything unusual about his GEDCOM record, such as missing dates that would confuse the isDead? calculations?
Otherwise, try turning Relationship Privacy off for this user, to see if it solves the problem. That might help pin-point where the issue is . If it does fix it, set it back to YES, and try adjusting the privacy path length.
This seems the most likely area, as its not a well used option, so might possibly have a bug we haven't seen before or found in testing.
Thanks. I couldn't find any issues with his data. I turned off relationship privacy, exited then logged back in and turned it on again. It seems to work now. Never had this issue before. I do admit that all the various privacy switches can be daunting to set. I wanted to lock it down fairly well. Maybe I tried too hard.
Again for whatever reason it worked correctly when I logged in as that user.
Thanks for the help.
Glad its fixed. Sounds like it might have been a browser cache issue perhaps?
Privacy setting are very much a personal taste. Personally I find the KISS principle works well (Keep It Simple …). I simply show living only to registered users, and not much more. But I manage who the users are, and their ability to edit, very carefully. It's worked for me for a few years now, with no major dramas.
The one setting I particularly avoid is Relationship Privacy. Just way too complex. I don't know how big your tree is, but as it grows that option WILL slow response times down, because its asking PGV to do a LOT of checking every time you need to display any individual, anywhere. The longer the relationship path, the worse it gets, and I would categorise your settings of 5/6 as high.