I was in the process of upgrading my wagtail app to Django 2.0. After resolving the on-delete errors I thought I had a working app until I went to the /admin page. The standard Wagtail admin interface has disappeared and has been replaced by the default Django admin interface. Can anyone help?
https://github.com/timcknowles/wagtailcmsdemo/tree/django2
Many thanks in advance
Your urls.py has the Django admin before the Wagtail admin, so the Django admin "wins out".
Swap the order of those two, or maybe rename the Django admin prefix to ^djangoadmin/.
Related
I finally deployed my django project to heroku but for some reason the styling of the admin page looks really ugly. I have no idea why that is.
I have built a Django application with a custom interface. It hasn't been changed in a couple of years.
These (previous) servers are running Django 3.0.8.
Recently I set up a new server, and the Django Admin interface now shows the model list in a scrolling iframe, and long tables on the right side are also scrolled independently of the page.
This server is running Django 3.2.3.
I don't like the new interface, but it more importantly it will require an extensive rewrite of our custom admin css.
Can anyone point me to information about the change, or tell me if there is a setting to disable it?
I found the answer in this Stack Overflow answer. I will leave this question up because the other answer doesn't mention iframes.
Django 3.1 added the new scrolling sidebar in an iframe.
To disable it add the following to the root urls.py file:
from django.contrib import admin
admin.autodiscover()
admin.site.enable_nav_sidebar = False
The 3.1 Release Notes say:
The admin now has a sidebar on larger screens for easier navigation. It is enabled by default but can be disabled by using a custom AdminSite and setting AdminSite.enable_nav_sidebar to False.
Reference links from the original answer:
Django 3.1 release notes
The Django admin site
I have a problem of collation between grappelli and django-constance moduls (the saving isn't working).
I'm using django-constance v.1.0.1 and cannot upgrade it because the new versions does not work with django 1.6 .
I want to disable grapelli on the constance specific page. How do I do that?
I'm currently struggling with django admin and mongodb, I found some solutions about combining django admin and mongodb, but none of them is perfectly integrated with django admin. What I need is that I can do CRUD to mongodb tables in admin site like I use MySQL.
mongonaut : besides mapping to mongodb tables, mongonaut has permissions to do CRUD, but I don't know how to integreted mongonaut into django admin index page, mongonaut has its own page and css style to do CRUD.
mongoadmin : lack of permissions management is why I skipped it.
I am new to django，could anyone tell me what is your solution to integrated django admin and mongodb, thanks a lot !
Following online tutorial, I create a very simple django blog. It seems all right, but after I log into 127.0.0.1:8000/admin/ , I can't find the place to add posts.
My django blog interface(I don't have enough reputation to add picture):
Django administration
Welcome,xxx change password / log out
Site administration
Authentication and Authorization
Groups Add Change
Users Add Change
Recent Actions
My Actions
None available.
Does anyone know why my administration interface don't have "add post"??? thanks in advance!! :)
I use:
Django 1.7
Operation: win 7 32
Seems like you haven't registered your posts model in the Django admin
https://docs.djangoproject.com/en/dev/intro/tutorial02/#make-the-poll-app-modifiable-in-the-admin
or your posts app isn't installed in your settings.py
https://docs.djangoproject.com/en/dev/intro/tutorial01/#activating-models
And the sites framework is no longer activated by default since Django 1.6
add admin.autodiscover() at urls.py. details here: https://docs.djangoproject.com/en/dev/ref/contrib/admin/