1. 09 Jan, 2012 1 commit
  2. 04 Jan, 2012 1 commit
  3. 21 Dec, 2011 1 commit
  4. 20 Dec, 2011 1 commit
  5. 16 Dec, 2011 3 commits
  6. 30 Nov, 2011 1 commit
    • Richard Mansfield's avatar
      Revert "Remove temporary session folder code (bug #817940)" · b5277b71
      Richard Mansfield authored
      This reverts commit 8e8132fb.
      That commit was not ready to be merged.  As it says in the commit
      message, "if the session directory goes away somehow between updates,
      there is currently _no_ way to restore it without one of these two
      options. This may need to be considered before merging in this
      We can revert this revert when we have a good alternative for creating
      the session directories.
      Change-Id: I5141832da3225e202feef19dccabfea9ff35beeb
  7. 14 Nov, 2011 1 commit
  8. 11 Nov, 2011 2 commits
  9. 07 Nov, 2011 1 commit
  10. 02 Nov, 2011 3 commits
  11. 31 Oct, 2011 1 commit
  12. 27 Oct, 2011 1 commit
  13. 06 Oct, 2011 1 commit
  14. 04 Oct, 2011 2 commits
  15. 03 Oct, 2011 1 commit
  16. 29 Sep, 2011 1 commit
  17. 28 Sep, 2011 1 commit
    • Richard Mansfield's avatar
      Create all profiles with logged-in access by default (bug #807278) · f820ea6c
      Richard Mansfield authored
      There is currently only a site-wide setting for logged-in profile view
      access.  This means that when two institutions share a site, and one
      wants open profiles and another only wants institution-visible profiles,
      new users in the open-profile institution must be asked to manually add
      logged-in access on their profile.  Because we expect many more
      open-profile institutions than closed-profile institutions on a site, it
      makes more sense to put the onus on the closed-profile institutions to
      ensure their members remove logged-in access manually.
      This change ensures logged-in access is added to all new profiles, but
      only locks that access when the loggedinprofileviewaccess setting is on.
      Change-Id: I3375d7b2f8eb635a11879bf7758267f48f74c508
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
  18. 15 Sep, 2011 1 commit
  19. 12 Sep, 2011 1 commit
  20. 08 Sep, 2011 2 commits
  21. 07 Sep, 2011 1 commit
  22. 02 Sep, 2011 1 commit
  23. 01 Sep, 2011 1 commit
  24. 29 Aug, 2011 2 commits
  25. 26 Aug, 2011 1 commit
    • Melissa Draper's avatar
      Remove temporary session folder code (bug #817940) · 8e8132fb
      Melissa Draper authored
      This patch removes the 'temporary' code that was checking for the
      existance of the session directories at each session creation. This
      check is performed at install and at update, however if the session
      directory goes away somehow between updates, there is currently
      _no_ way to restore it without one of these two options. This may
      need to be considered before merging in this change.
      Change-Id: Ia6020c0b73ce9e172e718c9638a312b1f0162295
      Signed-off-by: default avatarMelissa Draper <melissa@catalyst.net.nz>
  26. 25 Aug, 2011 1 commit
  27. 24 Aug, 2011 2 commits
  28. 22 Aug, 2011 1 commit
  29. 19 Aug, 2011 1 commit
    • Hugh Davenport's avatar
      Allow group members to view their own files · 7d9b3749
      Hugh Davenport authored
      If a file is in the groups area that doesn't have member access
      then the group member that initially uploaded it can't view it
      This patch allows the author (uploader) of a file to still have access
      no matter what the access is set to for the group role they belong to
      Bug #812673
      Change-Id: I1d5bbccb41d34af15617ac5abc673b1265ac9f3e
      Signed-off-by: default avatarHugh Davenport <hugh@catalyst.net.nz>
  30. 16 Aug, 2011 1 commit
    • Richard Mansfield's avatar
      Preserve admin/system user fields when committing LiveUser instance · 725ba929
      Richard Mansfield authored
      The $USER object is saved to the usr table in the db whenever it
      changes, and also periodically when the lastaccess property is updated.
      However, for some fields, it's not appropriate to overwrite the db
      value with the $USER property, because these fields are generally only
      modifiable by an admin (e.g. quota, suspended) or the system (e.g.
      active).  Previously we have tried to deal with this by removing the
      sessions of users whose properties are modified by an admin.  This is
      okay when suspending or deleting a user, because the user should be
      forced to log out anyway.  But for other properties like the user file
      quota, it shouldn't be necessary to force the user to log out because
      the value was modified by an admin.  It makes more sense to specify a
      list of fields (including quota) that should be reloaded into $USER on
      every commit.
      Change-Id: Id0268a29be976a506b09d81aeb6a5b80a26e72fa
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
  31. 03 Aug, 2011 1 commit