I have an admin page set up where I have two inlines for this one model I have. Both inlines have extra=3 so theres three instances per inline. One of the inlines behaves badly by saving all three objects, even if two of them are completely empty. The other inline behaves nicely by only saving the object that has actually been entered by the user.
In other words, if you click on "create new XXX" in the admin interface, then without entering any information on the resulting page, the object that gets created will have three empty objects for one field, and zero objects for another one. Does this make sense? What is causing the one inline to try to save the blank forms, while the other one does not? Looking at the model code, I can't figure out why. I tried fooling around with blank=True and null=True, but all that seems to do it cause a "Please correct the errors below." error when I leave empty fields in the problematic inline. Anyone know what may be causing this? I can post code if it will help. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
