On Mon, Mar 7, 2011 at 3:17 PM, poswald <paulosw...@gmail.com> wrote: > (Sorry Ramiro, I think I replied directly to you instead of to the > group. Resending here) > > Understood. I believed I was adding a testcase and expanding the scope > of the issue but it is certainly possible that they are two separate > causes. I will keep that in mind in the future and will certainly open > a new issue/revert this one here if everyone would prefer. > > For what it is worth I was able to reproduce the exception using the > original reporter's code but only if I follow the process I outlined > in my report.
Actually I've just reproduced (using trunk) the situation reported by the OP: Simple two-model generic foreign key plus generic inlines setup in the admin app, activation and usage of the save as button and no need to add a second browser window in the mix. A very simple to prepare and reproduce setup. The other users that added comments to the ticket before loosely described their problem as not related to the admin inlines at all rather with more low level model formsets; in any case they don't provide enough details to be able to know if they are really contributing to the isolation of the original issue or simply landed in that ticket with a search and found something similar in its symptoms to their own issues. Because of this I'm going to revert your changes to the ticket and I'd like to ask you to open another ticket and move what you've found so far there. We might be in presence of he same issue but I think the divergence of initial conditions show it's too early to be sure of that. Thanks, -- Ramiro Morales -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
