#28526: Remedy verbose, often unhelpful undefined tempate variable logging
------------------------------------------------+------------------------
Reporter: Tim Graham | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Template system | Version: master
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
As [https://groups.google.com/d/topic/django-
developers/zdULZcmAWNw/discussion discussed on django-developers], ticket
#18773 added logging of undefined template variables in Django 1.9
[dc5b01ad05e50ccde688c73c2ed3334a956076b0], however, I've seen several
reports of users finding this logging more confusing than helpful. For
example, [https://groups.google.com/forum/#!topic/django-
users/6Ve9dcv23sI/discussion admin templates log errors about missing
is_popup variables] which is how the template are designed (is_popup is
only in the contexts of pop ups) and the `TECHNICAL_404_TEMPLATE` (now
`django/views/templates/technical_404.html`) also logs errors (#26886)
without any obvious solution about how to prevent that. Also #28516 shows
the many warnings logged for an admin changelist page.
--
Ticket URL: <https://code.djangoproject.com/ticket/28526>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.17e3939318edfff83f53388852c324d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
