Re: [Phpgedview-talk] Making the dead as secure as the Living -how?!
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
Re: [Phpgedview-talk] Making the dead as secure as the Living -how?!
|
From: Cassidy <eam...@ho...> - 2007-11-08 20:37:10
|
Many, many thanks for all the suggestions ... I will try them out this weekend (except for the coding ones that is!!!) and let you all know what we decided, in the hope that it helps someone else who reads this thread later. John Finlay-2 wrote: > > I forgot one other feature. > > If you enable the Quick Update feature, then regular, "non-editing," users > will be able to use it to edit only their close relatives (parents, > siblings, and children). This is the most limited editing you can allow. > But their changes are not automatically accepted. > > --John > >> -----Original Message----- >> From: php...@li... [mailto:phpgedview- >> tal...@li...] On Behalf Of John Finlay >> Sent: Wednesday, October 31, 2007 11:52 AM >> To: All About PhpGedView >> Subject: Re: [Phpgedview-talk] Making the dead as secure as the Living - >> how?! >> >> For the most part, relatives will play nice and they won't change people >> that they shouldn't. >> >> Another option is to have several acceptors who you trust who will review >> each edit of the broader family to help divide up the work. >> >> Another approach would be to split your gedcom up into multiple files, >> one >> for each of the main families you want people to edit. Then you could >> link them together. >> >> The biggest reason why we haven't added the option to limit editing by >> relationships is because calculating relationships is a slow process and >> you would have to run through that process every time you visit a page. >> Also, you probably want people to be able to edit *any* of their >> ancestors >> no matter how far back they go, but you don't want them to edit the >> ancestors of their in-laws. Standard relationship privacy doesn't allow >> you to go up to infinity in one direction but not in another direction. >> Anyway, a technical problem I have yet to find a good solution for. >> Right >> now splitting into multiple GEDCOMS is the best solution to that problem. >> >> --John >> >> > -----Original Message----- >> > From: php...@li... [mailto:phpgedview- >> > tal...@li...] On Behalf Of Cassidy >> > Sent: Tuesday, October 30, 2007 2:57 PM >> > To: php...@li... >> > Subject: Re: [Phpgedview-talk] Making the dead as secure as the Living >> - >> > how?! >> > >> > >> > John, >> > >> > Many thanks for taking the time to reply. Much appreciated. >> > We could not figure a way to do this, so I understand your answer! >> > It is a pity this is not possible as we have a large implementation >> > brewing >> > and we were hoping to have people from the wider family just edit their >> > branch of the family tree and let them "accept" their own changes >> without >> > haveing them reviewed - but while allowing them to see their more >> distant >> > ancestors, we wanted to stop them from changing them. >> > Back to the drawing board! >> > >> > >> > >> > John Finlay-2 wrote: >> > > >> > > Editing is defined so that you can edit anyone that you can see. >> This >> > > means that she would be able to edit any dead people. There is not >> > > currently a workaround for this. >> > > >> > > However, most people don't have a problem because they always have >> the >> > > option to review any changes that are made and then accept or reject >> > them. >> > > So if your daughter does change something that you don't want her to >> you >> > > can always undo it. >> > > >> > > --John >> > > >> > >> -----Original Message----- >> > >> From: php...@li... >> [mailto:phpgedview- >> > >> tal...@li...] On Behalf Of Cassidy >> > >> Sent: Monday, October 29, 2007 5:51 PM >> > >> To: php...@li... >> > >> Subject: [Phpgedview-talk] Making the dead as secure as the Living - >> > >> how?! >> > >> >> > >> >> > >> I'd like to setup an account for my youngest daughter so she can >> edit >> > and >> > >> accept changes to 4 relationship levels of our family. However when >> I >> > do >> > >> so >> > >> it allows her to edit / accept withing the four levels as I might >> > expect >> > >> BUT >> > >> it also allows her to edit the dead who are more than 4 relationship >> > >> steps >> > >> away. any tips would be greatly appreciated!! >> > >> -- >> > >> View this message in context: http://www.nabble.com/Making-the-dead- >> as- >> > >> secure-as-the-Living---how-%21-tf4715418.html#a13479348 >> > >> Sent from the phpgedview-talk mailing list archive at Nabble.com. >> > >> >> > >> >> > >> >> --------------------------------------------------------------------- >> -- >> > -- >> > >> This SF.net email is sponsored by: Splunk Inc. >> > >> Still grepping through log files to find problems? Stop. >> > >> Now Search log events and configuration files using AJAX and a >> browser. >> > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> > >> _______________________________________________ >> > >> Phpgedview-talk mailing list >> > >> Php...@li... >> > >> https://lists.sourceforge.net/lists/listinfo/phpgedview-talk >> > > >> ---------------------------------------------------------------------- >> -- >> > - >> > > This SF.net email is sponsored by: Splunk Inc. >> > > Still grepping through log files to find problems? Stop. >> > > Now Search log events and configuration files using AJAX and a >> browser. >> > > Download your FREE copy of Splunk now >> http://get.splunk.com/ >> > > _______________________________________________ >> > > Phpgedview-talk mailing list >> > > Php...@li... >> > > https://lists.sourceforge.net/lists/listinfo/phpgedview-talk >> > > >> > > >> > >> > -- >> > View this message in context: http://www.nabble.com/Making-the-dead-as- >> > secure-as-the-Living---how-%21-tf4715418.html#a13494704 >> > Sent from the phpgedview-talk mailing list archive at Nabble.com. >> > >> > >> > >> ------------------------------------------------------------------------ >> - >> > This SF.net email is sponsored by: Splunk Inc. >> > Still grepping through log files to find problems? Stop. >> > Now Search log events and configuration files using AJAX and a browser. >> > Download your FREE copy of Splunk now >> http://get.splunk.com/ >> > _______________________________________________ >> > Phpgedview-talk mailing list >> > Php...@li... >> > https://lists.sourceforge.net/lists/listinfo/phpgedview-talk >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Phpgedview-talk mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpgedview-talk > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Phpgedview-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpgedview-talk > > -- View this message in context: http://www.nabble.com/Making-the-dead-as-secure-as-the-Living---how-%21-tf4715418.html#a13655297 Sent from the phpgedview-talk mailing list archive at Nabble.com. |
