Fatal error after making wrong couple

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

Bug Description

The error I got was a result of a mistake I made.
This was the error:
Fatal error: Uncaught exception 'Exception' with message 'Invalid family in WT_Individual::getStepFamilyLabel(F11408@1)' in /var/www/qb209310/data/www/familiezwaga.nl/library/WT/Individual.php:775 Stack trace: #0 /var/www/qb209310/data/www/familiezwaga.nl/modules_v3/family_nav/module.php(76): WT_Individual->getStepFamilyLabel(Object(WT_Family)) #1 /var/www/qb209310/data/www/familiezwaga.nl/library/WT/Controller/Individual.php(381): family_nav_WT_Module->getSidebarContent() #2 /var/www/qb209310/data/www/familiezwaga.nl/individual.php(42): WT_Controller_Individual->getSideBarContent() #3 {main} thrown in /var/www/qb209310/data/www/familiezwaga.nl/library/WT/Individual.php on line 775

Caused by this:
I had the following couple:
man1 X wife1
kids: son1 and son2

I wanted to add an existing woman (daugther1) to son1 as a wife to make a new family.
By mistake I made a couple of wife1 and daughter1. (I had selected wife 1 instead of son1)
webtrees did not mind doing this. (Good!!)
But after selecting son1 or son2 I got this fatal error. ( not so good)
So I am afraid it is not fool proof yet. (or idiot proof)

It was easily solved by deleting the wrong family. So not very crucial.

This error was a replay of the original event, so it's easily reproduced.
Greatings
Leo

Revision history for this message
fisharebest (fisharebest) wrote :

> so it's easily reproduced.

Here's a GEDCOM with the problem.

Changed in webtrees:
status: New → Confirmed
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.5.3

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

Bug attachments

Remote bug watches

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