- This topic has 10 replies, 2 voices, and was last updated 8 years, 6 months ago by
.
-
Happened to check for errors while on Admin page. Bit confused in that all the Family records have the Indi records linked back. Sample:
INDI A9242 has a FAMS link to F7169. F7169 does not have a link back to A9242.
0 @F7169@ FAM
1 HUSB @A16702@
1 WIFE @A9242@ <<<<<<<< A9242 is right here, same as all the others showing as error
1 ENGA
2 SOUR @S2992@
3 DATA
…----- [updated: 31Dec2022] MacOS: 10.15.7 (Catalina) Safari 14.1.2; Firefox 108.0.1 (64-bit); 108.0.1462.54 (Official build) (x86_64)
Alter-Drukarsh connections | The Garelick: 3.3.11b - PHP 8.0 FastCGI - mySQL 8.
-
I think / hope I would have been flooded with inquiries if that was a system bug.
Almost certainly a data error. Things to check first:
- Have you clicked the links in that error message to see if they take you where you would expect?
- Are you looking at the same tree for the error check as the GEDCOM data?
- “A” is a non-standard prefix for INDI records. Is it correctly set to that in the family tree configuration?
- Do you have a lower-case “a” somewhere in those records instead of “A” [or “f” instead of “F”]?
IGNORE ALL THAT – I DO SEE A PROBLEM.What version of kiwitrees are you running?
Nigel
My personal kiwitrees site is www.our-families.info -
Ha, ha. I read your reply via email and did the checks you mention. Only now that I’m replying did I find “ignore…. 🙂
I’m running 2.0.2, did you update?
PS: I replaced the “I” for “A” shortly after I started using PGV because of feeble eyes! Capital i looked like 1 too often. Yes, properly set in Admin immediately when converting over generations.
----- [updated: 31Dec2022] MacOS: 10.15.7 (Catalina) Safari 14.1.2; Firefox 108.0.1 (64-bit); 108.0.1462.54 (Official build) (x86_64)
Alter-Drukarsh connections | The Garelick: 3.3.11b - PHP 8.0 FastCGI - mySQL 8.
-
No that is the latest version.
I panicked because I did manage to replicate the problem, but only on a test site running the very latest beta code.
But the cause in my case was a corrupt set of GEDCOM data, caused by too many experiments during testing with the new (next release) renumber and append trees feature.
A quick re-import of my GEDCOM file fixed all the errors. I have also checked a few other sites running 2.0.2 and none show that problem.
Where did that GEDCOM snippet you posted come from. Was it a GEDCOM file or the raw GEDCOM edit screen?
Nigel
My personal kiwitrees site is www.our-families.info -
The snippet was from the raw GEDCOM edit screen. I just counted about 30 errors. Most peculiar is the edit dates of the records were all this past week. Very strange.
I don’t often remember to check errors but not all that long ago I did a massive check of data so decided to see if I did changes correctly and the few errors i made, cleaned up all of them. Those were definite mistakes that time round.
----- [updated: 31Dec2022] MacOS: 10.15.7 (Catalina) Safari 14.1.2; Firefox 108.0.1 (64-bit); 108.0.1462.54 (Official build) (x86_64)
Alter-Drukarsh connections | The Garelick: 3.3.11b - PHP 8.0 FastCGI - mySQL 8.
-
Can you think of anything that is different about this last week? A different machine, fresh upload of the GEDCOM file, anything related to youe work-flow?
It might never be possible to find the cause, but the fix will probably be to do the following:
- If you have a backup of the GEDCOM from before these entries put it somewhere safe [not the kiwitrees/data/ folder]
- Then run “Export” to create a new GEDCOM file with all those latest changes included.
- Now IMPORT that new GEDCOM file.
If that doesn’t fix everything, you will need to import your backup GEDCOM (step 1) and re-enter those changes.
Nigel
My personal kiwitrees site is www.our-families.info -
I did the remove & re-add routine for all the errors from within kiwitrees to resolve. The exported file, imported into GEDitCOM found no link problems, just two syntax errors (3 TYPE and a 5 CONT after a 3 CONT) which I fixed too.
Noticed many but not all, were records that I had added ASSO tags to the family record (marriage for example).
Am just doing updated export as clean. I add the date to file so that if I run export again, I don’t accidentally overwrite (which is I assume why you said not to store in data folder). I then download to local drive as grandfather backups.
(I knew there wasn’t kiwitrees coding problem as you said, others would have found problems too. Just couldn’t figure out why so many showed up “all of a sudden”.
Read about proposed 3.0 release. Interesting things coming.
----- [updated: 31Dec2022] MacOS: 10.15.7 (Catalina) Safari 14.1.2; Firefox 108.0.1 (64-bit); 108.0.1462.54 (Official build) (x86_64)
Alter-Drukarsh connections | The Garelick: 3.3.11b - PHP 8.0 FastCGI - mySQL 8.
-
Glad that’s fixed.
Have you removed all ASSO tags from family records?
You must, as apart from causing this sort of error it is not allowed in GEDCOM spec, as mentioned previously when you asked about it.
Did you add them through raw GEDCOM edit, or have I left a back-door open to let you add ASSO to FAM tag list? If so, I need to close that door.
Nigel
My personal kiwitrees site is www.our-families.info -
Glad that’s fixed.
Have you removed all ASSO tags from family records?
You must, as apart from causing this sort of error it is not allowed in GEDCOM spec, as mentioned previously when you asked about it.
Did you add them through raw GEDCOM edit, or have I left a back-door open to let you add ASSO to FAM tag list? If so, I need to close that door.
No, I’ve not removed them (FAM ASSO tags). Sorry, don’t recall that I wasn’t suppose to have them. The option is in the edit window for the event, like marriage. Two ASSO fields (unlike one for individual). Hence if you’re saying they’re not proper, then I had no idea.
What’s best way of finding the records affected if they’re wrong? How do I express associated people to a family event?
----- [updated: 31Dec2022] MacOS: 10.15.7 (Catalina) Safari 14.1.2; Firefox 108.0.1 (64-bit); 108.0.1462.54 (Official build) (x86_64)
Alter-Drukarsh connections | The Garelick: 3.3.11b - PHP 8.0 FastCGI - mySQL 8.
-
I was referring to the FAM record itself, not to events within it, and thought you were too.
Officially neither should be allowed, and no event should ever use it, but kiwitrees and webtrees have always broken the event rule and allowed them there.
The proper use of ASSO is as descibed in the GEDCOM spec. as “An indicator to link friends, neighbors, relatives, or associates of an individual” and “The association pointer only associates INDIvidual records to INDIvidual records.”
So:
0 @I7169@ INDI
1 NAME John /Smith/
1 ASSO @I1234@
2 RELA godson
Totally OK – the only GEDCOM approved use of the tag.0 @I7169@ INDI
1 NAME John /Smith/
1 BIRT
2 DATE 21 AUG 2014
2 ASSO @I8865@
3 RELA twin
Allowed by kiwitrees, but not correct GEDCOM0 @F7169@ FAM
1 HUSB @A16702@
1 WIFE @A9242@
1 ASSO @I1234@
Not allowed by kiwitrees and not correct GEDCOM0 @F7169@ FAM
1 HUSB @A16702@
1 WIFE @A9242@
1 MARR
2 DATE 10 OCT 1892
2 ASSO @I5224@
3 RELA witness
Allowed by kiwitrees, but not correct GEDCOMNigel
My personal kiwitrees site is www.our-families.info
- The topic ‘error check’ is closed to new replies.