Page MenuHomePhabricator

we need a warning if the image exists in the shared upload dir
Closed, ResolvedPublic

Description

Author: plugwash

Description:
on the wikimedia websites the shared upload dir is used to load images from commons.

a newbie just went and uploaded an image to the en wikipedia that blocked out an
image from commons.

when this happens there is no easy way to deal with it (especilly as we can't
move images). WORSE it may not even be noticed until much later by someone
viewing a page on which the image from commons was being used.

There needs to be at least a warning and possiblly more (maybe admin approval
needed) before users are allowed to upload an image that clashes with one in the
shared upload dir.


Version: unspecified
Severity: major

Details

Reference
bz1666
TitleReferenceAuthorSource BranchDest Branch
utils: update deb build and bump setuprepos/cloud/toolforge/jobs-cli!36sstefanovaslavina/update-build-and-version-scriptsmain
utils: update deb build and bump setuprepos/cloud/toolforge/envvars-cli!45sstefanovaslavina/update-build-and-version-scriptsmain
builds-api: bump to 0.0.155-20240607054956-c39a1ef1repos/cloud/toolforge/toolforge-deploy!319project_1317_bot_df3177307bed93c3f34e421e26c86e38bump_builds-apimain
openapi: refactor yamlrepos/cloud/toolforge/builds-api!96sstefanovaslavina/refactor-yamlmain
utils: update deb build and bump setuprepos/cloud/toolforge/builds-cli!73sstefanovaslavina/fix-bump-scriptmain
update submodules for 2024-06-04 deployrepos/phabricator/deployment!44brennenwork/2024-06-04-releasewmf/stable
Customize query in GitLab

Revisions and Commits

Event Timeline

bzimport raised the priority of this task from to High.Nov 21 2014, 8:15 PM
bzimport set Reference to bz1666.
bzimport added a subscriber: Unknown Object (MLST).

It's very easy to deal with it -- delete it!

But yes, a warning might be nice.

plugwash wrote:

i don't consider throwing away the local image (or reuploading it and losing its
history in the process) to be a good way of dealing with this.

not to mention the issue of untangling any links to the two images.

in this case it was caught quickly and probablly won't be a major issue but the
real cleanup problem comes if something like this goes undetected for a while.

fred_chessplayer wrote:

(In reply to comment #0)

on the wikimedia websites the shared upload dir is used to load images

from commons.

a newbie just went and uploaded an image to the en wikipedia that

blocked out an

image from commons.
when this happens there is no easy way to deal with it (especilly as

we can't

move images). WORSE it may not even be noticed until much later by

someone

viewing a page on which the image from commons was being used.
There needs to be at least a warning and possiblly more (maybe admin

approval

needed) before users are allowed to upload an image that clashes with

one in the

shared upload dir.

(In reply to comment #0)

on the wikimedia websites the shared upload dir is used to load images

from commons.

a newbie just went and uploaded an image to the en wikipedia that

blocked out an

image from commons.
when this happens there is no easy way to deal with it (especilly as

we can't

move images). WORSE it may not even be noticed until much later by

someone

viewing a page on which the image from commons was being used.
There needs to be at least a warning and possiblly more (maybe admin

approval

needed) before users are allowed to upload an image that clashes with

one in the

shared upload dir.

Just a suggestion: information about the commons page could be inserted
into the wikipedia image page, stating "this image is ''also'' available
at commons, would you chose to use this instead?"

rowan.collins wrote:

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

Gilles raised the priority of this task from High to Unbreak Now!.Dec 4 2014, 10:19 AM
Gilles added a project: Multimedia.
Gilles moved this task from Untriaged to Done on the Multimedia board.
Gilles lowered the priority of this task from Unbreak Now! to High.Dec 4 2014, 11:21 AM
epriestley added a commit: Unknown Object (Diffusion Commit).Mar 4 2015, 8:22 AM