re: "There shouldn't be a delete box for unsaved items, right?" This is a special case - you are taking an existing record and "Save as new"-ing (or however you say that), so there are existing associated records that you are copying as well. But, in this case, I think the user would change a few of those items, then would get rid of any subsequent ones that are not needed by clicking the "Delete" checkbox next to them. In the original record, all items are saved. In the new record, however, after "Save as new", none of the child records are saved, and only some are intended to be kept, while some are intended to be discarded.
As far as I know, if you just do "Save as new", then delete un-wanted records in a subsequent edit of the new record, everything works fine. On Wednesday, November 12, 2014 3:42:43 PM UTC-5, Collin Anderson wrote: > > Hello, > > That does seem odd. Are you using a custom form or custom template at all? > > There shouldn't be a delete box for unsaved items, right? > > Collin > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/36ad9cfd-3c7b-4f9b-80a4-2cf9a0223da0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
