-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11.10.2012 22:18, Tim Colletto wrote: > Long filename attachment (130 characters) fails to attach. Anyway we > can allow longer attachments? We need to be able to upload files with > long filenames. > > > > More output: > ...
Not enough for me. Would have liked to see a confirmation, that it really bails out on opening the file with r/w access, what is unfortunately hidden in your collapsed traceback copy. Short: Remove any white-space from your path and retry. I'm quite confident, that it's likely not file/path length, but some white-space in the path. The path for your Trac install reveals already, that you're comfortable with this practice. I do vote against that violently, claiming this broken and insane treatment of a computer storage system. The file system is no word-processor, not seen spaces in paths other than due to loss of attention to typos on directory/file creation time. Not seen a remotely valid excuse for white-space in paths by now - all sloppy naming policy IMHO. Steffen Hoffmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlB3R38ACgkQ31DJeiZFuHc2UACfS8lFldvOofRob97mWbaYDTwr FwAAn1fMhN61mvkxmzdLc9izfynLIxaC =AZpb -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
