On Sunday, May 19, 2013 9:14:47 AM UTC+1, rihad wrote: > > > I now think it may be the peculiarity of the model: it validates > > presence of password confirmation, which makes no sense when password > > itself isn't or shouldn't be updated.
That is indeed weird - the only validation I've ever used in conjunction with the confirmation field is validates_confirmation_of. You can check user.errors to see all the errors rails thinks the object has. Fred -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/96210449-c5ed-4d43-b0aa-4f848de4efbd%40googlegroups.com?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
