Hi George,
I believe this is a bug since any other errors in admin (not related
to inlines) don't pass silently.
Silencing errors should always be documented, especially if error is
silenced when DEBUG is turned on.
So it's either documentation or implementation bug.
By the way, does it show 500 error page if DEBUG is on?
On Wed, Sep 1, 2010 at 1: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?
--
Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov,
MSN: bu...@live.com
--
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.
