ERROR 8: Undefined index: M/F (both cases)
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
ERROR 8: Undefined index: M
0 Error occurred on line 503 of file individual_ctrl.php in function print_sex_record
1 called from line 95 of file individual.php
Got that error first on latest release, upgraded to SVN, still the same.
GEDCOM example:
0 @I181@ INDI
1 NAME John /Doe/
2 GIVN John
2 SURN Doe
1 SEX M
I see no problem, the format should be correct. The data was exported from MyHeritage, if that information helps.
Henrik
Did you reimport your gedcom when you upgraded? The SEX portion of the table was modified for version 4.2+ and has to be populated. BTW, usually an "example" as you offered will be of little help as there may be something particularly unique to the problem, although in this case, there is not.
Stephen
I'll jump on here since I have the exact same problem as ahven had after I upgradet to 4.2.
Question: How do I populate the 'sex' field with correct values for all entries? Do I have to manually edit each record?
I appreciate any help I can get.
Does this happen for every individual, or just some?
Also, when you say "updated to SVN", it would help to know exactly which version, as the code gets updated several times each day.
It is also not clear from your post whether this has never worked, or only stopped working after an upgrade.
Actually the SVN version made no difference, the problem was solved when I re-imported the GEDCOM. It was working partially before and haven't found any faulty profiles so far. I just started using PhpGedView this morning, it's just strange that it didn't work with the initial import.
Henrik
<it's just strange that it didn't work with the initial import. >
What does this mean? You don't say whether you had reimported the GEDCOM as soon as you upgraded to the newer SW version. This was essential to populate all the tables properly, but errors may not have been readily apparent. There are numerous threads here, similar to yours, which repeatedly ask whether an import had been performed. I suspect your issues are similar. Glad its working correctly. For future inquiries by others, Try a re-import (after you have backed up your current data and configuration.
-Stephen
You didn't say which version you upgraded from, which makes it harder to guess.
The i_sex column in the pgv_individuals table is populated when you import the gedcom.
OK. Thanks. It seems to be working now. I didn't know first what "importing the gedcom" meant, so for reference in case others are having the same problem, here is what I did:
Under "Manage GEDCOM", i selected to download a copy of the gedcom (.gdm) file to my local computer.
Back under "Manage GEDCOM" again, i chose to "upload replacement" and selected the gedcom file i just downloaded. I selected to erase old entries and keep media links when importing.
Quite simple, really. :)
Terje
If you were reimporting a PGV exported GEDCOM, it was not necessary nor desirous to "Keep Links". This is really only for supporting offline programs that don't support PGV's method of media tracking. If you "Keep Links" with PGV and reimport, you may have duplicated Mxxx records. Please review now, before you make changes and can't reimport the GEDCOM you DL'd and select NO - Don't Keep. Also, you can use the EXPORT function on the GEDCOM management screen to put a copy of the DB into your "index" folder/storage place specified for GEDCOMs. Check the permissions and look for the TRLR to be sure its complete, and then use that file as it eliminates the Download/Upload mechanism that could possibly induce errors.
-Stephen