I am getting a template error during rendering, which I think would be easy to fix if I could just see what’s in the context that is passed into the template that is being rendered. Django’s debug error page provides a lot of information, but I’m not seeing my context anywhere. Am I missing something? Also, I am using Django-debug-toolbar, but that only seems to come up if the page successfully renders. Not being able to see the contents of the context that is passed to the template makes debugging some types of template errors hard! What do I need to do to be able to see it in this scenario? (Note that I’m not asking for a fix to my specific error, which is why I’m not providing more information about it).
Share
From the comments:
I think you need to walk up the stacktrace (in the django debug page) to actually see your context variables. I don’t understand your problem exactly. If I have a template error I can inspect my context somewhere in the traceback.
Yes, setting a “breakpoint” in django can sometimes mean just inserting a non-defined variable at the point you want to inspect. The last entry in the traceback is usually the one for this variable. It will give you all context details in the traceback of the debug page.