#11909: Django 'eating up' method errors in templates
---------------------------------+--------------------------------------
Reporter: wojteks | Owner: nobody
Type: Uncategorized | Status: closed
Component: Template system | Version: 1.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by PetrDlouhy):
There is hacky way with assigning handler object to the
`string_if_invalid` variable, which work quite well in my oppinion:
http://stackoverflow.com/questions/4300442/show-undefined-variable-errors-
in-django-templates
The main problem is, that there is not enough information for complete
error report. So I suggest adding an official invalid string handler,
which would have at least the `request`, template path and the faulty
string as parameters.
It could be taken even further, and set of default handlers could be
implemented in Django with levels like `silent`, `warning` and
`exception`, where the `silent` handler would be the default.
--
Ticket URL: <https://code.djangoproject.com/ticket/11909#comment:9>
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/065.c02e074582f1b53960197451df999fd4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
