Jefferson49
Jefferson49
The "Geonames" module is listed twice as well. I also think it is confusing, because the descriptions are different, but the settings for the two modules seem to be identical....
While testing Gedcom 7, I also ran into this issue. What is inconvenient at the moment is that editing and saving any data, which contains @ VOID@ links, seems to...
Some further comments of @fisharebest from the discussion in #4883: > The submitter record could be empty - or it could contain the details of the user who created the...
> Thus I believe we are allowed to add CONC pretty much anywhere. It just looked very weird to me on first sight, but I agree. > allowing PAGE values...
Related pull request #4884 with a proposal for a fix.
O.k., I understand; I did not know that SUBM is mandatory. This explains the behavior in **Example A**. However, it is kind of confusing that a newly created tree is...
If SUBM is never ruled out by privacy rules, it might be possible to simply add AUTH::PRIV_HIDE as an access level to the calls of ->facts() in [createHeader](https://github.com/fisharebest/webtrees/blob/main/app/Services/GedcomExportService.php#L291): i.e. [line...
After further considerations, I addressed the issue of **Example B** by overwriting the createHeader method in the [DownloadGedcomWithURL](https://github.com/Jefferson49/DownloadGedcomWithURL) custom module.
> HEAD:SUBM is a mandatory field. Every valid GEDCOM has at least one SUBM record. > If we don't have one that we can safely include, then we will need...
One additional poiint, which I identified while working on the topic: For submissions (SUBN), the createHeader method also overrules privacy settings, although SUBN is not mandatory. If the privacy restrictions...