Yep, I reverted to revision 6669 (one before the autoescape update) and the problem went away. When I re-updated to the current revision the problem appeared again. Maybe I'll file a bug report
On Nov 19, 3:02 pm, RajeshD <[EMAIL PROTECTED]> wrote: > > Does this have something to do with the autoescape revisions that were > > just put out? I'm working off of the latest revision if that's of any > > help. Thanks. > > It's likely. If you've the time, perhaps revert to a revision just > prior to when the autoescape changes were committed and report back > here if the problem goes away (or even better, open a ticket.) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
