I have good and bad news. The bad news is, that I can’t reproduce the export error, not on Linux, nor on Windows 10 or 11, with Gramps 5.1.6 or my personal 5.1.7.
The good news is, that the handle shown in the error message can be found in the Gramps XML of your tree, as a link in a note. And that link points to a citation that doesn’t exist, so there is something wrong, and editing the note will most likely cure it, so that you can do the export yourself.
Other bad news is, that the check & repair doesn’t see this, at least not in 5.1.6/7. When I run it in the latest development version of 5.2.4, it does detect it, and says
2024-10-10 22:30:19.495: WARNING: check.py: line 2542: FAIL: Bad Note Link found, Citation: handle: f56465bc00c45f62f889e5695e
And as you can see, that’s the handle in the error message.
I don’t read all of the solutions, but it seems that no one talked about using tags.
Briefly, the way i think i’ll do :
Create a copy of the tree (export / import in a new tree) and work on this specific copy)
Creating a tag like “To keep” (not to remove)
Selecting objects (persons, families, events, etc.) with filters and adding tag “To Keep”
Little tips to know
You can use the result of a filter on a specific object in other filters of other object (like event).
Deleting ancestors from a specific branch and can delete a part of your own ancestors (implexes)
Some filters are easiest to create when you think you can use the “Display only values that do not correspond…” (I don’t know in english, but see following screenshot)
May be some additional and temporary “Tags” would be helpful for filtering.
Then using export with just one tag should be easiest.
That’s the way I would do it. it is a pain if your tree is too large but you are in control.
I have a variation of this I have a tag for every individual genetically related to and another for people who marry into these families but I have done this from the start.
So if I want a clean tree I simply filter on the tags.
phil
That’s because there was a discussion about slowness in mass adding and removal of thousands of tags last week. It kicked off a major performance review and a new major project.
Thanks for confirming @sam888 - being able to communicate with the reporter is important, so logging in makes sense.
@takaji I’m curious whether there’s any indication of the requirement to be logged in anywhere in the process of filing a bug report? Where would it make most sense to state that?
I don’t have so much persons (around 5,000 vs 48,819 ) so i don’t have much slowness by adding or removing tags.
But yet I remember wich feature seem slow… (I’ll post it in the appropriate discussion)
And just to follow-up here: Upgrading Gramps solved my problem. This is despite what I wrote earlier about upgrading NOT solving my problem.
(The second time I tried using the most recent Gramps, I got a dialogue pop-up which asked me to confirm to upgrade my database to a newer schema, while the first time I tried I did not get such a dialogue.)
) so i don’t have much slowness by adding or removing tags.