There has been talk about the privacy module here on the forum, but I can't seem to find it anywhere. The only module I've found is the PostNuke one.
In the privacy module you were supposed to be able to turn off the names of the living people as well, not just the dates. I've understood that it involves some code-hacking, and maybe you're just supposed to do that with the file privacy.php, which is "the privacy module"?
Since I've had some bad luck trying to change the config.php by hand after the actual configuration has set place, I'm afraid to change the privacy.php as well, in case everything crashes. Or is it just the config.php that is so sensitive?
I forgot to set the last slash in my own theme path, and I got an angry error message about it trying to load the theme without the slash, it was just one long filename instead..., but I couldn't go back and change it, cause of course I got the same angry error message in the editconfig too, since it requires the config-file... I solved it by downloading the config, add the slash, and just got a header-error-message, then I could change theme and then change back again AND remebering the last slash in the path, and the whole thing worked again...
And another question while we're talking privacy. My deathcauses won't print, and I've checked everywhere for some privacy rules about this. The GEDCOM-code for it is at the bottom of the translationslists (at least the Swedish), as if it was added late. But I haven't found any line saying anything about not showing that "event" or "type" or whatever it might be classified as. I'd like to be able to show the death causes. The sensitive deaths I can remove by hand, cause they are not many. But I think it's interesting to see all the old deathcauses, and want to show the ones I've collected. Maybe this is some cultural thing...?
/Siss
who still can't seem to figure out the importing of files thing. I will try a new angle today...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The privacy settings are modular, so when I talk about a "privacy module" that is what I mean. The default privacy module that comes with phpGedView is privacy.php and it has most of the things in it that people need. However, if someone wanted to extend or enhance it, all they would need to do is implement the functions in that file in their own script and they could completely change how the privacy settings work. The authentication is also modular to allow people to extend to different authentication schemes. The "PostNuke Module" that is available for download, modifies phpGedView to make it a module for PostNuke and modifies the authentication module of phpGedView to work with PostNuke users. So someone could extend the system to authenticate using LDAP or another directory system if they wanted to.
Here is a bit of history: I was approached a few months ago by someone starting another project who wanted to extend the privacy settings of phpGedView to do the things that phpGedView 2.13 can now do. It was his idea to make the privacy settings modular so that anyone who so desired could write their own privacy settings. I made the system modular, but he didn't have the time to work on it. phpGedView users, in the meantime began requesting these features. So I made the default privacy module capable of doing several different types of privacy settings by modifying a few of the variables in the file. Technically, when you modify the privacy.php file, you are writing your own "privacy module".
My reccommendation to people, would be to make a copy of the privacy.php called myprivacy.php and change the settings in the myprivacy copy. Then change your configuration to point to myprivacy.php instead of privacy.php.
If you post or email a copy of the gedcom code that isn't displaying correctly, then I will be able to fix it. There are many ways in gedcom to record a death cause. It's very possible that I haven't taken the way your program does it into account.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I've understood the privacy-thing now, and I checked the file. However, when I reinstalled now I took the beta-version 2.14, and it doesn't seem to want to understand when I set the two new settings for places in boxes and IDnumbers next to person.... I've set it to yes, and nothing happens, and next time I check my editconfig it's no again... Any suggestions?
It seems like the import works if I just restart or so after the import. Cause it worked better now, but I still got the 0 persons after the import. But after restarting it was all there... Must be something with IE...
Thanks for all the help!!!
/Siss
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't plan to issue a fix for 2.14b because I am already well into version 2.50 and the configuration is organized differently in 2.50. You can avoid this problem by editing the config.php file by hand and setting $SHOW_ID_NUMBERS and $SHOW_PEDIGREE_PLACES to true or false as you desire.
On the import problem I imagine it is because the cookie is getting set to an empty string before the import and is not getting reset after the import. I will make a note to test for this.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the support! I tried to edit it, and this time it didn't mess upp. Have to remeber my downloadsettings from the FTP and such for next time...
Please, do put all your effort into the next version, and don't mind little ol' me bugging you with stupid questions =oD I'll check the bug reports in the future too (gee, there's so much to keep track of...)
Yepp, the cookie-thing might be the problem.....
/Siss
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There has been talk about the privacy module here on the forum, but I can't seem to find it anywhere. The only module I've found is the PostNuke one.
In the privacy module you were supposed to be able to turn off the names of the living people as well, not just the dates. I've understood that it involves some code-hacking, and maybe you're just supposed to do that with the file privacy.php, which is "the privacy module"?
Since I've had some bad luck trying to change the config.php by hand after the actual configuration has set place, I'm afraid to change the privacy.php as well, in case everything crashes. Or is it just the config.php that is so sensitive?
I forgot to set the last slash in my own theme path, and I got an angry error message about it trying to load the theme without the slash, it was just one long filename instead..., but I couldn't go back and change it, cause of course I got the same angry error message in the editconfig too, since it requires the config-file... I solved it by downloading the config, add the slash, and just got a header-error-message, then I could change theme and then change back again AND remebering the last slash in the path, and the whole thing worked again...
And another question while we're talking privacy. My deathcauses won't print, and I've checked everywhere for some privacy rules about this. The GEDCOM-code for it is at the bottom of the translationslists (at least the Swedish), as if it was added late. But I haven't found any line saying anything about not showing that "event" or "type" or whatever it might be classified as. I'd like to be able to show the death causes. The sensitive deaths I can remove by hand, cause they are not many. But I think it's interesting to see all the old deathcauses, and want to show the ones I've collected. Maybe this is some cultural thing...?
/Siss
who still can't seem to figure out the importing of files thing. I will try a new angle today...
The privacy settings are modular, so when I talk about a "privacy module" that is what I mean. The default privacy module that comes with phpGedView is privacy.php and it has most of the things in it that people need. However, if someone wanted to extend or enhance it, all they would need to do is implement the functions in that file in their own script and they could completely change how the privacy settings work. The authentication is also modular to allow people to extend to different authentication schemes. The "PostNuke Module" that is available for download, modifies phpGedView to make it a module for PostNuke and modifies the authentication module of phpGedView to work with PostNuke users. So someone could extend the system to authenticate using LDAP or another directory system if they wanted to.
Here is a bit of history: I was approached a few months ago by someone starting another project who wanted to extend the privacy settings of phpGedView to do the things that phpGedView 2.13 can now do. It was his idea to make the privacy settings modular so that anyone who so desired could write their own privacy settings. I made the system modular, but he didn't have the time to work on it. phpGedView users, in the meantime began requesting these features. So I made the default privacy module capable of doing several different types of privacy settings by modifying a few of the variables in the file. Technically, when you modify the privacy.php file, you are writing your own "privacy module".
My reccommendation to people, would be to make a copy of the privacy.php called myprivacy.php and change the settings in the myprivacy copy. Then change your configuration to point to myprivacy.php instead of privacy.php.
If you post or email a copy of the gedcom code that isn't displaying correctly, then I will be able to fix it. There are many ways in gedcom to record a death cause. It's very possible that I haven't taken the way your program does it into account.
--John
Here's an example of a GEDCOM-code involving death cause from my files. I don't know if it's the many levels that might be confusing to interpret...
1 DEAT
2 DATE 21 NOV 1890
2 PLAC nnarp, Rke, Krist. (L)
3 SOUR @S15@
4 PAGE Rke SCB 1860-1897 90-97 Dda
3 SOUR @SR79@
4 PAGE Rke A1:12 1882-1892 1/9 p.14
2 AGE 77.3.8
2 CAUS fll i brunnen och drunknade
2 SOUR @S15@
3 PAGE Rke SCB 1860-1897 90-97 Dda
2 SOUR @SR79@
3 PAGE Rke A1:12 1882-1892 1/9 p.14
I think I've understood the privacy-thing now, and I checked the file. However, when I reinstalled now I took the beta-version 2.14, and it doesn't seem to want to understand when I set the two new settings for places in boxes and IDnumbers next to person.... I've set it to yes, and nothing happens, and next time I check my editconfig it's no again... Any suggestions?
It seems like the import works if I just restart or so after the import. Cause it worked better now, but I still got the 0 persons after the import. But after restarting it was all there... Must be something with IE...
Thanks for all the help!!!
/Siss
Thanks for the gedcom code. That will help me debug it. I will make sure it works in the next release.
The problem with the ID Numbers and places is described in bug report #785155 http://sourceforge.net/tracker/index.php?func=detail&aid=785155&group_id=55456&atid=477079
I don't plan to issue a fix for 2.14b because I am already well into version 2.50 and the configuration is organized differently in 2.50. You can avoid this problem by editing the config.php file by hand and setting $SHOW_ID_NUMBERS and $SHOW_PEDIGREE_PLACES to true or false as you desire.
On the import problem I imagine it is because the cookie is getting set to an empty string before the import and is not getting reset after the import. I will make a note to test for this.
--John
Thanks for the support! I tried to edit it, and this time it didn't mess upp. Have to remeber my downloadsettings from the FTP and such for next time...
Please, do put all your effort into the next version, and don't mind little ol' me bugging you with stupid questions =oD I'll check the bug reports in the future too (gee, there's so much to keep track of...)
Yepp, the cookie-thing might be the problem.....
/Siss