* Order Facts by Sort Date Plugin Problem
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Order Facts by Sort Date Plugin Problem
A user has discovered a typo for DicGed in the Plugin Store Version 1.0 script.
It is associated with handling Fact Witness GEDCOM entries: "3308 attempt to index global 'dicGed' a nil value".
The attached Order Facts by Sort Date Plugin Version 1.0.1 Date 30 Mar 2018 should fix the problem.
[ EDIT Plugin Attachment deleted as in Plugin Store ]
It is associated with handling Fact Witness GEDCOM entries: "3308 attempt to index global 'dicGed' a nil value".
The attached Order Facts by Sort Date Plugin Version 1.0.1 Date 30 Mar 2018 should fix the problem.
[ EDIT Plugin Attachment deleted as in Plugin Store ]
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Order Facts by Sort Date Plugin Problem
Version 1.0.1 by tatewise dated 30 March 2018 fixed my problem. Thank you.
It invoked Rule2 9244 times - as would be expected, but it invoked rule4 6298 times !
I will investigate the sort dates in (or NOT in) my TMG database.
It invoked Rule2 9244 times - as would be expected, but it invoked rule4 6298 times !
I will investigate the sort dates in (or NOT in) my TMG database.
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Order Facts by Sort Date Plugin Problem
Did you check the Help & Advice button? If not then review plugins:help:order_facts_by_sort_date:order_facts_by_sort_date|> Order Facts by Sort Date Plugin.
The large number of Rule 4 entries suggests that many of the TMG facts do not match with the FH facts.
The Result Set produced after running the Plugin should give you some clues as explained under GEDCOM Exceptions in the Help & Advice page.
If you no longer have that Result Set and have closed FH then you will have to revert to a Snapshot taken before the Plugin, via the File > Backup/Restore > Revert to Snapshot command, and then run the Plugin again.
You could save the Result Set to file for future reference.
But you will probably discover it is repetitive for certain facts, which when rectified will quickly reduce the number of exceptions.
Before closing FH, you can use Edit > Undo Plugin Changes to reverse the Plugin Sort Date changes.
You should be able to match up GEDCOM fact is missing entries with GEDCOM fact not used by Project entries for the same people, and it will probably be down to the TMG Tag definition of the GEDCOM Tag to export, particularly for custom facts that you have added to TMG.
If it is not clear from the Result Set exceptions where the problem lies, then post some representative examples for me to analyse.
The large number of Rule 4 entries suggests that many of the TMG facts do not match with the FH facts.
The Result Set produced after running the Plugin should give you some clues as explained under GEDCOM Exceptions in the Help & Advice page.
If you no longer have that Result Set and have closed FH then you will have to revert to a Snapshot taken before the Plugin, via the File > Backup/Restore > Revert to Snapshot command, and then run the Plugin again.
You could save the Result Set to file for future reference.
But you will probably discover it is repetitive for certain facts, which when rectified will quickly reduce the number of exceptions.
Before closing FH, you can use Edit > Undo Plugin Changes to reverse the Plugin Sort Date changes.
You should be able to match up GEDCOM fact is missing entries with GEDCOM fact not used by Project entries for the same people, and it will probably be down to the TMG Tag definition of the GEDCOM Tag to export, particularly for custom facts that you have added to TMG.
If it is not clear from the Result Set exceptions where the problem lies, then post some representative examples for me to analyse.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
E Wilcock
- Megastar
- Posts: 1181
- Joined: 11 Oct 2014 07:59
- Family Historian: V7
- Location: London
- Contact:
Re: Order Facts by Sort Date Plugin Problem
I have been using fh for more than two years now to run some substantial new Projects. So am familiar with the software. And no longer have the habit of working in TMG.
It was my intention this summer to move some of my TMG trees permanently to fh, and for the first time to run the trees which are already in fh through the Order by sort date plug in, referring to their TMG exported Gedcom.
A few days ago, I ran the plug in (tho not the latest version) on one of my most important trees that had always been unstable in TMG. It has 2287 people. Although many events were reported as being undated in TMG, there was no problem. I have opened the All tab for my grandfather and his residence has a sort date.
Yesterday I received an enquiry about a smaller tree of 409 people which I moved from TMG to fh in July 2017 when another researcher was adding to my information.
I decided it was time to make the move final and to run it with the sort date plug in and to be a bit more methodical. This time to download the latest version of the plug in.
This produced an error message.
"An error has occurred plug in failed to complete
[string "C:\ProgramData\Calico Pie\Family Historian\..."]3308 attempt to index global 'dicGed' a nil value."
I do not understand this message and am not sure Mike whether or not this is
my user error - that being old and forgetful I failed to carry out some vital tidying?
Or whether it is this particular Project?
Or whether the problem is in the latest version of the plug in.
I have not opened the Gedcom to find dicGED.
There is no hurry at all to sort this out. It can wait till after the bank holiday weekend - I have entered additional data in this Project in fh over the last year. The sort dates are only becoming important now Rootsweb are (I hope) about to restore my Genealogy website. Which means I shall need to get to grips with Gedsite.
It was my intention this summer to move some of my TMG trees permanently to fh, and for the first time to run the trees which are already in fh through the Order by sort date plug in, referring to their TMG exported Gedcom.
A few days ago, I ran the plug in (tho not the latest version) on one of my most important trees that had always been unstable in TMG. It has 2287 people. Although many events were reported as being undated in TMG, there was no problem. I have opened the All tab for my grandfather and his residence has a sort date.
Yesterday I received an enquiry about a smaller tree of 409 people which I moved from TMG to fh in July 2017 when another researcher was adding to my information.
I decided it was time to make the move final and to run it with the sort date plug in and to be a bit more methodical. This time to download the latest version of the plug in.
This produced an error message.
"An error has occurred plug in failed to complete
[string "C:\ProgramData\Calico Pie\Family Historian\..."]3308 attempt to index global 'dicGed' a nil value."
I do not understand this message and am not sure Mike whether or not this is
my user error - that being old and forgetful I failed to carry out some vital tidying?
Or whether it is this particular Project?
Or whether the problem is in the latest version of the plug in.
I have not opened the Gedcom to find dicGED.
There is no hurry at all to sort this out. It can wait till after the bank holiday weekend - I have entered additional data in this Project in fh over the last year. The sort dates are only becoming important now Rootsweb are (I hope) about to restore my Genealogy website. Which means I shall need to get to grips with Gedsite.
Genealogy site at http://freepages.genealogy.rootsweb.anc ... /~wilcock/
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Order Facts by Sort Date Plugin Problem
Sorry Evelyn, that is the bug fixed by the Plugin Version 1.0.1 Date 30 Mar 2018 attached to my first posting in this thread.
Please use that one instead of the Plugin Store Version 1.0.
Please use that one instead of the Plugin Store Version 1.0.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
E Wilcock
- Megastar
- Posts: 1181
- Joined: 11 Oct 2014 07:59
- Family Historian: V7
- Location: London
- Contact:
Re: Order Facts by Sort Date Plugin Problem
Thank you Mike. Sorry not to have noticed this thread.
Genealogy site at http://freepages.genealogy.rootsweb.anc ... /~wilcock/
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Order Facts by Sort Date Plugin Problem
I have belatedly updated the Order Facts by Sort Date Plugin to Version 1.1 Date 4 Sep 2018 in the Plugin Store.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry