No. There are no 0.9.1 blocker issues at this point that I'm aware of. I just wanted to make sure we're not missing anything major before we tag it.
-Chris On Mon, May 10, 2010 at 11:55 AM, Alex Robbins < [email protected]> wrote: > 1) Sorry, just found the issue in bitbucket where you guys already > discussed this. > > 2) Are there any issues blocking 0.9.1 right now that we can help out with? > > Alex > > > > On Mon, May 10, 2010 at 11:49 AM, Chris Moffitt <[email protected]> > wrote: > > Yep. Satchmo will not work with the new CSRF protection. As far as I > know, > > everything else will work with Django 1.2 so you just can't turn on the > new > > middleware and have it all work. > > > > My intent is to get 0.9.1 out the door and then the next release would > > require Django 1.2 and would be modified to use the new csrf. > > > > I can't think of any better way to do things. > > > > -Chris > > > > On Mon, May 10, 2010 at 11:32 AM, Alex Robbins > > <[email protected]> wrote: > >> > >> I'm running django 1.2rc1 for one of my projects and the new CSRF > >> protection is breaking Satchmo a lot. > >> > >> Docs about new csrf protection here: > >> http://docs.djangoproject.com/en/dev/ref/contrib/csrf/ > >> > >> Basically, the new recommended CSRF protection strategy involves > >> adding a middleware and a context processor, then adding a {% > >> csrf_token %} template tag to every form that posts. Also, you can add > >> the csrf_protect decorator to your own views, to protect against users > >> not adding the middleware. > >> > >> Right now, none of the forms that post work with django 1.2, if the > >> user adds the csrf middleware like they are supposed to. > >> > >> The major problem is that I don't think the changes are backwards > >> compatible. We'd need to require django 1.2. > >> > >> Anyway, anyone have thoughts on how we can move forward with this? > >> > >> Alex > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Satchmo users" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]<satchmo-users%[email protected]> > . > >> For more options, visit this group at > >> http://groups.google.com/group/satchmo-users?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Satchmo users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<satchmo-users%[email protected]> > . > > For more options, visit this group at > > http://groups.google.com/group/satchmo-users?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<satchmo-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/satchmo-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
