#10255 closed (duplicate)
FileField overwrite existing value with empty one
Reported by: | pierpaolodf | Owned by: | nobody |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Keywords: | FileField | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Since revision 9766 editing in admin will cause overwriting existing value in FileField with blank value.
1) create a new record setting FileField to some file and save it
2) edit the previous record in some field other than the FileField (or just save with no change)
3) check the record to find out that FileField is now empty
Change History (6)
follow-up: 2 comment:1 by , 16 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
follow-up: 4 comment:2 by , 16 years ago
comment:3 by , 16 years ago
Cc: | added |
---|
comment:4 by , 16 years ago
Replying to Valera_Grishin:
Replying to ramiro:
... this as a duplicate because
ImageField
is a sublcass ofFileField
This is why it is better to leave this one open not #10121
Convention is to keep the first ticket opened for a problem and close subsequent ones as dupes (though sometimes it is not always realized there is an older ticket already covering a new report, so it is not a convention always 100% followed), noting in the original if necessary anything pertinent. It's been noted the in #10121 that the problem is not specific to ImageField, that's good enough. We only need one ticket to track the problem and it's not particularly critical which one is used.
follow-up: 6 comment:5 by , 16 years ago
Cc: | removed |
---|
comment:6 by , 16 years ago
Replying to anonymous:
Ok, thanks for explanation. I'm removing my e-mail from cc then.
This has been already reported in #10121, although it was about
ImageField
I'm closing this as a duplicate becauseImageField
is a sublcass ofFileField