1. 06 Jan, 2014 1 commit
    • Aaron Wells's avatar
      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
  2. 23 Dec, 2013 5 commits
  3. 12 Dec, 2013 1 commit
    • Aaron Wells's avatar
      Writing a helpfile for "generate sitemap" · 6ad43a71
      Aaron Wells authored
      Bug 974855: It's not great that the helpfile doesn't actually contain the URL for your sitemap,
      but we'd need to implement the ability to put parameters or variables into help files to make that happen.
      Change-Id: I7cc414510ffe78432a4e21d61a829f67ff1d9929
  4. 10 Dec, 2013 2 commits
  5. 05 Dec, 2013 1 commit
  6. 27 Nov, 2013 1 commit
  7. 26 Nov, 2013 1 commit
  8. 21 Nov, 2013 1 commit
  9. 28 Oct, 2013 4 commits
  10. 25 Oct, 2013 5 commits
  11. 24 Oct, 2013 3 commits
  12. 22 Oct, 2013 1 commit
    • Robert Lyon's avatar
      Allowing pieform error text to not be escaped if needed (Bug 1239539) · bd33b9c8
      Robert Lyon authored
      Currently if there is html in an error message used by pieforms it
      escapes the html so the link becomes not usable.
      I have made a change where you can tell pieforms not to escape the
      error message.
      So instead of using:
      $form->set_error($field, $message);
      you can use:
      $form->set_error($field, $message, false);
      Where false means do not escape the message.
      As the terms and conditions are displayed on the page already I've
      updated the link to jump to the terms section
      Change-Id: Ia8650a9f2284fb007cbe81a4a94223f127c4f6cd
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
  13. 08 Oct, 2013 1 commit
    • Aaron Wells's avatar
      Update session-cached display name when deleting it · 6ecbe067
      Aaron Wells authored
      Bug 1223063: ArtefactTypeCachedProfileField was only updating
      the session cache when you updated a value, not when you deleted it.
      Of course, the only one that can get deleted and that is shown
      anywhere is the PreferredName (aka display name) so only this
      one shows the problem.
      Change-Id: I55f9c96b59c91ced5cba3cf6443ba2e222201ef7
      Signed-off-by: Aaron Wells's avatarAaron Wells <aaronw@catalyst.net.nz>
  14. 02 Oct, 2013 8 commits
  15. 01 Oct, 2013 3 commits
    • Kristina Hoeppner's avatar
      Add alt and title tag for blocks (Bug #1218684) · 971fa738
      Kristina Hoeppner authored
      IE only picks up the alt and not the title
      tag. I added both so that users will see the
      Change-Id: I2f1c9342363d3372e5aa1549da7fcfc3086177b1
      Signed-off-by: Kristina Hoeppner's avatarKristina D.C. Hoeppner <kristina@catalyst.net.nz>
    • Kristina Hoeppner's avatar
      Add missing lang string for warning (Bug #1227372) · e147f3c9
      Kristina Hoeppner authored
      Lang string was missing for "Allowed iframe sources"
      Change-Id: I1cab612134a334fac7f0ca54fcf406b4a08f3226
      Signed-off-by: Kristina Hoeppner's avatarKristina D.C. Hoeppner <kristina@catalyst.net.nz>
    • Hugh Davenport's avatar
      Fix permissions of group area (Bug #1034180) · f5cebdef
      Hugh Davenport authored
      A user should not be able to view/publish an artefact if
      - they don't have view/publish permission of that artefact
      - they don't have view permission of all parents of that artefact
      A user should not be able to edit an artefact if
      - they don't have edit permission of that artefact
      - they don't have edit permission of the immediate parent of that artefact
      - they don't have view permission of any parents below the immediate
      This is similar to the UNIX permissions, you shouldn't be able to view
      a directory unless all directories below have read (r) and executeable (x)
      bits set. The same for editing, you need write (w) permissions of the
      immediate parent, and rx for all parents.
      In Mahara, there are no executeable bits, but it can be assumed
      that view is basically the same as rw for container artefacts, and the same
      as r for non container artefacts.
      Change-Id: I4f84aca05dd08d02b05fbe084e4724f78c8681a0
      Signed-off-by: default avatarHugh Davenport <hugh@catalyst.net.nz>
  16. 24 Sep, 2013 1 commit
  17. 22 Sep, 2013 1 commit