Can anyone confirm that this bug was introduced into Rails 1.2.2? I think I'm encountering it with the 1.2.2 Gem, but I want to be certain that I'm not overlooking a different problem.
I seem to be having the same problem with 1.2.2
Keep up to date with Rails on Twitter and This Week in Rails
Policies: Conduct, License, Maintenance, Security, Trademarks