#33324: Missing static file errors with manifest storage are particularly hard
to
debug (no error email)
-------------------------------------+-------------------------------------
Reporter: Michael | Owner: nobody
Type: Uncategorized | Status: closed
Component: contrib.staticfiles | Version: 3.2
Severity: Normal | Resolution: needsinfo
Keywords: static manifest | Triage Stage:
storage | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
Hi Michael.
I'm likely being slow here but, I'm struggling to see exactly what the
issue is you're encountering here.
I'm expecting manifest errors to come up during the `collectstatic` run,
rather than in the request-response cycle.
Also, debug error pages are only used when `DEBUG=True`, so exactly when
file names are not hashed.
Can you put a sample project together that shows the issue exactly? — It's
much easier if I can see it in play, rather than trying to guess what
you're seeing.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/33324#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.6536450a0f4766d7972fd47cb956749a%40djangoproject.com.
