mahara-contributors team mailing list archive

[Aaron Wells <1237013@xxxxxxxxxxxxxxxxxx>]

On the other hand, the current system could be confusing too. Consider:
the site is set to a theme where the Skins CSS stylesheet has been
blanked. Users create pages, and pick skins for them, but this has no
effect on the page! That's pretty confusing as well.

So I don't know, maybe it is a good idea. Perhaps with some logic so
that under certain circumstances you can still see the Skins pages, but
with a message that says "Skins are disabled because of the theme." In
order for this to not further confuse users, you'd have to limit it to
circumstances where the user is actually able to change the theme. For
instance, for a normal user, if it's the Page theme or User theme that
has disabled Skins. For an institutional admin, if it's the Institution
theme that has disabled Skins. For a site admin, when any theme has
disabled Skins.

-- 
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/1237013

Title:
  Allow theme to turn off skins

Status in Mahara ePortfolio:
  New

Bug description:
  Say you made a special theme, like a moderator one, where the set of
  things one can access is a subset of all things one can access (eg
  less artefact options) and you thought hey I don't want this theme to
  have access to making/editing/displaying skins.

  So you'd want the theme to be able to turn off skins.

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