1. 05 Jun, 2014 1 commit
  2. 24 Apr, 2014 1 commit
    • Aaron Wells's avatar
      Fixes an "undefined index" warning on the account settings page · f91fbf0a
      Aaron Wells authored
      Bug 1311963. The call to get_records_assoc() assumes that institution.name
      will be the first column returned. But we've added an institution.id column
      that comes before that, so now we need to specifically tell it to use the
      name column instead.
      
      Change-Id: I51ef6e805b80894fa6af7bc732fb241adac0fdec
      f91fbf0a
  3. 26 Mar, 2014 1 commit
  4. 25 Mar, 2014 1 commit
  5. 07 Jan, 2014 1 commit
  6. 25 Nov, 2013 1 commit
  7. 14 Oct, 2013 1 commit
  8. 10 Sep, 2013 1 commit
  9. 02 Sep, 2013 1 commit
    • Aaron Wells's avatar
      Changing PluginAuth API to specifically indicate whether Auth requires remote username · 20512fdb
      Aaron Wells authored
      Bug 1160093: This adds a few new methods to the Auth class, which represents an auth instance:
      
       - is_parent_authority(): Indicates whether this auth instance is a parent authority or not
       - get_parent_authority(): Gets the ID of this auth instance's parent authority
       - needs_remote_username(): Indicates whether this auth instance needs the user to have a
            remote username setting (in auth_remote_user table)
      
      I've also updated the SAML and XMLRPC auth types, which are the only ones that use remote username.
      And I've updated create_user() to automatically populate auth_remote_user() for auth
      instances that use it.
      
      Note that an auth instance of ANY type will need a remote username if it's the parent to another
      authority (the parent feature allows a user to log in via the parent or the child auth instance;
      so it's quite possible for the user to have different usernames in the two of them. Currently
      only XMLRPC uses the parent auth feature.)
      
      Lastly, also updated the documentation of LiveUser->create_user() to indicate that it only
      uses the $remoteauth parameter as a boolean (which was true even before my code changes).
      
      Change-Id: I39b1b74e68cdbc9c2632b886655caaaece1bd312
      20512fdb
  10. 22 Aug, 2013 1 commit
  11. 23 Jun, 2013 1 commit
  12. 16 Jun, 2013 1 commit
  13. 20 Aug, 2012 1 commit
  14. 08 Jun, 2012 1 commit
    • Richard Mansfield's avatar
      Use clean profile urls when data is already available · e262b5bb
      Richard Mansfield authored
      Bug #1006634, part 3
      
      Adds a new profile_url function which respects the cleanurls
      configuration, and makes use of this function in many places where the
      user's url field is already available:
      
      - Admin user account settings page
      - Redirects after inviting/adding users to groups
      - Redirects & notifications after accepting/denying friend requests or unfriending
      - The name plate in the top right header & small view header
      - Online users sideblock
      - Display of threaded personal messages
      
      Change-Id: Ia43ae0867af12f6d78c0ad389fae25c58ac69b43
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
      e262b5bb
  15. 03 Apr, 2012 1 commit
  16. 16 Feb, 2012 1 commit
  17. 10 Jan, 2012 1 commit
    • Richard Mansfield's avatar
      Expire users when they've been inactive for too long (bug #890929) · 81f26254
      Richard Mansfield authored
      The "Default account inactivity time" setting allows the admin to
      specify a time period after which users who have not used the site
      will be unable to login, but this is not currently enforced.
      
      This change modifies the inactivity cron job to set the expiry date to
      the current date for any user who has been inactive for longer than
      the 'defaultaccountinactiveexpire' period.  It also now considers the
      lastaccess and ctime fields as well as the lastlogin field.
      
      This allows the admin to reactivate inactive users by resetting their
      expiry dates in account settings.
      
      The active column on the user table is currently only used to decide
      whether users should be displayed in search results, and users are set
      to inactive whenever they are deleted, suspended, or expire.
      
      Change-Id: Ieaf7a0b36865af726fc2526895146373efbb2741
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
      81f26254
  18. 06 Jan, 2012 3 commits
  19. 15 Sep, 2011 1 commit
  20. 20 Jul, 2011 2 commits
  21. 19 Jul, 2011 1 commit
  22. 23 Jun, 2011 1 commit
  23. 22 Jun, 2011 1 commit
  24. 01 Jun, 2011 1 commit
  25. 13 May, 2011 1 commit
  26. 09 May, 2011 1 commit
  27. 21 Apr, 2011 1 commit
  28. 15 Apr, 2011 1 commit
  29. 22 Dec, 2010 1 commit
  30. 09 Nov, 2010 1 commit
  31. 04 Nov, 2010 1 commit
  32. 16 Sep, 2010 1 commit
  33. 07 Sep, 2010 1 commit
  34. 03 Sep, 2010 1 commit
  35. 02 Sep, 2010 2 commits
  36. 01 Aug, 2010 1 commit