Closed
Bug 1195770
Opened 10 years ago
Closed 9 years ago
django deprecations: TEMPLATE settings
Categories
(Webtools Graveyard :: Elmo, defect)
Webtools Graveyard
Elmo
Tracking
(firefox43 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox43 | --- | affected |
People
(Reporter: Pike, Assigned: Pike)
References
Details
Once we're on 1.8 (bug 1147814), we should do the more invasive changes required by 1.8 deprecations, this bug is for template settings, https://docs.djangoproject.com/en/1.8/releases/1.8/#template-related-settings
Comment 1•9 years ago
|
||
Commit pushed to develop at https://github.com/mozilla/elmo
https://github.com/mozilla/elmo/commit/7f3b8b0e824c5b8940ecf914c0c7a785a378ef3a
bug 1195770, TEMPLATES setting instead of TEMPLATE_, deprecations.
This patch is bigger than it should be because the tests to
ensure that session_csrf is what we're using were kinda wonky.
In particular, django hard-codes that you have
django.template.context_processors.csrf on. (Used to be django.core..)
session_csrf works because it comes *after* it, and overrides the
csrf token with its own version. TIL.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → l10n
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•