Re: Many problems with edit_inline and unique_together
On 8/31/07, Nicola Larosa <[EMAIL PROTECTED]> wrote: > > > we should either fix the current admin (depending on > > how long it'll take newforms-admin to land), to work out what's going > > wrong so we don't have the same problem in newforms-admin (..and there > > are a few tickets open requesting edit_inline in newforms-admin > > already...). > > To this end, I tried making tests for some of those tickets, but I could > not find any test whatsoever for the admin interface. I would really know > how should I go in making one. There isn't much point writing tests for the oldforms-admin interface. It's due to be deprecated reasonably soon. However, if you wanted to contribute tests for newforms-admin, they would be most welcome. There are a number of ways you could approach the problem, but I suspect the easiest way will be to set up a new regressiontest directory with some sample data models, register those models with an admin site, and use django.test.Client to poke the relevant URLs. Yours, Russ Magee %-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Many problems with edit_inline and unique_together
Simon Greenhill wrote: > If anyone's looking for something to do over the weekend [1], there > seems to be one whole metric tonne of issues caused by people trying > to use edit_inline and unique_together at the same time in the admin > section. Yeah, it's the very first I stumbled into, when modeling. > we should either fix the current admin (depending on > how long it'll take newforms-admin to land), to work out what's going > wrong so we don't have the same problem in newforms-admin (..and there > are a few tickets open requesting edit_inline in newforms-admin > already...). To this end, I tried making tests for some of those tickets, but I could not find any test whatsoever for the admin interface. I would really know how should I go in making one. -- Nicola Larosa - http://www.tekNico.net/ Courage, self-confidence, and trust in each other. If we had these things we could live without money, and without wage slavery. Is it any wonder that the politicians, big businesses, the elites of the rich and powerful, work so hard to make us fearful, full of self-doubt, distrustful, and "just like everybody else"? -- Dave Pollack, August 2005 --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Many problems with edit_inline and unique_together
Hi all, If anyone's looking for something to do over the weekend [1], there seems to be one whole metric tonne of issues caused by people trying to use edit_inline and unique_together at the same time in the admin section. I think this has been largely ignored since we're trying to move the admin to newforms, but I've just marked 6 tickets as duplicated of #565 [3] where this was first noticed. People are repeatedly running into this, and we should either fix the current admin (depending on how long it'll take newforms-admin to land), to work out what's going wrong so we don't have the same problem in newforms-admin (..and there are a few tickets open requesting edit_inline in newforms-admin already...). For the record - edit_inline is causing a non-trivial proportion of all the bugs all by itself, and any clean up there is likely to close around 5 bugs by accident [3] --Simon [1] this is cheeky of me, I know. [2] http://code.djangoproject.com/wiki/FeatureGrouping#edit_inlineIssues [3] http://code.djangoproject.com/ticket/565 --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
