Commons:File renaming/Global replace

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Shortcut: GR · COM:GR

Other languages:
العربية • ‎Deutsch • ‎English • ‎Esperanto • ‎español • ‎français • ‎हिन्दी • ‎Bahasa Indonesia • ‎norsk bokmål • ‎русский • ‎українська • ‎中文
Commons File mover.svg

You are likely here because you followed a link in an edit summary. Please be advised: The edit was not done by a bot. It was done by a script that is enabled by default for all users on Wikimedia Commons. If the replacement was done by a file mover or administrator (verify) according to our policies, do not block this user at your project as it will not prevent the file itself from being renamed; blocking will only prevent the user from updating the file link. Unwanted replacement edits under user accounts other than bots might be prevented by using the AbuseFilter. If an individual is misbehaving or replacing usage with a different file you might block them of course. Controversial renames may also be reported and challenged on Commons.

The default “Move” link from the actions dropdown has been replaced by a “Move & Replace” gadget on this site. After a file has been renamed on Wikimedia Commons, the file usage will be replaced on all Wikimedia wikis by a JavaScript running in a user’s browser: All pages where a file is reported to be in use will be searched for the file name, and File:Old name.ext will be replaced with File:New name.ext in its source code. Edits are conducted under the user account of the administrator or file mover who renamed a media file. Since 2013 this extended functionality has been switched on by default for all file movers and administrators. If the replacement is not feasible, for example due to heavy usage, failed edits or slow connections, file usage will be replaced by CommonsDelinker as before.


Why we implemented the JavaScript replacement under individual user accounts[edit]

We believe that every file mover and administrator is solely responsible for their own actions; and if they rename a file, they must also justify all edits that are caused by renaming a media file. Additionally, we occasionally encountered technical issues with our replacement bot, CommonsDelinker and not updating file usage is dangerous as, as soon as files are moved twice, there are chances of double redirects which are not resolved by MediaWiki and file usage could break, if not curated like this. Also file renaming should bear some improvements to file names that we would like to share with our users.


System-search.svgSee also: Help:AjaxQuickDelete.