Public bug reported:
When reloading a user account's expiry date from the db into $USER, the
time is not converted to the correct format, causing users to be unable
to login even when their expiry date is in the future.
Also, the get_user function fails to convert db timestamps to unix
timestamps for some fields. This will interfere with the update of the
'active' flag if we want to base inactivity on lastaccess and/or ctime
as well as lastlogin.
** Affects: mahara
Importance: Medium
Assignee: Richard Mansfield (richard-mansfield)
Status: In Progress
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/907919
Title:
Bugs in expiry/inactivity due to bad time formatting
Status in Mahara ePortfolio:
In Progress
Bug description:
When reloading a user account's expiry date from the db into $USER,
the time is not converted to the correct format, causing users to be
unable to login even when their expiry date is in the future.
Also, the get_user function fails to convert db timestamps to unix
timestamps for some fields. This will interfere with the update of
the 'active' flag if we want to base inactivity on lastaccess and/or
ctime as well as lastlogin.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/907919/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
