Closed (works as designed)
Project:
FileField
Version:
6.x-3.0-alpha4
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jan 2009 at 17:21 UTC
Updated:
4 Feb 2009 at 00:45 UTC
It seems when you try to upload a image, that happens to have the same filename as another file in the same directory, it gets renamed to something like _#.xxx . Which isn't a big deal or anything, just as long as the filepath is recorded.
The problem is that when the file is inserted into the {files} table, that the filename reflects the outdated original filename, and not the updated -uinque- filename.
# CCK version: 6.x-2.1
# readable, writeable
# private
# ... not sure how to explain.
# n/a
| Comment | File | Size | Author |
|---|---|---|---|
| name_error.jpg | 34.6 KB | eknowlton |
Comments
Comment #1
drewish commentedIt's a filefield issue. I think there's already an issue or two open for this.
Comment #2
dopry commentedComment #3
dopry commentedahh now that I look more closely... no we do not update the filename when we have to automatically update a path... original filename may be better... but yeah that is by design. I thought the wrong path was being stored in the db... *phew*