Thanks. This works perfectly.
Is there a better way to implement what I am trying to do?
Also, does anyone know how I can capture these elements again in the
view when processing the form? Since there are an arbitrary number of
fields for songs, I don't know how many I should be looking for
On 11/04/2008, Brian Morton <[EMAIL PROTECTED]> wrote:
[...]
> The problem occurs in the template. I am trying to differentiate
> these fields from the other normal fields on the form for presentation
> purposes. I have tried assigning a custom property to each of the
> dynamic fields.
>
>
I have run into an interesting problem with newforms. I am trying to
create an arbitrary number of fields on a form based on model data.
This works fine.
class SonglistForm(forms.Form):
def __init__(self, *args, **kwargs):
super(SonglistForm, self).__init__(*args,
3 matches
Mail list logo
