You miss read... I know that. My problem is that when I update my user status I have no switch except build my own to not update the status of user that should stay blocked.
I mean when I go for maintenance I put everybody to blocked but then when I want to bring back access to user I put all the blocked to nothing so they get access again... But the one who should stay blocked I have to check (remember) and manually set them back to blocked... I could build a lookup table to know which should stay blocked but a new key word (for example "blocked_permanent") appear to me what I am searching for. Thanks. Richard On Tue, May 3, 2011 at 3:45 PM, Anthony <[email protected]> wrote: > In the auth_user table, set the user's registration_key to "blocked" (see > http://web2py.com/book/default/chapter/08#Restrictions-on-registration). > > Anthony > > On Tuesday, May 3, 2011 3:20:46 PM UTC-4, Richard wrote: > >> Hello Web2py friends, >> >> I am quite buzzy these days that why I have been out of the mailing list >> for a wild. >> >> I would like to know if the possibility to blocked a user permanently had >> been anticipated?? >> >> I mean if you can't remove a user from the auth_user for regulation reason >> is there a key word that could be used to set this user access to be blocked >> permanently?? >> >> There is not in the book about this eventuallity as far as I search (not a >> lot ;-) : http://www.web2py.com/book/default/chapter/08?search=blocked >> >> Thanks >> >> Richard >> >
