1. 15 Feb, 2017 1 commit
  2. 23 Dec, 2016 1 commit
  3. 11 Dec, 2016 1 commit
  4. 03 Oct, 2016 2 commits
  5. 01 Sep, 2016 6 commits
  6. 28 Aug, 2016 1 commit
  7. 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
  8. 01 Feb, 2016 1 commit
  9. 08 Aug, 2015 1 commit
  10. 30 Jul, 2015 1 commit
  11. 05 Feb, 2015 1 commit
  12. 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
  13. 22 Sep, 2014 1 commit
  14. 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
  15. 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
  16. 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
  17. 04 Jun, 2014 1 commit
  18. 07 Jan, 2014 1 commit
  19. 14 Oct, 2013 1 commit
  20. 27 Jun, 2013 1 commit
  21. 03 Jul, 2012 2 commits
    • Son Nguyen's avatar
      Add new parameter to template creation functions (Bug #886080) · 1ee390e5
      Son Nguyen authored
      
      
      Add new parameter $titlefromtemplate to
       - Collection::create_from_template()
       - View::create_from_template()
      
      If titlefromtemplate == true, the title of new collection or view
      will be exactly copied from the template
      
      Change-Id: Ib32058fae34d0df153e03b5e0d0ea45e6e0e9cf1
      Signed-off-by: default avatarSon Nguyen <son.nguyen@catalyst.net.nz>
      1ee390e5
    • Son Nguyen's avatar
      Enable collections in groups and institutions (Bug #886080) · 86d8cc21
      Son Nguyen authored
      
      
      1. For group collections
      Only roles that can edit group pages can do these:
      - Listing group collections
      - Creating a new group collection
      - Deleting and editing an selected group collection.
      - Copying a collection
      2. For institution collections
      Only institution admins can:
      - Listing insitution collections
      - Creating a new institution collection
      - Deleting and editing an selected institution collection.
      - Copying a collection
      
      Change-Id: I799bcfaf0f751d1a8c1fa9b5e5df4832832d8ea1
      Signed-off-by: default avatarSon Nguyen <son.nguyen@catalyst.net.nz>
      86d8cc21
  22. 02 Jul, 2012 1 commit
  23. 25 Jun, 2012 3 commits
  24. 21 Jun, 2012 1 commit
  25. 20 Jun, 2012 1 commit
  26. 17 Jun, 2012 1 commit
  27. 08 Jun, 2012 1 commit
  28. 16 Dec, 2011 1 commit
  29. 02 Dec, 2011 1 commit
    • Richard Mansfield's avatar
      Update navigation blocks when copying collections (bug #898923) · 480b38d4
      Richard Mansfield authored
      
      
      When copying a collection, navigation blocks in the copied pages
      should be updated to point at the new copy of the collection.
      
      After all the pages are copied, all the newly copied navigation blocks
      are examined to see if they navigate the collection being copied.  If
      so, they are updated to navigate the new copy of the collection.  When
      a navigation block points at some collection other than the one being
      copied, it is left alone.
      
      Change-Id: I4b817acfa2cbefafc37f98f3f3f7fc12e54f61c0
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
      480b38d4
  30. 04 Aug, 2011 1 commit
  31. 07 Jun, 2011 1 commit