Private profile

Started by Private User on Saturday, September 2, 2017
Problem with this page?

Participants:

  • Private User
    Geni member
  • Geni Pro
  • Private User
    Geni Pro

Related Projects:

Showing all 9 posts
Private User
9/2/2017 at 2:38 AM

How can a death profile be made private by the API?

I tried to set the value "public" as "false" but it is not working properly.

Thanks!

9/2/2017 at 5:52 AM

Hmm that should work. Our office is close for the weekend and I'm away at a conference, so we'll have someone get in touch with you on Tuesday (holiday Monday) to figure out why it didn't work.

Private User
9/2/2017 at 6:05 AM

What HTTP method and URL are you using to set public to false?

Private User
9/2/2017 at 10:15 AM

Guys, this thing is NOT urgent, it can easily wait a week, so do not rush and enjoy the weekend.

Concerning the question, I tried it using both add-child methods from union and profile, but likely will the same piece of code :)

I am introducing the data as a json params file, I know the way I am sending the data shall be ok as I have introduced other data and it worked pretty well.

Private User
9/5/2017 at 11:03 AM

You found a bug! Thanks!

We've fixed the bug, and you should be able to set
public to false now.

Please try it and let me know if there are any issues.

Private User
9/5/2017 at 3:19 PM

So I tried "public=false" and "public=False" both sandbox and production and I have not been able to make the profile private.

Just in case, I used the following (changing false and False) for production:

https://www.geni.com/api/union-77004115/add-child?first_name=Emilio...

(as you have the specific union you should have log traceability)

Private User
9/6/2017 at 6:52 AM

My mistake. I didn't realize you were testing on sandbox and I forgot about union/add-child.

I've pushed a fix to both sandbox and production.

Please try, again, and let me know if there are any issues.

Private User
9/6/2017 at 6:56 AM

Oh! Were you using HTTP POST when you were testing?

Private User
9/7/2017 at 2:02 PM

I prefer to use sandbox for testing adding information, so that if I mess it out I do not touch production. Just to be safe! But for a limited testing like this one I can use production.

I am using POST as GET should not be used for sensitive data, remains in browser history!

Anyhow, I tested it in both production and sandbox and it works smooth!!! Thanks!

Quick question, is possible to solve the certificate issue in the sandbox?

Showing all 9 posts

Create a free account or login to participate in this discussion