#24452: Staticfiles backends using HashedFilesMixin don't update CSS files' hash when referenced media changes -------------------------------------+------------------------------------- Reporter: Paul McLanahan | Owner: Paul | McLanahan Type: Bug | Status: closed Component: contrib.staticfiles | Version: 1.7 Severity: Normal | Resolution: fixed Keywords: | Triage Stage: Ready for | checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Tim Graham): I'm wondering if there should be some release notes and documentation about this considering that it sort of looks like a bug to the untrained eye. Should there really be multiple versions of some admin CSS files that differ only in their hash (base.css, fonts.css, widgets.css)? Only forms.css has different hashed files with difference contents. If a project is uploading static files to some remote storage, the increased disk usage and upload time due to the increased number of files could be a nuisance. About "the manifest lists the final filename and any intermediates could be dropped." -- is a ticket needed for this enhancement? -- Ticket URL: <https://code.djangoproject.com/ticket/24452#comment:19> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/068.515a05a4fb9a3dc7f1251602462c8f66%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.