#2766 Death estimation is wrong in the public dislay

v4.2.2
closed-invalid
nobody
None
5
2010-01-25
2010-01-23
Bodo
No

Even if persons which are still alive, in the list the are display a deat. This is a very bad situation, if people are searching in the Internet for their name and find themself as death.
I didn't check this before, and now I get some trouble and had to close this side in the moment.

Discussion

  • Bodo

    Bodo - 2010-01-23
     
  • Anonymous - 2010-01-23

    What do you have set as "Age at which to assume a person is dead " - it might be too low, which would cause a living person older than that to be listed as 'dead'. (setting in Privacy config). The default is 120 yrs, which is generally "safe".

    Also, do you have "Show estimated dates for birth and death" set to "Yes" (Setting in Gedcom config / Display & Layout / Hide & Show).

     
  • Bodo

    Bodo - 2010-01-23

    Hi
    I just check the Settings in the Privacy config It is 120 years, I guess I never changed there something the same I can tell You to the second point, it is setted to "no"
    Is there another place whee to customize ??

     
  • Bodo

    Bodo - 2010-01-23

    May I should add, that I used normaly german version

     
  • Greg Roach

    Greg Roach - 2010-01-23

    This is not normal behaviour.

    Can you post the URL of your website so we can look?

     
  • Stephen Arnold

    Stephen Arnold - 2010-01-24

    Bodo
    Have you marked these people with a DEAT Y (Ja) ?
    None of them have any dates from which the system can calculate an age to compare them against the 120 years for assumed death. There is a sophisticated algorithm for which examines relatives (GP, Parents, siblings, spouses) for dates if none are noted for an INDI, but if you provide absolutely no dates, the system will be confused. Still, it would appear you have somehow marked these records a DEAD, either during import (is DEAD function) or you have a DEAT tag with or without a Y.

    Since we can't see the code (or even access the site) we'd have little to no way to know what you've done.
    Stephen

     
  • Greg Roach

    Greg Roach - 2010-01-24

    <<Here the link to the persons>>

    This link asks for a login.

     
  • Bodo

    Bodo - 2010-01-24

    Okay, I'm bit scared to keep the site open, bcause of this fault. I have enable for You the acccess.
    Upto now I have seen the fault only by this persons. For my person Bodo Schade its okay.
    May You can help me.
    Thanks
    Bodo

     
  • Greg Roach

    Greg Roach - 2010-01-24

    Send me a login?

     
  • Anonymous - 2010-01-24

    schaborj

    We can't help until you give one of us at least a login to your site. You have privacy set so that ALL visitors must login. I've tried requesting a login through the site, but you haven't responded.

    Nigel

     
  • Bodo

    Bodo - 2010-01-24

    Hello
    I enabele for You the request to Login this Morning. Please try, You should be able to login. I gave you acces right as administrator. I hope You can find the reason. The birth day of the people is set to 1970 or 1972.
    Please watch out the name "Pfeifferling"
    Thank You

    Bodo

     
  • Anonymous - 2010-01-24

    Thank you. Now I can see the problem. It is an error in your data.

    Those two people have a father (I1389108) who has a date of death of "1632". So PGV is using that to try and estimate if the children might still be alive!

    That person has a yellow warning triangle by his age (on his INDI page, and the Individual Lists) - you should always investigate those when you seem them.

    Nigel

     
  • Bodo

    Bodo - 2010-01-24

    Hi
    changed this wrong date to the correct year 1975. The fault is still there. Then I edit one of the faulty individual. I changed via GEDCOM edit the "PEDI" und called up the name to get the split. Now this person is fine, but the other are still wrong. I'am scared now, that other induviduals are also wrong.
    The problem, i guess is still not sovled.
    Regards
    Bodo

     
  • Anonymous - 2010-01-24

    No, the fault is corrected. You need to refresh the cache. If you look again now they are all correct now.

     
  • Bodo

    Bodo - 2010-01-24

    Hi

    thanks a lot for all of You for the help. I don't know how this straingh date entered, may bei an import from another program I used before.
    Any way I hope verything is fine no and thanks a lot for the help. I hope it will help other people to avoid such trouble.
    You have made a nice program

    All the best

    Bodo

     
  • Greg Roach

    Greg Roach - 2010-01-25
    • status: open --> closed-invalid
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks