Potential contribution: filebrowser-browse-upload

[andybak]

https://github.com/DjangoAdminHackers/django-filebrowser-browse-upload-field

We find this incredibly useful and it's become our default replacement for FileField and ImageField on all projects. It's been in production for over a year now and is fairly solid.

I'd be curious to see if it's useful to other people (or indeed maybe even worthy of being added to this project). It's based on the filebrowse field but I think it gives a better overall user experience for typical use-cases.

1. It's not tested on the 3.7 branch
2. It's not tested on the main django-filebrowser repo - I use the no-grappelli fork
3. It's not been tested outside our standard CMS deployment - there might be a dependency somewhere that I've not thought about.

[int-ua]

Can it be used just for the widget, without changing field type?

[andybak]

So - you are using django-filebrowser?

Why does it matter that the field type changes? The underlying database representation is the same.

[int-ua]

1. Yes.
2. Because we are already using a custom subclassed ImageField. And I'd like to make less modifications, I'm not sure why field type change needed. Because it allows some per-field settings? Can't they in theory be specified on the widget itself?

[sehmaschine]

@andybak you never added a PR. should we close this issue?

[sehmaschine]

see also #236

[sehmaschine]

closing this since no PR has been made.