Closed aledeniz closed 5 years ago
I suggest you to change your FS password since you forget to remove it from your message. However, could you log in to your familysearch account then give the result of https://www.familysearch.org/platform/tree/couple-relationships/MGGG-000/changes.json ?
GGGG-000, GGGG-001 and MGGG-000 are placeholders. As the actual profiles are confidential, I thought it was meaningless to provide them. I performed the query with one of those couple relationship between confidential profiles (MVKN-6KM), this is the outcome:
HTTP/1.1 204 No Content
Content-Type: application/json
Connection: keep-alive
Cache-Control: no-transform, must-revalidate, max-age=0
Date: Sat, 10 Nov 2018 18:17:14 GMT
Link: <https://www.familysearch.org/platform/tree/couple-relationships/MVKN-6KM.json?flag=fsh>; rel="relationship"
Link: <https://www.familysearch.org/platform/tree/couple-relationships/MVKN-6KM/changes.json?flag=fsh>; rel="self"
Server: Apache-Coyote/1.1
Vary: Accept, Accept-Language, Accept-Encoding, Expect
Vary: Accept-Encoding
Warning: 199 FamilySearch Best Practice Violation: Should specify versioned media type in Accept header, e.g. one of [ "application/x-gedcomx-v1+xml", "application/x-gedcomx-v1+json", "application/atom+xml", "application/x-gedcomx-atom+json", "application/x-fs-v1+xml", "application/x-fs-v1+json" ].
X-PROCESSING-TIME: 9
X-Cache: Miss from cloudfront
Via: 1.1 [..].cloudfront.net (CloudFront)
X-Amz-Cf-Id: [..]==
Should be fixed with 3b87242d0ae02b588bd9fcba2e8cdffcbf0ad552
Just to confirm that the fix works. Thanks.
As a FamilySearch user I want to download a gedcom using the -m and the -r options with the profile of a deceased person which has been marked as confidential.
To replicate, we may create the GGGG-000 and a GGGG-001 profile, both with a place of birth or a place of death in Turkey, and we add GGGG-001 as a spouse of GGGG-000. Eventually the profiles will be marked as confidential, and managed in a private space, as the ones of living people.
When trying to download a gedcom of one of those confidential deceased persons with getmyancestors.py called with the -m and the -r options, we get a similar error:
The gedcom is generated, but it is empty. This is the log file:
When executing the same line without the -m option, the gedcom gets generated successfully:
This is the resulting gedcom: