1. 31 Mar, 2015 1 commit
  2. 26 Mar, 2015 1 commit
  3. 26 Feb, 2015 1 commit
  4. 25 Feb, 2015 1 commit
  5. 05 Feb, 2015 1 commit
  6. 16 Dec, 2014 1 commit
  7. 16 Nov, 2014 3 commits
  8. 05 Nov, 2014 1 commit
  9. 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
  10. 16 Sep, 2014 1 commit
    • Nigel Cunningham's avatar
      (Bug548021) Add support for anonymising pages. · 9624d430
      Nigel Cunningham authored
      
      
      This patch adds support for anonymising pages.
      
      It creates a site option in the General Settings section named 'Allow
      anonymous pages' that must be checked for any page to be anonymised.
      
      If the site option is enabled, a new 'Anonymise' setting in the
      'Edit title and description' tab of pages is enabled, allowing the owner
      to request that this page be anonymised.
      
      When both settings are enabled and a user views a page, two things may
      happen to the author's information.
      
      First, if the user is not logged in or does not have admin, staff or
      owner privileges for the page, the author's name is replaced by the
      anonymous text (defaulting to "(Author's name hidden)") in both the
      body of the page and the metadata author field.
      
      If the user does have admin, staff or owner privileges for the page,
      the author's name is anonymised as above except that the text displayed
      is made into a link. When this link is clicked, the anonymous author
      text is replaced by the normal author information for the page.
      
      Anonymous pages displayed in the 'Latest pages' block and shared with
      a group are also anonymised by this patch.
      
      Change-Id: I2e2c92f641329a1a305cf58a5c5d47bf95436a8b
      Signed-off-by: default avatarNigel Cunningham <nigelc@catalyst-au.net>
      9624d430
  11. 24 Jul, 2014 1 commit
  12. 16 Jul, 2014 1 commit
  13. 22 Apr, 2014 1 commit
  14. 16 Apr, 2014 1 commit
    • Yuliya Bozhko's avatar
      Move objectionable forms from view library (Bug #1298646) · 2df0d557
      Yuliya Bozhko authored
      
      
      So that we can later use them separately for artefact level access,
      and report artefacts separately from pages.
      
      When testing, everything should work as it worked before with
      reporting objectionable material.
      
      Also fixed "Creating default object from empty value" error
      when ActivityTypeObjectionable object is constructed.
      
      Change-Id: I6d95a5546b2425d9b522435da26902e420139d84
      Signed-off-by: default avatarYuliya Bozhko <yuliya.bozhko@totaralms.com>
      2df0d557
  15. 28 Feb, 2014 1 commit
  16. 17 Feb, 2014 1 commit
    • Jono Mingard's avatar
      Made Attachments expander keyboard-accessible (Bug #1279530) · 9d52504d
      Jono Mingard authored
      
      
      - Changed trigger to an anchor instead of a <td>, moved js file out of resume (since
      resume isn't the only thing using it) and added focus management - the first link in
      the expander is focused when it's opened
      - Modified the expander in Cookie Consent 2 to use the same logic
      - Fixed Resume blocktypes, which were no longer displaying properly after the change
      
      Change-Id: I399ea9558482c1af91bd904f4057851cdb0b3ee7
      Signed-off-by: default avatarJono Mingard <jonom@catalyst.net.nz>
      9d52504d
  17. 09 Jan, 2014 1 commit
    • Robert Lyon's avatar
      Allowing a theme to disable skins from being viewed (bug 1237013) · 7aaeb1c4
      Robert Lyon authored and Aaron Wells's avatar Aaron Wells committed
      
      
      To get a theme to stop showing skins on portfolio pages add this
      to the theme's themeconfig.php
      $theme->skins = false;
      
      When you go to add a skin to a page it will warn you that skins are
      incompatible with this theme - you still can add a skin to the page
      but it will not show up when you view the page.
      
      Also if 'Page themes' are turned on it will warn you that the chosen
      page theme for the page is not compatible with skins.
      
      Change-Id: I694bf14dffddd12373c4079b57c047fa509ab7b7
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      7aaeb1c4
  18. 11 Nov, 2013 1 commit
  19. 14 Oct, 2013 1 commit
  20. 07 Oct, 2013 1 commit
  21. 19 Sep, 2013 3 commits
  22. 23 Aug, 2013 1 commit
  23. 21 Aug, 2013 1 commit
  24. 19 Jul, 2013 1 commit
  25. 06 Jun, 2013 1 commit
  26. 20 Nov, 2012 1 commit
  27. 02 Jul, 2012 1 commit
  28. 27 Jun, 2012 1 commit
  29. 25 Jun, 2012 1 commit
    • Richard Mansfield's avatar
      Modify release form to release entire collections (bug #786389) · 65c3fccd
      Richard Mansfield authored
      When a submitted view is part of a submitted collection (and they're
      both submitted to the same group), the release button is modified to
      say "Release collection", and on submitting the form, the entire
      collection is released.  There is no longer any way to release a
      single page out of a submitted collection.
      
      Change-Id: Ic6bcfab3865e5fb81f90c327598be6cb6e1195bf
      65c3fccd
  30. 21 Jun, 2012 1 commit
  31. 08 Jun, 2012 3 commits
  32. 01 Jun, 2012 1 commit
  33. 30 May, 2012 1 commit
  34. 27 Feb, 2012 1 commit
    • Jono Mingard's avatar
      Add author information to header (Bug 897057) · 6d6f1e0f
      Jono Mingard authored
      
      
      Added the author name to pages (regardless of whether
      they are in a collection) below the page title.
      Added a language string "viewauthor" in
      lang/en.utf8/view.php.
      
      Added a function in lib/view.php to output this string
      with the proper username and URL.
      
      Added this to theme/raw/templates/view/view.tpl by
      passing a new string to smarty ($author) in
      htdocs/view/view.php
      
      Also moved page description to be below tabbed collection
      navigation in view.tpl
      
      Change-Id: I5799ccda3a7f29888692fbd3b4d6aac836cbc677
      Signed-off-by: default avatarJono Mingard <reason.koan@gmail.com>
      6d6f1e0f