1. 29 Mar, 2012 1 commit
  2. 28 Mar, 2012 1 commit
    • Richard Mansfield's avatar
      Display a message when plpgsql cannot be created (bug #960631) · c5b26f2c
      Richard Mansfield authored
      The upgrade to 1.5 requires that the plpgsql language is available in
      postgres, but sometimes (e.g. versions of postgres < 8.3), the
      database owner doesn't have permission to create the language, and the
      admin will have to do it manually.
      During the attempt to issue the CREATE LANGUAGE command, an sql
      exception can be thrown when the db user has insufficient privileges,
      so a generic 'nonrecoverable error occured' message is displayed
      instead of the useful message instructing the admin to create plpgsql.
      Catching the sql exception fixes this problem.
      Change-Id: I176bdd1eee2247426ceedc6f165156d33eefbb42
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
  3. 10 Feb, 2012 2 commits
  4. 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>
  5. 15 Nov, 2011 1 commit
  6. 24 Aug, 2011 2 commits
  7. 13 May, 2011 1 commit
  8. 23 Feb, 2011 1 commit
  9. 01 Oct, 2010 1 commit
  10. 14 Jan, 2010 1 commit
  11. 01 Dec, 2009 1 commit
  12. 22 Oct, 2009 1 commit
  13. 03 Sep, 2009 1 commit
  14. 21 Apr, 2009 1 commit
  15. 14 Apr, 2009 1 commit
  16. 22 Jan, 2009 1 commit
  17. 15 Jan, 2009 1 commit
  18. 05 Jan, 2009 1 commit
  19. 13 Oct, 2008 2 commits
  20. 30 Sep, 2008 1 commit
  21. 21 Sep, 2008 1 commit
  22. 15 Sep, 2008 1 commit
    • Penny Leach's avatar
      More work on profile views and three new blocktypes... · 8465aa3f
      Penny Leach authored
      More work on profile views and three new blocktypes (myfriends/mygroups/myviews) to emulate current profile page TODO: - write wall blocktype - change install default profile view hook to add blocks - upgrade path (xmldb & migration) - blocktype and category and singleblockperview implementation
          - TESTING
  23. 18 Jun, 2008 1 commit
  24. 18 Mar, 2008 1 commit
    • Nigel McNie's avatar
      Make db_format_timestamp return null for any value that is 'empty'. · d6596676
      Nigel McNie authored
      Otherwise, $db->BindTimestamp() will return the string 'null' for 0 and '0', which no code in Mahara is expecting.
      Noticed as part of the previous commit, where $user->lastlogin defaulted to 0 (which was incorrect), and which db_format_timestamp was converting to 'null'.
  25. 20 Feb, 2008 1 commit
    • Nigel McNie's avatar
      Work around a bug in insert_record, where the table columns were cached for a... · e1c17aea
      Nigel McNie authored
      Work around a bug in insert_record, where the table columns were cached for a table the first time the table was inserted into, making it impossible to do inserts into the table in the same request if the table is changed.
      Added a global variable, $INSERTRECORD_NOCACHE, that can be set in order to force re-looking up the table columns.
      Use this feature to fix the installation of the forum interaction activity type "new post" when upgrading.
  26. 16 Feb, 2008 1 commit
  27. 12 Feb, 2008 1 commit
  28. 07 Dec, 2007 1 commit
    • Nigel McNie's avatar
      Make admin users/staff users scripts show all users rather than just users... · b1a4173f
      Nigel McNie authored
      Make admin users/staff users scripts show all users rather than just users that would be returned by standard search. Fxies #1756.
      This is actually quite a large patch, which does the following:
       * adds a db_ilike() method, which returns the correct keyword (LIKE or ILIKE) to do case insensitive searching.
       * Switches the templates used for the admin user search for strings, rather than using files. This prevents problems when the theme is not the default and the templates are not there.
       * Implements admin_search_user in the internal search plugin for MySQL as well as postgres, without needing two separate methods since the query works on both.
       * Make the userlist element use the new json/adminusersearch.php script, which performs an admin user search.
      One happy upside is that the admin user search screen now works in MySQL.
  29. 04 Dec, 2007 1 commit
  30. 03 Dec, 2007 1 commit
  31. 22 Nov, 2007 1 commit
  32. 20 Nov, 2007 1 commit
  33. 19 Nov, 2007 1 commit
    • Nigel McNie's avatar
      Implement transaction level counting for db_begin() and friends. · 9578988e
      Nigel McNie authored
      This means that we can safely call db_begin() and db_commit() anywhere, and as long as the calls balance, the transaction will only be committed when the last one is committed.
      If a rollback is asked for at any time, the entire transaction is rolled back.
  34. 06 Nov, 2007 1 commit
  35. 04 Nov, 2007 1 commit
    • Nigel McNie's avatar
      Added a new function, insert_record_if_not_exists. · 14496c8c
      Nigel McNie authored
      This uses the postgres SELECT FOR UPDATE syntax to ensure we don't have a race condition when inserting a record that previously didn't exist. The other database one is a bit more race condition-ey.
  36. 25 Oct, 2007 1 commit
  37. 24 Oct, 2007 1 commit