mahara-contributors team mailing list archive

[Mahara Bot <907919@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/955
Committed: http://gitorious.org/mahara/mahara/commit/f7dcdf818b8e59337d0929d97547cc52fd582e7a
Submitter: Francois Marier (francois@xxxxxxxxxxxxxxx)
Branch:    master

commit f7dcdf818b8e59337d0929d97547cc52fd582e7a
Author: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>
Date:   Thu Dec 22 17:03:10 2011 +1300

    Convert expiry date when reloading user object (bug #907919)
    
    Commit 725ba9294039b82bec947be5301acf160f4744ae tries to reload
    certain admin-settable fields from the database into a LiveUser when
    committing, but fails to convert the expiry date to a timestamp when
    doing so.  This causes logins to fail for users who have an expiry
    date set in the future.
    
    Change-Id: I53e962a0f5bab56ab130e1945b251f70447e9411
    Signed-off-by: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>

-- 
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