> Given that both MEDIA_PREFIX and ADMIN_MEDIA_PREFIX are easily set in > settings.py, I can't see the issue.
Having sensible default settings is a worthy goal for a lot of reasons. > My standard setup sets > ADMIN_MEDIA_PREFIX to /admin-media/ As this exemplifies, having something other than /media/ for the ADMIN_MEDIA_PREFIX makes a lot of sense. It takes someone new to Django quite a while to form an opinion on that, though. if / admin_media/ really is a better default, then it's not worth discounting simply because it's possible to change the value yourself. -wes On Sep 11, 11:51 am, Brett Parker <[email protected]> wrote: > On 11 Sep 06:33, drozzy wrote: > > > > > Reference: > >http://docs.djangoproject.com/en/dev/howto/static-files/#how-to-do-it > > > I propose we change the admin's media prefix from "media" to > > "admin_media". > > When I was just starting out with Django, this was a major problem, as > > I could not figure out why my static media did not display correctly. > > > Admin should stay out of the way as much as possible, and it's media > > is currently very tightly bound with django. But that is another > > discussion... > > Given that both MEDIA_PREFIX and ADMIN_MEDIA_PREFIX are easily set in > settings.py, I can't see the issue. My standard setup sets > ADMIN_MEDIA_PREFIX to /admin-media/, the runserver will happily use this > setting, and my live environment knows what to serve for that too. Can't > see why you'd need to change the django default... > > -- > Brett Parker --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
