On Tue, 2008-02-12 at 13:11 -0800, Jeff wrote:
> You can't raise an exception from a template short of writing a custom
> template tag that would raise an uncaught exception. It is a better
> practice to put that kind of logic in your model or view.
To give a bit more information to the original poster: the reason this
is the case is because it's often useful to just try and use a feature
on an object, rather than having to test that the feature is first
present. If the attribute or method is not present, we return the empty
string. This means you can do things like
{% if object.has_super_powers %}
Do something special
{% endif %}
and if the object doesn't have a "has_super_powers" function, the
if-check just fails quietly. For reusable templates, this is quite
powerful.
The drawback is that we cannot know the difference between errors that
you don't mind being raised and errors you want to see.
For debugging purposes in a particular template, you might want to look
at the TEMPLATE_STRING_IF_INVALID setting (but note that this is not
intended to be used in live sites, because there can be unintended
side-effects, such as the admin site showing all sorts of weird stuff).
Regards,
Malcolm
--
Remember that you are unique. Just like everyone else.
http://www.pointy-stick.com/blog/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
