Class: Merb::MailController

Inherits:
AbstractController
  • Object
show all
Defined in:
lib/merb-mailer/mail_controller.rb

Overview

Sending mail from a controller involves three steps:

  • Set mail settings in merb_init.rb (Not shown here…see the Mailer docs).

  • Create a MailController subclass with actions and templates.

  • Call the MailController from another Controller via the send_mail method.

First, create a file in app/mailers that subclasses Merb::MailController. The actions in this controller will do nothing but render mail.

# app/mailers/article_mailer.rb
class ArticleMailer < Merb::MailController

  def notify
    @user = params[:user]
    render_mail
  end

end

You also can access the params hash for values passed with the Controller.send_mail method. See also the documentation for render_mail to see all the ways it can be called.

Create a template in a subdirectory of app/mailers/views that corresponds to the controller and action name. Put plain text and ERB tags here:

# app/mailers/views/article_mailer/notify.text.erb
Hey, <%= @user.name %>,

We're running a sale on dog bones!

Finally, call the Controller.send_mail method from a standard Merb controller.

class Articles < Application

  def index
    @user = User.find_by_name('louie')

    send_mail(ArticleMailer, :notify, {
      :from => "[email protected]",
      :to => "[email protected]",
      :subject => "Sale on Dog Bones!"
    }, { :user => @user })
    render
  end

end

Note: If you don’t pass a fourth argument to Controller.send_mail, the controller’s params will be sent to the MailController subclass as params. However, you can explicitly send a hash of objects that will populate the params hash instead. In either case, you must set instance variables in the MailController’s actions if you want to use them in the MailController’s views.

The MailController class is very powerful. You can:

  • Send multipart email with a single call to render_mail.

  • Attach files.

  • Render layouts and other templates.

  • Use any template engine supported by Merb.

Instance Attribute Summary collapse

Class Method Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(params = {}, controller = nil) ⇒ MailController

Parameters

params<Hash>

Configuration parameters for the MailController.

controller<Merb::Controller>

The base controller.



115
116
117
118
119
 
# File 'lib/merb-mailer/mail_controller.rb', line 115

def initialize(params = {}, controller = nil)
  @params = params
  @base_controller = controller
  super
end

Instance Attribute Details

#base_controller ⇒ Object (readonly)

Returns the value of attribute base_controller.



72
73
74
 
# File 'lib/merb-mailer/mail_controller.rb', line 72

def base_controller
  @base_controller
end

#mail ⇒ Object

Returns the value of attribute mail.



71
72
73
 
# File 'lib/merb-mailer/mail_controller.rb', line 71

def mail
  @mail
end

#mailer ⇒ Object

Returns the value of attribute mailer.



71
72
73
 
# File 'lib/merb-mailer/mail_controller.rb', line 71

def mailer
  @mailer
end

#params ⇒ Object

Returns the value of attribute params.



71
72
73
 
# File 'lib/merb-mailer/mail_controller.rb', line 71

def params
  @params
end

Class Method Details

.dispatch_and_deliver(method, mail_params, send_params = {}) ⇒ Object

A convenience method that creates a blank copy of the MailController and runs dispatch_and_deliver on it.

Parameters

method<~to_s>

The method name to dispatch to.

mail_params<Hash>

Parameters to send to MailFactory.

send_params<Hash>

Configuration parameters for the MailController.



337
338
339
 
# File 'lib/merb-mailer/mail_controller.rb', line 337

def self.dispatch_and_deliver(method, mail_params, send_params = {})
  new(send_params).dispatch_and_deliver method, mail_params
end

.inherited(klass) ⇒ Object

Sets the template root to the default mailer view directory.

Parameters

klass<Class>

The Merb::MailController inheriting from the base class.



130
131
132
133
 
# File 'lib/merb-mailer/mail_controller.rb', line 130

def self.inherited(klass)
  super
  klass._template_root = Merb.dir_for(:mailer) / "views" unless self._template_root
end

.subclasses_list ⇒ Object

Returns

Array

Classes that inherit from Merb::MailController.



79
 
# File 'lib/merb-mailer/mail_controller.rb', line 79

