Opened 16 years ago
Closed 16 years ago
#10179 closed (duplicate)
admin broken on FileField with blank=True
Reported by: | malte | Owned by: | nobody |
---|---|---|---|
Component: | Core (Management commands) | Version: | 1.0 |
Severity: | Keywords: | admin filefield bug | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
If you have a FileField declared like so:
image_1 = models.FileField(upload_to=get_image_path, null=True, blank=True)
Then in django admin, the field becomes voluntary as it should. If you save a file in an optional field that works as expected. But if you come back to the item in the admin, and just hit 'save' without touching the optional file that is uploaded, the db record gets updated with a blank value for the FileField, effectively killing the connection with the file.
I'm using Sqlite, may make a difference here I suppose.
Change History (6)
comment:1 by , 16 years ago
follow-up: 3 comment:2 by , 16 years ago
Description: | modified (diff) |
---|
follow-up: 4 comment:3 by , 16 years ago
Replying to ramiro:
(reformatted description)
malte: What version of Django are you using? If youa re using a revision from trunk latter that r9766, can you please try with r9765 and report back?
Ramiro: I can confirm that this problem does not exist in r9755 and starts appearing as of r9766.
(For others: A thread on this on Django Users Google Group can be found here http://groups.google.com/group/django-users/browse_thread/thread/b618845843bced67/8905992cb00ec0a1)
comment:4 by , 16 years ago
Malte suggests that this might have something to do with using SQLite, but I came across this problem on PostgreSQL as well.
I'm guessing this is a consequence of the file assignment stuff from a week or two ago.