This project is archived and is in readonly mode.
retrieve_connection failure processing error template
Reported by Sam Ruby | May 5th, 2010 @ 11:50 AM | in 3.x
Runtime errors in the development environment typically render a rescue page that shows the error, extracted source, various traces, request and response parameters. Starting with commit 841c01fa0fa92aa6e3c2e5029444a9cbb4f161f3, a 500 Internal Server Error is produced instead unless there is no data involved.
Reproduction scenario: generate an app, generate a model w/scaffold, insert an error into index.html, fetch the index (and see the rescue page), create an instance of the model, and refetch the index.
Comments and changes to this ticket
-
-
Repository May 8th, 2010 @ 05:00 PM
- State changed from “new” to “resolved”
(from [788684d75a7102107c0d99e5cb32a11a610f628f]) get the rescue error page back [#4536 state:resolved] http://github.com/rails/rails/commit/788684d75a7102107c0d99e5cb32a1...
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>
People watching this ticket
Jason Weathered
Jeremy Kemper
Sam Ruby
Santiago Pastorino
Attachments
Referenced by
-
4536
retrieve_connection failure processing error template
(from [788684d75a7102107c0d99e5cb32a11a610f628f])
get the...