Vital Records Report does not sort - 1.5.1 stale

Bug #1266160 reported by meliza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webtrees
Fix Released
Medium
fisharebest

Bug Description

See http://dev.webtrees.net/demo-stable/reportengine.php?ged=demo&action=setup&report=modules_v3%2Fbdm_report%2Freport.xml
for instance for London.

I try to sort by birth date or by death date.
The report is not sorted.

Meliza

Revision history for this message
fisharebest (fisharebest) wrote :
Changed in webtrees:
status: New → Invalid
Changed in webtrees:
status: Invalid → New
Revision history for this message
meliza (meliza) wrote :

When I log-in to the demo-dev site and create the report for London sorted by death-date, I see 1910 before 1901. After that the records are sorted OK.

Between the date groups there are individuals without death dates.

Is the wrong report data cached?

Meliza

Revision history for this message
meliza (meliza) wrote :

On the demo-dev when I log-in to the site the people who are alive are printed in an odd sequence, when I sort by death dates. The sequence is persons born 2002, 1964, then dead 1841, 1999, 1964, 1996, 1999 and then dead 1819, ...

Meliza

Revision history for this message
fisharebest (fisharebest) wrote :

The routine to calculate estimated death dates (max-alive-years after estimated birth date) does not return any future dates.

This is a courtesy to living individuals - we do not want to predict their death date.

But the lack of a date causes the sort algorithm to fail.

Changed in webtrees:
status: New → Confirmed
Revision history for this message
fisharebest (fisharebest) wrote :

The issue also affects the individual list, which uses the same logic.

The fix is to always calculate the future estimated death date, but not display it on the lists.

Changed in webtrees:
status: Confirmed → Fix Committed
importance: Undecided → Medium
assignee: nobody → fisharebest (fisharebest)
Revision history for this message
fisharebest (fisharebest) wrote :

Fix released in 1.6.0

Changed in webtrees:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.