Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update SpeakerMailer for engine-style email configuration #86

Open
reidab opened this issue Apr 29, 2014 · 2 comments
Open

Update SpeakerMailer for engine-style email configuration #86

reidab opened this issue Apr 29, 2014 · 2 comments
Labels

Comments

@reidab
Copy link
Member

reidab commented Apr 29, 2014

Currently, the OCW mailer makes assumptions about what's going to be configured that don't match well with what actually gets configured by the host app, especially in Speaker#mailer.configured?

@reidab reidab added the bug label Apr 29, 2014
@reidab
Copy link
Member Author

reidab commented Nov 15, 2014

A workaround:

  1. Configure ActionMailer in your config/environments/*.rb files, per http://guides.rubyonrails.org/action_mailer_basics.html#action-mailer-configuration
  2. Edit config/initializers/01_open_conference_ware.rb to include the config that OCW expects to see:
# Set the default address from which to send outgoing mail
config.default_from_address = "you@yourdomain.org"

# Set an address to BCC on all outbound communication (optional)
config.default_bcc_address = "you@yourdomain.org"

# Fulfill the expectations of SpeakerMailer.configured?
config.email = {
  "action_mailer" = {"enabled" => true}
  "default_from_address" = config.default_from_address
}

@kuwaharg
Copy link

Correction on the config.email setting in the 01_open_conference_ware.rb file. It should be:

# Fulfill the expectations of SpeakerMailer.configured?
config.email = {
  "action_mailer" => {"enabled" => true},
  "default_from_address" => config.default_from_address
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants