What's New in Edge Rails: Prettier Error Pages!

Posted by ryan
at 4:40 PM on Tuesday, October 10, 2006

This may not seem like a biggie, but we all know you haven’t gotten around to prettying up your error pages yet..

The new, pretty, 404 error page

and

The new, pretty, 500 error page

It’s the little things sometimes…

tags: rubyonrails, rails

Comments

Leave a response

  1. Jon Maddox – October 10, 2006 @ 05:11 PM
    oh yes, just gorgeous. The maintenance.html file always made my error pages jealous. ;)
  2. Chris Abad – October 10, 2006 @ 05:45 PM
    That great! Granted we should all be making our own 404s and 500s anyways, but you know how that goes... You're absolutely right, this is one of those little things that just makes it that much better.
  3. joost – October 10, 2006 @ 07:54 PM
    I found this page: http://www.smackthemouse.com/error404 to be of great help in designing my error page. A best practice of sorts. And the guy has valid points!
  4. Tim Lucas – October 10, 2006 @ 10:44 PM
    It's an improvement, but why is the html code so dodgy? (patch filed)
  5. Dr Nic – October 11, 2006 @ 12:29 AM
    Has there been any discussion by core on RJS support for server errors? E.g. returning some Javascript that displays the error information, instead returning HTML error information that the Ajax eval can't process?
  6. Ryan Daigle – October 11, 2006 @ 03:45 AM
    Joost: Wow, I never knew so much could be written about 404 pages. Thanks for the pointer. Tim: I am the last person you'd want to talk to about CSS, but I definitely recognize the value of valid markup. Great patch, and great turn-around time too. I hope it gets picked up by core. Dr. Nic: I'm not quite sure what the intentions of core are on the matter...
  7. noz – December 26, 2006 @ 04:19 PM
    A 404 error page should say "404 Not Found" somewhere, at least in the title. And "We're sorry, but something went wrong" isn't any more helpful than just saying "ERROR ERROR ERROR".