Load ActionMailer templates only if it is included in configuration.frameworks
Reported by Sam Granieri | July 24th, 2008 @ 01:27 PM | in 2.x
I'm developing on edge, and my app doesnt currently require ActionMailer or ActiveResource, so I disabled them in RAILS_ROOT/config/environment.rb
config.frameworks -= [ :active_resource, :action_mailer ]
I'm on edge rails commit # 3fd9036fc554979e951422a79f0f77f061112bdc
I then typed rake spec and got the following stacktrace: http://pastie.org/240477.
(I know some if you might think this could be an rspec problem, but i'm not so sure. Hear me out a little bit more..)
I opened up vendor/rails/railties/lib/initializer.rb and looked at load_view_paths on line 342.
I changed line 344 from
ActionMailer::Base.template_root.load
to
ActionMailer::Base.template_root.load if configuration.frameworks.include?(:action_mailer)
and my problem went away.
This just seems like a common sense fix for those of us on edge, or on vendor rails.
Comments and changes to this ticket
-
Joshua Peek July 24th, 2008 @ 01:29 PM
- → State changed from “new” to “open”
- → Assigned user changed from “” to “Joshua Peek”
-
Jason Roelofs July 24th, 2008 @ 01:34 PM
Running into the same issue. I've got a patch that includes a test as well.
-
Joshua Peek July 24th, 2008 @ 01:53 PM
- → State changed from “open” to “resolved”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
