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

Don't restrict user model name and fix travis python3 build #2

Merged
merged 2 commits into from Feb 27, 2014

Conversation

koirikivi
Copy link

Your changes seemed to work ok when testing locally. I'd just like to propose this small change to permit the custom user model to be named anything, not just "User".

Travis' python 3 build also broke due to wrong syntax with relative import. It's fixed in the other commit.

I enabled Travis CI for my local fork, so this change can be seen at https://travis-ci.org/koirikivi/django-cms/builds

Thanks!

@tanderegg
Copy link
Owner

The requirement that the model be named "User" was pre-existing, I was just taking this opportunity to reinforce it. The name must be "User" currently becuase of hard coded reverse relations with the Group model. However, I can look into removing this restriction completely. If I can, then I'll pull this PR.

tanderegg added a commit that referenced this pull request Feb 27, 2014
Don't restrict user model name and fix travis python3 build
@tanderegg tanderegg merged commit 0a262f5 into tanderegg:develop Feb 27, 2014
tanderegg pushed a commit that referenced this pull request Feb 27, 2014
removing the spaceless tags as it mucks with html output
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants