Last modified: 2014-11-17 10:34:48 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T22971, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20971 - Upload new versions of files with different file type
Upload new versions of files with different file type
Status: RESOLVED DUPLICATE of bug 4421
Product: MediaWiki
Classification: Unclassified
Uploading (Other open bugs)
unspecified
All All
: Low normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://it.wikipedia.org/
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-03 10:40 UTC by Mattia
Modified: 2014-11-17 10:34 UTC (History)
9 users (show)

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


Attachments

Description Mattia 2009-10-03 10:40:28 UTC
Hello, 

I have opened this bug to require the introduction of a new functionality to the software MediaWiki. 

More specifically I would like it was possible the loading of a new version of a file, even if not having the same extension of the original. 

Also I would ask you to kindly to ensure that all items bearing that specific file were changed automatically by the software in order to aim automatically to the new name of the file in question.

These my requests are due to the fact that very often it can happen to have to change suddenly extension to a file, but to do this we must necessarily load it with a new name, other than that which should be.

This is all. Of course I rest available for further clarification. 

Thank you
Mattia
Comment 1 Brion Vibber 2009-10-03 21:55:40 UTC
You should be able to work around this currently like this:

1) Upload the new file with new extension
2) Turn the old file into a redirect to the new one

(It _might_ be necessary to delete the old file in there too for the redirect to work, I don't recall exactly what reqs we put on those for now.)

Longer term, there's an idea to stop including the file extension in the on-wiki addressable name (splitting the raw filename from the on-wiki name, essentially) which this bug entry should either be duped to or set to depend on, but I can't find it at the moment.
Comment 2 Alexandre Emsenhuber [IAlex] 2009-10-04 07:40:54 UTC
(In reply to comment #1)
> Longer term, there's an idea to stop including the file extension in the
> on-wiki addressable name (splitting the raw filename from the on-wiki name,
> essentially) which this bug entry should either be duped to or set to depend
> on, but I can't find it at the moment.

That's bug 4421.

Comment 3 p858snake 2009-10-04 08:05:59 UTC
(In reply to comment #1)
> Longer term, there's an idea to stop including the file extension in the
> on-wiki addressable name (splitting the raw filename from the on-wiki name,
> essentially) which this bug entry should either be duped to or set to depend
> on, but I can't find it at the moment.
That bug was so that the File page contents (eg: licenses) could get index by the engines since some of them just forgot about it based on the web address extension.

This would break things, especially where we have two completely different images which have the same name.
For example on en.wikipedia [[File:Example.png]] and [[File:Example.svg]] (technically commons) which are designed differently because different formats support different things.
Comment 4 Brion Vibber 2009-10-04 20:58:18 UTC
Bug 4421 as currently discussed wouldn't force changes to any existing files (but would allow them to be bulk-renamed to drop the extensions where there's not a conflict).
Comment 5 Mattia 2011-08-18 21:07:17 UTC
I decided to close this my bug because I consider my request already included in bug 4421. Thank you for the attention.

*** This bug has been marked as a duplicate of bug 4421 ***

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


Navigation
Links