Closed Bug 789965 Opened 13 years ago Closed 13 years ago

Update zadmin's media to Django 1.4

Categories

(Marketplace Graveyard :: Code Quality, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED FIXED
2013-01-31

People

(Reporter: robhudson, Assigned: spasovski)

Details

(Whiteboard: u=admin p=2)

We upgraded to Django 1.4, but the django admin media assets haven't been updated for quite some time. It'd be slick to copy the admin's media assets to a self-contained directory that we then build with our build scripts. This will also make it easy to update them as it's a simple copy from Django's sources.
Blocks: 789501
I looked into this once and found the media in media/css/zamboni, but it wasn't clear to me how that was created or generated and feared overwriting something important. Anyone have historical knowledge of this?
Davor probably knows
Assignee: nobody → dspasovski
Priority: -- → P4
Target Milestone: --- → 2013-01-10
Target Milestone: 2013-01-10 → 2013-01-17
Target Milestone: 2013-01-17 → 2013-01-24
Target Milestone: 2013-01-24 → 2013-01-31
Whiteboard: u=admin p=1
Images are not fixed unfortunately: http://cl.ly/image/0n1p0k1e2v29/o I'd hate to use staticfiles: https://docs.djangoproject.com/en/1.4/ref/contrib/staticfiles/ We might just want to do something like this: https://docs.djangoproject.com/en/1.4/howto/deployment/wsgi/modwsgi/#serving-the-admin-files Maybe one of the djangonauts can enlighten me!
Whiteboard: u=admin p=1 → u=admin p=2
No longer blocks: 789501
We can track a better solution for this elsewhere...I am not happy with the splicing of base.css either. https://github.com/mozilla/zamboni/commit/a9a0bd4
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
This does not fix the icons at all: http://cl.ly/image/283a2N35030S They're still missing And this 100% breaks the Featured Admin tool: http://cl.ly/image/272Y14281S28 Please revert :-)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Allan can you take a look at: http://cl.ly/image/0Z3l3v1G2z0D seems the XHR is throwing a 500 and the CSS changes made should not have caused this.
Also @cvan the broken images are <img> elms. Not saying my commit didn't break that but I am not sure how.
(In reply to Davor Spasovski [:dspasovski] from comment #8) > Also @cvan the broken images are <img> elms. Not saying my commit didn't > break that but I am not sure how. Yes, but that's what this bug is all about
looks like this is bug 843801
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Comment 9 still applies. Lots of confusion over this bug lol.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.