-
Notifications
You must be signed in to change notification settings - Fork 367
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
Login after setup does not work with Python 2.7 #49
Comments
Do you have a different version of django installed in python2.7? |
import django; print django.get_version() yields "1.3" in both python2.6 and python2.7 |
Do you have a django 1.3 installed in your system? |
No, this django version is from seahub/thirdpart (as added to PYTHONPATH in seahub.sh). I have Django 1.4.5 installed globally on my system. |
We use a modified user module. Maybe your problem is caused by accidentally using the user app from django 1.4.5. This problem will be solved in the next release. |
Okay, thanks. I'll wait for the next release and just use python-2.6 in the meantime. |
After a fresh install (following https://github.com/haiwen/seafile/wiki/Download-and-setup-seafile-server), logging in with the admin account simply redirects back to the login page.
Installation works fine, so does starting the server using the provided scripts (seafile.sh, seahub.sh, seahub runs using gunicorn), no errors or warnings.
Log files seahub.log and seahub_django_request.log in /tmp are both empty.
Starting seahub using Django's development webserver (python2.7 manage.py runserver 0.0.0.0:8000) yields the same problem, logging in does not work and no error messages appear.
Forcing seahub to use python2.6 (by adding the line "PYTHON=python2.6" before "$PYTHON {$manage_py} run_gunicorn (...)") resolves this issue, login and everything else works.
I've tested this using the bundled seahub (the one in http://seafile.googlecode.com/files/seafile-server_1.6.1_x86-64.tar.gz) and the latest version (http://seafile.googlecode.com/files/seahub-latest.tar.gz).
The text was updated successfully, but these errors were encountered: