#22109: clarify difference between relative and absolute STATIC_URL -------------------------------------+------------------------------------- Reporter: cjerdonek | Owner: nobody Type: | Status: new Cleanup/optimization | Version: 1.6 Component: Documentation | Resolution: Severity: Normal | Triage Stage: Keywords: static_url,static | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 1 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by cjerdonek): I can try to find time to come up with a patch. In the meantime, to say a little more about what I'm getting at, it turns out that the point I was trying to raise in this issue is discussed in the Django documentation, though not in the `STATIC_URL` documentation itself (which is supposed to contain details about the setting). Namely, the point is discussed [https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/ here] in the "The staticfiles app" section. For example, it says, "This helper function will only work if `DEBUG` is `True` and your `STATIC_URL` setting is neither empty nor a full URL such as http://static.example.com/." In other words, the functionality I'm referencing only becomes enabled when `STATIC_URL` is a relative URL reference (i.e. does not contain the host name, etc). -- Ticket URL: <https://code.djangoproject.com/ticket/22109#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 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/067.ba3eb3622a3892868d78da66ab6cc6b4%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.