1. 15 Apr, 2019 1 commit
  2. 30 Sep, 2018 1 commit
  3. 19 Sep, 2018 1 commit
  4. 31 Aug, 2018 1 commit
  5. 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.
      
      behatnotneeded
      Change-Id: I7a2062f77431d6371f95d7f55bedcc499dd7caa2
      3e76e38e
  6. 04 Jul, 2018 1 commit
  7. 19 Jun, 2018 2 commits
  8. 20 May, 2018 1 commit
    • Robert Lyon's avatar
      Bug 1763163: record who has been given what page for one time copy · 1dcaef85
      Robert Lyon authored
      
      
      This changes the parent patch a bit. Instead of recording on the view
      table if a page is able to be copied to existing group members we
      insetad record in a new existing copy table if a group page/collection
      has been copied to a member and if not make the copy.
      
      We've also made the switch a slide switch, eg when switching it to
      'Yes' it does the task on save and then switches back to 'No'.
      
      This means at a later time if set to 'Yes' again it will do the copying
      again and give any newer members a copy of all pages/collections as
      well as give older members copies of any newer pages / collections /
      collection pages since the previous switching to 'No'
      
      Note: Currently adding new collection pages to older members will only
      add the pages as singular pages to their portfolio.
      
      behatnotneeded
      
      Change-Id: Ia22d8138d80ec5fdb5a401de7289b256f9e5fc69
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      1dcaef85
  9. 14 Sep, 2017 1 commit
    • Robert Lyon's avatar
      Bug 1692385: Adjusting the handle event for 'updateviewaccess' · a3d904e1
      Robert Lyon authored
      
      
      We want to record things like so:
      
      resourceid = view_access.id
      resourcetype = what type the view_access row is for, eg 'token',
      'user', 'loggedin' etc
      parentresourceid = the id if the view the access is for
      parentresourcetype = 'view';
      ownerid = the id of the owning resource, eg usr.id / group.id / institution.name
      ownertype = what owns the resource, eg user / group / institution
      
      Also this patch adjusts how we index things into elasticsearch
      
      behatnotneeded
      
      Change-Id: I079a42ded2fefaab64a6e49fc26e8aad303c9e8a
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      a3d904e1
  10. 09 Sep, 2017 1 commit
    • Robert Lyon's avatar
      Bug 1692385: Adjusting the event_log table · ebd928b1
      Robert Lyon authored
      
      
      Add 5 new new columns to event_log table make searching over the
      data easier and also record the id of any parent/related info as well
      
      Eg, if one deletes an image block from a page we now record:
      id - the event id
      resourceid - the block id
      resourcetype - the blocktype, eg image
      parentresourceid - the id of the parent, eg view id
      parentresourcetype - the type of parent, eg 'view'
      
      Because we would not be able to find related view info from just the
      block id anymore.
      
      Also added the ability to index and search over event information in
      elasticsearch search type event_log
      
      Change-Id: I280c1c75c35a6c58f42d8acb36cf5c24c70b902d
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      ebd928b1
  11. 19 Apr, 2017 1 commit
  12. 20 Mar, 2017 1 commit
  13. 16 Mar, 2017 1 commit
  14. 15 Feb, 2017 1 commit
  15. 09 Feb, 2017 1 commit
    • Cecilia Vela Gurovic's avatar
      Bug 1655456: fix shared collection not displaying · 359f3540
      Cecilia Vela Gurovic authored
      Collection shared to a group was not displaying
      in group page and shared with me page
      after first page of collection was deleted.
      Fixed by resetting the order when deleting a view.
      
      behatnotneeded
      
      Change-Id: I096114ecf50b7a3af6d1393b387073676a984006
      359f3540
  16. 23 Dec, 2016 1 commit
  17. 11 Dec, 2016 1 commit
  18. 03 Oct, 2016 2 commits
  19. 01 Sep, 2016 6 commits
  20. 28 Aug, 2016 1 commit
  21. 03 Jul, 2016 1 commit
    • Robert Lyon's avatar
      Bug 1594579: Copy view artefacts only once · baac44f1
      Robert Lyon authored
      
      
      Rather than copy the same artefact once per page we should only copy
      it once per copy of page(s) transaction. Eg if we are to copy a
      collection of 5 pages and they all have a block pointing to the same
      image we should copy that image only once not 5 times.
      
      behatnotneeded - behat file to come
      
      Change-Id: Iecdde53515cdd9d5ee02918252b486aa0f662fab
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      baac44f1
  22. 01 Feb, 2016 1 commit
  23. 08 Aug, 2015 1 commit
  24. 30 Jul, 2015 1 commit
  25. 05 Feb, 2015 1 commit
  26. 16 Oct, 2014 1 commit
    • Aaron Wells's avatar
      Make Collection::save() play well with existing collections & non-null columns · 1f779bdd
      Aaron Wells authored
      Bug 1381811: Collection::save() would create a new (empty) collection by
      passing 0 as the id to the Collection constructor, even if the supplied
      $data included an "id" field. Since the id was not supplied to the
      constructor, it does not pull the collection's current data from the
      database.
      
      It would then call Collection->commit(), which would notice the "id"
      field and do an update instead of an insert into the database. But due to
      the way the Collection class is written, it would try to populate every
      field of the collection table, rather than just those supplied in $data.
      
      This means that all the database fields not supplied in $data, would
      attempt to be filled with NULL. This threw an error because of the new
      collection.submittedstatus NOT-NULL column.
      
      Change-Id: I6a2927892459bd25d51bd58de1bd3e3584df0793
      1f779bdd
  27. 22 Sep, 2014 1 commit
  28. 18 Sep, 2014 1 commit
    • Robert Lyon's avatar
      The archiving of submitted pages/collections from groups (Bug #1335670) · 5c57b565
      Robert Lyon authored
      
      
      This patch contains:
      - The export queue system where pages/collections on release from
      submission are added to the export queue table ready to be archived.
      - The export queue admin page showing what is in the queue to be
      exported. The cron runs every 6 minutes. Queue items failed to export
      are also shown here.
      - The archive list admin page, where one can download the generated
      leap2a files for the archived submissions.
      
      In this patch you should be able to add things to the export queue by
      either releasing a sumbission on a group that has 'archive
      submissions' option ticked. This will add the archive to that archived
      submission page, or you can also run a leap2a export from portfolio
      export which will add the export queue and send you an email once the
      export is done.
      
      Things to note:
      - The is a server busy function that stops the export queue from
      running but I'm not too sure if the threshold is too low/high
      - The export queue tries to export the first 100 items each run but if
      resources are fine in handling that easily then the number could be
      higher but I'm not sure of what will be a good number.
      - Currently there is alsoe infrastructure like table columns for dealing
      with releasing submissions from external systems (eg moodle) but that
      functuionality is yet to be built.
      - The checking of server busy in MS windows untested - may need to
      just let MS ignore server busy check as there doesn't seem to be
      standard way to check this.
      
      Change-Id: If4c1d272e9c5d46fbf16b2ff73ceb2687c06ffd4
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      5c57b565
  29. 21 Aug, 2014 1 commit
    • Aaron Wells's avatar
      Don't let locked views be added to collections · 86a87d4f
      Aaron Wells authored
      Bug 1323163. This patch still allows locked views to be *removed*
      from collections. Whether that should be banned as well is a separate
      question.
      
      Change-Id: I54ffa3fecdeeb7ef9d4d8c382750659d59d2722e
      86a87d4f
  30. 13 Jul, 2014 1 commit
    • Robert Lyon's avatar
      Allow collection's pages list to be added/edited by drag/drop (Bug #1320716) · e3d38601
      Robert Lyon authored
      
      
      You can now alter the sorting of the list by dragging the page name to
      a new position.
      
      You can also add in new pages to the collection by dragging them in
      from the 'add pages to collection' list. If there are no existing
      pages in collection you need to drop a page onto the 'No pages' grey
      box.
      
      Also added touch-punch js lib to allow for the drag/drop to work as
      well on mobile devices.
      
      Change-Id: Id1af83abc50b76a7a8d56da8767ed4ce0ef76f77
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      e3d38601
  31. 04 Jun, 2014 1 commit
  32. 07 Jan, 2014 1 commit
  33. 14 Oct, 2013 1 commit