mirror of
https://github.com/django/django.git
synced 2025-07-24 05:36:15 +00:00
Fixed #21221 -- Made form Media and static template tag use staticfiles if installed.
This commit is contained in:
parent
6be9589eb3
commit
cf546e11ac
34 changed files with 145 additions and 144 deletions
|
@ -26,7 +26,7 @@ In your custom ``change_form.html`` template, extend the
|
|||
.. code-block:: html+django
|
||||
|
||||
{% extends 'admin/change_form.html' %}
|
||||
{% load admin_static %}
|
||||
{% load static %}
|
||||
|
||||
{% block admin_change_form_document_ready %}
|
||||
{{ block.super }}
|
||||
|
@ -65,7 +65,7 @@ namespace, just listen to the event triggered from there. For example:
|
|||
.. code-block:: html+django
|
||||
|
||||
{% extends 'admin/change_form.html' %}
|
||||
{% load admin_static %}
|
||||
{% load static %}
|
||||
|
||||
{% block admin_change_form_document_ready %}
|
||||
{{ block.super }}
|
||||
|
|
|
@ -285,11 +285,16 @@ following requirements are met:
|
|||
* the :setting:`STATICFILES_STORAGE` setting is set to
|
||||
``'django.contrib.staticfiles.storage.ManifestStaticFilesStorage'``
|
||||
* the :setting:`DEBUG` setting is set to ``False``
|
||||
* you use the ``staticfiles`` :ttag:`static<staticfiles-static>` template
|
||||
tag to refer to your static files in your templates
|
||||
* you've collected all your static files by using the
|
||||
:djadmin:`collectstatic` management command
|
||||
|
||||
.. versionchanged:: 1.10
|
||||
|
||||
In older versions, you also had to use
|
||||
``{% load static from staticfiles %}`` in your template. The
|
||||
:ttag:`static` template tag (``{% load static %}``) now uses
|
||||
:mod:`django.contrib.staticfiles` if it's installed.
|
||||
|
||||
Since creating the MD5 hash can be a performance burden to your website
|
||||
during runtime, ``staticfiles`` will automatically store the mapping with
|
||||
hashed names for all processed files in a file called ``staticfiles.json``.
|
||||
|
@ -331,43 +336,6 @@ If you want to override certain options of the cache backend the storage uses,
|
|||
simply specify a custom entry in the :setting:`CACHES` setting named
|
||||
``'staticfiles'``. It falls back to using the ``'default'`` cache backend.
|
||||
|
||||
.. currentmodule:: django.contrib.staticfiles.templatetags.staticfiles
|
||||
|
||||
Template tags
|
||||
=============
|
||||
|
||||
static
|
||||
------
|
||||
|
||||
.. templatetag:: staticfiles-static
|
||||
|
||||
Uses the configured :setting:`STATICFILES_STORAGE` storage to create the
|
||||
full URL for the given relative path, e.g.:
|
||||
|
||||
.. code-block:: html+django
|
||||
|
||||
{% load static from staticfiles %}
|
||||
<img src="{% static "images/hi.jpg" %}" alt="Hi!" />
|
||||
|
||||
The previous example is equal to calling the ``url`` method of an instance of
|
||||
:setting:`STATICFILES_STORAGE` with ``"images/hi.jpg"``. This is especially
|
||||
useful when using a non-local storage backend to deploy files as documented
|
||||
in :ref:`staticfiles-from-cdn`.
|
||||
|
||||
If you'd like to retrieve a static URL without displaying it, you can use a
|
||||
slightly different call:
|
||||
|
||||
.. code-block:: html+django
|
||||
|
||||
{% load static from staticfiles %}
|
||||
{% static "images/hi.jpg" as myphoto %}
|
||||
<img src="{{ myphoto }}" alt="Hi!" />
|
||||
|
||||
.. admonition:: Using Jinja2 templates?
|
||||
|
||||
See :class:`django.template.backends.jinja2.Jinja2` for information on
|
||||
using the ``static`` tag with Jinja2.
|
||||
|
||||
Finders Module
|
||||
==============
|
||||
|
||||
|
@ -390,8 +358,10 @@ files:
|
|||
which adds :setting:`STATIC_URL` to every template context rendered
|
||||
with :class:`~django.template.RequestContext` contexts.
|
||||
|
||||
- The builtin template tag :ttag:`static` which takes a path and
|
||||
urljoins it with the static prefix :setting:`STATIC_URL`.
|
||||
- The builtin template tag :ttag:`static` which takes a path and urljoins it
|
||||
with the static prefix :setting:`STATIC_URL`. If
|
||||
``django.contrib.staticfiles`` is installed, the tag uses the ``url()``
|
||||
method of the :setting:`STATICFILES_STORAGE` instead.
|
||||
|
||||
- The builtin template tag :ttag:`get_static_prefix` which populates a
|
||||
template variable with the static prefix :setting:`STATIC_URL` to be
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue