Kiwitrees on Twitter

    mobile, 3.1, individual resource, ckeditor, tags, simpl_pages, errors, administration pages, logout, message contactform, partner, NCHI, configure, click, .mo, users, DIV, 3.2.3, calendar, census assistant, album, css, children, missing data, name, burial, 3.2.2, kiwitrees theme, I18N, zend, research tasks, bug, future, kiwitrees, notes, Fancy imagebar, data errors, married, birth, json, locked out, 3.0.0. setup, 7.1, 3.0.0 widgets, ID notes, image, fancy tree view, beta, media, DSGVO, title, hover, relationships, fatal error, 3.2.0, ID facts, HTML block, wish, support, custom


    1643 posts

    No matter if I accept the change it is the same result. Also same result for anybody else I have added with ASSO

    That is good. One possible cause eliminated.

    I do understand what you are saying. This is why I said it might be looking at the husbands death in error. The calculation of estimated dates for event sorting is complex, so there is never a perfect solution to sort all facts perfectly when dates are missing. It is even more complex when applying inter-connected events such as ASSO. I find it best to always include a date, and I believe that if you know an event occurred, then you do also know enough to add an estimated date. If you add a date like AFT 1890 (or any date later than the last event you do have a date for) then her death will be in the right place.

    My personal kiwitrees site is