Forum: Rails Engines development 1.2.1 errors?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
ben wiseley (Guest)
on 2007-01-28 04:49
(Received via mailing list)
Any ideas on this?  On a "from scratch, do nothing app" I'm getting
this error when mixing engines plugin and the exception_notification

Engines by themselves work and exception_notification by itself works
but I can't seem to combine the two

I read through the news site on engines and didn't see this covered...
anyone have any ideas.

*  Upgraded to Rails 1.2.1 (and updated all gems)

*  Did a Rails rails12test

*  script/plugin install

*  set that up like you normally do (enviroment/application settings)

* put up a dummy controller... app runs fine

* ruby script/plugin install

* added the line to environment:
    config.plugins = %W( engines exception_notification )

* run app and I get a:

ben-wiseleys-computer:~/dev/rail12test wiseleyb$ mongrel_rails start
** Starting Mongrel listening at
** Starting Rails with development environment...
`load_missing_constant': Expected
to define ExceptionNotifier (LoadError)
        from /Users/wiseleyb/dev/rail12test/config/environment.rb:61
         ... 6 levels...
        from /opt/local/bin/mongrel_rails:18:in `load'
        from /opt/local/bin/mongrel_rails:18
James A. (Guest)
on 2007-01-28 12:36
(Received via mailing list)
Hi Ben,

The main release of the engines plugin hasn't yet been updated to work
with Rails 1.2. Instead, could you use SVN to check out the 1.2
release branch?

  svn co

That should work, but if you do experience any problems please post
back to list list, or onto the issue tracker (see the docs)


ben wiseley (Guest)
on 2007-01-28 19:00
(Received via mailing list)

Seems to be working pretty well on both of our fairly large apps that
are using engines.

The only problem I've run into so far is with  mailers...

In engines/lib/engines/rails_extransion/templates.rb in method
render_with_engine_additions(opts) at line 133 I had to make this
small change

        template_path_for_method =
Dir["#{template_path}/#{opts[:file]}.*"].first ||

My Input data (if it helps) was:

For opts.to_yaml:

  notification_type: new_comment
  blog_entry_title: asdf
  comment_by_html: " by <a href=''>Ben
  comment: asdf<br />
  blog_entry_url: http://localhost:3000/blogsview/33218/asdf
  comment_by_text: " by Ben Wiseley"
:file: blog_notification_email.text.html.rhtml

And for template_path.to_yaml:

James A. (Guest)
on 2007-01-28 19:58
(Received via mailing list)
Hi Ben,

There's currently a ticket for this on the issue tracker
(, but since I
don't use ActionMailer day-to-day, it's not trivial for me to
replicate this error. Could you add a failing test case to the test
application ( and
submit it as a patch to that ticket?

Failing that, a zip of the failing mailer model, mail views and so on
would also be useful.

Thanks - this seems to be the only blocker before I release 1.2 :)
ben wiseley (Guest)
on 2007-01-28 23:17
(Received via mailing list)

Updated the ticket that mentions this with a zip file that can be used
test this.  Sorry - kind of new to the patch thing with open source
and am not sure what exactly people are supposed to do :).  Tried to
in to your project but it wouldn't let me so I sent a zip file instead.
README.txt has details on how to get the unit test to pass.  There's
some basic UI stuff included for mucking about from the browser if it

Thanks for all your work on Engines... this has made my work much easier

James A. (Guest)
on 2007-01-29 01:19
(Received via mailing list)
Thanks for that Ben,

The reason I hadn't picked up on this was because of some changes in
ActionMailer (namely picking up method_name.text.whatever.rhtml
templates). The way ActionMailer::Base has been put together, it's
quite tricky to untangle it into a state where we can start to make it
play nice with plugins. The fixes suggested on that ticket work with
*implicit* multipart mails, but not with explict ones (where parts are
defined via part "text/plain" { ... } ), or so it seems.

I'll have a think, but if anyone comes up with a general fix (plus
tests), please do throw them up against this ticket.

This topic is locked and can not be replied to.