Last modified: 2014-11-04 22:53:13 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 889 - Improve conflict-handling between shared upload repository (commons) and local one
Improve conflict-handling between shared upload repository (commons) and loca...
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
All All
: Normal normal with 8 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: crosswiki
: 1666 (view as bug list)
Depends on:
Blocks: 4243
  Show dependency treegraph
Reported: 2004-11-15 23:38 UTC by Erik Moeller
Modified: 2014-11-04 22:53 UTC (History)
5 users (show)

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


Description Erik Moeller 2004-11-15 23:38:19 UTC
Two changes are needed, primarily:

1) During file uploads, throw an overwrite warning if the image exists in the

2) If the upload replaces a commons file, add the text "An alternative copy of
this image exists in the shared upload repository" or something similar.
Comment 1 Rowan Collins [IMSoP] 2005-06-21 00:39:11 UTC
I would add:
3) ability to explicitly refer to the commons version ("[[commons:Image:Foo]]"
or similar); without this, (2) is only partially useful.
Comment 2 Rowan Collins [IMSoP] 2005-06-25 13:57:30 UTC
*** Bug 1666 has been marked as a duplicate of this bug. ***
Comment 3 emddudley 2006-04-12 04:08:03 UTC
I'm upgrading this image from an enhancement to normal severity. Users uploading
images to Wikipedia with the same name as an image on Commons can cause a lot of
disruption on articles that use Commons images.

We either need a way to explicitly include the Commons version of an image
(right now we can only explicitly link to them) or we need to prevent images on
Wikipedia from overwriting Commons images.

There's no point to moving images to Commons if this problem isn't fixed; moving
the images just creates more difficulties.
Comment 4 Brion Vibber 2006-04-12 07:31:41 UTC
We already prevent images on Wikipedia form overwriting Commons images.
Only sysops can do it, and I think there's a warning displayed for them.
Comment 5 emddudley 2006-04-12 21:05:51 UTC
Ah, I'm a sysop, so I didn't see that regular accounts can't overwrite Commons

However, there is no warning displayed for sysops, which is why I didn't realize
it in the first place. Should I file it as a seperate bug? Once there is a
warning, this bug can be closed.
Comment 6 peter green 2006-04-12 21:31:34 UTC
not really, there is still the issue of existing images that the commons
uploader is unaware of and existing conflicts

to REALLY close this issue we need a way to reference the commons image even
when there is a local image of the same name.
Comment 7 Gennaro Prota 2006-05-09 13:30:10 UTC
I would rather propose to *prevent* name collisions between the commons and the
local images. KISS principle. Besides this, I think we should have a way to
rename images, both on commons and on single wikis, and a well-done image naming
policy. It is a mess now, as we have names such as asuslogo, AsusLogo,
asus_logo1, as187whoknowsm etc; and these are all things which cause error and
waste of time for everyone.

The reason for supporting image renaming and a naming policy is maybe better
illustrated with an example: let's say I upload, an image named origami.jpg to
en.wikipedia while an image with the same name exists on commons. On receiving
the warning I go to commons and see that the image showed there is about the
Microsoft ultra mobile PC, while mine concerns the paper-folding art. There
should then be an unambiguos way to decide what to rename and how; it could be
origami (paper folding)/origami (umpc) or origami/origami (computer) or anything
else (the example is purely illustrative, it's obvious that "origami" is such a
generic name that it is obviously inappropriate for the image of a particular
origami example).

Maybe we could just enforce that all (and only) image from commons have a name
beginning with "common_"
I don't object to having a syntax to specify that the image is from commons, but
I don't support the use of "namespaces", so to speak. IOWs, common::name would
just be an alternative to common_name.
Comment 8 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-05-09 23:11:19 UTC
(In reply to comment #7)
> common::name would just be an alternative to common_name.

Is there a difference between the two punctuation marks?  The latter, since
MediaWiki treats underscores as spaces, would incidentally prevent any
non-Commons image to be identified by anything beginning with the word "common"
(which is a fairly, well, common word), and would also mess up localization
(since the prefix would be added centrally at the Commons rather than a
"virtual" namespace being added locally at each project).

As for moving, that's Bug 709.  You can try voting for it if you like.
Comment 9 phi1ipp 2008-02-09 16:40:04 UTC
Commons should likewise indicate impending name collisions with e.g. images on any of the local projects (Wikipedia, Wikibooks, etc.). If we can check usage globally (, we ought to be able check for those collisions.

I also agree with the first sentence of Gennaro's comments.
Comment 10 Victor Vasiliev 2008-04-28 16:28:41 UTC
Fixed in r33972.

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