Given that we are reverting it for now, we probably should make db variable used for cron only and update it automatically it if user has changed the host address.
-- 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: In Progress 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)? To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/780177/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
