Thanks on the 404 stuff, that was easy.
I'm going to stick with the reconnect => true until that is proving
not to work. It's the easiest as it's a one liner addition to my yaml.
Dave
On Fri, Feb 19, 2010 at 3:13 PM, Magnus Holm wrote:
> 404 on 1.5:
> module App::Controllers
> class NotFound
404 on 1.5:
module App::Controllers
class NotFound
def get(path)
"Do something with path"
end
end
end
404 on 1.9/2.0:
module App
def r404(path)
"Do something with path"
end
end
There appears to be two solutions:
Call ActiveRecord::Base.verify_active_connections! before e
I have a few camping projects that are about to go into production in
a few weeks, just picking your brains to see if I can add some
robustness.
What's the best way to catch any "Camping Problem! /XXX not found"
errors that a user might see if they start typing URLs themselves?
Ideally I'd just li
3 matches
Mail list logo
