Forum: Ruby on Rails Application error (Rails)

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.
hreyaatnh (Guest)
on 2006-03-15 00:17
After I attempted to add ActionMailer functionality, it gave the
"Application error (Rails)" and now, everything on my site works, except
for the part where the Actionmailer 'would have' sent the email.

I took that out now, re-uploaded the file, and ran "killall -USR1
dispatch.fcgi" and still nothing.  Everything else works, except that.

Any idea what else was affected?  Should I just copy my app folder
overtop of it again?  Thanks for any help...I really want to fix this!
Manish S. (Guest)
on 2006-03-16 05:12
(Received via mailing list)
is your configuration correct for the environment your server is running
in?  You need to be sure that sendmail (with the -i -t options) works or
have the correct smtp settings for ActionMailer
Michael G. (Guest)
on 2006-03-16 05:16
(Received via mailing list)
What is your log displaying?
Richard W. (Guest)
on 2006-03-16 16:22
(Received via mailing list)
Suggestion to core developers:  Have an configuration option that you
can set to allow exception tracebacks to appear in production mode (like
that which appears in development mode) rather than "Application Error

We would much prefer that a user can report (or take a screen dump) when
an error occurs so that we can see what went wrong - instead of the
Application Error where we have to try and figure out what he was doing
at the time... etc...

Thanks for the consideration.
Mikkel B. (Guest)
on 2006-03-16 16:41
(Received via mailing list)
in production.rb

ActionController::Base.consider_all_requests_local = false


ActionController::Base.consider_all_requests_local = true

On Thursday, March 16, 2006, at 2:20 PM, Richard W. wrote:
>Thanks for the consideration.
Mikkel B.    - Football Portal(DK) - Football News(DK)      - Buy Old Stuff!(DK)
Craig W. (Guest)
on 2006-03-16 17:21
(Received via mailing list)
On Thu, 2006-03-16 at 14:20 +0000, Richard W. wrote:
> Thanks for the consideration.
I think you can adjust the environment file to act similarly - the issue
is that the 'tracebacks' is more of what is considered 'local'

There is a methodology to trap the errors and use ActionMailer to send
an email (presumably to the developer) in the AWDWR book and I asked
about this a week ago and I think the upshot was that something inside
of Rails changed since the book was published that caught Dave

which suggests that following the methodology in the book is probably
not a very good idea.

In my drive to finish the most perplexing problems so I can move on,
this still remains on my list of things to do so it appears that the
only methodology that ***should*** work would be here...

Richard W. (Guest)
on 2006-03-17 16:25
(Received via mailing list)
Thanks for the responses.

I will define a local_request? method in the app as a solution.

class ApplicationController < ActionController::Base
  def local_request?
Richard W. (Guest)
on 2006-03-24 23:00
(Received via mailing list)
>in production.rb
>ActionController::Base.consider_all_requests_local = false
>ActionController::Base.consider_all_requests_local = true

Exactly what I needed.

production.rb is config/environments/production.rb
This topic is locked and can not be replied to.