Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

has_secure_password should allow optional password confirmation #2879

Closed
wants to merge 1 commit into from
Closed

has_secure_password should allow optional password confirmation #2879

wants to merge 1 commit into from

Conversation

edgarjs
Copy link
Contributor

@edgarjs edgarjs commented Sep 5, 2011

Squash of #2837

Update doc for password_confirmation => false
@timothyklim
Copy link

Yep, please merge it!

@new2
Copy link

new2 commented Sep 14, 2011

+1

@edgarjs
Copy link
Contributor Author

edgarjs commented Oct 7, 2011

So is this merging ? 3.1.1 already out without this :(

@bloomdido
Copy link

+1

1 similar comment
@relativkreativ
Copy link

+1

@josevalim
Copy link
Contributor

Closing this. If password_confirmation = nil, it is not going to be triggered anyway. Just don't set it and it won't bother you.

@josevalim josevalim closed this Dec 10, 2011
@josevalim
Copy link
Contributor

And @bloomdido, please be nice. Github is about social coding, you are missing the social.

@gitsetgo
Copy link

gitsetgo commented Oct 9, 2012

@josevalim I have the following validations set up:

validates_presence_of :password, on: :create
validates_confirmation_of :password

The behavior I currently see during :update is that if only :password is set and :password_confirmation is nil, confirmation does not kick in. How do I get confirmation to kick in whenever :password is set?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants