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.

Sign up for GitHub

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

Jump to bottom

Pipeline user_details not changing empty and protected user fields #671

Closed
cmltaWt0 opened this issue Jul 9, 2015 · 1 comment
Closed

Pipeline user_details not changing empty and protected user fields #671

cmltaWt0 opened this issue Jul 9, 2015 · 1 comment

Comments

@cmltaWt0
Copy link
Contributor

cmltaWt0 commented Jul 9, 2015

If user entry have empty field such as email - getattr(user, name, None) give as u'' (tested on Django 1.7.8).
And expression current_value is None will always return False if user field is empty. So we never can change empty and protected user fields.
@cmltaWt0 cmltaWt0 mentioned this issue Jul 9, 2015
Merged
omab added a commit that referenced this issue Jul 9, 2015
@omab
Add comment refering to ticket. Refs #671, #672
fff27d7
@omab
Copy link
Owner

omab commented Jul 9, 2015

Fixed by #672

@omab omab closed this as completed Jul 9, 2015
cmltaWt0 added a commit to raccoongang/socraticqs2 that referenced this issue Jul 14, 2015
@cmltaWt0
chore(psa): update python-social-auth version to 0.2.12
fd49882 
python-social-auth version was freezed to 0.2.9 because of issue omab/python-social-auth#671
This issue was fixed in omab/python-social-auth#672 and have appeared in 0.2.12 version
So now we can move to python-social-auth 0.2.12 version
This was referenced Jul 14, 2015
Closed
Closed
Closed
@dixon-che dixon-che mentioned this issue Jul 17, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@omab @cmltaWt0