Support clearing FileFields in the admin if blank=True

I think that I asked it in the developers list, and the idea is not spend time in FileFields? because they are being refactored. Marking this ticket as fs-rf to be considered.

The filestorage refactor does indeed make it easier to delete files from within Python, but it doesn't extend to the admin interface at all. Removing the fs-rf keyword.

I'm very interested in a solution to this problem and would love to help out. Let me know if I can do something.

Claiming the ticket as there hasn't been any activity in the last month. If there exists a patch from the Yandex sprint now would be a good time to post it :)

Looks like we didn't get to it after all. Feel free to take it, thanks!

I don't have a patch for it, but this feature is working in a field that subclasses FileField? on the stdimage application. So it should be easy to extract from there, and create a patch. Probably the patch will need to be improved later, but at least is a starting point.

stdimage is available at http://code.google.com/p/django-stdimage/

Cool, thx! I also got code from brosner. I will probably use both sources to compile a patch :)

First version of the patch, no test fixes yet, docs are separate

Docs as a simple text file as the docs refactor is going to land anyway ...

After talking to brosner on #django-dev we decided to implement this on the ModelForm? level. The attached patch introduces file deletion functionality for ModelForms? which can be customized via its Meta class (see attached docs).

Work still to be done:

• Check admin CSS
  • at least for the RTL design this is bound to break
  • what about inlines?
• Fix regression tests
• Write new tests ;)

Notes on the patch:

• I had to add some special admin CSS to align everything properly. That can only be achieved with a fixed padding to the left ...
• For the DeletableFileField? I started with a MultiValueField? till i had overwritten every piece of code in it ... now it just sublcasses Field. The widget still subclasses MultiWidget? though.
• The display of the current file moved from the admin to ModelForm?. It just doesn't make sense to provide a delete option if the presence of a file isn't visible ;)

If I missed anything in this short description let me know. Please test and tell me what breaks I'll keep the patch up to date :)

After seeing what is really involved in this ticket. jarrow and I decided it is best to avoid this pre-1.0. There is just too much design decisions that need to be made to make this work the right way. I personally appreciate jarrow's work. This will certainly make it post-1.0. :)

Just a note to myself: Maybe the CSS could be shorter as I introduced <br/>s after writing the style rules. Haven't checked though. The <br/>s are there for a sensible default display without CSS when using for example as_table().

#6405 is about making MultiValueField? pass through initial data. Maybe this could be closed if a deletable FileField? is the only use case.

Updated patch to r9381, included docs, checking blank=True before deleting (against forged POST data)

The attached patch seems to work fine. The tests still need fixing though. I wanted to wait for some feedback on the code and approach :) RTL CSS also not done yet. But there seems to be an admin redesign forthcoming anyway.

Moved documentation to the correct file

With the current default values for the ModelForm? Meta class options the admin shows the delete checkbox and removes the file from disk. It does not remove empty directories. To enable this in the admin one currently needs to do something like this:

class TestModelAdmin(admin.ModelAdmin):
    def get_form(self, request, obj=None, **kwargs):
        defaults = {
            "files_delete_empty_dirs": True,
        }
        defaults.update(kwargs)
        return super(TestModelAdmin, self).get_form(request, obj, **defaults)

Maybe a settings option to make deletion of empty dirs the default would be nice. Or we could add a files_delete_empty_dirs option to the ModelAdmin? class and pass it to the ModelForm? (like we do with exclude etc.).