On Thu, Jul 5, 2012 at 3:35 PM, Melvyn Sopacua <m.r.sopa...@gmail.com> wrote: > Nice solution, but weren't formsets made for this type of thing? I'm > trying to figure out why formsets couldn't be used here and coming up > blank, unless the naming convention is somehow unchangeable.
Possibly. Formsets are great if you want to repeat the same form over and over again, but sometimes you don't want to do that. I've made forms like this for things like personal preferences. Certain fields are always required (name, etc), some fields are only collected for users if their organization permits, and some organizations have a list of custom properties that must be collected. In this scenario, formsets are useless, but dynamically created form fields fit perfectly, providing you can generate the form in the template in a sane manner. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
