-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When birthdate for at least one child not set at a level, please preserve original webtrees order. #43
Comments
Have you tried version 1.5.1? If so, could you please provide me with a GEDCOM example so that I can understand the problem more easily? |
Yes I have tried v1.5.1. It is the same issue as in previous versions 1.4.1, 1.4.2, 1.5.0. Unfortunately, I can not provide the GEDCOM file as it is has over 500 individuals and I will have to get permission to export it. But using my example from #39, when all the children C1, C2, C3, C4 have birthdate set, the sorting by date works as expected. But :
edit: |
Could you please check, if e887286 fixes your problem? |
Thank you - this seems to work! I will do more testing to confirm. |
This looks fine now. Thank you for your swift response and hard work! |
Describe the bug
When birthdates not set, children at a particular level/tree appear to be sorted randomly.
To Reproduce
In a branch where at least one child does not have birthdate set, order of children is random instead of original webtrees order.
Expected behavior
When birthdate for at least one child not set at a level, please preserve original webtrees order.
The text was updated successfully, but these errors were encountered: