Hi Michael,
> This should only be needed if you did not do what Malcolm called "Simple
> backwards compatibility", i.e. to set {% autoescape off %}.
>
> So, am I right that you didn't put such a {% autoescape off %} tag in your
> root template? Then you have to examine whether you use any html fragments
> in your template variables.
You're right, I didn't.
In my particular case, it is a better option to use autoescape off, so
I've switched to that instead of using safe.
Here's my base.html now:
{% autoescape off %}
{% block breadcrumbs %}
<a href="{% url homepage %}">Home</a>
{% endblock %}
{% endautoescape %}
I guess a "DRY-alert" didn't go off in my head when I thought of
adding safe to all those block.super's.
- Josh
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
