#24960: Blank pages due to {{ block.super }}
-------------------------------------+-------------------------------------
Reporter: srkunze | Owner: nobody
Type: Bug | Status: new
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: block.super blank | Triage Stage:
pages | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by srkunze):
Are you sure that render_to_string(...) works as intended here? Should a
view not return a HttpResponse?
We used Django 1.6. We upgraded to Django 1.8 and it seems as if the error
is returned properly now.
We looked into the corresponding Django source code and found that Django
catches more errors as before and re-raises them. That approach seems a
bit error especially when using custom exceptions.
Don't you think that a check whether a context variable is callabed/has
attribute/has dictionary key should be handled not by trail and error but
by a check-before-do?
--
Ticket URL: <https://code.djangoproject.com/ticket/24960#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.a242678f5d150fdf1b2c989b93b67a3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
