Ruby on Rails

Paul wrote in post #999045:
> Not knowing, but as a guess I'd look at the way passwords are being
> encrypted. When you log in the first time, it probably doesn't get
> your password out of the database. So, do the encryption and
> decryption match? Are you correctly using the salt?
>
> Just a shot in the dark...

Thanks for the reply.

I've narrowed it down a bit. I decided to not override the sessions
controller with my own, and using devise's default view and controller,
I can sign in fine.

I've commented out the before filter on my custom sessions controller,
and copied the whole form from the devise view to my custom view. Still
can't log in. Weird thing though is that no password_salt is being
created for my users....

So maybe a new question. I do need to override the registrations
controller because I'm doing all kinds of stuff when a user is created.
Is there a "best practices" way of using devise and doing that? Right
now it's just doing

@user = User.new(params[:user])
@user.save!

if there a User.new_with_cool_devise_stuff(params[:user]) ??

Thanks

~Jeremy

--
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-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.