This does not look to be happening for a deleted user anymore. It does, however, happen for a suspended user.
The problem is the ./htdocs/auth/user.php has an authenticate() function that saves the new 'lastlogin' value and it is called before the check to see if one is suspended. If we swap this around it should sort the problem. But then comes the question: Do we want the database to reflect the last legitimate login or the last time they tried to to login? -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/850580 Title: Attempt to log in when deleted updates lastlogin field Status in Mahara ePortfolio: Confirmed Bug description: When a deleted user attempts to log in, the lastlogin field is updated, but it shouldn't be. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/850580/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
