actionmailer 3.2.12 → 3.2.13.rc1
Sign up to get free protection for your applications and to get access to all the features.
Potentially problematic release.
This version of actionmailer might be problematic. Click here for more details.
- checksums.yaml +4 -4
- data/CHANGELOG.md +46 -4
- data/lib/action_mailer/base.rb +11 -11
- data/lib/action_mailer/version.rb +2 -2
- metadata +12 -12
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: c7b395230e50f870701fea19681c7ddbfea674d0
|
4
|
+
data.tar.gz: 328b08c8f5a1b1fc21f6063bd5627b0dfd7af2c9
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: d29d77cd43e8b5ddfdb8ccbcdaa0491867a332c89055aebf60f596ddea0b0992a9392128e78f8b435d1f993e157a061f7e4c93ef1b231503989fa8899bb23269
|
7
|
+
data.tar.gz: 1c2b8bf7b9e5aa2b6f41e6eb621a11675d9172647d50ba6eefa1a00269cca45a69b765120bbf4b5c9e282014492a952ea5f12a39df42126f65b9c78b06e60890
|
data/CHANGELOG.md
CHANGED
@@ -1,11 +1,53 @@
|
|
1
|
-
##
|
1
|
+
## unreleased ##
|
2
|
+
|
3
|
+
* No changes.
|
4
|
+
|
5
|
+
|
6
|
+
## Rails 3.2.13 (Feb 17, 2013) ##
|
7
|
+
|
8
|
+
* No changes.
|
9
|
+
|
10
|
+
|
11
|
+
## Rails 3.2.12 (Feb 11, 2013) ##
|
12
|
+
|
13
|
+
* No changes.
|
14
|
+
|
15
|
+
|
16
|
+
## Rails 3.2.11 (Jan 8, 2013) ##
|
17
|
+
|
18
|
+
* No changes.
|
19
|
+
|
20
|
+
|
21
|
+
## Rails 3.2.10 (Jan 2, 2013) ##
|
22
|
+
|
23
|
+
* No changes.
|
24
|
+
|
25
|
+
|
26
|
+
## Rails 3.2.9 (Nov 12, 2012) ##
|
27
|
+
|
28
|
+
* The return value from mailer methods is no longer relevant. This fixes a bug,
|
29
|
+
which was introduced with 3.2.9.
|
30
|
+
Backport #8450
|
31
|
+
Fix #8448
|
32
|
+
|
33
|
+
class ExampleMailer < ActionMailer::Base
|
34
|
+
# in 3.2.9, returning a falsy value from a mailer action, prevented the email from beeing sent.
|
35
|
+
# With 3.2.10 the return value is no longer relevant. If you call mail() the email will be sent.
|
36
|
+
def nil_returning_mailer_action
|
37
|
+
mail()
|
38
|
+
nil
|
39
|
+
end
|
40
|
+
end
|
41
|
+
|
42
|
+
*Yves Senn*
|
43
|
+
|
2
44
|
|
3
45
|
## Rails 3.2.9 (Nov 12, 2012) ##
|
4
46
|
|
5
|
-
*
|
6
|
-
|
47
|
+
* Do not render views when mail() isn't called.
|
48
|
+
Fix #7761
|
7
49
|
|
8
|
-
|
50
|
+
*Yves Senn*
|
9
51
|
|
10
52
|
|
11
53
|
## Rails 3.2.8 (Aug 9, 2012) ##
|
data/lib/action_mailer/base.rb
CHANGED
@@ -123,8 +123,8 @@ module ActionMailer #:nodoc:
|
|
123
123
|
#
|
124
124
|
# <%= users_url(:host => "example.com") %>
|
125
125
|
#
|
126
|
-
# You should use the <tt>named_route_url</tt> style (which generates absolute URLs) and avoid using the
|
127
|
-
# <tt>named_route_path</tt> style (which generates relative URLs), since clients reading the mail will
|
126
|
+
# You should use the <tt>named_route_url</tt> style (which generates absolute URLs) and avoid using the
|
127
|
+
# <tt>named_route_path</tt> style (which generates relative URLs), since clients reading the mail will
|
128
128
|
# have no concept of a current URL from which to determine a relative path.
|
129
129
|
#
|
130
130
|
# It is also possible to set a default host that will be used in all mailers by setting the <tt>:host</tt>
|
@@ -133,7 +133,7 @@ module ActionMailer #:nodoc:
|
|
133
133
|
# config.action_mailer.default_url_options = { :host => "example.com" }
|
134
134
|
#
|
135
135
|
# When you decide to set a default <tt>:host</tt> for your mailers, then you need to make sure to use the
|
136
|
-
# <tt>:only_path => false</tt> option when using <tt>url_for</tt>. Since the <tt>url_for</tt> view helper
|
136
|
+
# <tt>:only_path => false</tt> option when using <tt>url_for</tt>. Since the <tt>url_for</tt> view helper
|
137
137
|
# will generate relative URLs by default when a <tt>:host</tt> option isn't explicitly provided, passing
|
138
138
|
# <tt>:only_path => false</tt> will ensure that absolute URLs are generated.
|
139
139
|
#
|
@@ -150,8 +150,8 @@ module ActionMailer #:nodoc:
|
|
150
150
|
#
|
151
151
|
# = Multipart Emails
|
152
152
|
#
|
153
|
-
# Multipart messages can also be used implicitly because Action Mailer will automatically detect and use
|
154
|
-
# multipart templates, where each template is named after the name of the action, followed by the content
|
153
|
+
# Multipart messages can also be used implicitly because Action Mailer will automatically detect and use
|
154
|
+
# multipart templates, where each template is named after the name of the action, followed by the content
|
155
155
|
# type. Each such detected template will be added as a separate part to the message.
|
156
156
|
#
|
157
157
|
# For example, if the following templates exist:
|
@@ -448,6 +448,7 @@ module ActionMailer #:nodoc:
|
|
448
448
|
# method, for instance).
|
449
449
|
def initialize(method_name=nil, *args)
|
450
450
|
super()
|
451
|
+
@mail_was_called = false
|
451
452
|
@_message = Mail.new
|
452
453
|
process(method_name, *args) if method_name
|
453
454
|
end
|
@@ -455,10 +456,8 @@ module ActionMailer #:nodoc:
|
|
455
456
|
def process(*args) #:nodoc:
|
456
457
|
lookup_context.skip_default_locale!
|
457
458
|
|
458
|
-
|
459
|
-
unless
|
460
|
-
@_message = NullMail.new
|
461
|
-
end
|
459
|
+
super
|
460
|
+
@_message = NullMail.new unless @mail_was_called
|
462
461
|
end
|
463
462
|
|
464
463
|
class NullMail #:nodoc:
|
@@ -616,8 +615,9 @@ module ActionMailer #:nodoc:
|
|
616
615
|
# end
|
617
616
|
#
|
618
617
|
def mail(headers={}, &block)
|
619
|
-
# Guard flag to prevent both the old and the new API from firing
|
620
|
-
#
|
618
|
+
# Guard flag to prevent both the old and the new API from firing.
|
619
|
+
# On master this flag was renamed to `@_mail_was_called`.
|
620
|
+
# On master there is only one API and this flag is no longer used as a guard.
|
621
621
|
@mail_was_called = true
|
622
622
|
m = @_message
|
623
623
|
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: actionmailer
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 3.2.
|
4
|
+
version: 3.2.13.rc1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- David Heinemeier Hansson
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2013-02-
|
11
|
+
date: 2013-02-27 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: actionpack
|
@@ -16,28 +16,28 @@ dependencies:
|
|
16
16
|
requirements:
|
17
17
|
- - '='
|
18
18
|
- !ruby/object:Gem::Version
|
19
|
-
version: 3.2.
|
19
|
+
version: 3.2.13.rc1
|
20
20
|
type: :runtime
|
21
21
|
prerelease: false
|
22
22
|
version_requirements: !ruby/object:Gem::Requirement
|
23
23
|
requirements:
|
24
24
|
- - '='
|
25
25
|
- !ruby/object:Gem::Version
|
26
|
-
version: 3.2.
|
26
|
+
version: 3.2.13.rc1
|
27
27
|
- !ruby/object:Gem::Dependency
|
28
28
|
name: mail
|
29
29
|
requirement: !ruby/object:Gem::Requirement
|
30
30
|
requirements:
|
31
|
-
- -
|
31
|
+
- - ~>
|
32
32
|
- !ruby/object:Gem::Version
|
33
|
-
version: 2.
|
33
|
+
version: 2.5.3
|
34
34
|
type: :runtime
|
35
35
|
prerelease: false
|
36
36
|
version_requirements: !ruby/object:Gem::Requirement
|
37
37
|
requirements:
|
38
|
-
- -
|
38
|
+
- - ~>
|
39
39
|
- !ruby/object:Gem::Version
|
40
|
-
version: 2.
|
40
|
+
version: 2.5.3
|
41
41
|
description: Email on Rails. Compose, deliver, receive, and test emails using the
|
42
42
|
familiar controller/view pattern. First-class support for multipart email and attachments.
|
43
43
|
email: david@loudthinking.com
|
@@ -70,18 +70,18 @@ require_paths:
|
|
70
70
|
- lib
|
71
71
|
required_ruby_version: !ruby/object:Gem::Requirement
|
72
72
|
requirements:
|
73
|
-
- -
|
73
|
+
- - '>='
|
74
74
|
- !ruby/object:Gem::Version
|
75
75
|
version: 1.8.7
|
76
76
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
77
77
|
requirements:
|
78
|
-
- -
|
78
|
+
- - '>'
|
79
79
|
- !ruby/object:Gem::Version
|
80
|
-
version:
|
80
|
+
version: 1.3.1
|
81
81
|
requirements:
|
82
82
|
- none
|
83
83
|
rubyforge_project:
|
84
|
-
rubygems_version: 2.0.0
|
84
|
+
rubygems_version: 2.0.0
|
85
85
|
signing_key:
|
86
86
|
specification_version: 4
|
87
87
|
summary: Email composition, delivery, and receiving framework (part of Rails).
|