Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Place Hierarchy Links Broken After Gedcom Import #4958

Open
samiona2 opened this issue Mar 1, 2024 · 1 comment
Open

Place Hierarchy Links Broken After Gedcom Import #4958

samiona2 opened this issue Mar 1, 2024 · 1 comment

Comments

@samiona2
Copy link

samiona2 commented Mar 1, 2024

If I create a link to a specific place, the next GEDCOM import will just continue the numbering, thus invalidating the link and redirecting to location 0 - World. For example if I create the following link to London in my tree

link to London
On the next GEDCOM import, the links probably start at the max of the previous import.
Since webtrees has a table of all locations (optionally with latitude and longitudes for maps), can't the link reference the actual location name and not an ID? At the least, if that table has IDs, it can reference the IDs in that table, something that seemingly does not change (since I see that the maps do not lose their latitude and longitude with every import).
Thanks

@Norwegian-Sardines
Copy link

What do you mean by: "If I create a link to a specific place". What kind of "link" are you creating? Can you supply GEDCOM code? Where does this "Link" get added? Normally when we add a place to a fact we add it in the PLAC tag which will give you a dropdown of all the current "Places" in the database.
Dropdown

We can't see the example: "Link to London"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants