TOPIC:

I am doing genealogical research for my son's father-in-law's family, and I want to present the results as a separate webtrees tree. I've set it up as a second tree in my webtrees database with myself as the sole administrator for both trees and the family members as 'members'. So, I have two trees on one site, with a single user with administrator access to both trees.

I've added a few individuals to the file and built a rudimentary tree which displays for me without error. Still, when the family members view their tree, the records show 'INDI:BIRT:_PRIM: Y' messages beside each individual and 'FAM:MARR:_PRIM: Y' against each marriage event, indicating invalid Gedcom.

Do I need to set up separate User/Administrators for each tree instance?

> indicating invalid Gedcom.

These tags begin with an underscore, which means that they are technically valid - but webtrees has no idea what they are for.

So, I guess these "_PRIM Y" tags were created by another genealogy application. Out of interest, which one?

You can delete them, or we can try to add support for them (if we knew what they meant...)

> Do I need to set up separate User/Administrators for each tree instance?

You can, if you want to. But you don't have to.

These records were created by manual data entry directly into Webtrees, not from imported Gedcom files

What version of webtrees did you use to enter these individuals?

2.1.16

When I add a marriage fact to a family in the Demo System I don’t see any subtags of _PRIM Y.

1 MARR
2 TYPE CIVIL
2 DATE 01 JAN 2020

Please explain!

I'm not surprised you don't see a problem.

As I said in my original question, the problem only becomes apparent when a 'member' of the tree subsequently accesses a record/event added by a 'manager'.

Do these members have update rights or just display?

I tried displaying the family record with a member on the demo system and nothing changed.

But I can’t test it with a member having higher access rights.

Someone else needs to look at this with their system.

Do you have any add on modules? Can they be turned off and a new test run on your system?

This is a really standard deployment re add-on modules, everything is 'out-of-the-box'

Members do not have any access rights, only display, seems odd you don't see this on the demo system.

I'll set-up a more controlled test system tomorrow and report back.

Thanks for your help.

A record like 'INDI:BIRT:_PRIM: Y' does not appear magically. Someone has added _PRIM Y to the birth event of a person. You can check this: go to this person, edit the birth event and select "raw GEDCOM". Now you should see this very unusual _PRIM entry.

You can delete all those entries using the search and replace function in the control panel. Are you familiar with that? Have you ever used "regular expressions" for search?

After extensive testing, I cannot recreate the insertion of _PRIM Y records into the Gedcom file.

On investigating the Gedcom file, the _PRIM Y records are only the 'tip of the iceberg' of non-standard records in the file - they were the only ones being shown as illegal tags to 'display only' users. The root cause of the problem was how I had chosen to build the tree by using the interactive tree-building feature of 'Find My Past', then exporting an embryonic Gedcom to webtrees and adding notes and sources directly.

Approximately 10% of the Gedcom comprised non-standard tags introduced by Find My Past.

Luckily I spotted this problem after adding only 17 individuals to the file, and I plan to rebuild the tree from scratch.

The webtrees issue remains; why were a small proportion of non-standard tags being highlighted to display only users, who could do nothing about them, but not shown to an administrator who could follow up on them and correct the problem?

Thanks to everybody that helped me identify the issue.

So you did use another app ('Find My Past') for gedcom creation + Import!!!!!!!!!!!!

Yes, in my defence, I didn't consider FMP as a family history records compiler, just as a records source, I know better now!

> The webtrees issue remains; why were a small proportion of non-standard tags being highlighted to display only users, who could do nothing about them, but not shown to an administrator who could follow up on them and correct the problem?

This sounds odd.

There is a config option "Hide/Show GEDCOM errors" in the family-tree preferences page. What is it set to?

Yes, I just found it, and set to 'don't display' - problem solved, thanks