mahara-contributors team mailing list archive

[Mahara Bot <1185297@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/2633
Committed: http://gitorious.org/mahara/mahara/commit/a5af1aa2665962edc6070842305504b72a340ac3
Submitter: Aaron Wells (aaronw@xxxxxxxxxxxxxxx)
Branch:    master

commit a5af1aa2665962edc6070842305504b72a340ac3
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Tue Oct 22 16:50:17 2013 +1300

Document the $cfg->cacertinfo option

Bug1185297

Change-Id: I30ca497cbd2f37a63bcce2b7346a737f75612b94

-- 
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:
  In Progress

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