#29446: Include template context in error page when relevant
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner: Bhupesh
| panwar
Type: New feature | Status: assigned
Component: Error reporting | Version: 2.0
Severity: Normal | Resolution:
Keywords: template debug | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by Shai Berger):
First of all, I apologize for missing the calls for more details all these
years ago.
Somehow, I only saw them now.
Second,
Replying to [comment:7 Bhupesh panwar]:
> So i have a solution that can we create an middleware.py file that logs
template context when error happens
I think it would be more helpful to put the context in the error page with
all the other relevant info, but if you can pick the right context and put
it in the log, then IMO:
- It's a good first step towards putting it on the page
- It's already helpful in and of itself
--
Ticket URL: <https://code.djangoproject.com/ticket/29446#comment:8>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701956d02f203-8f030017-761b-4b93-bd2d-b4722fb5682a-000000%40eu-central-1.amazonses.com.
