Re: Initial values and unbound forms (apparently a bug?)

Hi, Manu, Thanks for writing. I tried what you suggested, and the forms were displayed exactly as I wanted. However, when I tried to submit the form, it triggered validation errors for all the fields that were left blank. So, the behavior is not quite what I want. I'm guessing that setting the

Re: Initial values and unbound forms (apparently a bug?)

Hello, I would say that the behavior you have is normal. Quoting the doc "Using initial data with a formset: Initial data is what drives the main usability of a formset. As shown above you can define the number of extra forms. What this means is that you are telling the formset how many

Re: Initial values and unbound forms (apparently a bug?)

i use in my form form = MatchForm(instance=match, initial={'startDate':'%s-%s-%s'% (y,mo,d),'startTime':'%s:%s:%s'%(h,mi,s)}) but ur initial value is a list, initial=[bla bla] instead of this use dict {} On Dec 5, 11:35 pm, Liam wrote: > Haven't been able to get

Re: Initial values and unbound forms (apparently a bug?)

Haven't been able to get this to work, and no one has responded with advice or a workaround. Can anyone confirm that this is a bug, or tell me what I'm doing wrong? On Dec 3, 5:28 pm, Info Cascade wrote: > Hi -- > > I am trying to set some reasonable defaults