This project is archived and is in readonly mode.
Default 500 error message shouldn't imply notification
-
Pratik- 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 CHi 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
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
- Tag set to patch
Can anyone tell me how to get rails to make some sort of notification in this case? Perhaps send an email?
-
pjdeklerk
Never mind. I found a plugin called ExceptionNofifier which does the right thing.
-
joshaidanI really wish the default 500.html would be changed to not imply the site administrators of the application received notification of the error. I have had lots of users assume I knew what was going wrong with the application, and therefore would not bother to give me any details of the error.
I know it's not hard to change the default message, and neither is it difficult to install ExceptionNotifier (which I have). It's just my opinion the default message is misleading, and that it should be the other way around (change the message if you actually do have a notification system in place).