#django

I am using django rest framework and I need to add put functionality in a viewset, what do

abyss42: You need custom router.

abyss42: Or use decorator.

abyss42: @action(methods=['PUT']) should do the trick.

jtiai: but i have a class based viewset, i think what you are talking about only applies to method based ones

abyss42: Nope. See http://www.django-rest-framework.org/api-guide/...

abyss42: @action and @link decorators are specially for viewset class. Though they are limited to object handling. If you need something that doesn't take pk of object in you need to do custom router.

object handling as in just GET, not updating the object?

abyss42: Nope, @link and @action will generate urls like: /<base>/{pk}/action_name

jtiai: so i have to implement put method by myself when i use django rest framework? In tastypie it came out of the box

abyss42: Err... Of course you need to write code that does something... Or what you mean?

jtiai: rest framework seemed to do get post delete out of the box

abyss42: default viewset router does have actions for basic CRUD.

jtiai: yea thought so

abyss42: rest framework also supports PATCH which is really nice, no need to send whole object over.

I know it's slightly OT, but anyone experienced in configuring graphite? I'm getting a long delay between when the stats get sent to carbon-cache, and when they show up in the webapp. Suggestions?

So, I'm trying to get some custom forms working, and getting CSRF errors up the wazoo. Anyone out there willing to provide a little help?

When you subclass a MPTTModel can you automatically get the tree manager?

I've added the token to the <form>, the middleware is active, and the cookie is getting generated.

But I still get a 403 CSRF error.

recoil42, how are you rendering your template?

With render()

The form is custom, because I'm varying the number of fields with js.

It isn't generated with a Django Form.

are you using a csrf decorator?

try that

from django.views.decorators.csrf import csrf_protect

then use @csrf_protect on the desired view

So what do people use now instead of django-registration?

Haven't found a reason to switch away from it yet.

Fair enough. As long as it supports 1.7 I'll be happy.

@zlio: No luck with that approach.

bah.. im sorry, I can't do much :(

My generated form source right now: http://cl.ly/image/0f1S1A0v0Q19

Here's an abridged view of my view, mind you, I have no idea what I'm doing at this point. http://cl.ly/image/2H0N0O0j2L1g

Just trying to get the damn thing not spitting out errors.