ThomasP wrote: > Hello, > > On Mon, May 28, 2007 21:26, IchBin wrote: >> # pr - may change his profile >> >> Given the above info I have a question. >> >> - I have a groups '@group_a'. I want to allow all users using this group >> be able to read\write to their own profile page. I add 'pr' into the >> @group_a' but when I login, as a user with this security group, I can >> view but not edit that users profile. What may I be doing wrong. > > There is a simple reason for this: Profiles are not implemented. > > I originally planned some custom profile mechanism in UserAuth2, where > profile information would be stored as array in files as is done currently > with the permission records. This profiles could have then been viewed in > the same web-form manner as with the permissions now. To access these > profiles, one would have clicked on the link "Profile" of the respective > user in the admin table, and would have been allowed to access, if ... > well, if the level "pr" was set for the viewing client. > > I have completely abandoned this, since saving profile information in wiki > pages is a far more convenient and flexible way. An add-on which would > then achieve similar functionality to the one imagined before is just to > make these pages ACTIVE: settings the user might want to use would be read > directly from designated places in the wiki page. Though it is not yet > implemented, this is clearly the easiest way to do it (*). > > For what you want to do right now, it is sufficient to have something like: > > rd_Profiles.{$AuthId}, > ed_Profiles.{$AuthId} > > in the LoggedInUserGroup. (Note it has to be in the LoggedInUserGroup, > otherwise the {$AuthId} will not be filled with the actual username.) > > Thomas > > NB: I will take the "pr" line out of the help. > > ---- > (*) As an example, every recipe can implement this easily itself by > parsing the Profiles page of a user for a special line and then set e.g. > skin settings etc. during the script call. > > For example > > !!Preferences > [@ > $Skin = 'jhgjg'; > @] > [@ > notify = 'kdhfklsdhf'; > @] > > (The code lines would be read and interpreted either by each recipe > separately or by a "user settings reader".)
Thanks Thomas, as it turns out, I did what you just mention already by chance. I will fool around with your example. - I still have a big question mark about the use of term "parent" in the context of creating a new user or @group. What are the OOD implications. I have not been able to find any docs on this for UserAuth2. - Is UserAuth2 suppose to be compatible with presence-v1.1 as it now is with presence-light-v1.0 but then already asked this question in another thread here yesterday. -- Thanks in Advance... http://weconsulting.org IchBin, Philadelphia, Pa, USA http://ichbinquotations.weconsulting.org ______________________________________________________________________ 'If there is one, Knowledge is the "Fountain of Youth"' -William E. Taylor, Regular Guy (1952-) _______________________________________________ pmwiki-users mailing list pmwiki-users@pmichaud.com http://www.pmichaud.com/mailman/listinfo/pmwiki-users