No, you have to save self before you can add categories to it, because you can't save an M2M if either object is missing a primary key.
In any case, it turns out that the reason is that the admin saves the submitted M2M data after the save() method is called on the main model. So it erases and overwrites anything you've added. The solution was to intercept the form data in the ModelAdmin's save_form () method and to add the default to cleaned_data if the list of categories is empty. On Jun 9, 6:30 am, Frédéric Hébert <fg.heb...@gmail.com> wrote: > Hi, > > > defsave(self, *args): > > models.Model(save, *args) > > category = Category.objects.all()[0] > > self.categories.add(category) > > > This does not work, I'm sure it's saving ManyToMany relationships > > later on in thesaveprocess. Is there a way to make this work? > > IMHO, it's make sense : you call the parent save method before > defining new categories on it. How parent save method could know > anything about these new categories ? > > Have you try : > > def save(self, *args, **kwargs): > category = Category.objects.all()[0] > self.categories.add(category) > super(Product, self).save(*args, **kwargs) > > Frédéric --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
