[Mahara-contributors] [Bug 738267] Re: noreplyaddress config directive not picked up into database config table

2011-06-13 Thread François Marier
** Changed in: mahara Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/738267 Title: noreplyaddress config directive not picked up into database

[Mahara-contributors] [Bug 738267] Re: noreplyaddress config directive not picked up into database config table

2011-04-28 Thread Hugh Davenport
** Changed in: mahara Status: Triaged = In Progress -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/738267 Title: noreplyaddress config directive not picked up into database config

[Mahara-contributors] [Bug 738267] Re: noreplyaddress config directive not picked up into database config table

2011-04-28 Thread Hugh Davenport
** Changed in: mahara Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/738267 Title: noreplyaddress config directive not picked up into database

[Mahara-contributors] [Bug 738267] Re: noreplyaddress config directive not picked up into database config table

2011-03-21 Thread Ruslan Kabalin
IMHO it should be possible to set these settings from the config file and config file should have precedence over DB settings. I assume here that DB settings will have configuration interface in the site options (like we discussed concerning email settings, see bug #670683). I will try to explain

[Mahara-contributors] [Bug 738267] Re: noreplyaddress config directive not picked up into database config table

2011-03-21 Thread François Marier
You're making a good point about settings migrating from config.php (where they typically tend to start their life) to site options. I like your idea of graying them out to provide a visual clue that the DB setting will be overriden by config.php. In order words, when an option can be set both in

[Mahara-contributors] [Bug 738267] Re: noreplyaddress config directive not picked up into database config table

2011-03-21 Thread Richard Mansfield
I believe the config.php override and greying out was already done some time ago by Lorena in bug #548084, though there's a bit of duplication in that commit that could probably be tidied up. -- You received this bug notification because you are a member of Mahara Contributors, which is

[Mahara-contributors] [Bug 738267] Re: noreplyaddress config directive not picked up into database config table

2011-03-21 Thread Richard Mansfield
Er, commit a6f274234ca8466baa715b559a7c75475664467d I mean. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. https://bugs.launchpad.net/bugs/738267 Title: noreplyaddress config directive not picked up into database config

[Mahara-contributors] [Bug 738267] Re: noreplyaddress config directive not picked up into database config table

2011-03-20 Thread François Marier
I guess we need to decide which of these have precedence when they're not the same: 1- the address in config.php 2- the address in the database Or perhaps we should remove one of them (probably the config file one) and only have a single place where this can be set. Mahara could issue a warning