For a couple of content types we have a list of acceptable file types (the defaults actually) for an imagefield.

However on two of the 3 content types, going to node/add/xxxxx doesn't list the acceptable filetypes - thus no JavaScript file check is performed upon selection of a file.

Comments

sirkitree’s picture

sirkitree commented

Were these upgraded from a previous version? If so, you should try to resave the field's configuration (edit the field config and just hit save) and then see if they are printed afterwards.

budda’s picture

budda
Primary language English
Location Cheshire
commented

i can't remember if they have been upgraded or not now. i think i found the reason they weren't being listed though:

if you delete all filetypes from the fields config, save, then go back to the field edit page, the default file extensions are put in to the field. so looking (but not saving) at a field config makes it appear that you have filetypes set up. however in the dbase the actual setting is blank for the file extensions.

it's just a bug in the admin settings for the widget. it assumes that if the file extension field is empty, use the default list of extensions (naughty!).

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (fixed)

Please open a new request for the bug you describe if it is still a problem in the 2.6 version of ImageField. I'm not sure it's necessarily a "bad" behavior, since ImageField can't process images other than png, gif, and jpg, so why should it allow them to be uploaded? You can use a FileField if needing more types that aren't supported web images.