#2600 closed defect (fixed)
[patch] Development server doesn't serve custom admin media
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Core (Other) | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If the ADMIN_MEDIA_PREFIX is set to a relative path containing customised files, and the urls.py configured to serve static files from that path, the development server (django-admin runserver) will still serve the standard admin media from django/contrib/admin/media/
The attached patch adds a setting SERVE_DEFAULT_ADMIN_MEDIA (default True), which if False will prevent this behaviour.
Attachments (2)
Change History (6)
by , 18 years ago
| Attachment: | SERVE_DEFAULT_ADMIN_MEDIA.diff added |
|---|
comment:1 by , 18 years ago
| Summary: | [patch] Development server doesn't serve custom admin media → Development server doesn't serve custom admin media |
|---|
Hmmm, I think introducing a setting for this would be overkill, because it's such an edge case. I would be more comfortable with an option to manage.py runserver, such as manage.py runserver --no-admin-media or something. Would you be willing to contribute a patch that does that?
(Removing the [patch] designation.)
by , 18 years ago
| Attachment: | admin_media_path.diff added |
|---|
patch that adds --adminmediapath setting to manage.py
comment:2 by , 18 years ago
| Summary: | Development server doesn't serve custom admin media → [patch] Development server doesn't serve custom admin media |
|---|
Apart from not using a 'settings' setting, this patch has different semantics: the option lets you specify the path to use instead of the default.
comment:3 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
patch