1. 20 May, 2015 1 commit
  2. 16 Apr, 2015 1 commit
  3. 26 Mar, 2015 1 commit
  4. 09 Mar, 2015 1 commit
  5. 01 Feb, 2015 1 commit
  6. 16 Dec, 2014 1 commit
  7. 10 Dec, 2014 1 commit
  8. 11 Nov, 2014 1 commit
  9. 07 Nov, 2014 1 commit
  10. 05 Nov, 2014 1 commit
  11. 23 Oct, 2014 1 commit
    • Aaron Wells's avatar
      Add a <meta name="generator"> tag with the Mahara major version number · 847754aa
      Aaron Wells authored
      Bug 1384497. This also adds a new $config->series to lib/version.php,
      which stores the major version (or as we sometimes call it, "the series")
      of the current release. It seemed better to store this separately rather
      than to try to parse it from $config->release, because we may change
      our release numbering strategy in the future.
      
      Change-Id: If4c0d7352e9433cdaf54a03bb922356d6c950e7d
      847754aa
  12. 14 Oct, 2014 1 commit
    • Robert Lyon's avatar
      Making sure core message notifications are correct on upgrade · 47ee961e
      Robert Lyon authored
      
      
      Bug 1380200 - make sure main two do not have 'none' option
      Bug 1380829 - make sure the previous default email method is respected
      
      On upgrade from 1.9 the default core notifications 'System message'
      and 'Message from other users' can be set to 'none' - which is not
      allowed.
      
      This patch will fix that problem by making sure the default core
      notifications are set to email and that any users are also updated to
      beusing the newly set default method.
      
      Also deals with setting the default email method correctly - the prev
      change to notifications didn't set the default email method with the
      correct currently being used method.
      
      Change-Id: I98dcc8374876e20cb5c2952121b69dab99c7cf19
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      47ee961e
  13. 23 Sep, 2014 1 commit
  14. 22 Sep, 2014 1 commit
  15. 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
  16. 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
  17. 15 Sep, 2014 1 commit
    • Aaron Wells's avatar
      Fixing cli install / upgrade regression (Bug #1367998) · 5d1ea9b3
      Aaron Wells authored and Robert Lyon's avatar Robert Lyon committed
      When you request that check_upgrades() checks for upgrades in all
      components, the return data now includes a false component called
      "settings". I've moved "disablelogin", "newinstallcount" and "toupgradecount" into that settings component.
      
      Change-Id: I57e26e0e05848da607b8a44089c92547ebda078b
      5d1ea9b3
  18. 24 Aug, 2014 1 commit
  19. 24 Jun, 2014 1 commit
  20. 19 Jun, 2014 1 commit
  21. 05 Jun, 2014 1 commit
  22. 23 May, 2014 1 commit
  23. 09 May, 2014 1 commit
    • Yuliya Bozhko's avatar
      Some artefact refactoring (Bug #1298646) · 3ba72d71
      Yuliya Bozhko authored and Robert Lyon's avatar Robert Lyon committed
      
      
      Fixes in this patch:
      
      - Moved artefact.php to artefacts directory to separate it from pages.
      - Fixed reference to a wrong 'artefactonlyviewableinview' string.
      - Removed add_to_render_path() and its calls which have no purpose at all.
      - Removed 'artefact_parent_cache' table.
      - Removed cron jobs related to 'artefact_parent_cache' from DB.
      - Added 'path' column in 'artefact' table to easier calculate hierarchy.
      - Added ArtefactTest.php for artefacts unit tests
      
      Change-Id: Ia14cd85b94c32a950354446ee3565bd2964c625c
      Signed-off-by: default avatarYuliya Bozhko <yuliya.bozhko@totaralms.com>
      3ba72d71
  24. 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
  25. 06 Apr, 2014 1 commit
  26. 02 Apr, 2014 1 commit
  27. 30 Mar, 2014 1 commit
    • Aaron Wells's avatar
      Renaming general pages to static pages · d4c63e88
      Aaron Wells authored and Robert Lyon's avatar Robert Lyon committed
      Bug1282219: See the lengthy discussion on the bug tracker. No perfect name
      for these items has arisen yet, but I think "static pages" is the best
      so far because:
      
      1. It means they're obviously not the same type of thing as the Pages in your
      portfolio, because those are dynamic.
      
      2. It's more self-evident. If I were brand new to Mahara and were
      trying to figure out how to change the "Privacy Policy" page, "Static pages"
      is probably what I would think to click on.
      
      Change-Id: I7dd4e3fe6e86fd35dce973afb78b3e56049aab69
      d4c63e88
  28. 26 Mar, 2014 1 commit
    • Tobias Zeuch's avatar
      New watchlistnotification Plugin (Bug 1041228) · 6fe99d5f
      Tobias Zeuch authored and Robert Lyon's avatar Robert Lyon committed
      
      
      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
  29. 23 Feb, 2014 1 commit
  30. 24 Jan, 2014 1 commit
    • Robert Lyon's avatar
      Allow site_content to be institution specific (bug #1254299) · d268d11b
      Robert Lyon authored
      
      
      Changes include:
      - added an institution column to the site_content table
      - added an 'Edit site pages' page under Admin -> Institutions
      that is accessibe by institution admins
      - added an 'institution' option to the edit site pages form - this is
      a hidden field if user can edit only one institution.
      
      On upgrade it updates the site_content table to give current data the
      institution on 'mahara' (incl. local site pages) and for each
      institution it replicates the data already in the db for the default site (excl.
      local site pages) so that every site has their own versions, which can
      be adjusted as one sees fit.
      
      On creation of new institution it creates the rows in site_content
      table but with the default strings (like what you see when you first
      install a mahara) but sets the sitepages column in institution table
      to default (mahara). On deletion of institution it removes the rows in
      site_content.
      
      A user on login sees the institution site page based on what
      institution theme they see.
      
      On logout the 'lastinstitution' cookie is set allowing for them to see
      institution specific site pages.
      
      The 'No institution' (mahara) site pages can only be edited through
      Configure site -> Edit site pages.
      
      Also allow for an institution site page to be viewed if 'institution'
      variable is passed to it eg terms.php?institution=testing allowing for
      another way to access info when logged out.
      
      Change-Id: I2ed30b63c15bf676d83eb2231f48c4ca23ce8b53
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      d268d11b
  31. 06 Jan, 2014 1 commit
    • Mike Kelly's avatar
      Restructure usr_custom_layout table to take groups into account · 2214b02a
      Mike Kelly authored and Robert Lyon's avatar Robert Lyon committed
      
      
      Bug #1266317
      
      Group pages, site and institution pages were set as having usr = 0 in
      usr_custom_layout because the view owner is null.
      
      Fix by adding group column to table, foreign keyed to group table.
      
      usr column and group column have to be changed to allow null values, and
      to have null as default values.
      
      When saving a custom layout, check context, then set usr and group
      values accordingly. 
      e.g. 
      usr = 5, group = null 
      usr = null, group = 321
      In the case of site and institution pages:
      usr = null, group = null
      
      Change-Id: Id42ebcc543d29ee2455aef73227b57c569171385
      Signed-off-by: default avatarMike Kelly <m.f.kelly@arts.ac.uk>
      2214b02a
  32. 12 Nov, 2013 1 commit
  33. 14 Oct, 2013 1 commit
  34. 25 Sep, 2013 1 commit
  35. 23 Sep, 2013 1 commit
  36. 19 Sep, 2013 1 commit
  37. 22 Aug, 2013 1 commit
  38. 21 Aug, 2013 1 commit
  39. 20 Aug, 2013 1 commit
  40. 19 Jul, 2013 1 commit