Last modified: 2010-05-15 14:36:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 362 - Can't upload non-ASCII filenames on Mac-hosted Latin-1 wiki
Can't upload non-ASCII filenames on Mac-hosted Latin-1 wiki
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Uploading (Other open bugs)
unspecified
Macintosh Mac OS X 10.3
: Normal minor with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: utf8
Depends on: 363
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-03 07:26 UTC by Brion Vibber
Modified: 2010-05-15 14:36 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Brion Vibber 2004-09-03 07:26:40 UTC
Noticed this while investigating bug 215. If a wiki hosted on Mac OS X is set for Latin-1 and a file with a 
non-ASCII filenames is uploaded, the file can't be copied into place and the upload ultimately fails. An error 
message like this is shown:

Warning:  move_uploaded_file(/Users/brion/Sites/head/images/c/cc/Wiki_test_é.png): failed to open 
stream: Invalid argument in /Users/brion/Sites/head/includes/SpecialUpload.php on line 217
Warning:  move_uploaded_file(): Unable to move '/var/tmp/phpIVDrW5' to '/Users/brion/Sites/head/
images/c/cc/Wiki_test_é.png' in /Users/brion/Sites/head/includes/SpecialUpload.php on line 217

The problem is likely that the Mac's HFS+ filesystem, unlike traditional Unix filesystems, doesn't just use a 
bag of bytes for filenames. BSD-level programs are expected to speak UTF-8, and the fs layer uses Unicode 
internally. The literal latin-1 names are rejected as invalid and the file can't be written.

Note: check if Windows has similar problems.
Comment 1 Brion Vibber 2005-06-14 21:45:08 UTC
Resolving as FIXED; since Latin-1 support is being dropped in 1.5 this will no longer be relevant.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links