Thats right, its deployed on Heroku. The only thing I see in log/ is passenger.3000.log, and it does not contain any recent information. And yes, I always get the custom error page :( Bryan, It would be greatly appreciated if you could expand on your example using the code I'm using? I can't find any similar situations to learn from.
Tomkins. On Tuesday, July 24, 2012 11:06:13 PM UTC+1, Matt jones wrote: > > > On Jul 24, 2012, at 8:56 AM, tomkins wrote: > > > Like I say I'm new to rails and I don't know how to get the actual error > or stacktrace. Our site uses its own error screen so it just says something > went wrong. > > Wait - are you debugging this on a production server? :( > > If so, then step 1 is definitely "get this running in development mode > locally". In dev mode, a crash will show a page detailing exactly what went > wrong and where. It's not always easy to read those traces at first, but > they're incredibly helpful when requesting help over mailing lists. > > If the custom error page is still coming up in development mode, first > sack whoever's responsible for that idea. (joking) > > In all seriousness, if you *must* debug in production you should be able > to find a stacktrace in log/production.log. > > --Matt Jones > > > -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/hobousers/-/IqMzBd1Wmy8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
