This is related to http://www.wikitree.com/g2g/17777/possible-bug-privacy-levels-changing-automatically .
I did a bit of experimenting to see if I could replicate the problem I reported in the previous question.
First I created an intentional duplicate of a profile over 300 yrs old but did not input any dates. The new profile was, as expected, generated with privacy set to "Public". I changed it to "Open". I next exited Wikitree, cleared my cache and closed my browser. I reopened the profile and the privcy was still set to "Open". I noted the Wikitree ID and went to the known father of the created dupe. I added the dupe as a child. When I went back to the created duplicate the privacy had reset to "Public". I then changed the privacy and merged the duplicate away.
As a control, I repeated the above this time entering a DOB (1648) when creating the duplicate. With the DOB the generated profile was "Open" and remained so through out the rest of the steps.
My conclusion is that when a "Open" profile without a DOB is added as a relative to another profile the system automatically resets privacy from "Open" to "Public". Whether this is by design or just a quirk or bug, I don't know.
The work around I would use in the future (if I wasn't the PM or on the trusted list) is to enter a birth date in the profile before adding the profile as a relative.
I hope this was helpful to the Sysops.
