mahara-contributors team mailing list archive

[Richard Mansfield <780177@xxxxxxxxxxxxxxxxxx>]

Hugh, config.php is normally in the document root, which shouldn't be
writable by the webserver.

I don't think anyone's claiming cron needs wwwroot to be in the db,
though I noticed that comment in init.php about wwwroot (either in db or
config file) being needed by cron.  That comment's true but out of date
though, nearly everything needs wwwroot these days, though nothing cares
whether it's in config.php or in the db.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/780177

Title:
  Storing wwwroot in the database: possible implications

Status in Mahara ePortfolio:
  New

Bug description:
  Basically this issue comes from bug #684190. Are there any
  implications of impossibility to change wwwroot once it is stored in
  the database? In the hostname change wiki manual we suggest people to
  clear this variable manually in the database which is somewhat
  complicated. In addition, protocol changes (upgrade to using https or
  downgrade to http) might not be considered as hostname change by the
  user, so database config variable will be left in inconsistent state.

  Do we need to keep it in the database for specific reason (e.g.
  comment says it used by cron, I did not quickly find where exactly)?