Changes to be compatible with django 1.5. custom user model #180
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SOCIALREGISTRATION_USER_FUNCTION which points to the new-type function. The function fills up necessary fields in the user model and returns tuple: user, profile SOCIALREGISTRATION_SEAMLESS_SETUP is just rename for SOCIALREGISTRATION_GENERATE_USERNAME which does not make sense if/when the old function will be removed. Both variables are kept and used as dispatcher. Changes are backward compatible
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I have made new branch with clean commit history. I think that this is really good idea and necessary in order to remain compatible with django 1.5. This pull request solves problems with registering custom user model, which is available since django 1.5.
There are two new settings variables.
SOCIALREGISTRATION_USER_FUNCTIONwhich points to the new-type function. The function fills up necessary fields in the user model and returns tuple:(user, profile)SOCIALREGISTRATION_SEAMLESS_SETUPis just rename forSOCIALREGISTRATION_GENERATE_USERNAMEwhich does not make sense if/when the old function will be removed. Both variables are kept and used as dispatcher.The change is backward compatible.