#django

modelform

why are you touching the modelform?

gah

I came into this late

<tindus> uh, there is no request object in the ModelForm

mcspud: no, there's no request on the modelform.... so what?

the code I gave you goes on the view

where you already have a form_valid method

mcspud

Its a Serializer instance

FunkyBob: Yeah, I know, but I think hes confused :) (I came onto this late)

because I'm passing like this: 'user': UserSerializer(data=user)

bed666: great, thats the right way to do it

Whats the error now?

tindus: please excuse my manner... I'm a little tired and stressed from sitting in a hospital all y/day as my son got his appendix out

FunkyBob: is he ok?

mcspud: yep

Good stuff

how old?

really? mm look the complete code: https://dpaste.de/pQcm

the error is : ValueError: Cannot assign "UserSerializer(data=<User: d>)": "Question.user" must be a "User" instance.

oh, no problem, FunkyBob

your knowledge is worth your curmudgeonliness ;)

tindus: as I said... rip all that shit out of your form.. and to it in the view's form_valid method

yes, mcspud, that was my point, that request isn't passed to modelForm. Not in scope, or however you'd describe it

tindus: not needed in the form...

well, in another class, I have a required foreign key. I don't want to even show it to the user, so that's the way I figured out to not have the user have to pick himself from a list of users.

...

"another class" ... ooh... all mysterious

bed666: can you post your model code please

of what

question?

its very big

I made a form that doesn't have that item, and I stored the current user as a _user "loose" variable on the form object that is created. (the unbound form?)

yeah

thats ok

the thingy class

tindus: ... again... move your work into the view's form_valid method

members list all the movies, books, &c they have, and other people in their club(s) can peruse them and ask to borrow them

mcspud https://dpaste.de/qexr

so, a member who adds a thingy doesn't need to select themselves from a pop-down list. The thingy should get created with the current user as the owner

hello o/

FunkyBob, hi

FunkyBob, which is the better approach to go; uWSGI+Nginx or Gunicorn+Nginx ?

d3prof3t: depends

tindus: You said above if a member creates a club, then they should be added to that club right

If so, this is pretty much what you want: https://dpaste.de/CRZ3

FunkyBob, hm, on?

mcspud: given tindus has already linked to their class-based view code...

mcspud: nad I already gave sample code showing how to do it..

mcspud: we can only conclude tindus is ignoring the solution

FunkyBob: didn't see that. I just wanted to stop you committing suicide with frustration :)

yours is superior, FunkyBob

LOL

mcspud: not really... it just fits with what you already have

i would love to use form_valid() to do all this kind of stuff

FunkyBob: ?

but sometimes, an object has required fields, so how can your form object create a model object with missing stuff?

in other words, when does a form object become an instantiated model object which MUST have required info?

FunkyBob: I think you meant tindus perhaps.

anyway, I think a form object gets created "unbound", sent via "GET", filled in with info back to django via "POST"...

does it need to have required fields at this point?

does what I believe accurately model reality?

tindus: unbound means it wasn't passed data...

your idea of when the objects are created and persists is warped

lots of my ideas are, but about this:

GET request comes in, unbound form is created, template is renderd, response is sent to browser. end

POST request comes in, bound form is created, validation is checked...

ModelForm creates a form class, right? but it has no data in it when GET presents it to the user?

it has no data bound to it when it is not passed data t obe bound to

in a CreateView, it does not pass data to bind in a GET request....

don't conflate these two things

tindus - When you "return" the HTML response in a GET request, the "unbound form" is destroyed/garbage collected

let me read what you have so far, and digest.

remember, you're dealing with two HTTP requests... the GET and the POST

both are wholely independant

so, bound form != valid data

correct... bound form simply means it was passed data

it could be invalid data

there are two different things entirely

bound form just means you can't edit the data in the extant form object?

this is all covered in the form docs

no, it does not mean that

i read those docs, and they are not pedantic enough

jebus

This one is tough work

this is one of the reasons I think it's better people learn to write views well before they're exposed to CBGV

yeah

I agree

I think

;)

you mean I should dick with function=based stuff until my understanding increases?

in the end, all views are functions

oh, it's bound to a http action OR to data?

tindus: This may help you understand: https://dpaste.de/yovT

Otherwise I'm giving up

is there a way to let only superuser see a page?

A modelform becomes "bound" when it relates exactly to a model instance

So in the example I posted, it checks the database, if it can't find an existing model it creates one, and it returns a "bound" form, which means that it is displaying data

tindus: to data

Now, if it creates a model, there might be a whole bunch of default data that gets created with it

why is it "insurance, created = ... "

i though that was how you assign two variables, but you gotta have two on the right

The get_or_create method returns:

the new/existing model instance, and a boolean letting you know if it was created or not

anybody read my question?

ok, docs.django v1.8 can't find AbstractRegistrationView

I really did try to rtfm this time.

tindus - thats my custom view class

ignore it

Ignore everything I wrote, its confusing you.

Do what FunkyBob said and go and write simple function based views

When you understand that, then dip your toes into CBV

Paradisee_: maybe permission_required decorator on the view?

eka: gonna check.

has mention of a similar method in queryset

thanks, guys. I have gotten actual work done with your help.

Paradisee_: or you can use is_staff to build your own decorator

red turned to green. Refactor is next