John Woods wrote: > For the record, I believe I have discovered the problem. > > Authlogic absolutely requires that there be a login field of some sort > in the User model -- even if you don't actually use it for logging in.
No. Authlogic is smart enough to use email if login doesn't exist. Further configuration is probably possible; check the docs. > It also needs to contain some unique value, presumably, or there will > be validation problems. Well, yes, Authlogic expects that the username or e-mail address will actually be in the users table. :) > I simply used the email address people sign up > with initially, and also keep a copy of that in the emails table. You shouldn't need to keep the same data in two places. Try reworking your associations or your Authlogic configuration. > > I assume this is a bug of some sort. It'd be great if Authlogic were > more informative with its error messages; without a login field, it > produces all kinds of unrelated errors. > > Thanks so much for the help. > > John Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/.
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
