Guyren Howe Wed, 13 Apr 2011 14:32:30 -0700
Reverting devise to 1.1.7 fixed the error.
-- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby