On Thu, Oct 14, 2010 at 5:58 PM, Sithembewena Lloyd Dube
<zebr...@gmail.com> wrote:
> Hi all,
>
> I just installed django-forum (http://code.google.com/p/django-forum/) in my
> Django 1.2.3. project and all went well (admin) until I got CSRF errors
> while trying to load a new forum I created in the admin.
> I added @csrf_protect tags to the forms of the pages concerned and also made
> sure to have the CSRF Middleware in settings.py - still no joy.
>
> On the Issues tab of the dango-forum project, the author/s state that this
> is a known problem with no plans to rectify as Django 1.2 is not supported.
>
> What would be an ideal way to handle this problem? The rest of the app seems
> like just what I need.
In almost all cases, updating to provide CSRF requires exactly one
thing - that you find every <form> tag in your templates, and you put
a {% csrf_token %} right after it.
If the authors of the app are saying that they're not going to update
to support Django 1.2, and you think that the app is otherwise
worthwhile, I would suggest preparing a patch for them and submitting
it for their consideration. They've got an open ticket logging that
this is a known problem [1], and to my reading, it's a matter that is
on the plan to be resolved, it just hasn't been resolved *yet*. If you
provide the patch, that might accelerate matters.
[1] http://code.google.com/p/django-forum/issues/detail?id=91
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
