I use the form_for_instance(instance, form=<name of custom form>) and
this works great for me, however I found a bug (which is documented),
that doesn't actually populate the data, so if you're not getting the
POST data, and you just want to display the current instance, you'll
need to do a theform = form(instance.__dict__)
So here's my whole code to edit one of my stock portfoliios:
def editportfolio(request, port_id):
#edit a portfolio
instance = Portfolio.objects.get(id=port_id)
modelform = form_for_instance(instance, form=PortfolioForm)
if request.method == 'POST':
form = modelform(request.POST)
if form.is_valid():
obj = form.save()
return HttpResponseRedirect('/portfolio/' + port_id)
else:
# This seems like a work around since the form_for_instance
doesn't work with the
# form= parameter
form = modelform(instance.__dict__)
return render_to_response('aim/portfolio_update.html', {'form':
form} )
On Sep 24, 10:18 pm, Cat <[EMAIL PROTECTED]> wrote:
> Hello
>
> I'm starting out with newforms and although I have found a lot of
> examples using form_for_instance I haven't found enough on custom
> forms to answer (at least for me) the following questions:
>
> 1) What is best practice to populate a custom form with instance data?
>
> 2) What is the recommended way to create a single custom form that
> allows two models (related by a foreign key) to be editted/added to?
>
> As always for us newbies, code samples would be much appreciated
>
> Thanks
>
> Cat
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
