Default 500 error message shouldn't imply notification
Reported by Adam C | May 25th, 2008 @ 08:17 PM
The default 500.html error message shouldn't imply a notification when no notification has actually taken place.
Comments and changes to this ticket
-
Pratik May 28th, 2008 @ 11:04 AM
- → State changed from “new” to “invalid”
The current one sounds more "professional" and it's very easy to change if you wish to for your application.
Feel free to disucss it over rails core mailing list.
Thanks.
-
Adam C May 28th, 2008 @ 11:11 AM
Hi Pratik,
It doesn't really affect me as I don't use the default anyway - as I'm sure lots of people do. But, although it sounds professional, it isn't accurate.
I simply felt that users who left it in might find that users don't alert them to possible problems because the message implies they have already been made aware.
Thanks
Adam
-
Wincent Colaiuta May 28th, 2008 @ 01:00 PM
I also don't use the default, but I think that accuracy is more important than creating an illusion of professionalism. It's about integrity: if Rails tells little lies in the default templates, how does one know it's not being similarly "dishonest" in other places too?
-
pjdeklerk October 27th, 2008 @ 03:20 PM
- → Tag changed from “” to “patch”
Can anyone tell me how to get rails to make some sort of notification in this case? Perhaps send an email?
-
pjdeklerk October 27th, 2008 @ 06:20 PM
Never mind. I found a plugin called ExceptionNofifier which does the right thing.
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
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
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"..
