1. 01 Feb, 2019 2 commits
  2. 31 Jan, 2019 1 commit
  3. 09 Jan, 2019 1 commit
  4. 18 Oct, 2018 1 commit
  5. 12 Sep, 2018 1 commit
  6. 09 Sep, 2018 1 commit
  7. 31 Aug, 2018 1 commit
  8. 16 Aug, 2018 1 commit
  9. 08 Aug, 2018 1 commit
    • Kevin Dibble's avatar
      Bug 1781844: Lock blocks on pages · 3e76e38e
      Kevin Dibble authored and Robert Lyon's avatar Robert Lyon committed
      A lot of users in Mahara create (Template) pages to share out to users.
      This reduces the setup a new user will have to do to. There is an issue
      that on their personal copy, the blocks that were so carefully setup can
      be deleted.
      This functionality creates a new column in the database called
      "lockblocks" that can be enabled/disabled on the share page.
      When the user copies the page, this setting is copied over and the
      "delete" icon is hidden from view should the lockblocks setting be
      enabled. This only happens on normal portfolio pages.
      To unset - the user can edit the page settings and
      disable the lock blocks feature to enable the deletion of the blocks as
      per normal.
      Change-Id: I7a2062f77431d6371f95d7f55bedcc499dd7caa2
  10. 28 Jun, 2018 1 commit
  11. 19 Jun, 2018 1 commit
  12. 04 Mar, 2018 1 commit
    • Kristina Hoeppner's avatar
      Bug 1734164: Update default legal statements · 00c18420
      Kristina Hoeppner authored and Kristina Hoeppner's avatar Kristina Hoeppner committed
      Removed the template text so as not to imply
      that it is sufficient for an institution. Every
      site admin will need to check with the institution's
      legal team on what needs to be provided in the
      "Terms and conditions" and "Privacy statement".
      Template text was also removed for the default
      homepage and dashboard to encourage institutions
      to write their own text.
      Change-Id: I81481dca7f16b29c57dfcdd3d211e8c7b76432dc
  13. 05 Feb, 2018 1 commit
    • Maria Sorica's avatar
      Bug 1734174: Add the after login privacy page · 44a6284e
      Maria Sorica authored
      Upon login, if the user has not yet agreed to the most
      recent Privacy statement versions, he will be redirected
      to this page.
      On install admin user accepts default privacy
      Change-Id: I6afc3d4d4db0676782a8b1501a962862108eab6b
  14. 09 Jan, 2018 1 commit
  15. 19 Oct, 2017 1 commit
  16. 26 Sep, 2017 1 commit
    • Rebecca Blundell's avatar
      Bug 1674850 - journal block tests · 223b372d
      Rebecca Blundell authored
      Just fixed merge conflict - other issues still to fix
      New feature adding test for all 4 journal types to see they display correctly
      Also includes new 'journals' background step to create journals
      and new 'journalposts' background step to create journal entries
      I called the one for journal entries 'journalposts' to keep it
      consistent with noun plural being an 's'
      Also updated an existing feature for taggged posts to use the new
      'journalposts' step so that we have an examples of it's use with and
      without using the 'journals' step
      Change-Id: I0200e5a263359610c6ad49d38a9f2cc866f9af61
  17. 08 Sep, 2017 1 commit
    • Robert Lyon's avatar
      Fixing behat for testing webservices · c740a5cf
      Robert Lyon authored
      This patch
      - moves webservice tests into their own directory
      - allows one to create an institution with 'webservice' auth
      - allows creation of a user using 'webservice' auth
      @TODO actually test things in webservices
      Change-Id: Ib64687dbd647179233fed2c3937418847bfda27c
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
  18. 07 Jun, 2017 1 commit
    • Robert Lyon's avatar
      Bug 1696601: Fixing behat uninstall process · 40251ca6
      Robert Lyon authored and Kristina Hoeppner's avatar Kristina Hoeppner committed
      Currently gives an error:
      [WAR] ca (lib/errors.php:859) Failed to get a recordset: postgres8
      error: [-18: ERROR:  relation "behat_artefact_installed_type" does not
      The fix still shows errors but they are just uncaught sql exceptions
      the fix actually allows the site to uninstall and install correctly
      Change-Id: I2af1b32ee1d88f30126681517afb069050586d27
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
  19. 20 Mar, 2017 1 commit
  20. 09 Feb, 2017 1 commit
  21. 26 Jan, 2017 1 commit
  22. 06 Jan, 2017 2 commits
  23. 27 Sep, 2016 1 commit
  24. 01 Sep, 2016 1 commit
  25. 18 Feb, 2016 1 commit
  26. 10 Jan, 2016 2 commits
  27. 13 Oct, 2015 1 commit
  28. 13 Aug, 2015 1 commit
  29. 10 Aug, 2015 1 commit
  30. 03 Aug, 2015 2 commits
  31. 20 Jul, 2015 1 commit
    • Tobias Zeuch's avatar
      Bug 1468156: Change plugin type of plugin multirecipientnotification to module · dd0e1dab
      Tobias Zeuch authored
      To change the plugin type from artefact to module, the code is moved and the
      superclass reference is changed to PluginModule. Obsolete classes for the
      former unused artefact types are deleted. The references to the old script
      paths are changed. Plugin Tables are renamed and references updated.
      The new plugin mustn't be installed when the old plugin is still active, but on
      upgrade, the database tables are renamed and references in artefact_installed
      and artefact_event_subscription and the triggers are changed.
      Change-Id: Id5f1198b780ffb92181f7d60785aad9ffe2259da
      Signed-off-by: default avatarTobias Zeuch <tobias.zeuch@rwth-aachen.de>
  32. 21 May, 2015 1 commit
  33. 22 Mar, 2015 1 commit
  34. 19 Dec, 2014 1 commit
  35. 04 Dec, 2014 2 commits