mahara-contributors team mailing list archive

[Hugh Davenport <780177@xxxxxxxxxxxxxxxxxx>]

I think this may be related to the error I found in bug #778272
https://bugs.launchpad.net/mahara/+bug/778272

Basically if an error was displayed to the screen before wwwroot was loaded from the database it developed errors further on.
I didn't test what the effect of this was postinstall, but definitely a problem during install (as most users won't know the default admin password)

Myself I would say that we should make wwwroot compulsory, or just cope
with the working it out each time.

This is because it is a hard task for users to play about with databases just to change the setting,
and there is a possible bug with it being there (not seen much though)

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