Last modified: 2014-10-07 06:14:52 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 T25830, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23830 - Warn when filename on shared repo clashes with a local repo file
Warn when filename on shared repo clashes with a local repo file
Status: NEW
Product: MediaWiki
Classification: Unclassified
Uploading (Other open bugs)
1.17.x
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-07 22:46 UTC by Derk-Jan Hartman
Modified: 2014-10-07 06:14 UTC (History)
6 users (show)

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


Attachments

Description Derk-Jan Hartman 2010-06-07 22:46:48 UTC
When you upload an image to Commons, you are not warned when your chosen filename is already used on a local wiki to host another file. Your upload will then show the 'wrong' image if you return to that local wiki. This is confusing behavior

Possible solutions:
1: check 'uselang' and en.wp repo only for a clash
2: eradicated clashes alltogether and outlaw them
3: make hundreds of queries. Due to the many non-shared repositories being fed by Commons, this is probably very difficult to implement due to performance issues.
Comment 1 Bryan Tong Minh 2010-06-18 15:00:47 UTC
The only reasonable solution to this is keeping a global image table I think, and I'm not sure if that is desirable.
Comment 2 Platonides 2010-06-18 15:02:04 UTC
Forbid local uploads!
Comment 3 Rd232 2011-11-26 16:51:54 UTC
If checking all local wikis is not feasible, what about, for SUL accounts, checking just the user's home wiki? That's the most likely collision to cause immediate problems, certainly for Commons. 

On the other hand, now that Special:GlobalUsage exists, is it really too expensive to initiate a globalusage query on the proposed filename, and show the user the results if there are any hits?
Comment 4 db [inactive,noenotif] 2012-11-09 19:04:14 UTC
Maybe the Extension GlobalUsage can give the information (Needs a hook in core, which than can be aborted by the Extension or so)
Comment 5 Bryan Tong Minh 2012-11-11 19:45:27 UTC
(In reply to comment #4)
> Maybe the Extension GlobalUsage can give the information (Needs a hook in core,
> which than can be aborted by the Extension or so)

No, it can't, since it only tracks links to images that do not exist locally.

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


Navigation
Links