mahara-contributors team mailing list archive

[Howard Miller <1185297@xxxxxxxxxxxxxxxxxx>]

I think the description in that file is probably fair. I suspect the use
case is where all your users authenticate against the same source. So -
typically - one Mahara, multiple Moodle's, direct login to Mahara, all
of which are authenticating against a common LDAP server.

Essentially, I suppose it would be "Permits multiple/departmental
Moodles with a single Mahara all authenticating against a common
authentication source (e.g. ldap) where unique usernames are
guaranteed".

There's no nice way to describe it but you know it when you need it ;-)

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

Title:
  Document more $cfg options

Status in Mahara ePortfolio:
  Triaged

Bug description:
  I think it would be a great idea if we went through the code, found as
  many of the config options as we can (by searching for $CFG and
  get_config()), and made sure they were properly documented in one of
  three ways:

  1. If it's a setting that should be hard-coded and most users will
  want/need to set it, put it in config-dist.php

  2. If it's a setting that should be hard-coded but is experimental,
  advanced, or less likely to be used, put it in lib/config-defaults.php

  3. Or give it a UI front-end setting on the Admin pages. But keep in
  mind possible security implications -- anything settable by the UI can
  be abused by XSS, so for instance filesystem paths should not be set
  in the UI because that makes a handy escalation from XSS to
  filesystem.

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