mahara-contributors team mailing list archive

[Kristina Hoeppner <1250302@xxxxxxxxxxxxxxxxxx>]

Site admins are often not members of institutions and if skins are
turned on in general, i.e. "No institution", they'll be able to use
them. However, if site admins are members of institutions, the
institution settings should be respected for their personal pages. Site
pages could have skins, but then they aren't editing their personal
pages, but a general page that doesn't bear their name.

Your last idea sounds good to me.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1250302

Title:
  A site admin who belongs to an institution with skins disabled, gets
  an error trying to edit site skins

Status in Mahara ePortfolio:
  New

Bug description:
  To replicate:

  1. Set $cfg->skins = true; in your config.php to enable skins
  2. Disable skins for at least one institution, by using the institution configuration screen
  3. Log in as a site admin who belongs to that institution
  4. Navigate to "Configure site -> Skins".
  5. Click on "Create skin"

  Expected result: You should be able to create a skin
  Actual result: You see a "feature not available" exception

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1250302/+subscriptions