Last modified: 2010-05-15 15:38:57 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 1105 - Upload form should allow setting "Save as" filename
Upload form should allow setting "Save as" filename
Product: MediaWiki
Classification: Unclassified
Uploading (Other open bugs)
All All
: Low enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2004-12-15 04:23 UTC by Erik Moeller
Modified: 2010-05-15 15:38 UTC (History)
0 users

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


Description Erik Moeller 2004-12-15 04:23:16 UTC
The upload form should have a "Save as:" box which would default to the name of
the selected file. For security and usability reasons, it should NOT be possible
to change the extension.

Upload file: [Bla.jpg                 ] [ Browse ] 
Save as:     [Sunrise in Turin        ].jpg

The "Save as" could be set with a JavaScript after a file is selected. If no JS
is available or the field is left blank for another reasons, the normal filename
would be used.

Rationale: People often upload files from local collections that do not follow
naming conventions. This makes it easier for them to do so.
Comment 1 Erik Moeller 2005-04-16 17:38:32 UTC
Fixed by Tim Starling as "Destination filename" field
Comment 2 Ævar Arnfjörð Bjarmason 2005-04-16 17:42:56 UTC
It was only applied to HEAD, added the 'fixed-in-cvs' keyword.

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