could someone please give some details on this issue? of course, one can use custom views to integrate editing of multiple records. on the other hand, i can do _almost everything_ with custom views - so, that doesn´t really help.
before i start writing custom views for that, i just want to be sure that this is a very specific functionality which nobody else needs - and therefore is _not_ going to be part of future admin-interfaces. thanks, patrick > >> The Django admin site can't do that out of the box, but you could >> create your own custom views that do that. > > I'm wondering when you say this, do you mean within the generated admin > interface, or without using the auto-admin functions? > > This is an area I've long been a bit hazy on -- whether or not it's > sensible (in a maintainability, sanity-preserving-way) to [for example] > shoehorn in my own views in between contrib.admin views, wrapping > default admin views, modifying default admin templates, etc. > > I've got situations (like others here) where the auto-admin stuff does > 95% of what I need, and I can't really tell if I should go "outside" > the system to create 100% what I need, or if I can bridge that 5% > within the auto-admin somehow. > > There are mentions of the new-admin branch making extending and > modifying things easier, but no examples that I've come across -- could > you or someone maybe explain what sort of mods this will allow? > > Thanks! >
