1. 15 Jun, 2015 4 commits
  2. 14 Apr, 2015 1 commit
  3. 13 Apr, 2015 1 commit
  4. 17 Mar, 2015 1 commit
  5. 15 Feb, 2015 1 commit
  6. 16 Nov, 2014 1 commit
  7. 12 Oct, 2014 1 commit
  8. 16 Jun, 2014 1 commit
  9. 04 Jun, 2014 1 commit
  10. 02 May, 2014 1 commit
  11. 14 Apr, 2014 1 commit
  12. 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
  13. 25 Mar, 2014 1 commit
  14. 23 Feb, 2014 1 commit
  15. 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
  16. 16 Jan, 2014 1 commit
  17. 14 Jan, 2014 1 commit
  18. 08 Jan, 2014 1 commit
    • Aaron Wells's avatar
      Introducing the institution_config table · 5be3b920
      Aaron Wells authored
      Bug 1264429: This patch creates the table, refactors the get_institution_config() method,
      the Institution class, and the institution editing page, to use the new table.
      
      Henceforth columns should only be added to the main "institution" table if they represent
      a required setting (like name and displayname), or they need to be accessed frequently by
      direct SQL queries.
      
      Change-Id: I4564240d2c55ec2b6ec90868290a61cf4321460a
      5be3b920
  19. 17 Nov, 2013 2 commits
  20. 13 Nov, 2013 1 commit
  21. 11 Nov, 2013 1 commit
  22. 21 Oct, 2013 1 commit
  23. 14 Oct, 2013 1 commit
  24. 19 Sep, 2013 1 commit
  25. 21 Aug, 2013 1 commit
  26. 12 Jul, 2013 1 commit
    • Robert Lyon's avatar
      Drop-down navigation overridden at institutional level (Bug #1194672) · cd08104c
      Robert Lyon authored
      
      
      Create the ability for Institutions to override the site default for
      displaying drop-down navigation instead of tabs for main menu.
      
      Can now: Set drop-down navigation option on Administer institutions
      screen /admin/users/institutions.php
      
      Users who are in more than one institution will have drop-down setting
      of the institution whose theme they are using as their theme.
      
      If $cfg->sitethemeprefs = true, where a user can pick any theme then
      for those themes associated with an institution they will use the
      institution's setting otherwise they will use the site's setting for
      drop-down navigation.
      
      Can not do: Have user make their own choice for whether they see drop
      down or not for any particular theme
      
      Change-Id: I580953c62b35cbc8169d47781c8bf88cc94d9fe8
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      cd08104c
  27. 15 Feb, 2013 1 commit
  28. 17 Jan, 2013 1 commit
  29. 03 Jan, 2013 1 commit
  30. 08 Aug, 2012 1 commit
  31. 06 Jul, 2012 1 commit
  32. 31 May, 2012 1 commit
    • Richard Mansfield's avatar
      Add support in User for theme preference · c1fda6fe
      Richard Mansfield authored
      
      
      Part of bug #793308
      
      If a user has the 'theme' property set in their account preferences,
      this is used instead of the site or institution's theme.
      
      The LiveUser::reset_institutions() function, which recalculates the
      institution theme, is now called in place of LiveUser::update_theme()
      whenever a user's institutions have changed.  reset_institutions() now
      calls update_theme() if the user is a LiveUser.
      
      Change-Id: I75b36da85a5aa249c3098078b8588b8a20ac9b48
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
      c1fda6fe
  33. 30 May, 2012 1 commit
  34. 02 Mar, 2012 1 commit
  35. 17 Jan, 2012 1 commit
    • Richard Mansfield's avatar
      Check for authinstances in use when deleting institutions (bug #917873) · d1310840
      Richard Mansfield authored
      
      
      When you delete an institution, and one of the institution's
      authinstances is still in use by some users, you get an sql error and
      a nonrecoverable error screen. (This can only happen when the users
      still using the authinstance are not institution members, because
      there is already a check to stop deletion of institutions with
      members).
      
      This patch allows the institution to be deleted anyway, reassigning
      the offending users to a 'default' authinstance.  If we can't find a
      sensible default authinstance, it will at least display a more helpful
      error message.
      
      Also, when attempting to delete an institution with members, set an
      error on the form rather than throwing a ConfigException.
      
      Change-Id: I9c85a3c8c80411e3cf526767b9142efb12907e5c
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
      d1310840
  36. 20 Dec, 2011 1 commit