Changes between Version 147 and Version 148 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
12/21/2007 05:08:56 PM (7 years ago)
Author:
lukeplant
Comment:

Small clarification about autoescaping.

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v147 v148  
    446446Also note that the {{{escape}}} filter's behaviour has changed slightly (it is only applied once and only as the last thing done to the output) and new filters {{{force_escape}}} and {{{safe}}} have been introduced if you need them.
    447447
    448 If you never intentionally insert raw HTML into your context variables, no changes will be needed.
     448If you never intentionally insert raw HTML into your context variables, and if all your templates are supposed to output HTML, no changes will be needed.
    449449
    450450If you have any variables in your templates that do insert raw HTML output and you do ''not'' want this output automatically escaped, you will need to make some changes. There are two approaches here, the first one being the easiest (but not the safest) and can act as a temporary step whilst you do the more detailed second step.
Back to Top