1. 05 Apr, 2016 1 commit
  2. 15 Sep, 2015 3 commits
  3. 27 May, 2015 1 commit
  4. 21 Apr, 2015 2 commits
  5. 13 May, 2014 2 commits
  6. 12 May, 2014 2 commits
  7. 11 May, 2014 1 commit
    • Responsive navigation menu doesn't collapse in iPad in portrait mode · 4df99a8b
      Kamaya Sho authored
      Bug 1308857. The problem appears to be that the collapse logic is based
      around a <= and a >=, and the iPad in portrait mode falls right in the middle
      so it triggers both. Changing this to a more logical <= and > pair fixes things.
      
      Change-Id: Iacb8d53daff0f06a6f414bf5e4aafdee1337dfa3
  8. 14 Apr, 2014 3 commits
  9. 03 Apr, 2014 4 commits
  10. 02 Apr, 2014 10 commits
  11. 01 Apr, 2014 3 commits
    • Check that account is valid before logging in via password reset · 3475f03a
      Aaron Wells authored
      Bug1284876: Without this, a suspended user can log in via a password
      reset email
      
      Change-Id: I5cb8f2978cdc2c6c0a6975a3fbfd2dfdc1d9bcc5
    • Bug1075760: reporting objectional material with no message doesn't get sent to… · 8c7a5e68
      Ghada El-Zoghbi authored
      Bug1075760: reporting objectional material with no message doesn't get sent to admin with digest emails
      
      Email digest table has a not null contraint for the message field:
      1. Force the user to enter something in the objectionable comment.
      2. Other areas: if a user enteres a message (i.e. in a forum)
      which is made up of html (i.e. a smiley face),
      the message gets 'cleaned' by stripping html tags.
      This leaves it empty and fails when trying to insert into the
      email digest table.
      Clean the message with html2text instead of str_shorten_html.
      3. As a last resort, before inserting into the email digest table,
      make sure there is at least a space in the message field (if it's empty).
      
      Change-Id: I05a77e0682017839b34e74241eefb98fb788eab5
      Signed-off-by: 's avatarGhada El-Zoghbi <ghada@catalyst-au.net>
    • Getting mysql not to use CAST() (bug #1081947) · e35d3ea8
      Robert Lyon authored
      In the 1.8+ codebase there are only two places where both mysql and
      postgres use CAST(). So I've tried altering the calls so that mysql
      doens't need to use CAST().
      
      This will probably need to be tested with a large data mysql db site
      to see if any speed gains are made, and also the calls are still
      working correctly.
      
      All other places it is being used by postgres only
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      
      Change-Id: I9eaf196d062ef2a62bfdae0df179281f3411c392
  12. 31 Mar, 2014 1 commit
  13. 25 Mar, 2014 1 commit
  14. 25 Feb, 2014 1 commit
  15. 12 Feb, 2014 1 commit
  16. 14 Jan, 2014 2 commits
  17. 06 Jan, 2014 1 commit
    • Override MySQL's check for accidental large queries · f4e4b44f
      Aaron Wells authored
      Bug 1070046: MySQL has an optional server config option, "MAX_JOIN_SIZE",
      which throws an error if you try to run a SQL query that MySQL's strategizer
      thinks will require it to evaluate more than MAX_JOIN_SIZE rows. This is
      intended to prevent the user from accidentally running giant queries that
      will never finish, but some Mahara queries (which are large but will finish)
      can trip it. Adding SQL_BIG_SELECTS=1 tels it that our queries are *not*
      accidentally large.
      
      Also has order change for bug 1184450
      
      Change-Id: I6db4699ea765d3213d13eb93b8de098914db24e0
  18. 23 Dec, 2013 1 commit