On Oct 28, 2011, at 9:55 PM, WBT wrote: > "We're sorry, but something went wrong. We've been notified about this > issue and we'll take a look at it shortly."
I was also always bothered by it. By default, nobody was notified about any issue and they will only take a look if someone tells them or if they accidentally see exceptions in production.log. The default 500.html is a lie. > "Application Error: An error occurred in the application and your page > could not be served." With risk of this turning into a bike shed discussion, I'll throw my own tweak in here: "Application Error: An error occurred in the application and the page could not be served." This is a good message. It doesn't tell you lies and it doesn't suggest to "try again" because, in my experience, most errors are persistent so telling users to "try again" will lead to frustration. I wouldn't put the "If you are the owner, check the logs" bit. If you know enough to boot up an application in production mode, you know about the existance of application logs for each environment. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
