We’ve spent the past couple days upgrading the Travergence site from Rails 3.0 to 3.1 and while it hasn’t been entirely smooth, it hasn’t been horrible either. Except for one issue:
This would cause recursion somewhere in the stack, eventually leading to:
After much digging, googling, commenting-out of code, and swearing I finally figured out that it was rails3_acts_as_paranoid causing the issue. One more google led to this solution by Chris Hilton, which involves patching rails3_acts_as_paranoid to prevent circular aliasing.
Hopefully Gonçalo Silva will fix it in the official branch on Github. Until then you can either fork and patch it yourself or grab ours: