Forgot about this one... My error cause of mixup between dev db and prod db... ;-D
Richard On Wed, Nov 17, 2010 at 11:50 AM, Richard Vézina < ml.richard.vez...@gmail.com> wrote: > Hello, > > I note that "blocked" in registration_key not prevent the user to login > under 1.88.2... > > Is the keyword for that task as change?? > > Richard > > > On Thu, Aug 26, 2010 at 2:27 PM, mdipierro <mdipie...@cs.depaul.edu>wrote: > >> What Thadeus suggests forces the user to logout. >> >> Before you do that you may also want to use appadmin and write >> "blocked" in their registration key. This will prevent them from >> logging in again. >> >> On Aug 26, 11:58 am, Thadeus Burgess <thade...@thadeusb.com> wrote: >> > Two ways, delete their session file... unless you know their IP it >> > might be hard to find the right one, so if its ok just delete them >> > all. >> > >> > The other way is a design thing. Add a column to the auth_user table >> > that says "force_logout" that is a boolean type. If you just flag that >> > to true, make the login mechanism sign them out and require them to >> > sign back in. >> > >> > -- >> > Thadeus >> > >> > On Thu, Aug 26, 2010 at 11:41 AM, Jean-Guy <jean...@gmail.com> wrote: >> > > Hello, >> > >> > > I would like to know how may I revoked a user logged in "server side"? >> > >> > > Can I just edit app/sessions/file... And comment appropriate line? >> > >> > > Which lines are the appropriate lines? ;-) >> > >> > > Jonhy >> > >
