Confidential query

Herdsman Janet 1

I have a person on the tree, Walter Bayford, KND9-L3W, I can see him, and assume I entered him, as when I try to look at his changes it comes up saying he is an unknown living person, that only I can see, but I cant see his changes, even though changes have been made by multiple people, so I assume others can see him, This seems to be some sort of glitch in the system, how can it be resolved.

Gail Swihart Watson

KND9-L3W is not a living person in a private space. Walter is deceased, given a death date of 15 June 1901. When I looked at the changes (which you can look at too), you did not create him. A user called FamilySearch created him in 2012. And yes, other people have added information on him. Someone added a source, another added a note. There is nothing to be resolved. Everything appears to be working as designed. You have collaborators in your research.

Áine Ní Donnghaile

The change you have made to that profile, today, are visible for me.

I suggest you try using a different browser to access or clearing your cache and FS cookies, as a first troubleshooting step.

Chas Howell

@Herdsman Janet 1. are you sure you are looking at KND9-L3W and not a different PID of a Walter Bayford in your living area? I may have missed the point, not really clear what you are seeing. What happened when you took Aine Ni Donnghaile's advise?

Gordon Collett

I can also see KND9-L3W just fine.

However, I have had times when I have tried to look at a person that I have worked on before and gotten that Unknown person notice. Generally the page loads just fine if I refresh the page a time or two. I've always chalked it up to a server hiccup or internet connection problems somewhere since it is so temporary.

Herdsman Janet 1

Thanks for all the comments, it does seem to have resolved itself.

dontiknowyou

when I try to look at his changes it comes up saying he is an unknown living person

Is the message displayed as white text on black background? I am seeing this too, sometimes. It is intermittent and I think it has to do with latency problems internal to FamilySearch servers. If I try again later, the page loads as expected.