id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
6907	Rethink the silent eating of exceptions in templates	miohtama	nobody	"Currently, it is impossible to attach a custom logger/stack trace printer which would print a traceable error message when a call from template files. 

E.g. in the following template call:

{{{
<p>{% get_free_comment_count for webbridge.BlogAllEntry event.blog_all_entry.id as comment_count %} comments</p>
}}}

We cannot know the reason causing ''get_free_comment_count'' fail - we have only empty string printed. The only way to debug this is to put some try...except and logging code to Django internals (comments.DoCommentCount in this case).

Django should provide a hook to 1) print exceptions fallen to templates as a normal debug page when DEBUG=True 2) provide a hook to catch these exceptions and log them in a custom way. 

Have you been planning anything related to this?




''''"	New feature	closed	Template system	dev	Normal	fixed	exception template silent failure		Accepted	0	0	0	0	0	0