Hi Caroline, hi Oliver,
I started searching for this "protect_private_p" parameter nearly one hour ago and did not find it. Could it be removed from the current dotLRN version?
I looked at dotlrn-members-portlet.tcl/.adp and noticed that three properties are created/used:
1. admin_p
2. spam_p
3. read_private_data_p
The last one is the interesting property. It is evaluated by using the function 'dotlrn::user_can_read_private_data_p'.
Having a closer look to the source code I saw that the 'protect_private_data_p' is a global parameter and not a parameter which could be set for each community.
So, my results:
In (my) current installation parameter 'protect_private_data_p' seems to be missing; the function uses the default value 1 instead. Therefore a limited access guest user can not see the list of members.
But even if the parameter was there, it would be used for all communities.
And telling community admins to create only limited access users will not work, too, because in the current dotLRN version, a community admin can not set up a limited access user, but only a limited access guest user. To change this, I could delete just one or two lines in the admin-adp-file, but I think, the programmers followed a special thought, when implementing this.
So, what to do best:
Either restore missing parameter 'protect_private_data_p' again, which would allow one setting for all communities, or giving community admins the possibility of creating limited access users?
Greetings,
Martin
