Good call on the ModelAdmin spot. (user contacted me by email to see if I had a solution yet.)
I got the formset.save() from here: http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#the-save-method saying: "If your formset contains a ManyToManyField, you'll also need to call formset.save_m2m() to ensure the many-to-many relationships are saved properly." Works now just had it in the wrong spot. thx! On Jan 6, 9:23 pm, "Karen Tracey" <kmtra...@gmail.com> wrote: > On Tue, Jan 6, 2009 at 10:10 PM, Timboy <corn13r...@gmail.com> wrote: > > > Still no solution to this. It has been confirmed by another user. Is > > it a bug? > > (Where was it confirmed by another user? I don't see that.) > > The doc list "save_formset" under "ModelAdmin methods" yet you seem to have > added it to your inline admin class. I also don't see any indication in the > traceback you posted that your custom method is being called, which leads me > to think where you have put it is not where it needs to be in order for it > to be called. > > (Also you changed formset.save_m2m() from the example in the docs to > formset.save(). I doubt that this change is correct.) > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
