Upgraded Django 1.8 to 1.11, getting lots of VariableDoesNotExist errors
See original GitHub issueThe keys it’s trying to look for include:
- in
pipeline/js.html
:async
defer
- in
pipeline/css.html
:title
charset
The keys available are:
url
media
(only available inpipeline/css.html
type
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Error loading admin page after upgrading to django-1.11
So previously, I was using django-1.8 version & I am in the process of upgrading to django-1.11. When I load my /admin page,...
Read more >Upgrading templates to Django 1.8
A new setting was introduced in Django 1.8: TEMPLATES . All existing template-related settings were deprecated. During the deprecation period, Django will ...
Read more >Migrating Django 1.6 to 1.11. Field Notes | by Jim Simon
This deployment strategy was not planned, but came as a solution to having to large of a delta between Django 1.6 in Django...
Read more >Release Notes - Django REST framework
Release Notes. Versioning. Minor version numbers (0.0.x) are used for changes that are API compatible. You should be able to upgrade between minor...
Read more >@media, MathML, and Django 1.11: MDN Changelog for May ...
They updated submodules for the 1.7 effort, and switched to hashed requirements files for 1.8. A lot of codebase and process improvements were ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The most prominent place where this always appears in pipeline is
pipeline/css.html
All 3 variables
media
,title
andcharset
don’t have default values and raise aKeyError
in the renderer. Adding a default value in pipeline’s render context will resolve this, and most probably reduce some noise (which could result in a slight performance boost).I can submit a PR if adding defaults sounds reasonable, but not sure what I would go with, probably either empty string or
None
, what do you say @hsiaoyi0504 ?Solution for us was to create default “extra content” objects and add it to all of our stylesheets and scripts, e.g.:
@asfaltboy’s suggested solution would’ve been great though.