On 11/9/06, Phil Davis <[EMAIL PROTECTED]> wrote: > > On 8/13/06, John <[EMAIL PROTECTED]> wrote: > > edit_inline seems to be doing something funky when I use it through > > update_object generic view. I've got a model that looks something like > > this: > [...] > > At first glance it appears to be working -- the update_oject view for > > StationEvent lists its fields and a field for a participant. But when > > it's actually saved, what happens is that for each participant listed, > > it will create a new StationEventParticipant object whether or not it > > already existed. So every time I come back after saving the list of > > participants doubles! > > Did you ever find out the answer to this problem? > > I have just tried a 'by-the-docs' generic view with simple 2 model > master/detail update form and get exactly the same problem or > duplicated detail rows after each save.
This result is common if you omit the <input type='hidden' ...> that is part of each row of the edit_inline table. The hidden input argument is requried, as it ties the row of the edit_inline table to the existing element. Check your template to make sure it contains all the required input elements (including the hidden ones) - if you are looking for a comparison, look at the generated HTML for the admin pages. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
