anyone?
On May 27, 10:29 am, anywho
<eydai...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> I''ve been looking at rescue_from and rescue_action_in_public
however,
> none of them have worked without making a catch-all route.
>
> So currently, my solution is to use the catch-all route: match
> ''*path'' => "controller#action" # custom 404
which then renders a 404
> with the appropriate layout whether the user is logged in or not.
> I''ve also set up a rescue_from to handle
ActiveRecord::RecordNotFound
> errors.
>
> It feels like an unsatisfactory solution, and I''m not dealing with
500
> errors at all. I would like to keep the informative errors that rails
> gives during development, but simply have a choice to render a non-
> static page in production.
>
> Help appriciated.
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.