Fwd: RE: [thesite] thecode FAQ - everyone read

[rudy]

> As far as viewing member info, at this point that only applies
> to email addresses on the user pages.  However, I'm not at
> all sure if this will change with the new members' pages.

i would think so, eventually, but it doesn't have to right away

right now that user page is pulling data from the USERS table,
including links to articles

the member pages we've been talking about are for MEMBER records

i know the confusion is partly my fault, because i tend to use the word
"member" without always making the above qualification, but you have to
start thinking about "member pages" and "members" as something different
from all the users and userids and so on that we have in our database up to
this point

the situation is further complicated by people talking about "evolt
members" as including everyone who makes up the community -- list
subscribers, article authors, admins, and even casual site visitors

anyhow, the member pages project, which will allow people to enter
information about themselves, makes a pretty major assumption -- a MEMBER
is a person who has a USER record, i.e. userid/password, and you must log
in to enter member page information -- and will get an *additional*
database record, a new MEMBER record which will be tied to the USER record

existing code which references the USER table should not be affected
(except some may want to be enhanced, see below)


> Are we going to have different Priv levels for info aside from Privs 1
and 2,
> which are logged in and not logged in user?  (The member pages will also
> change slightly the writeups provided for anon and logged in user.)

i gotta clarify this again too, my bad for not doing so in my other email
yesterday

the PRIV levels are

   0=public
   1=user (i.e. has a USER record, userid/password)
   2=member (i.e. has a MEMBER record)
   3=admin
   4=god

let's say you're a user, and you come to the evolt site

unless you log in, you will be treated as though you were PRIV=0

if you log in, you will be treated according to your PRIV level

note: the login procedure has to be revised to put this into effect --
right now it doesn't search for a MEMBER record to assign userpriv=2


helps?

rudy