Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

455
Views
Django Admin Styling corrupted

I recently made some changes to my django site, one big one being upgrading from Django 2.2 to 3.1. Now my admin site styling is all messed up. I can't figure out what went wrong or how to fix. Any pointers would be appreciated! See image of what it looks like after update.... The main home page for admin looks fine, but when I click on one of the models to view, the formatted is definitely not correct. Also, some not all, of my images on the site are saying 404 not found... enter image description here

enter image description here

over 4 years ago · Santiago Trujillo
4 answers
Answer question

0

It looks like your browser is caching the CSS / JS from the old version, you can clear your cache and reload. In chrome use ctrl + shift + r to reload.

over 4 years ago · Santiago Trujillo Report

0

I was facing the same problem, First I thought it was a Cache issue but it wasn't. I checked the page source and found a css file being applied to the page which wasn't even present on my drive.

In my case the file was: static/admin/css/nav_sidebar.css

So I created new file in static/admin/css named nav_sidebar.css, then copy pasted the code which I got from page source and added "display:none;" in the #nav-sidebar section(line:34) and [dir="rtl"] #nav-sidebar section(line:45 in my case).

You can find the Original code here by using Google Chrome's inspect tool. Where to find the code

over 4 years ago · Santiago Trujillo Report

0

I had the same issue after bumping django from v3.0 to v3.1. I run python manage.py collectstatic to update css which solved my issue

over 4 years ago · Santiago Trujillo Report

0

I think the other answers here are necessary, but I'll add one more: You might have to bust caches in your server itself. In our example, nginx was configured to provide really long caches to our static files, so we just had to reset it to make changes come through.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!