Thanks Ramiro - I have *just* found that blog and was about to report back here on it.
There are, unfortunately, a few "gotchas" that need some clever coder to help resolve... see my reply on the blog. (PS I hope that this approach finds its way into the official docs sometime.) On Jan 12, 2:54 pm, Ramiro Morales <cra...@gmail.com> wrote: > On Wed, Jan 12, 2011 at 9:24 AM, Derek <gamesb...@gmail.com> wrote: > > Unfortunately my existing web app relies heavily on what I now see is a > > feature that was "was never documented or supported" i.e. the ability to > > filter a change list in the Admin by passing in field:value items in the > > URL. e.g. of the type admin/app/model/?foo=bar&eggs=spam > > > So... from now on this is "banned", but I still need to be able to create > > these arbitrarily filtered lists, with the ability to link to them via > > embedded URLs, created in various templates. > > > What should be the "official" way to do this? (For a number of reasons, I do > > not want to simply add all of a model's fields to the list_filter tuples) > > Override the method used to do that lookups validation in your ModelAdmin. > See this very recent blog post for a description of the clever idea: > > http://chris.improbable.org/2010/12/23/custom-admin-filters-django-124/ > > -- > Ramiro Morales -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
