Re: bound form with ModelChoiceField

2011-04-23 Thread Andy McKay
> what is the best way of do what I want to do? > I don't think it will be store firstForm.data o request.POST in > session it's a good idea, so, what are the other possibilities? I would recommend taking a copy of the clean data, then run through and just change your ModelChoiceField back into t

Re: bound form with ModelChoiceField

2011-04-22 Thread ekms
I'm sorry, maybe I didn't explain it correctly. I have a form (not a modelform) with a modelchoicefield. class myForm(forms.Form): recorridos = Recorrido.objects.filter(showinform=True) option = forms.ModelChoiceField(recorridos) User selects a choice, and POST. In my view, after valida

Re: bound form with ModelChoiceField

2011-04-21 Thread Andy McKay
On 2011-04-21, at 4:07 PM, ekms wrote: > So, what is the correct way to create a bound form of > ModelChoiceField? I could store request.POST or myform.data instead > of myform.cleaned_data, but I don't know if this is right. You are confusing me when you say a bound form of a ModelChoiceField.

bound form with ModelChoiceField

2011-04-21 Thread ekms
Hello, I have a form with a ModelChoiceField, and when I want to create a new bound form using the first form cleaned_data (that I stored in a session before), I get an error when rendering the template ("Caught TypeError while rendering: int() argument must be a string or a number"). This is beca