1. 20 Oct, 2015 1 commit
  2. 19 Oct, 2015 1 commit
  3. 16 Oct, 2015 1 commit
  4. 07 Oct, 2015 1 commit
  5. 20 Sep, 2015 1 commit
  6. 17 Aug, 2015 1 commit
  7. 30 Jul, 2015 1 commit
  8. 23 Jul, 2015 1 commit
    • Robert Lyon's avatar
      Bug 1467368: Allowing the main menu structure to be cached · ec41d0e0
      Robert Lyon authored
      This will allow the rendering of the main nav to use less resources.
      
      The cached menus are saved for each institution into the
      institution_config table for these types of menus:
      
      adminnav     - site administration navigation
      instadminnav - institution admin navigation
      staffnav     - site staff admin navigation
      inststaffnav - institution staff admin navigation
      standardnav  - navigation seen in normal section of site
      
      To clear cache menus call clear_menu_cache($institution)
      
      Change-Id: I3b58090830b6d28f10f24e23abeef775c6863aa5
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      ec41d0e0
  9. 06 Jul, 2015 1 commit
  10. 23 Jun, 2015 1 commit
  11. 15 Jun, 2015 4 commits
    • Naomi Guyer's avatar
      NEW:Optionally include parent theme, Forms, icons, tidyup (bootstrap) · 4739efeb
      Naomi Guyer authored
      Bug 1465107: Use Bootstrap CSS Framework
      
      Change-Id: I1f631d6f2637b22e00ea9e0972f0447a52304f4c
      4739efeb
    • Naomi Guyer's avatar
      Form cleanup (bootstrap) · 5fba0303
      Naomi Guyer authored
      Bug 1465107: Use Bootstrap CSS Framework
      
      Change-Id: I760a099bf0759cdf07a17bf599c43567b77b8c65
      5fba0303
    • Naomi Guyer's avatar
      Admin (bootstrap) · cfde5745
      Naomi Guyer authored
      Bug 1465107: Use Bootstrap CSS Framework
      Admin area
      File browser fixes
      Style resume pages excluding collapsible elements
      
      Change-Id: Ica76a112b6fcf589f34bcb667ecc1cf426bd7339
      cfde5745
    • Naomi Guyer's avatar
      Navigation (bootstrap) · 85b78c1f
      Naomi Guyer authored
      Bug 1465107: Use Bootstrap CSS Framework
      Applied bootstrap tabs and tidy up form styling
      Mobile menu
      Add bootstrap accessibility, tab styling to bootstrap
      
      Change-Id: Ifa42d482f5fd7e1cdfb52bae1ebb5ff3bf5085a9
      85b78c1f
  12. 22 Mar, 2015 1 commit
  13. 13 Mar, 2015 1 commit
  14. 09 Mar, 2015 1 commit
  15. 04 Mar, 2015 1 commit
  16. 21 Jan, 2015 1 commit
  17. 16 Jan, 2015 1 commit
  18. 14 Jan, 2015 1 commit
  19. 22 Sep, 2014 1 commit
  20. 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
  21. 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
  22. 15 Sep, 2014 1 commit
  23. 14 Sep, 2014 1 commit
  24. 07 May, 2014 1 commit
  25. 16 Apr, 2014 1 commit
    • Nathan Lewis's avatar
      Improvements to notification system (Bug #1299993) · 63e0484d
      Nathan Lewis authored
      - Each activity type can specify a default notification method. They default
        to 'email' to remain backwards compatible.
      - Each activity type can specify if it is allowed to be set to 'none'. Defaults
        to 'allowed' for backwards compatibility.
      - Removed 'required' from notification settings - it didn't make sense, and the
        change above deals with this in a better way.
      - The site wide defaults for each activity type can be edited in
        Site options -> Notification settings. These are applied to new users or
        whenever a user does not have the appropriate usr_activity_preference records.
      - Removed 'Default notification method' as it's functionality is now covered by
        the change above.
      - There is a separate help next to each activity type to explain what messages
        will be affected by the setting.
      
      Change-Id: I131cdeefbeaa8e43688aefd9d770fc8cb9bceea8
      Signed-off-by: default avatarNathan Lewis <nathan.lewis@totaralms.com>
      63e0484d
  26. 27 Mar, 2014 2 commits
  27. 26 Mar, 2014 1 commit
    • Tobias Zeuch's avatar
      New watchlistnotification Plugin (Bug 1041228) · 6fe99d5f
      Tobias Zeuch authored
      Introducing a new plugin watchlistnotification that responds to the
      events saveartefact, blockinstancecommit and deleteblockinstance. It
      stores the changed view and the blockinstance in a table watchlist_queue
      and checks via cron if there were any changes on a view and if for that
      view the last change has happened some time ago (the minutes are stored
      in config under watchlistnotification_delay, the default is 20min).
      
      If so, a message is generated that informs the watchlist recipient about
      which view and which block-instances on this view have been touched
      (added or changed).
      
      As there is no way to disable the built-in/old watchlist-notification-
      system, this is disabled in the mahara-core code, that is,
      artefact/lib.php and lib/view.php
      
      Change-Id: I039c5285cdd1b09ed9eb38a647e0c1510c3cabb9
      Signed-off-by: default avatarTobias Zeuch <tobias.zeuch@kit.edu>
      6fe99d5f
  28. 25 Mar, 2014 1 commit
  29. 12 Mar, 2014 1 commit
  30. 22 Jan, 2014 1 commit
    • Robert Lyon's avatar
      Allowing for users to not show up in public search (bug 1257953) · e8f57ea6
      Robert Lyon authored
      Thinking of privacy issues here - when should the users showup on
      search results.
      
      This patch allows users to show up based on the access of their
      profile page (accesstypes: public, loggedin, friends) and whether
      'Show users in public search' is set or not.
      
      Normally all profile pages are accessible by logged in users - but
      this can be altered if 'Logged-in profile access' is unchecked and
      users remove the access off their profile page.
      
      Change-Id: I4daa8cb2812bddb231ba489dfeefb4843b653d40
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      e8f57ea6
  31. 05 Dec, 2013 1 commit
  32. 27 Nov, 2013 1 commit
  33. 17 Nov, 2013 1 commit
  34. 11 Nov, 2013 1 commit
  35. 14 Oct, 2013 1 commit
  36. 09 Oct, 2013 1 commit
    • Aaron Wells's avatar
      Fixing variable name typo · 083baf17
      Aaron Wells authored
      Bug1237183 : This typo caused a warning to be thrown when changing the search plugin
      
      Change-Id: Ia8b6cc9eb8fd878a90437a2212f915e0450cd063
      083baf17