Dear Russell,
I don't quite understand how an error in the admin template is
different from the error in the inline template -- why one gets
silenced and another one doesn't?
Well if I am the only person who got repeatedly hit by that
particular issue, then I guess I'll have to deal with that.
On Sep 1, 10:44 pm, Russell Keith-Magee <russ...@keith-magee.com>
wrote:
> On Wed, Sep 1, 2010 at 2:03 PM, George Karpenkov
>
> <true.chesh...@gmail.com> wrote:
> > Steps to reproduce:
> > 1) Specify a custom admin class (say A) which mentions a custom inline
> > with a custom template, say "a.html"
> > 2) Write anything to "a.html" which will raise TemplateSyntaxError -
> > ie "{% extends "a.html" %}
> > 3) Observe the change_form for A. Note that you do not see any errors,
> > but instead the whole inline does not appear at all.
>
> > I find this behavior extremely confusing and annoying. Is it just a
> > bug or is there any reasoning behind that?
>
> The broad reasoning is that a partial page rendering is preferable to
> a 500 error when rendering a template. This is driven by production
> requirements -- the end user shouldn't ever see a 500 error.
>
> Admittedly, this can make template debugging difficult at times. There
> has been some discussion in the past about whether the TEMPLATE_DEBUG
> mode should be used allow for more aggressive error reporting during
> testing; however, this discussion hasn't really moved beyond the
> "vague initial discussion" phase.
>
> Yours,
> Russ Magee %-)
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
