The extension field is too short: maxlength="64"
I think it should be longer, for example:
txt doc odt xls jpg gif tif pdf png ods rtf mp3 ogg wma zip rar

eats all the space.

#7 149789.patch272 bytesOwen Barton
#6 149789.patch854 bytesOwen Barton


jjk005’s picture

The question becomes, is it safe to change that number in the form? Or is there something that would make such an edit problematic? I too need this field to be longer.

jpetso’s picture

I looked this up, and it goes this way:

  • All the settings, including the allowed extensions, are stored by CCK in a serialized array.
  • I have already forgotten the database table, but the field is of the type "mediumtext".
  • "mediumtext" is long enough to store good amounts of allowed extensions.
  • Let's remove the maxlength restriction! I'll ask dopry and commit that afterwards.
jpetso’s picture

The table is {node_field_instance}, and I decided that it's trivial enough to not having to ask dopry for this. Committed and FIXED. Rejoice.

jpetso’s picture

Status:Active» Fixed

And when I say FIXED, I certainly want to set the status accordingly. Ungh.

Anonymous’s picture

Status:Fixed» Closed (fixed)
Owen Barton’s picture

Version:5.x-1.x-dev» 6.x-3.x-dev
Status:Closed (fixed)» Needs review
new854 bytes

It looks like this regressed at some point - check around line 25 of:

Attached is a simple patch that fixes this.

Owen Barton’s picture

new272 bytes

Actually, that was the wrong fapi parameter - this one is correct...

quicksketch’s picture

Status:Needs review» Reviewed & tested by the community

Thanks, looks good to me.

quicksketch’s picture

Title:file extension field too short» File extension field too short
Version:6.x-3.x-dev» 6.x-3.5
Status:Reviewed & tested by the community» Fixed

Committed to CVS. It'll be in 3.6.

Owen Barton’s picture


Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.