#24452: Staticfiles backends using HashedFilesMixin don't update CSS files' hash
when referenced media changes
-------------------------------------+-------------------------------------
     Reporter:  pmclanahan           |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  contrib.staticfiles  |                  Version:  1.7
     Severity:  Normal               |               Resolution:  duplicate
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by pmclanahan):

 Hi timgram,

 I did see that one, but it is dealing with a different issue. I've
 actually not seen that problem. For me the hashed image names are being
 correctly updated in the CSS. It's the name of the CSS file itself that
 needs to update in my case. What I'm suggesting is that a change in a
 media file contained in a CSS file should result in a difference in the
 hashed content value of the CSS file itself.

 It's possible that the fix for #22353 could be included in the fix for
 this one or vice versa, but I do think that these problems are distinct.

--
Ticket URL: <https://code.djangoproject.com/ticket/24452#comment:3>
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/068.b29da63ce90ec88077df130ba36c6bb6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to