Search Forums
Forums
Kiwitrees on Twitter
    Tags

    nickname, kiwitrees 2.0.2, latest version, 3.0.0 widgets, Favourites 3.0.0, dead, IE problem, GEDCOM, marriage, styles, calendar, logs, internal messaging, census, menu, links, emmigration, .mo, gettext, descendant, Require visitor authentication, 3.3.1, future, users, feedback, progress, logout, survey, close, .po, merge, theme, slideshow, lists individuals families, 5.6, person, folder, click, tabs, Georgian, Administration, bug, image, name, php 7, contacts, design, advent, 3.1, php 5.6, Extra menus, cookie, lists, REFN, calendar.php issue, fatal error, fancy image bar, flags, login upgrade, fancy tree view

    Topic:   _UID  

    This topic contains 5 replies, has 2 voices, and was last updated by kiwi kiwi 2 years, 9 months ago.

    Viewing 6 posts - 1 through 6 (of 6 total)
    • Author
      Posts
    • #4111
      macalter
      macalter
      Participant

      551 posts

      I did the setting in Privacy to hide _UID (Globally unique identifier) from everyone. However, I’m now looking at a record (as Admin), that’s showing it. it also showing to visitors** (I have the site totally open). I reactivated your account, kiwi, if required.

      http://alterfamily.woodengems.com/wtroyalty/

      Q17: Princess Maud Charlotte Mary Victoria of Wales SAXE-COBURG-GOTHA of Wales

      ** it’s opened to let me decide what I want on/off for my own site

      -----
      Kiwitrees:
      "A-D connections 3.3.1"
      PHP 7.0 Fast CGI

      "The Royals 3.3.1"
      PHP 7.0 Fast CGI
      mySQL server: 5.1.56
      MacOS: 10.11.6  (El Capitan)
      Browsers (mac): Safari  Version 11.0;  Firefox 56.0
      [updated: 07 Oct 2017]

      #4112
      kiwi
      kiwi
      Keymaster

      1575 posts

      You still have Privacy – disabled. So NO privacy settings will be working.

      You also do not have the login module enabled, so you have no login link to use.

      Nigel
      My personal kiwitrees site is www.our-families.info
      #4113
      macalter
      macalter
      Participant

      551 posts

      See, this is why I’m playing in an “unimportant” tree! Thought I had to disable to not require login. I set to enable; _UIC is gone.

      Objective – reasons I thought I had to disable:
      *no login for visitors; just admin (I already have login block show to visitors)
      * both living and dead people available to everyone (does that mean set Age at which to assume a person is dead: 120 year to 0?

      -----
      Kiwitrees:
      "A-D connections 3.3.1"
      PHP 7.0 Fast CGI

      "The Royals 3.3.1"
      PHP 7.0 Fast CGI
      mySQL server: 5.1.56
      MacOS: 10.11.6  (El Capitan)
      Browsers (mac): Safari  Version 11.0;  Firefox 56.0
      [updated: 07 Oct 2017]

      #4114
      kiwi
      kiwi
      Keymaster

      1575 posts

      Your objectives make no sense to me I’m afraid.

      1 – “*no login for visitors; just admin (I already have login block show to visitors)” The part in brackets seems to contradict the first part. You are NOT currently showing a login block on the home page, neither are you displaying a Login menu item, so NO-ONE can login (not even you) without manually entering /login.php after the url.

      2 – “both living and dead people available to everyone” – surely not??? That means you have no privacy settings at all. Almost certainly illegal in every jurisdiction in the world. But if you want this, then just disable privacy.

      I realise you are playing with an “unimportant tree”, but surely that’s no reason to ignore privacy concerns, even if its only so that you learn how to use them.

      On your front page you have a statement telling viewers not to request a registration. That is not necessary. In Administration > Site administration set “Allow visitors to request account registration” to NO. Then they can’t register, and won’t see a “Request new user account” option anywhere, so the statement becomes superfluous.

      May I suggest that you think about how you would prefer your “real” site to be displayed, write those objectives down so they are clear, and use your test site and Royals data to experiment with settings that would achieve that.

      Nigel
      My personal kiwitrees site is www.our-families.info
      #4115
      macalter
      macalter
      Participant

      551 posts

      not using CAPS to yell at you, just to note my reply after your comments. My site was, from day 1, “locked down” so the idea of lifting that is new to me

      1 – “*no login for visitors; just admin (I already have login block show to visitors)” The part in brackets seems to contradict the first part. You are NOT currently showing a login block on the home page, neither are you displaying a Login menu item, so NO-ONE can login (not even you) without manually entering /login.php after the url.

      >>> FIXED

      2 – “both living and dead people available to everyone” – surely not??? That means you have no privacy settings at all. Almost certainly illegal in every jurisdiction in the world. But if you want this, then just disable privacy.

      >>> THE ROYALS “VITAL INFO”, IS ON WIKIPEDIA, AND PUBLICLY AVAILABLE EVERYWHERE. I’m MODIFYING NAMES, DATES AND PLACES. AND ADDING SOME WIKI IMAGES FOR MY AMUSEMENT (THEY’RE IN PUBLIC DOMAIN TOO)

      I realise you are playing with an “unimportant tree”, but surely that’s no reason to ignore privacy concerns, even if its only so that you learn how to use them.

      On your front page you have a statement telling viewers not to request a registration. That is not necessary. In Administration > Site administration set “Allow visitors to request account registration” to NO. Then they can’t register, and won’t see a “Request new user account” option anywhere, so the statement becomes superfluous.

      >>DONE; WHEN I SEE SITES WITH LOGIN, I TEND TO THINK I CAN’T USE SO ADDED THE COMMENT; MODIFIED.

      May I suggest that you think about how you would prefer your “real” site to be displayed, write those objectives down so they are clear, and use your test site and Royals data to experiment with settings that would achieve that.

      >>>BECAUSE ONTARIO HAS DIFFERENT PRIVACY FOR EACH VITAL AND CENSUS, IT’S HARD FOR ME TO KNOW JUST WHAT “ASSUMED DEAD AT 120 YEARS” PRIVACY DOES IN RELATION TO MY TREE. ONTARIO ISNT THAT CUT-AND-DRY. WHILE I CAN FIND MARRIAGES AFTER 40 YEARS, I CAN’T FIND BIRTHS UNTIL AFTER 97 YEARS AND ONE DEATH IS PUBLIC AFTER 72 YEARS.
      THE ROYALS IS DIFFERENT. EVERYONE KNOWS ABOUT PRINCE GEORGE’S BIRTH, BUT NO, I DON’T WANT EVERYONE KNOWING ABOUT THE BIRTH OF MY 3RD COUSIN THIS YEAR.
      [/quote]

      PS: I’ll say it again, I really like kiwitrees and am glad to have switched over from webtrees.

      -----
      Kiwitrees:
      "A-D connections 3.3.1"
      PHP 7.0 Fast CGI

      "The Royals 3.3.1"
      PHP 7.0 Fast CGI
      mySQL server: 5.1.56
      MacOS: 10.11.6  (El Capitan)
      Browsers (mac): Safari  Version 11.0;  Firefox 56.0
      [updated: 07 Oct 2017]

      #4116
      kiwi
      kiwi
      Keymaster

      1575 posts

      BECAUSE ONTARIO HAS DIFFERENT PRIVACY FOR EACH VITAL AND CENSUS, IT’S HARD FOR ME TO KNOW JUST WHAT “ASSUMED DEAD AT 120 YEARS” PRIVACY DOES IN RELATION TO MY TREE. ONTARIO ISNT THAT CUT-AND-DRY. WHILE I CAN FIND MARRIAGES AFTER 40 YEARS, I CAN’T FIND BIRTHS UNTIL AFTER 97 YEARS AND ONE DEATH IS PUBLIC AFTER 72 YEARS.

      Kiwitrees manages privacy through a simple dead vs alive rule. By default (privacy enabled) living people are hidden, dead are visible (to non-logged in visitors). It is no more complicated than that.

      This is not therefore directly comparable to any government rules about accessing BMD data that do often look like your Ontario ones. Mine are similar in NZ. The birth and death rules can approximately be catered for through the “years after birth” and “years after death” adjustments. But there is no way to match the marriage rule. If either party to a marriage are alive their marriage is hidden. If both are dead it is visible.

      The “120 yr rule” is really something quite different. It exists only to assist in determining dead vs alive in cases where death is not stated. If you have a tag like “1 DEAT Y” or you have a date or source added to the death tag, then death is confirmed and the 120 yr rule is irrelevant and ignored. It, in itself, does NOT determine privacy.

      So:

      1. Ontario want to hide births until 97 years after birth. Kiwitrees will reveal those births as soon as the person is recorded as dead, or xx years later if you set “Extend privacy to dead people born in the last xx yrs“. So to match Ontario, set that to 97.
      2. Ontario want to hide deaths until 72 years after death. So you need to set “Extend privacy to dead people died in the last xx yrs” to 72.
      3. Ontario want to hide marriages until 40 years after marriage. As per comment above, there is no easy way to manage this for marriages. But you can rely on the fact that no marriage will be visible until BOTH partners have been dead for 72 years (if you set as per 2. above). That’s stricter than you need by a minimum of 32 years and often far more. You can over-rule that manually (on a per-marriage basis) by adding a “1 RELA none” tag to any marriage that you want to force to be visible. Personally I would not bother.

      NOTE:
      All of the above assumes you want to follow exactly the rules Ontario have set. But personally I would carefully check those rules. I suspect you will find they are NOT general privacy rules, but specific ones related to the release by them of data they hold. In most jurisdictions if your information is gathered for genealogy purposes, and you strictly limit access to deceased persons data, and you modify that on request of direct relatives, then you are probably
      ‘legal’ (but you cannot rely on anything I say, in a court of law 🙂 )

      Nigel
      My personal kiwitrees site is www.our-families.info
    Viewing 6 posts - 1 through 6 (of 6 total)

    You must be logged in to reply to this topic.