This project is archived and is in readonly mode.

#252 ✓invalid
Adam C

Default 500 error message shouldn't imply notification

Reported by Adam C | May 25th, 2008 @ 09:54 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

    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

    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

    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

    pjdeklerk October 27th, 2008 @ 03:20 PM

    • 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

    pjdeklerk October 27th, 2008 @ 06:20 PM

    Never mind. I found a plugin called ExceptionNofifier which does the right thing.

  • joshaidan

    joshaidan December 25th, 2009 @ 04:31 AM

    I 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).

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>

Attachments

Tags

Pages