mahara-contributors team mailing list archive

[Aaron Wells <1185297@xxxxxxxxxxxxxxxxxx>]

We now do this as standard practice with new options, and I'm not aware
of any old undocumented ones lying around anymore. If there are any
remaining undocumented cfg options, feel free to reopen this bug for
them if you want, or file a new bug.

** Changed in: mahara
       Status: In Progress => Fix Committed

** Changed in: mahara
    Milestone: 1.10.0 => None

-- 
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:
  [Ongoing] Document more $cfg options

Status in Mahara ePortfolio:
  Fix Committed

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