would probably be the best, otherwise we may run into issues later down the track when users try and follow old documentation that says change it in database, etc.
Cheers, Hugh -- You received this bug notification because you are a member of Mahara Committers, 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)? _______________________________________________ Mailing list: https://launchpad.net/~mahara-core Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-core More help : https://help.launchpad.net/ListHelp
