CiviCRM Community Forums (archive)

I would like to disable mail on a staging sites in the civicrm.settings.php file instead of in the database so that when the database is cloned from live -> staging, it's not left for someone to remember to reset that.  Is that possible?

I found a reference to the fact that the in versions > that 4.3 all values stored in the domain table can be set in the civicrm.settings.php.  I've also found where the settings are referenced in the Admin UI, https://github.com/civicrm/civicrm-core/blob/master/CRM/Admin/Form/Setting/Smtp.php#L49 and where that's stored in the mailing_backend settings in the civicrm_settings table.

What I can't figure out is how/where values from the domain table are being overridden by the civicrm.settings.php file and if it's possible to do that for the civicrm_settings table values. 

If it's not possible, I was thinking about adding a settings to determine the live vs. staging environments in the CiviCRM Cron module and updating the mailing_backend value before running CiviCRM's cron from Drupal's cron.  Not ideal, but it would achieve the goal of not accidentally emailing thousands of users.

Thanks.  That was REALLY easy.  Wrapping settings in civicrm.settings.php with environment check for Pantheon users...

if ( $pantheon_conf['pantheon_environment'] == 'dev' || $pantheon_conf['pantheon_environment'] == 'test' ){
      /**
      * This setting logs all emails to a file. Useful for debugging any mail (or civimail) issues.
      * This will not send any email, so ensure this is commented out in production
      */
     define( 'CIVICRM_MAIL_LOG', '/srv/bindings/' . $pantheon_conf['pantheon_binding'] . '/code/sites/default/files/civicrm/templates_c//mail.log' );
    }
https://drupal.org/node/2018769