Last modified: 2012-09-29 19:30:27 UTC
This (deleted) file cannot have thumbnails: http://commons.wikimedia.org/wiki/File:Устройство_приемно-контрольное_охранно-пожарное_взрывозащищенное_с_видом_взрывозащиты_Искробезопасная_электрическая_цепь_УПКОП135-1-1.JPG The thumbnail page said: === Error generating thumbnail Error creating thumbnail: convert: unable to open image `/mnt/thumbs/wikipedia/commons/thumb/1/17/Устройство_приемно-контрольное_охранно-пожарное_взрывозащищенное_с_видом_взрывозащиты_Искробезопасная_электрическая_цепь_УПКОП135-1-1.JPG/393px-Устройство_приемно-контрольное_охранно-пожарное_взрывозащищенное_с_видом_взрывозащиты_Искробезопасная_электрическая_цепь_УПКОП135-1-1.JPG': File name too long. ===
It isn't possible to open a deletion request, either: [[Commons:Deletion requests/File:Устройство приемно-контрольное охранно-пожарное взрывозащищенное с видом взрывозащиты Искробезопасная электрическая цепь УПКОП135-1-1.JPG]] is an invalid page name.
Is there a proper way to determine the maximum path length and filename length?
ext3, which I assume is used by the Wikimedia servers, has a maximum file name length of 255 bytes, as indicated by a very simple google search. If you're interested, NTFS is 255 characters. There is no maximum path length in ext3, it's 32Kchars in NTFS. If these limits are exceeded, things are likely to get confusing, so use shorter filenames. Since we don't want to design our own file system, closing this wontfix.
Sorry, I am not asking to make it possible to use infinite file names, but to make it less easy to bump into the limit that way. Why not warn the uploader before he chooses a name which would cause problems?
On 1.19alpha (r99208) the upload form prevents one from uploading a file with a name which is too long. However, the error message received is wrong. Instead of indicating that the file name is too long it gives the following error message: The filename ... contains characters that are not allowed in page titles. Please rename the file and try uploading it again.
Dedicated message in r99224.
Already fixed
