Why don't you just keep a last_activity date? Also, the auth event log keeps track of the last login automatically. Why not check it to see what it's doing regarding last login when user has the "remember" checkbox checked? Technically, if it's checked, they're not logging in, right? Can you better articulate what you are really trying to measure?
On May 21, 2:18 am, Adi <aditya.sa...@gmail.com> wrote: > Sure. Thanks for the update. > > On May 21, 9:34 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > need to work on this. On the case but being distracted sorry. > > > On May 20, 10:50 pm, Adi <aditya.sa...@gmail.com> wrote: > > > > Any help on this? > > > > On May 20, 3:45 pm, Adi <aditya.sa...@gmail.com> wrote: > > > > > Hi, > > > > > I use the "Remember me for 30 days" feature in our app. I used a > > > > custom auth_table with a column "last_login" to update every time a > > > > user logs into the application. > > > > > Currently I update it in a function call like this: > > > > ------------------------------------------------------------------- > > > > def updateLastLogin(form): > > > > > db(db.auth_user.id==auth.user.id).update(last_login=datetime.datetime.now() > > > > ) > > > > > auth.settings.login_onaccept = updateLastLogin > > > > > ---------------------------------------------------------------------- > > > > > However if a user chooses to "remember me for 30 days" then there's no > > > > actual login action. What is the way to track last_login for such > > > > users who visit the app but don't actually login? I basically need it > > > > for analytics. > > > > > Thanks, > > > > Aditya- Hide quoted text - > > - Show quoted text -
