Home/ Questions/Q 6537661
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T10:38:37+00:00

When I go to a bogus url like: /posts/99999999 On my local machine, I

  • 0

When I go to a bogus url like:

/posts/99999999

On my local machine, I see:

ActiveRecord::RecordNotFound in Posts#show

Showing /Users/patrick/rails/my_app/app/views/posts/show.html.haml where line #1 raised:

Couldn’t find Post with ID=99999

… The log shows:

Rendered posts/show.html.haml within layouts/application (29.6ms)
Completed   in 423ms

ActionView::Template::Error (Couldn't find Post with ID=99999)

— However, when I do this in production, I get the public/500.html error page, not 404… I’m kind of confused because in development mode, the browser shows ActiveRecord::RecordNotFound (which should mean 404, yes?) but the log shows ActionView::Template::Error– not one mention of ActiveRecord::RecordNotFound.

So, ultimately, my question is, how can I make this a 404 not a 500? And– why is it a 500?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From what I have seen, Rails should automatically make an ActiveRecord::RecordNotFound render the 404.html page… The problem I discovered was I am using the gem decent_exposure, and because of it’s nature of lazy loading, it causes the error to happen in the view rather than the controller, and therefore Rails doesn’t know to render the 404 page because it shows up as an actual ActionView::Template::Error…

    • 0