radiant-mailer-extension 1.0.4 → 1.0.6

data/README.md

@@ -0,0 +1,240 @@
+# Mailer Extension for Radiant
+
+[![Build Status](https://secure.travis-ci.org/radiant/radiant-mailer-extension.png)](http://travis-ci.org/radiant/radiant-mailer-extension)
+
+The Mailer extension enables form mail on a page.
+
+## Usage
+
+You can define email templates using pages parts (email, and/or email_html).
+You configure the recipients and other Mailer settings in a "mailer" part:
+
+    subject: From the website of Whatever
+    from: noreply@example.com
+    redirect_to: /contact/thank-you
+    recipients:
+      - one@one.com
+      - two@two.com
+
+The following tags are available to help you build the form:
+
+    <r:mailer:form name=""> ... </r:mailer:form>
+    <r:mailer:text name="" />
+    <r:mailer:password name="" />
+    <r:mailer:reset name="" />
+    <r:mailer:checkbox name="" />
+    <r:mailer:radio name="" />
+    <r:mailer:file name="" />
+    <r:mailer:radiogroup name=""> ... </r:mailer:radiogroup>
+    <r:mailer:select name=""> ... </r:mailer:select>
+    <r:mailer:date_select name=""/>
+    <r:mailer:textarea name=""> ... </r:mailer:textarea>
+    <r:mailer:option name="" />
+    <r:mailer:submit name="" />
+    <r:mailer:image name="" />
+    <r:mailer:submit_placeholder />
+
+When processing the form (in email and email_html), the following tags are
+available:
+
+    <r:mailer:get name="" />
+    <r:mailer:get_each name=""> ... </r:mailer:get_each>
+      <r:mailer:index />
+
+Simple example of a form:
+
+    <r:mailer:form>
+     <r:mailer:hidden name="subject" value="Email from my Radiant site!" /> <br/>
+      Name:<br/>
+     <r:mailer:text name="name" /> <br/>
+      Message:<br/>
+     <r:mailer:textarea name="message" /> <br/>
+     <r:mailer:submit name="Send" />
+    </r:mailer:form>
+
+### Required fields
+
+You can specify fields which must be populated or the form will be invalid and will redisplay the page with an error informing the user to populate those fields.
+
+Simple example of a required field:
+
+    <r:mailer:form>
+     ...
+      Name:<br/>
+     <r:mailer:text name="name" required="true"/> <br/>
+     ...
+     <r:mailer:submit name="Send" />
+    </r:mailer:form>
+
+Simple example of a required field with user-defined message:
+
+    <r:mailer:form>
+     ...
+      Name:<br/>
+     <r:mailer:text name="name" required="should not be blank"/> <br/>
+     ...
+     <r:mailer:submit name="Send" />
+    </r:mailer:form>
+
+You can also specify fields which must be validated 'as_email' (i.e. a@b.com).
+
+Simple example of a required field with email address validation:
+
+    <r:mailer:form>
+     ...
+      Reply-To:<br/>
+     <r:mailer:text name="reply_email" required="as_email"/> <br/>
+     ...
+     <r:mailer:submit name="Send" />
+    </r:mailer:form>
+
+You can also specify fields which must be validated as defined regexp (i.e. /^\d{2}\.\d{2}\.\d{4}\$/ for date dd.mm.yyyy).
+
+
+Simple example of a required field with regexp validation:
+
+    <r:mailer:form>
+     ...
+      Birthday:<br/>
+     <r:mailer:text name="birthday" required="/^\d{2}\.\d{2}\.\d{4}\$/"/> <br/>
+     ...
+     <r:mailer:submit name="Send" />
+    </r:mailer:form>
+
+Finally, you can put all field validations in the "mailer" part:
+
+    subject: From the website of Whatever
+    from: noreply@example.com
+    redirect_to: /contact/thank-you
+    recipients:
+      - one@one.com
+    required:
+      name: "true"
+      email: as_email
+      message: "true"
+
+The field names above are "name," "email," and "message." Note the quotation marks around true values. If you do your field validations this way, Mailer will ignore any validations you attempt through your radius tags. This method of validation keeps Mailer from adding hidden inputs to keep track of required fields. See the caveat below.
+
+
+### Spam blocking
+
+#### No Links
+
+You can specify which fields may not contain anything that looks like a link in the "mailer" part. For example:
+
+    subject: From the website of Whatever
+    from: noreply@example.com
+    redirect_to: /contact/thank-you
+    recipients:
+      - one@one.com
+    disallow_links:
+      - comments
+      - questions
+
+The comments and questions fields would throw an error if the user or a spam bot entered the following phrases: "www", "&amp;", "http:", "mailto:", "bcc:", "href", "multipart", "[url", or "Content-Type:".
+
+#### Hidden field must be blank
+
+You can also include one field on your form that must be left blank. If anyone enters something in the field, the field throws an error. The tactic here is to hide the field from human readers, but to leave the field visible to spam bots. Here is how you would edit the "mailer" part to implement this:
+
+    subject: From the website of Whatever
+    from: noreply@example.com
+    redirect_to: /contact/thank-you
+    recipients:
+      - one@one.com
+    leave_blank: your_field_name
+
+"your_field_name" is the name of the field you want to hide. It is up to you to hide the field when you construct your form. I would recommend against using a traditional hidden input field. Use style="display:none" instead.
+
+#### Blocked Words
+
+You can also add specific words to the mail config, which if present in any of the input fields, will throw an error.  This way if you get hit by a barage of say, 'imabot@spammer.net', you just add that term to the block list.  Here is how you would edit the "mailer" part to implement this:
+
+    subject: From the website of Whatever
+    from: noreply@mydomain.com
+    redirect_to: /contact/thank-you
+    max_filesize: 100000
+    recipients:
+      - one@one.com
+      - two@two.com
+    block_words:
+      - spammer
+      - badword
+      - imabot
+
+### File attachments
+
+In many cases it is desirable to limit the maximum size of a file that may be uploaded. This is set as the max_filesize attribute for mailers in the mailer page part. Any file included in the form will have the limit imposed. Following is a simple example mailer part that includes a file size limit of 100,000 bytes:
+
+    subject: From the website of Whatever
+    from: noreply@mydomain.com
+    redirect_to: /contact/thank-you
+    max_filesize: 100000
+    recipients:
+      - one@one.com
+      - two@two.com
+
+The following is a simple form that might be used to submit a file for the above configuration:
+
+    <r:mailer:form name="contact">
+        Type your message: <r:mailer:text name="themessage" /> <br/>
+        Select a file: <r:mailer:file name="thefile" /> <br/>
+        <r:mailer:submit value="submit"/>
+    </r:mailer:form>
+
+If a user does not select a file the other form contents will still be e-mailed. The `<r:mailer:get name="foo" />` (with `<r:mailer:file name="foo" />`) will provide the uploaded file name.
+
+If you are using email or email_html parts then the `<r:mailer:get name="" />` tag can be used to retrieve the name of the uploaded file. If no file was uploaded "" will be returned.
+
+### Submit placeholder
+
+If you wish to show that activity is taking place during submission you may use the `<r:mailer:submit_placeholder />` tag in your form. This will insert a hidden div with the contents of the submit_placeholder page part. The div will be displayed when the user clicks any submit button.
+
+### User-provided Configuration
+
+Sometimes, rather than explicitly configuring the recipients and such in the mailer part, you'd rather have them passed in by the person submitting the form. Mailer supports this by allowing you to specify a form field to pull the value from:
+
+    from_field: my_form_field_that_contains_the_from_email_address
+
+Then you just have to add that field to your mailer form and you're all set.
+
+This is supported for the from (from_field), recipients (recipients_field) and reply_to (reply_to_field) properties.
+
+## Enabling action_mailer
+
+In environment.rb you'll probably need to change:
+
+    config.frameworks -= [ :action_mailer ]
+
+to:
+
+    config.frameworks -= []
+
+## Updating from the older mailer extension
+
+If you get this error "The single-table inheritance mechanism failed to locate the subclass: 'MailerPage'.", run `rake:radiant:extensions:mailer:migrate`. This will change all pages with a MailerPage classname into regular pages. Second, your 'config' page part has to be renamed to 'mailer', and the first two YAML levels should be deleted (see instructions above).
+
+If you are getting a stack level too deep error, it may be caused by using `<r:mailer:get />` in your 'mailer' part. Use the from_field or other options to get to the email adress that was posted (see User-provided configuration).
+
+## Caveats
+
+Relative urls will almost certainly not work if the mailer fails validation. Solution? Only use absolute urls.
+
+Unless you set up the field validations in the "mailer" part, validation will be implemented via easily spoofable HTML attributes. Think of them of more like guidelines in that case.
+
+## Initial History
+
+Created by: M@ McCray - mattmccray.com
+  Version: 0.2.1
+  Contact: mmccray@elucidata.net
+
+Ported to 'mental' by: Sean Cribbs - seancribbs.com
+  Version: 0.1
+  Contact: seancribbs@gmail.com
+
+Seriously restructured by: Nathaniel Talbott - terralien.com
+  Version: 0.2
+  Contact: nathaniel@terralien.com
+  Work sponsored by: Ignite Social Media, http://ignitesocialmedia.com/
+
+## [Contributors](https://github.com/radiant/radiant-mailer-extension/graphs/contributors)

data/Rakefile

@@ -14,6 +14,7 @@ end
 require 'rake'
 require 'rdoc/task'
 require 'rake/testtask'
+require 'bundler/gem_tasks'
 
 rspec_base = File.expand_path(RADIANT_ROOT + '/vendor/plugins/rspec/lib')
 $LOAD_PATH.unshift(rspec_base) if File.exist?(rspec_base)

data/app/models/mail.rb

@@ -1,11 +1,12 @@
 class Mail
-  attr_reader :page, :config, :data, :leave_blank, :disallow_links, :errors
+  attr_reader :page, :config, :data, :leave_blank, :disallow_links, :block_words, :errors
 
   def initialize(page, config, data)
     @page, @config, @data = page, config.with_indifferent_access, data
     @required = required_fields
     @leave_blank = leave_blank_field
     @disallow_links = disallow_link_fields
+    @block_words = block_words
     @errors = {}
   end
 
@@ -74,7 +75,7 @@ class Mail
         end
       end
       
-      if @disallow_links.present?
+      unless @disallow_links.blank?
         pattern = /www|&|http:|mailto:|bcc:|href|cc:|multipart|\[url|Content-Type:/i
         @disallow_links.each do |field|
           if @data[field] =~ pattern
@@ -84,12 +85,24 @@ class Mail
         end
       end 
 
-      if @leave_blank.present?
+      unless @leave_blank.blank?
         unless @data[@leave_blank] == ''
           errors[@leave_blank] = "must be left blank."
           @valid = false
         end
       end
+      
+      unless @block_words.blank?
+        @data.each do |label,value|
+          @block_words.each do |word|
+            if value.include?(word.strip)
+              errors[label.titleize] = "is not valid"
+              @valid = false
+            end
+          end
+        end
+      end
+      
     end
     
     @valid
@@ -199,4 +212,8 @@ The following information was posted:
   def disallow_link_fields
     @config[:disallow_links] if @config.has_key?(:disallow_links)
   end
-end
+  
+  def block_words
+    config[:block_words] if @config.has_key?(:block_words)
+  end
+end

data/lib/mailer_process.rb

@@ -1,7 +1,9 @@
 module MailerProcess
   def self.included(base)
-    base.class_eval { 
-      alias_method_chain :process, :mailer 
+    base.class_eval {
+      unless self.instance_methods(false).include?(:process_without_mailer)
+        alias_method_chain :process, :mailer
+      end
       attr_accessor :last_mail
     }
   end

data/lib/mailer_tags.rb

@@ -308,6 +308,18 @@ module MailerTags
     mail = tag.locals.page.last_mail || tag.globals.page.last_mail
     tag.expand if name && mail.data[name] && (eq.blank? || eq == mail.data[name])
   end
+  
+  desc %{
+    Renders the contained block unless a named datum was submitted via a mailer 
+    form.  Used in the 'email', 'email_html' and 'mailer' parts to generate 
+    the resulting email.
+  }
+  tag 'mailer:unless_value' do |tag|
+    name = tag.attr['name']
+    eq = tag.attr['equals']
+    mail = tag.locals.page.last_mail || tag.globals.page.last_mail
+    tag.expand unless name && mail.data[name] && (eq.blank? || eq == mail.data[name])
+  end
 
   def format_mailer_data(element, name)
     data = element[name]
@@ -370,7 +382,7 @@ module MailerTags
       'width' => nil}.merge(extras)
     result = attrs.sort.collect do |k,v|
       v = (tag.attr[k] || v)
-      if k == 'class' && tag.attr['required'].present?
+      if k == 'class' && ! tag.attr['required'].blank?
         v = [v, 'required', tag.attr['required']].compact.join(' ')
       end
       next if v.blank?

data/lib/radiant-mailer-extension.rb

@@ -1,8 +1,8 @@
 module RadiantMailerExtension
-  VERSION = '1.0.4'
+  VERSION = '1.0.6'
   SUMMARY = %q{Form mailing for Radiant CMS}
   DESCRIPTION = %q{Provides support for email forms and generic mailing functionality.}
   URL = "https://github.com/radiant/radiant-mailer-extension"
-  AUTHORS = ["Nathaniel Talbott", "Sean Cribbs", "Matt McCray", "Jim Gay", "John Muhl", "Benny Degezelle"]
-  EMAIL = ["radiant@radiantcms.org"]
+  AUTHORS = ["Nathaniel Talbott", "Sean Cribbs", "Matt McCray", "Jim Gay", "John Muhl", "Benny Degezelle", "Andrew vonderLuft"]
+  EMAIL = ["radiant@radiantcms.org"]  
 end

data/mailer_extension.rb

@@ -4,6 +4,13 @@ class MailerExtension < Radiant::Extension
   description RadiantMailerExtension::DESCRIPTION
   url RadiantMailerExtension::URL
   
+  # Backward compatibility for routes. 
+  unless defined?(Radiant::Extension.extension_config)
+    define_routes do |map|
+      map.resources :mail, :path_prefix => "/pages/:page_id", :controller => "mail"
+    end
+  end
+  
   def activate
     Page.class_eval do
       include MailerTags

data/spec/ci/before_script

@@ -0,0 +1,28 @@
+cd ~
+git clone git://github.com/radiant/radiant.git
+cd ~/radiant
+if [[ $RADIANT_VERSION != "master" ]]
+then
+  git checkout -b $RADIANT_VERSION $RADIANT_VERSION
+fi
+if [[ $RADIANT_VERSION == "0.9.1" ]]
+then
+  touch Gemfile
+  echo "source :rubygems" >> Gemfile
+fi
+cp -r ~/builds/*/radiant-mailer-extension vendor/extensions/mailer
+gem install bundler --pre
+echo gemspec >> Gemfile
+bundle install
+
+case $DB in
+  "mysql" )
+    mysql -e 'create database radiant_test;'
+    cp spec/ci/database.mysql.yml config/database.yml;;
+  "postgres" )
+    psql -c 'create database radiant_test;' -U postgres
+    cp spec/ci/database.postgresql.yml config/database.yml;;
+esac
+
+bundle exec rake db:migrate
+bundle exec rake db:migrate:extensions

data/spec/ci/script

@@ -0,0 +1,2 @@
+cd ~/radiant
+bundle exec rake spec:extensions EXT=mailer

data/spec/lib/mailer_process_spec.rb

@@ -20,61 +20,70 @@ describe SiteController, "receiving a mailer request", :type => :controller do
   dataset :mailer_page
 
   before :each do
-    Radiant::Cache.clear
+    # Radiant backward compatibility
+    begin
+      Radiant::Cache.clear
+    rescue NameError
+      ResponseCache.instance.clear
+    end
     Radiant::Config['mailer.post_to_page?'] = true
     @page = pages(:mail_form)
     @mail = mock("Mail", :send => false, :data => {}, :errors => {})
-    Page.stub!(:find_by_path).and_return(@page)
+    if defined?(Page.find_by_path)
+      Page.stub!(:find_by_path).and_return(@page)
+    else
+      Page.stub!(:find_by_url).and_return(@page)
+    end
     Mail.stub!(:new).and_return(@mail)
   end
 
   it "should not process a mail form if the request was GET" do
     @page.should_receive(:process_without_mailer).with(request, response)
     Mail.should_not_receive(:new)
-    get :show_page, :url => @page.path
+    get :show_page, :url => @page.url
   end
 
   it "should not process a mail form if mailer.post_to_page? is set to false" do
     Radiant::Config['mailer.post_to_page?'] = false
     @page.should_receive(:process_without_mailer).with(request, response)
     Mail.should_not_receive(:new)
-    post :show_page, :url => @page.path
+    post :show_page, :url => @page.url
   end
 
   it "should not process a mail form unless there are mailer parameters" do
     @page.should_receive(:process_without_mailer).with(request, response)
     Mail.should_not_receive(:new)
-    post :show_page, :url => @page.path
+    post :show_page, :url => @page.url
   end
 
   it "should process a mail form if the request was POST, posting to the page is enabled, and mailer parameters were submitted" do
     Mail.should_receive(:new).and_return(@mail)
     @page.should_receive(:process_without_mailer).with(request, response)
-    post :show_page, :url => @page.path, :mailer => {:foo => 'bar'}
+    post :show_page, :url => @page.url, :mailer => {:foo => 'bar'}
   end
 
   it "should create a Mail object and assign it to the page's last_mail accessor" do
     Mail.should_receive(:new).and_return(@mail)
     @page.should_receive(:last_mail=).with(@mail).at_least(:once)
-    post :show_page, :url => @page.path, :mailer => {:foo => 'bar'}
+    post :show_page, :url => @page.url, :mailer => {:foo => 'bar'}
   end
 
   it "should attempt to send the mail" do
     @mail.should_receive(:send).and_return(false)
-    post :show_page, :url => @page.path, :mailer => {:foo => 'bar'}
+    post :show_page, :url => @page.url, :mailer => {:foo => 'bar'}
   end
 
   it "should clear out the mail data and errors when sending is successful" do
     @mail.should_receive(:send).and_return(true)
     @mail.data.should_receive(:delete_if)
     @mail.errors.should_receive(:delete_if)
-    post :show_page, :url => @page.path, :mailer => {:foo => 'bar'}
+    post :show_page, :url => @page.url, :mailer => {:foo => 'bar'}
   end
   
   it "should redirect to the configured URL when sending is successful" do
     @page.should_receive(:mailer_config_and_page).and_return([{:redirect_to => "/foo/bar"}, @page])
     @mail.should_receive(:send).and_return(true)
-    post :show_page, :url => @page.path, :mailer => {:foo => 'bar'}
+    post :show_page, :url => @page.url, :mailer => {:foo => 'bar'}
     response.redirect_url.should match(%r{/foo/bar})
   end
 end

data/spec/models/mail_spec.rb

@@ -146,7 +146,7 @@ describe Mail do
     @mail.errors['form'].should_not be_blank
   end
 
-  it "should be invalid when the recipients contains invalid email adresses" do
+  it "should be invalid when the recipients contains invalid email addresses" do
     @mail.config[:recipients] = ['sean AT radiant DOT com']
     @mail.should_not be_valid
     @mail.errors['form'].should_not be_blank
@@ -294,7 +294,16 @@ describe Mail do
       @mail.errors['comments'].should_not be_blank
       @mail.errors['comments'].should == 'must not contain the following text: "www", "&", "http:", "mailto:", "bcc:", "href", "multipart", "[url", or "Content-Type:"'
     end
-  end    
+  end   
+  
+  it "should be invalid when a field contains blocked words" do
+    ['spammer','badword','imabot'].each do |message|
+      @mail = Mail.new(@page, {:recipients => ['foo@bar.com'], :from => 'foo@baz.com', :block_words => ['spammer','badword','imabot']}, 'comments' => message)
+      @mail.should_not be_valid
+      @mail.errors['comments'.titleize].should_not be_blank
+      @mail.errors['comments'.titleize].should == 'is not valid'
+    end
+  end   
 
   it "should not send the mail if invalid" do
     @mail.should_receive(:valid?).and_return(false)

data/spec/spec_helper.rb

@@ -12,9 +12,11 @@ end
 require "#{RADIANT_ROOT}/spec/spec_helper"
 
 Dataset::Resolver.default << (File.dirname(__FILE__) + "/datasets")
-
-if File.directory?(File.dirname(__FILE__) + "/matchers")
-  Dir[File.dirname(__FILE__) + "/matchers/*.rb"].each {|file| require file }
+# Include any datasets from loaded extensions
+Radiant::Extension.descendants.each do |extension|
+  if File.directory?(extension.root + "/spec/datasets")
+    Dataset::Resolver.default << (extension.root + "/spec/datasets")
+  end
 end
 
 require 'action_controller'

metadata

@@ -1,28 +1,39 @@
---- !ruby/object:Gem::Specification
+--- !ruby/object:Gem::Specification 
 name: radiant-mailer-extension
-version: !ruby/object:Gem::Version
-  version: 1.0.4
+version: !ruby/object:Gem::Version 
+  hash: 27
   prerelease: 
+  segments: 
+  - 1
+  - 0
+  - 6
+  version: 1.0.6
 platform: ruby
-authors:
+authors: 
 - Nathaniel Talbott
 - Sean Cribbs
 - Matt McCray
 - Jim Gay
 - John Muhl
 - Benny Degezelle
+- Andrew vonderLuft
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-03-04 00:00:00.000000000 Z
+
+date: 2014-07-15 00:00:00 Z
 dependencies: []
+
 description: Provides support for email forms and generic mailing functionality.
-email:
+email: 
 - radiant@radiantcms.org
 executables: []
+
 extensions: []
+
 extra_rdoc_files: []
-files:
+
+files: 
 - app/controllers/mail_controller.rb
 - app/models/mail.rb
 - app/models/mailer.rb
@@ -45,7 +56,9 @@ files:
 - mailer_extension.rb
 - radiant-mailer-extension.gemspec
 - Rakefile
-- README.rdoc
+- README.md
+- spec/ci/before_script
+- spec/ci/script
 - spec/controllers/mail_controller_spec.rb
 - spec/datasets/mailer_page_dataset.rb
 - spec/lib/mailer_process_spec.rb
@@ -56,29 +69,40 @@ files:
 - spec/spec_helper.rb
 homepage: https://github.com/radiant/radiant-mailer-extension
 licenses: []
+
 post_install_message: 
 rdoc_options: []
-require_paths:
+
+require_paths: 
 - lib
-required_ruby_version: !ruby/object:Gem::Requirement
+required_ruby_version: !ruby/object:Gem::Requirement 
   none: false
-  requirements:
-  - - ! '>='
-    - !ruby/object:Gem::Version
-      version: '0'
-required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
+      version: "0"
+required_rubygems_version: !ruby/object:Gem::Requirement 
   none: false
-  requirements:
-  - - ! '>='
-    - !ruby/object:Gem::Version
-      version: '0'
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
+      version: "0"
 requirements: []
+
 rubyforge_project: 
-rubygems_version: 1.8.11
+rubygems_version: 1.8.24
 signing_key: 
 specification_version: 3
 summary: Form mailing for Radiant CMS
-test_files:
+test_files: 
+- spec/ci/before_script
+- spec/ci/script
 - spec/controllers/mail_controller_spec.rb
 - spec/datasets/mailer_page_dataset.rb
 - spec/lib/mailer_process_spec.rb

data/README.rdoc

@@ -1,225 +0,0 @@
-= Mailer Extension for Radiant
-
-The Mailer extension enables form mail on a page.
-
-== Usage
-
-You can define email templates using pages parts (email, and/or email_html).
-You configure the recipients and other Mailer settings in a "mailer" part:
-
-  subject: From the website of Whatever
-  from: noreply@example.com
-  redirect_to: /contact/thank-you
-  recipients:
-    - one@one.com
-    - two@two.com
-
-The following tags are available to help you build the form:
-
-  <r:mailer:form name=""> ... </r:mailer:form>
-  <r:mailer:text name="" />
-  <r:mailer:password name="" />
-  <r:mailer:reset name="" />
-  <r:mailer:checkbox name="" />
-  <r:mailer:radio name="" />
-  <r:mailer:file name="" />
-  <r:mailer:radiogroup name=""> ... </r:mailer:radiogroup>
-  <r:mailer:select name=""> ... </r:mailer:select>
-  <r:mailer:date_select name=""/>
-  <r:mailer:textarea name=""> ... </r:mailer:textarea>
-  <r:mailer:option name="" />
-  <r:mailer:submit name="" />
-  <r:mailer:image name="" />
-  <r:mailer:submit_placeholder />
-
-When processing the form (in email and email_html), the following tags are 
-available:
-
-  <r:mailer:get name="" />
-  <r:mailer:get_each name=""> ... </r:mailer:get_each>
-    <r:mailer:index />
-
-Simple example of a form:
-
-  <r:mailer:form>
-   <r:mailer:hidden name="subject" value="Email from my Radiant site!" /> <br/>
-    Name:<br/>
-   <r:mailer:text name="name" /> <br/>
-    Message:<br/>
-   <r:mailer:textarea name="message" /> <br/>
-   <r:mailer:submit name="Send" />
-  </r:mailer:form>
-
-=== Required fields
-
-You can specify fields which must be populated or the form will be invalid and will redisplay the page with an error informing the user to populate those fields.
-
-Simple example of a required field:
-
-  <r:mailer:form>
-   ...
-    Name:<br/>
-   <r:mailer:text name="name" required="true"/> <br/>
-   ...
-   <r:mailer:submit name="Send" />
-  </r:mailer:form>
-
-Simple example of a required field with user-defined message:
-
-  <r:mailer:form>
-   ...
-    Name:<br/>
-   <r:mailer:text name="name" required="should not be blank"/> <br/>
-   ...
-   <r:mailer:submit name="Send" />
-  </r:mailer:form>
-
-You can also specify fields which must be validated 'as_email' (i.e. a@b.com).
-
-Simple example of a required field with email address validation:
-
-  <r:mailer:form>
-   ...
-    Reply-To:<br/>
-   <r:mailer:text name="reply_email" required="as_email"/> <br/>
-   ...
-   <r:mailer:submit name="Send" />
-  </r:mailer:form>
-
-You can also specify fields which must be validated as defined regexp (i.e. /^\d{2}\.\d{2}\.\d{4}\$/ for date dd.mm.yyyy).
-
-
-Simple example of a required field with regexp validation:
-
-  <r:mailer:form>
-   ...
-    Birthday:<br/>
-   <r:mailer:text name="birthday" required="/^\d{2}\.\d{2}\.\d{4}\$/"/> <br/>
-   ...
-   <r:mailer:submit name="Send" />
-  </r:mailer:form>
-
-Finally, you can put all field validations in the "mailer" part:
-
-  subject: From the website of Whatever
-  from: noreply@example.com
-  redirect_to: /contact/thank-you
-  recipients:
-    - one@one.com
-  required:
-    name: "true"
-    email: as_email
-    message: "true"
-
-The field names above are "name," "email," and "message." Note the quotation marks around true values. If you do your field validations this way, Mailer will ignore any validations you attempt through your radius tags. This method of validation keeps Mailer from adding hidden inputs to keep track of required fields. See the caveat below.
-
-
-=== Spam blocking
-
-You can specify which fields may not contain anything that looks like a link in the "mailer" part. For example:
-
-  subject: From the website of Whatever
-  from: noreply@example.com
-  redirect_to: /contact/thank-you
-  recipients:
-    - one@one.com
-  disallow_links:
-    - comments
-    - questions
-
-The comments and questions fields would throw an error if the user or a spam bot entered the following phrases: "www", "&amp;", "http:", "mailto:", "bcc:", "href", "multipart", "[url", or "Content-Type:".
-
-
-You can also include one field on your form that must be left blank. If anyone enters something in the field, the field throws an error. The tactic here is to hide the field from human readers, but to leave the field visible to spam bots. Here is how you would edit the "mailer" part to implement this:
-
-  subject: From the website of Whatever
-  from: noreply@example.com
-  redirect_to: /contact/thank-you
-  recipients:
-    - one@one.com
-  leave_blank: your_field_name
-
-"your_field_name" is the name of the field you want to hide. It is up to you to hide the field when you construct your form. I would recommend against using a traditional hidden input field. Use style="display:none" instead.
-
-
-=== File attachments
-
-In many cases it is desirable to limit the maximum size of a file that may be uploaded. This is set as the max_filesize attribute for mailers in the mailer page part. Any file included in the form will have the limit imposed. Following is a simple example mailer part that includes a file size limit of 100,000 bytes:
-
-  subject: From the website of Whatever
-  from: noreply@mydomain.com
-  redirect_to: /contact/thank-you
-  max_filesize: 100000
-  recipients:
-    - one@one.com
-    - two@two.com
-
-The following is a simple form that might be used to submit a file for the above configuration:
-
-  <r:mailer:form name="contact">
-      Type your message: <r:mailer:text name="themessage" /> <br/>
-      Select a file: <r:mailer:file name="thefile" /> <br/>
-      <r:mailer:submit value="submit"/>
-  </r:mailer:form>
-
-If a user does not select a file the other form contents will still be e-mailed. The <r:mailer:get name="foo" /> (with <r:mailer:file name="foo" />) will provide the uploaded file name.
-
-If you are using email or email_html parts then the <r:mailer:get name="" /> tag can be used to retrieve the name of the uploaded file. If no file was uploaded "" will be returned.
-
-=== Submit placeholder
-
-If you wish to show that activity is taking place during submission you may use the <r:mailer:submit_placeholder /> tag in your form. This will insert a hidden div with the contents of the submit_placeholder page part. The div will be displayed when the user clicks any submit button.
-
-=== User-provided Configuration
-
-Sometimes, rather than explicitly configuring the recipients and such in the mailer part, you'd rather have them passed in by the person submitting the form. Mailer supports this by allowing you to specify a form field to pull the value from:
-
-  from_field: my_form_field_that_contains_the_from_email_address
-  
-Then you just have to add that field to your mailer form and you're all set.
-
-This is supported for the from (from_field), recipients (recipients_field) and reply_to (reply_to_field) properties.
-
-== Enabling action_mailer
-
-In environment.rb you'll probably need to change:
-
-  config.frameworks -= [ :action_mailer ]
-
-to:
-
-  config.frameworks -= []
-
-== Updating from the older mailer extension
-
-If you get this error "The single-table inheritance mechanism failed to locate the subclass: 'MailerPage'.", run 'rake:radiant:extensions:mailer:migrate'. This will change all pages with a MailerPage classname into regular pages.
-  Second, your 'config' page part has to be renamed to 'mailer', and the first two YAML levels should be deleted (see instructions above).
-
-If you are getting a stack level too deep error, it may be caused by using <r:mailer:get /> in your 'mailer' part.
-Use the from_field or other options to get to the email adress that was posted (see User-provided configuration).
-
-== Caveats
-
-Relative urls will almost certainly not work if the mailer fails validation. Solution? Only use absolute urls.
-
-Unless you set up the field validations in the "mailer" part, validation will be implemented via easily spoofable HTML attributes. Think of them of more like guidelines in that case.
-
-== History
-
-Created by: M@ McCray - mattmccray.com
-  Version: 0.2.1
-  Contact: mmccray@elucidata.net
-
-Ported to 'mental' by: Sean Cribbs - seancribbs.com
-  Version: 0.1
-  Contact: seancribbs@gmail.com
-  
-Seriously restructured by: Nathaniel Talbott - terralien.com
-  Version: 0.2
-  Contact: nathaniel@terralien.com
-  Work sponsored by: Ignite Social Media, http://ignitesocialmedia.com/
-
-
-== Todo
-
-* Tests