#21221: Widgets and Admin's Media should use the configured staticfiles storage
to
create the right path to a file
-------------------------------------+-------------------------------------
Reporter: Guilherme Gondim | Owner: codingjoe
<semente@…> |
Type: New feature | Status: closed
Component: contrib.staticfiles | Version: 1.5
Severity: Normal | Resolution: fixed
Keywords: staticfiles, admin, | Triage Stage: Ready for
CachedFilesMixin, media, widgets | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"20e2b228aa87f2ce6341d5e96642c53b87a87459" 20e2b22]:
{{{
#!CommitTicketReference repository=""
revision="20e2b228aa87f2ce6341d5e96642c53b87a87459"
Refs #21221 -- Added test for legacy static usage in form Media.
Before cf546e1, static files in form or widget Media were usually
wrapped with contrib.staticfiles.templatetags.staticfiles.static.
This test ensures compatibility with third-party code that's still
using this pattern.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21221#comment:22>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/097.a29869406ccd571be0f972ce688c3fe0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