def self.subclasses_list() _subclasses end

Instance Method Details

#_absolute_template_location(template, type) ⇒ Object

The location to look for a template and mime-type. This is overridden from AbstractController, which defines a version of this that does not involve mime-types.

Parameters

template<String>

The absolute path to a template - without mime and template extension. The mime-type extension is optional - it will be appended from the current content type if it hasn’t been added already.

type<~to_s>

The mime-type of the template that will be rendered. Defaults to nil.



108
109
110
 
# File 'lib/merb-mailer/mail_controller.rb', line 108

def _absolute_template_location(template, type)
  template.match(/\.#{type.to_s.escape_regexp}$/) ? template : "#{template}.#{type}"
end

#_template_location(action, type = nil, controller = controller_name) ⇒ Object

Parameters

action<~to_s>

The name of the action that will be rendered.

type<~to_s>

The mime-type of the template that will be rendered. Defaults to nil.

controller<~to_s>

The name of the controller that will be rendered. Defaults to controller_name.

Returns

String

The template location, i.e. “:controller/:action.:type”.



91
92
93
 
# File 'lib/merb-mailer/mail_controller.rb', line 91

def _template_location(action, type = nil, controller = controller_name)
  "#{controller}/#{action}.#{type}"
end

#absolute_url(name, *args) ⇒ Object

Mimic the behavior of absolute_url in AbstractController but use @base_controller.request



264
265
266
267
 
# File 'lib/merb-mailer/mail_controller.rb', line 264

def absolute_url(name, *args)
  return base_controller.absolute_url(name, *args) if base_controller
  super
end

#attach(file_or_files, filename = file_or_files.is_a?(File) ? File.basename(file_or_files.path) : nil, type = nil, headers = nil) ⇒ Object

Attaches a file or multiple files to an email. You call this from a method in your MailController (including a before filter).

Parameters

file_or_files<File, Array>

File(s) to attach.

filename<String>
type<~to_s>

The attachment MIME type. If left out, it will be determined from file_or_files.

headers<String, Array>

Additional attachment headers.

Examples

attach File.open("foo")
attach [File.open("foo"), File.open("bar")]

If you are passing an array of files, you should use an array of the allowed parameters:

 attach [[File.open("foo"), "bar", "text/html"], [File.open("baz"),
   "bat", "text/css"]

which would attach two files ("foo" and "baz" in the filesystem) as

“bar” and “bat” respectively. It would also set the mime-type as “text/html” and “text/css” respectively.



293
294
295
296
 
# File 'lib/merb-mailer/mail_controller.rb', line 293

def attach( file_or_files, filename = file_or_files.is_a?(File) ? File.basename(file_or_files.path) : nil,
  type = nil, headers = nil)
  @mailer.attach(file_or_files, filename, type, headers)
end

#dispatch_and_deliver(method, mail_params) ⇒ Object

Parameters

method<~to_s>

The method name to dispatch to.

mail_params<Hash>

Parameters to send to MailFactory (see below).

Options (mail_params)

MailFactory recognizes the following parameters:

  • :to

  • :from

  • :replyto

  • :subject

  • :body

  • :cc

Other parameters passed in will be interpreted as email headers, with underscores converted to dashes.



313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
 
# File 'lib/merb-mailer/mail_controller.rb', line 313

def dispatch_and_deliver(method, mail_params)
  @mailer         = self.class._mailer_klass.new(mail_params)
  @mail           = @mailer.mail
  @method         = method

  # dispatch and render use params[:action], so set it
  self.action_name = method

  body             = _dispatch method
  if !@mail.html.blank? || !@mail.text.blank?
    @mailer.deliver!
    Merb.logger.info "#{method} sent to #{@mail.to} about #{@mail.subject}"
  else
    Merb.logger.info "#{method} was not sent because nothing was rendered for it"
  end
end

#filters_halted ⇒ Object

Override filters halted to return nothing.



136
137
 
# File 'lib/merb-mailer/mail_controller.rb', line 136

def filters_halted
end

#render_mail(options = @method) ⇒ Object

Allows you to render various types of things into the text and HTML parts of an email If you include just text, the email will be sent as plain-text. If you include HTML, the email will be sent as a multi-part email.

Parameters

options<~to_s, Hash>

Options for rendering the email or an action name. See examples below for usage.

Examples

There are a lot of ways to use render_mail, but it works similarly to the default Merb render method.

First of all, you’ll need to store email files in your app/mailers/views directory. They should be under a directory that matches the name of your mailer (e.g. TestMailer’s views would be stored under test_mailer).

The files themselves should be named action_name.mime_type.extension. For example, an erb template that should be the HTML part of the email, and rendered from the “foo” action would be named foo.html.erb.

The only mime-types currently supported are “html” and “text”, which correspond to text/html and text/plain respectively. All template systems supported by your app are available to MailController, and the extensions are the same as they are throughout the rest of Merb.

render_mail can take any of the following option patterns:

render_mail

will attempt to render the current action. If the current action is “foo”, this is identical to render_mail :foo.

render_mail :foo

checks for foo.html.ext and foo.text.ext and applies them as appropriate.

render_mail :action => {:html => :foo, :text => :bar}

checks for foo.html.ext and bar.text.ext in the view directory of the current controller and adds them to the mail object if found

render_mail :template => {:html => "foo/bar", :text => "foo/baz"}

checks for bar.html.ext and baz.text.ext in the foo directory and adds them to the mail object if found.

render_mail :html => :foo, :text => :bar

the same as render_mail :action => {html => :foo, :text => :bar }

render_mail :html => "FOO", :text => "BAR"

adds the text “FOO” as the html part of the email and the text “BAR” as the text part of the email. The difference between the last two examples is that symbols represent actions to render, while string represent the literal text to render. Note that you can use regular render methods instead of literal strings here, like:

render_mail :html => render(:action => :foo)

but you’re probably better off just using render_mail :action at that point.

You can also mix and match:

render_mail :action => {:html => :foo}, :text => "BAR"

which would be identical to:

render_mail :html => :foo, :text => "BAR"



212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
 
# File 'lib/merb-mailer/mail_controller.rb', line 212

def render_mail(options = @method)
  @_missing_templates = false # used to make sure that at least one template was found
  # If the options are not a hash, normalize to an action hash
  options = {:action => {:html => options, :text => options}} if !options.is_a?(Hash)

  # Take care of the options
  opts_hash = {}
  opts = options.dup
  actions = opts.delete(:action) if opts[:action].is_a?(Hash)
  templates = opts.delete(:template) if opts[:template].is_a?(Hash)

  # Prepare the options hash for each format
  # We need to delete anything relating to the other format here
  # before we try to render the template.
  [:html, :text].each do |fmt|
    opts_hash[fmt] = opts.delete(fmt)
    opts_hash[fmt] ||= actions[fmt] if actions && actions[fmt]
    opts_hash[:template] = templates[fmt] if templates && templates[fmt]
  end

  # Send the result to the mailer
  { :html => "rawhtml=", :text => "text="}.each do |fmt,meth|
    begin
      local_opts = opts.merge(:format => fmt)
      local_opts.merge!(:layout => false) if opts_hash[fmt].is_a?(String)

      clear_content
      value = render opts_hash[fmt], local_opts
      @mail.send(meth,value) unless value.nil? || value.empty?
    rescue Merb::ControllerExceptions::TemplateNotFound => e
      # An error should be logged if no template is found instead of an error raised
      if @_missing_templates
        Merb.logger.error(e.message)
      else
        @_missing_templates = true
      end
    end
  end
  @mail
end

#session ⇒ Object 



121
122
123
 
# File 'lib/merb-mailer/mail_controller.rb', line 121

def session
  self.base_controller.request.session rescue {}
end

#url(name, *args) ⇒ Object Also known as: relative_url

Mimic the behavior of absolute_url in AbstractController but use @base_controller.request



255
256
257
258
 
# File 'lib/merb-mailer/mail_controller.rb', line 255

def url(name, *args)
  return base_controller.url(name, *args) if base_controller
  super
end