mahara-contributors team mailing list archive

[Richard Mansfield <780177@xxxxxxxxxxxxxxxxxx>]

Yep, personally I don't think having it in the db is a big deal, but I'm
not too fussed about making it compulsory in config.php either.

I should say though, we currently get very very few people who change
sites and then complain on the forums about their wwwroot being broken.
But way back before Nigel added that automatic generation, we got lots
of people, mostly on shared hosts, who wrote to the forums because they
couldn't work out what their wwwroot was.

-- 
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)?