It took me a while but I have opensourced a tool to clean the media folder
from all the
leftovers. It's a cron job with a simple admin gui. Also handles multiple
upload folders.
We have been using something similar to this internally for more than a
year,
and we are pretty happy about it.
http
By default Admin saves an empty string in those TextFields and
CharFields defined as null = True.
Whatever the semantic reasons are, this default behavior creates
problems in those fields which are both unique = True and null = True
because by saving an empty string they do not respect that null !
Have you considered the possibility that it would be a client/browser
side error?
Both windows7 and chrome have a known open bug with large file
uploads. Many of my customers have reported this bug, all of them
using windows7 and chrome.
Has anyone seen this happening from a Mac or from Linux?
O
I am referring to this:
http://docs.djangoproject.com/en/dev/releases/1.3/#filefield-no-longer-deletes-files
Instead of preventing the data loss from happening a very usefull
feature has been removed.
Why not simply letting the developer decide when to enable or disable
it with a constructor boole
> One query for each model
> containing one or more FileFields is enough to build a list of the files
> that ought to exist, and any file not in that list can presumably be
> removed.
How can I sleep at night knowing that there is a maintenance cron job
deleting files which can be "presumably be r
