Re: How about adding a noop {% csrf_token %} tag to the Django 1.1 branch

[SmileyChris]

Bah! Yes, just like that.

However, it would be nice to release a 1.1.2 containing this for those
who use released versions as opposed to svn branches before 1.2 hits.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: How about adding a noop {% csrf_token %} tag to the Django 1.1 branch

[Russell Keith-Magee]

On Fri, Feb 19, 2010 at 8:34 AM, SmileyChris  wrote:
> I was thinking that it would help third-party apps to be able to work
> across both 1.1 and 1.2 installations without workarounds if the 1.1
> branch had a csrf_token tag, just to stop templates choking with a
> "Invalid block tag: 'csrf_token'" message.
>
> Does this fit within the policy for supporting old versions? Seemed
> like a good idea to me anyway.

You mean... something like:

http://code.djangoproject.com/changeset/11674

??

:-)

Russ %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.