Hallo!
Working with the Extended Profiles module, I banged
into a problem. That led an idea of a general concept
as a whole. This idea may not work as a general
approach, however its worth a consideration.
If not it would be atleast helpful to implement in the
extended profiles.
Due to legal reasons it becomes manytimes necessary to
have fileds in the extended profiles secured in the
manner that a User could choose and give it free.
Table xoops_group_permission
There are four kinds of permissions, namely
profile_show, profile_edit, profile_search and
profile_visible.
The quality of fields becomes restrictive and falls
beyond the scope of further betterment in regards to
the choice by an User in view of
..... profile_show ......
The above field is restrictive. If the admin gives it
free for show and if the user wants to give if free for
internal use but not for the public, the field quality
definately does not help.
Hence the following happens in case for e,g, in an
association:
The Admin gives the field free for all i.e.
profile_show is set to yes!
The information given by the user is for e.g. Home
telefone. The User X wants his Home_Tel NOT to be given
free for all and User Y does want it.
Therefore the Admin has to offer two following fields
public_field_home_telefone
internal_field_home_telefone
Solution:
Hence there requires a switch to be offered to the
users, if they generally want to give a field free.
In the above case one could offer:
field_home_telefone >> switch >> Show_Public: Yes/No
If there is a general routine somewhere in the
Form_Class developed that detects a field quality to be
presented and offers each and every user to choose to
give a field free for public view or not, would be helpful.
By doing so, all the modules would profit out of this
routine/class.
The field property like Radio buttons could be
filtered. Hence this routine needs to be enbedded in
the core.