mahara-contributors team mailing list archive

[Ruslan Kabalin <738267@xxxxxxxxxxxxxxxxxx>]

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 why I think so. Basically we have three types of mahara users (or rather owners):
    * new ones who do not care where email is configured - in DB or in config
    * old users who already have their settings in config.php
    * old and new users that for some reason want to control these settings from config file (e.g. multiple instance deployment with config-managed configuration)

In the case of new users, given that we do not force them to configure
email settings (including no-reply address) in the config file (they are
commented out by default), it will be easier to persuade them to fill in
relevant settings fields after installation (add additional after-
install screen asking to set up email), so email configuring bit can be
changed accordingly in installation docs and these users will never need
to care about adding email setting to config file (unless they need that
for specific reason).

Users who already have their settings in the config file should be
informed that now it is possible to configure the same using the
interface, but to do that, email configuration should be removed from
config file (they may see greyed out filled-in settings in configuration
interface with explanation that they are imported from config file, but
you can't change them in the interface until they exist in the config
file).

Those who want to maintain the settings using the config file for some
reason, may continue doing so, config setting will always win and
rewrite what is stored in the database, configuring the same using the
interface will not be possible.

-- 
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
  table

Status in Mahara ePortfolio:
  Triaged

Bug description:
  I am using Mahara 1.3.3 clean install on shared hosting with
  inmotionhosting.  Everything works, but my emails sent by mahara are
  getting blocked.  I had the same problem with my moodle installation,
  but was able to configure it with SMTP email and a defined, working
  noreply address. However, this is not working with mahara.

  I have defined the cfg->noreplyaddress directive and ensured it's
  pointing to the correct address.  However, in the database config
  file, it wasn't picked up, instead pointing to
  noreply@xxxxxxxxxxxxxxxxxxxx (I use subdomains to separate the various
  applications on the server) which was the default probably put in
  before I set it in the config file myself.  So I changed the config
  file back to match what's in the database, again checking all the
  credentials, authentication, and that that email address can
  send/receive mail.

  So I created several dummy accounts with any other email address I
  have, and it works on the user creation on roaming over via mnet and I
  get the email with the correct noreply setting.

  The database didn't pick up a noreplyaddress change in the config, and
  instead kept the original value.  Once I made the database and the
  config file match, all was ok.  But I shouldn't have to have gone
  digging into the database once fixing the config file-- so that's a
  bug.

  Forum post with full details:
  http://mahara.org/interaction/forum/topic.php?id=3110#post13442