* Change any Fact Tag Plugin Error

[Chrisv]

I am getting an error message when I try to run the Change and Fact Tag plugin. It occurs as soon as I press the Run command. Other plugins seem to work okay (the couple I tried). Can anyone give me a suggestion of what I need to do? See below...
Thanks!

[Chrisv]

Sorry, I forgot the screenshot!

[tatewise]

Sorry about that Chris. It is something rather unusual regarding some undefined custom facts in your data.
Please use Tools > Fact Types..., tick Show Hidden on the right, then click the Fact Set column heading.
You may have to widen the window a little to achieve a screenshot similar to the one below.
The facts I'm interested in are those with Fact Set <none> and Visible <undefined> so ensure they are all displayed.

FactTypesUndefind.png (96.04 KiB) Viewed 1572 times

[Chrisv]

That showed me what the offending item was, but I'm the one that should say sorry. I had tried out a few things earlier this week, and didn't realise the consequences. All I had to do was create a new definition for that new event and it made everything good.
Thank you!

[Mark1834]

I was having a play with this in case there are any implications for my fact plugin.

Can undefined facts only come from an import? I couldn't see any way of creating one directly in FH, or have I missed something?

[tatewise]

That is correct Mark, or by editing the GEDCOM file.

Chris I would still like to know the details of your case as it should still be OK in the plugin.
I've tested it against all the <undefined> custom facts shown in my screenshot and it is OK.
So your example is a special exception that I would like to understand.

[Chrisv]

Okay Mike.
I will explain more tomorrow.

[Chrisv]

I was using AS to input a custom Population Register entry. In the AS Template Editor > Fact field I chose "Use custom event" and then entered the following Event name in the field: "+ ♦Pop Register:" I had forgotten to first create a Fact Type in FH to match it. It came through into FH just fine and I forgot all about it. I was attempting to get the AS Event to look like my standard Event with the + that indicates there is a Source. The "♦" is an alt code 4 symbol. I have used alt codes to highlight some of my Events in FH, and ran them through AS for almost a year without any problems. I have also never had a problem with any of the Plugins while using them, including the Change any Facts plugin. When you told me where to look for the problem, it was pretty obvious what caused it. As soon as I created a definition for it, the problem went away.
Since then, I have decided not to use the + and - to indicate if I have a source. I have found it to be redundant since all my Sources have media linked to them and I have never linked media to Events without a Source.
I hope this has helped and thanks for your assistance!

[tatewise]

Chris, I tried a copy & paste of your + ♦Pop Register custom event and Change Any Fact Tag is happy with it.
I'm unsure what you mean by an 'Alt code 4 symbol'. I imagine it is holding the Alt key while entering 0004 on the keypad.
However, that would produce an EOT control character, not a Black Diamond which is Unicode 2666.
Could you explain more precisely how ♦ is created?

[Chrisv]

My keyboard produces it with holding the Alt key while entering 4 on the keypad. I think we must have different keyboards because if I hold the Alt key while entering 0004 on the keypad, I get absolutely no response. I am on windows 10. This is where I got the Alt+4 from: https://altcodeunicode.com/
I will attempt to reproduce what I did on my side also.

[tatewise]

OK, I was not aware that Alt+4 did that but as explained in the website you quote it produces a Black Diamond ♦ which is Unicode 2666 and causes the Change Any Fact Tag plugin no problems.
So it is still not clear what you entered that upsets the plugin!

[Chrisv]

I just attempted numerous times to replicate what may have caused it and have been unable to make it happen again. Each time, it creates an undefined Event and each time the plugin works as it should. Sorry Mike, I can't seem to reproduce it.
If I think of anything, I will certainly let you know.

[tatewise]

Never mind, but next time please preserve the problem data, perhaps by creating a Project Copy if you need to urgently fix the cause of the problem.

[Chrisv]

Hmmm, Let me look to see if I made a backup around that time, and if it might produce the error message. I'll let you know if I'm successful.

[tatewise]

I wonder if you have a Snapshot with the problem?
In a copy of the Project, use File > Backup/Restore > Revert to Snapshot... and select a date when the problem might have existed. Remember that Snapshots are taken the first time FH is opened on any day.

[Chrisv]

Okay, that worked. I am showing the same Plugin error message. I am not going to touch anything until you tell me what you need me to do! I do have to leave in 45 minutes... Will return in about 3 hours.

[Chrisv]

Would it be helpful if I email this to you?

[tatewise]

The Tools > Fact Types..., tick Show Hidden display I described earlier would be a good first step.

[Chrisv]

Here you go.

[tatewise]

I've changed the custom event to + ♦Pop. Register: to exactly match your screenshot, but it still won't fail.

So could you attach just the Project GEDCOM file, or if you are not comfortable with that then Email it to me via:
post at tatewise.co.uk where ' at ' = @

[Chrisv]

I will send the GEDCOM out right away. I did notice that the next Snapshot to dissapear will be the one you want, which is the Saturday, March 04, 2023 file. Is there a way to keep it from disappearing? And a question of curiosity - Is the Snapshot part of the GEDCOM, or part of FH? If part of FH, how will you get to the correct Snapshot?

[tatewise]

You must have restored the Snapshot to be the GEDCOM in your temporary Project for the plugin to fail.
So the GEDCOM file is a copy of the Snapshot file and should contain all the information I need.
The Snapshot files are held within the Project sub-folders and are simply copies of the GEDCOM file on the day the snapshot was taken.