On Mon, 2008-03-31 at 04:40 -0700, Marc Garcia wrote: > I was thinking in giving a option on field definition, to make it safe > on all templates at same time. Anyway using safe filter as you > proposed is clearer than my initial solution.
The slight problem you're running up against here is that Django doesn't have an "HTML" field. For a normal text field, it just holds the data and tries to stay clear of saying how it should be represented in the final presentation. People have asked for the ability to add a "this text is always safe" marker to the field definition for TextField in the past. It hasn't developed a huge positive following, though. Personally, I strongly dislike encouraging adding random presentation-specific information to model fields, so I'm not advocating this route. I'm also not sure at this point that we have enough experience with auto-escaping to know whether there are some hidden bad practices that we might fall into with this route. One alternative is to create a custom field that is inherited from TextField, but has a __get__ method that returns the content wrapped in a mark_safe() call. So you're essentially creating an HTMLField for your own use. Regards, Malcolm -- Everything is _not_ based on faith... take my word for it. 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 -~----------~----~----~----~------~----~------~--~---
