I am following the django docs tutorial to build a polls app i just created the superuser but whenever i try to access the admin page the server quits on its own with no error message that's in both chrome and firefox i'm on windows
You need to check your version numbers of Django and Python to ensure compatibility. There is a problem with Django 3.0 (the latest version) and with version 3.7.0 of Python and potentially its older versions as well.
Try updating your Python installation to see if that fixes the issue.
Related
i currently work on a project , i want to build it with django 3.0.2 python version 3.7, but after running the server
python manage.py runserver
it will quit immediately when i try to access the admin url without raise any error , and even i havn't do any changes in my new app ,and also tried django version 2x it worked as i expected .
i tried to remove and reinstall django , but still give the same output ,
thanks for advice
You're very likely to be running into this issue:
Python 3.7 crashes after trying to visit admin page on Windows and MacOS.
The solution is to upgrade to Python version 3.7.1 or higher.
Has anyone been successful in being able to run the Django-wiki app on Django 3.0.1/2 project?. On their docs page, it says that v0.5 supports Django 3.0, but when I try to install it via pip, it downgrades my Django version from 3.0.1 -> 2.2.9. In their requirements file, I see this:
Django>=2.2,<3.0
If someone is able to get it working, it'd be great if they can point me to some instructions.
I'm a noob trying to learn Django for the first time, I created a project in a virtualenv on Windows 10. It worked well in the beginning where I was able to login to the admin section after running '''python manage.py runserver'''
But now when I run the same command I'm able to see the Django landing page but as soon as I try to hit http://localhost:8000/admin/ or http://127.0.0.1:8000/admin the server automatically disconnects and I get the "This site can’t be reached" error on Chrome.
I tried changing the port number by running python manage.py runserver 0.0.0.0:8001 but it didn't work. I tried to check if the port (8000) is currently in use by running the cmd (as an admin) netstat -a -b but couldn't find any issues.
The server just quits without any error message
Edit: Currently using Python 3.7.0 and django-3.0.1
There's a ticket about this issue: https://code.djangoproject.com/ticket/31067.
This seems to be a bug in Python 3.7.0, and appears to be fixed in Python 3.7.1. It's still unknown what the exact trigger is for this bug.
Since Django officially only supports the latest patch release of a Python series, this won't be fixed in Django. You can either upgrade your Python version to the latest patch release of 3.7, or downgrade Django to 2.2.
It's a Django 3.0 issue as I've seen. There are so many issues on GitHub, regarding this error.
You may try downgrading to Django 2.* versions for now. Version 2.1/2.2 works fine.
I was working on a Django project in version 2.0, but my client was unhappy about it as he wants that project to be made with Django 1.1.3. So, I switched back to old version and tried to setup the project on that version but was unable to do so.
After that, I created a new project in Django 1.1.3 and created a Django app too. I tried to run command python manage.py syncdb but I got this error message:
Error: No module named messages
What's the issue? I am not able to find Django 1.1.3 documentation on this.
The module django.contrib.messages is available only for Django versions >= 1.2, unfortunately.
You could maybe convince your client to switch to 1.2.X, or write your own messages as part of your server's responses, and create your own client-side message renderer.
I am trying to use Django Facebook to register users in my app.
Right now I am in local develoment and after giving persmissions to the app in Facebook and following all indications in readthedocs, I get the next error:
Please specify a Facebook app id and ensure the context processor is enabled
Django version: 1.8
Python version: 3.8
This was an error django-facebook code, which has been fixed. Make sure you are using django-facebook 6.0.4 or later. Even if the latest model is not yet shipped you can get it by doing pip install git+git://github.com/tschellenbach/Django-facebook.git