Using the latest version....when I upload a GEDCOM file, I get an error message that reads "Unable to find individual with id." If I continue and import the file, I get what looks like a successful import, but the trees are all empty. I can enter individual ids, but only the first generation is populated with data, the rest of the tree is empty.
Searching for an ID with the "findID" link doesn't appear to work either. I suspect a corrupt GEDCOM file, but I'm not seeing any errors on import. I've deleted/uploaded/imported several times, but no luck.
I've noticed lots of "Notices" as well for undefined variables and indexes...is this indicative of a bad GEDCOM import, or a configuration issue?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There was mention of a test GEDCOM file floating around (doesn't appear to be part of the distribution, though). Would this help determine whether I have a configuration or file import issue?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the GEDCOM torture tests can be found at http://www.geditcom.com/gedcom.html
ftp://www.dcs.hull.ac.uk/public/genealogy/presidents.ged
is a us presedential gedcom.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, I'm getting closer to success, but not quite there yet:
Tried changing to MySQL, uploaded GEDCOM torture tests, no go. Pedigree trees are still empty (but the database is populated).
So I tried presidents.ged. Works like a charm, everything is populated with what looks like valid data.
Looks like the configuration is OK, the issue resides in the GEDCOM format. Has anyone been successful in importing the GEDCOM torture tests? Any ideas why the torture tests don't work, but the presidents GEDCOM file does?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Mac vs Windows issue is to do with the line terminators. If you use GEDitCOM on the Mac for instance, then you have to ensure the GEDCOM file has Windows type line breaks. I do this by just opening the GEDCOM file in WordPad, then saving it straight back out again. No changes, just a open then save. It adds a few kb to the file, but it then works.
You can probably achieve the same using BBEdit's Save Options.
GEDCOM files are text files. So you may have to tell the ftp client not to transfer it in binary. (Does this actually matter?)
Oh and you need to use UTF-8 format in the Gedcom ...
Just some ideas anyway, early on Christmas morning.
Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Success! After comparing the various GEDCOM files, I discovered the allegedly 5.5-compliant GEDCOM file I was trying to import had tags that were all more than 4 characters long (INDIVIDUAL, PLACE, MARRIAGE, etc.). Using vim and a copy of one of the torture tests, I did global search and replaces for all of the tags (the obvious ones...I couldn't figure out DIVORCE, so I just assumed ANUL was the correct tag).
I guess FTM doesn't really export GEDCOM 5.5-compliant files after all...a simple Perl script should do the trick though.
Thanks for all the suggestions!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using the latest version....when I upload a GEDCOM file, I get an error message that reads "Unable to find individual with id." If I continue and import the file, I get what looks like a successful import, but the trees are all empty. I can enter individual ids, but only the first generation is populated with data, the rest of the tree is empty.
Searching for an ID with the "findID" link doesn't appear to work either. I suspect a corrupt GEDCOM file, but I'm not seeing any errors on import. I've deleted/uploaded/imported several times, but no luck.
I've noticed lots of "Notices" as well for undefined variables and indexes...is this indicative of a bad GEDCOM import, or a configuration issue?
First thing to check is what got imported. Are you using MySQL or Index files?
If using MySQL, use a tool like PhpMyAdmin to see what was imported into the pgv_individuals and pgv_families table.
If you are using index files, open the index/gedcom.ged_index.php file and see if the gedcom records are in there.
If the records are missing from the database then there is most likely a problem with your gedcom.
If you created the gedcom on a mac, you will need to convert it to a windows or unix file before it will work.
--John
>>First thing to check is what got imported. Are you using MySQL or Index files?
Index files.
>>If you are using index files, open the index/gedcom.ged_index.php file and see if the gedcom records are in there.
Records are there.
>>If you created the gedcom on a mac
The GEDCOM file was created in Windows, but uploaded/imported from a Mac. phpGedView is hosted on a Linux box.
There was mention of a test GEDCOM file floating around (doesn't appear to be part of the distribution, though). Would this help determine whether I have a configuration or file import issue?
the GEDCOM torture tests can be found at http://www.geditcom.com/gedcom.html
ftp://www.dcs.hull.ac.uk/public/genealogy/presidents.ged
is a us presedential gedcom.
OK, I'm getting closer to success, but not quite there yet:
Tried changing to MySQL, uploaded GEDCOM torture tests, no go. Pedigree trees are still empty (but the database is populated).
So I tried presidents.ged. Works like a charm, everything is populated with what looks like valid data.
Looks like the configuration is OK, the issue resides in the GEDCOM format. Has anyone been successful in importing the GEDCOM torture tests? Any ideas why the torture tests don't work, but the presidents GEDCOM file does?
The Mac vs Windows issue is to do with the line terminators. If you use GEDitCOM on the Mac for instance, then you have to ensure the GEDCOM file has Windows type line breaks. I do this by just opening the GEDCOM file in WordPad, then saving it straight back out again. No changes, just a open then save. It adds a few kb to the file, but it then works.
You can probably achieve the same using BBEdit's Save Options.
GEDCOM files are text files. So you may have to tell the ftp client not to transfer it in binary. (Does this actually matter?)
Oh and you need to use UTF-8 format in the Gedcom ...
Just some ideas anyway, early on Christmas morning.
Mark
Success! After comparing the various GEDCOM files, I discovered the allegedly 5.5-compliant GEDCOM file I was trying to import had tags that were all more than 4 characters long (INDIVIDUAL, PLACE, MARRIAGE, etc.). Using vim and a copy of one of the torture tests, I did global search and replaces for all of the tags (the obvious ones...I couldn't figure out DIVORCE, so I just assumed ANUL was the correct tag).
I guess FTM doesn't really export GEDCOM 5.5-compliant files after all...a simple Perl script should do the trick though.
Thanks for all the suggestions!
The Divorce tag is DIV