Closed (fixed)
Project:
FileField
Version:
6.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
2 Oct 2008 at 06:26 UTC
Updated:
16 May 2024 at 00:49 UTC
Jump to comment: Most recent
Comments
Comment #1
mike_r1977 commentedI can confirm this error. This is because imagefield calls a filefield function, where the values are hardcoded:
Comment #2
Anonymous (not verified) commentedMoving to the FileField issue queue.
File extensions displayed on node creation forms need to match the chosen extensions, not be hard-coded.
Comment #3
dopry commented@mike_r1977: can you write a patch for it?
Comment #4
dixon_Is the function
filefield_validate_is_image_help()necessary at all? It just duplicates information.Comment #5
dopry commented@dixon_: I don't know... I just put it there for fun... why don't you read the code and tell us.
As for the help text... It's limited to what FileField will potentially support, but I agree it may be nice to pass some context into the help callbacks, but what am I going to do? implement cases for each possible file extension? any great ideas besides objections?
Comment #6
Anonymous (not verified) commentedI might have misunderstood what you're asking, but can't you just have some sort or array that lists the different file extensions, then loop through that for validation and help text display...?
Comment #7
quicksketchThis is corrected in #397578: Uncouple ImageField from FileField Custom Hooks. Marking postponed until that patch is committed.
Comment #8
quicksketchI went ahead and committed #397578: Uncouple ImageField from FileField Custom Hooks, there was too much held up by its changes.
Comment #9
quicksketch