> It has a kind of goofy option for deleting
> empty directories when removing a file leaves said directory empty.
Hey, it's not goofy. It's handy ;) I also took _great_ care when
writing the code for directory deletion and it's happily deleting
directories on our production server since a year or
Hi,
I just wanted to mention there still is ticket #7048 "Support clearing
FileFields with ModelForms" [1], which also deletes files, if
configured to do so. I don't think this is particularly evil, if off
by default (which it is not in the current patch, but that's easy to
change).
This was ori
Just to be clear we are talking about the same thing: With "persistent
filters" I just mean "going back to the _filtered_ change list after
editing an item". I don't think it makes sense to make them any more
persistent :) Clicking on the link to the change list on the admin
home page should give
The idea of an ordered many-to-many field is very old [1] and has been
proposed a lot over the years (e.g. [2], [3]). So the general
consensus seems to be that we want such a thing. I’d like to share
some thoughts on how to approach the whole ordering problem on the API
side (leaving aside the Jav
Currently if you search in the admin, use some kind of filter or even
just go to the second page in the change list this selection is reset
when you edit an item and hit save. The user gets the default list
again. Needless to say this can be quite annoying. Especially if you
want to edit a specifi
Dear Django developers,
The code importing urls.py has a flaw that is easy to fix but has the
potential to cause a lot of frustration especially for inexperienced
developers -- which I do hope will try out Django in large numbers
soon :)
The problem is this: When importing urls.py _any_ exceptio
> I think Django is really wonderful, but I am puzzled that it contains
> so few "ordering features". We often have the case that a user wants
> to select from a list of possible choices (normal select) *plus* wants
> to specify an ordering. Typically in applications this is done using
> up/down a
