Opened 18 years ago
Closed 17 years ago
#3426 closed (duplicate)
FileField / ImageField - old files left around
| Reported by: | Ionuț Ciocîrlan | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
When uploading a new file as a replacement for an old one using the FileField, the old file is left lying around on the file system.
The old one should be deleted, which would be consistent with the behavior exhibited when deleting an object with a FileField.
Change History (3)
comment:1 by , 18 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:2 by , 18 years ago
comment:3 by , 17 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
#4339 talks about the same thing, but has a patch so I'm marking this one duplicate of that one.
Note:
See TracTickets
for help on using tickets.
I'm very suspicious of allowing automatic file deletion as a default. It's *forever* so if anything else in the system is using the file, it's bad.
Maybe an attribute on the field for deleting replaced files?