From: <ad...@tu...> - 2003-06-03 18:02:26
|
I also agree that disabling the account may be a better method for handling this situation. I'd like to add that if the account is disabled that when the user tries to log in, a message is printed to that effect notifying them their account has been disabled and to contact the site administrator. +1 to Sumilang's method. Adam > +1 > > Sorry, I got this message as soon as I sent mine off. > I agree wholeheartedly with Richard. > > > ----- Original Message ----- > From: "Richard Sumilang" <ri...@ri...> > To: <ad...@tu...> > Cc: <php...@li...> > Sent: Tuesday, June 03, 2003 1:19 PM > Subject: Re: [Phpwebsite-developers] allow_access() question > > >> Almost their but it still seems a bit redundant. Instead of making it a >> 'Activate Permissions' switch, how about a 'Activate / Disable Account' >> switch? Typically when I don't want to have a user access the system >> anymore I don't delete the account or remove all their permissions but >> rather deactivate it. Permissions should always be available which is >> why I find a 'Activate Permissions' switch a bit redundant. I think >> that will be more overall useful in general and and cause less >> confusion. >> >> I was personally stuck for a long time writing my module when I >> couldn't figure out why my permissions where not working with the >> allow_access() function. I think the Administer switch causes confusion >> from a developer and user point of view. >> >> Best Regards, >> Richard Sumilang > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > -- Adam Morton Developer - Electronic Student Services http://phpwebsite.appstate.edu Founder - Appalachian Linux Users Group http://alug.appstate.edu |