results of relationship calculation

Bug #1006781 reported by Otmar Mayr
38
This bug affects 5 people
Affects Status Importance Assigned to Milestone
webtrees
Invalid
Wishlist
Unassigned

Bug Description

Some of my relatives had written to me, that some results of the relationship-calculation in WT in some cases are incorrect.

e.g. in Brothers Keeper (shows only blood relationships): second cousin, once removed (german: Cousine 2. Grades, 1 Generation versetzt).

WT show this as "second cousin once removed ascending", without commas.

Additional are shown from WT other pathes, without blood relationship.

a) Mutters Cousine 2. Gradess Schwester (it should be "Grades" - only 1 "s", comma is missing)
b) Urgroßonkels Sohns Stieftochter (in this case she is a daughter (Tochter), not a stepdaughter (Stieftocher))

and other less usefull declarations how "Urgroßonkels Enkelsohns Schwester", and others words...

I like it, that WT can show this connections. But puzzling is the text of the explanations.

Another problem is, the PHP-server hangs sometimes with complex calculations of the relationship.

Of this reason I would prefer, if non blood relationsships have no text of explanations. It where also very important if WT have a option for a limitation for the relationship calculation:

a) Deselection of the modul (menu) "relationship calculation")
b) only blood relationship
c) Calculation relationship till the grad 1, 2, 3, ... 10 or all.

Revision history for this message
kiwi (kiwi3685-deactivatedaccount) wrote :

Otmar, you might want to raise this on the forum, but I can tell you something about these issues here as well. They are not truly "bugs", though I am sure they are incorrect for you.

Many of these are issues with translations. These should be handled by proposing different translations in the translation system here on Launchpad. Anyone can suggest a new translation, and then the German translation team leader will consider if to approve it. (https://translations.launchpad.net/webtrees)

But some of the problem is that the existing relationship code is not perfect (though better than almost any other software in the world). Greg has plans to change it, so you should get involved in the discussions. Read http://webtrees.net/en/forums/8-translation/23242-translation-into-dutch especially post #9 by Greg. Do not think because its title includes "Dutch" that it is just about that language. It is not. It is about relationships in all languages.

A separate problem is your comment "Another problem is, the PHP-server hangs sometimes with complex calculations of the relationship."
We agree. It is the most resource-hungry page in the entire system. In part the changes proposed by Greg will help this. In part, we need a completely new way to compute relationships. Greg has experimented with some, but they all have limitations. The biggest is that they require versions of MySQL most web hosts do not yet implement.

We believe that with these improvements, your final suggestion for de-selecting non-blood relations will never be necessary.

For all these reasons, I urge you to discuss the issues on the forum, and propose translation changes in the translation system. For these reasons, and NOT because we disagree with anything you say, I will mark this "bug" as a "wishlist" item.

Changed in webtrees:
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
kiwi (kiwi3685-deactivatedaccount) wrote :

Sorry, I just realised that the category "wish list" no longer exists here (launchpad change, not ours). So I have marked it as "In progress", as although not a bug, we are working on solutions.

Changed in webtrees:
importance: Medium → Wishlist
Revision history for this message
Hermann Hartenthaler (hermann-hartenthaler) wrote :

I have the same problems since I updated from 1.2.6 to 1.3.0 now. With the old version it was no problem for webtrees to show a relationship with 50 or more steps between two persons, now I have problems when there more than 10 steps inbetween. Very bad, because this was a very good function of webtrees. For me this is a bug, not a point for the wishlist.

Revision history for this message
kiwi (kiwi3685-deactivatedaccount) wrote :

<<For me this is a bug>>

For us too. But we're not going to waste time patching a fundamentally broken piece of code. It WILL be fixed. We agree that it is a valuable tool. But not until we are able to do the job correctly. It is "wishlist' because we "wish" it was easy to fix, and that we had 50 hours free every day to work on things like this.

We also "wish" that everyone would get their web hosts to upgrade PHP and MySQL to the very latest versions, so we could build a good solution to this. It needs features that only the latest code supports.

Latest PHP is 5.4, but 34% of webtrees sites still use ancient 5.2
Latest MySQL is 5.5, but only 33% of sites use that.

Revision history for this message
Michele Salvador (bluelettrico) wrote :
Revision history for this message
fisharebest (fisharebest) wrote :

The relationship code needs to be rewritten. Any further comments should be made at https://github.com/fisharebest/webtrees/issues/256

Changed in webtrees:
status: In Progress → Invalid
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.