Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content).
You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki.
-- 05:01, 23 December 2011 (UTC)
Code issues in User:SimmeD/common.js
Curious about the reason? Possibly not but I will tell you anyway:
- Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
line 4 character 91: Script URL. - Evidence:
You renamed earlier today this file to File:Flag of the Republic of Macedonia.svg using criterion 2 "wrong or confusing name". Note that the name is neither wrong nor confusing, though it does not fit political agenda of some users. Thus, the file is not eligible to be moved under this criterion, and I had to move it back. Please be more careful when you move files. Thank you.--Ymblanter (talk) 07:34, 22 May 2017 (UTC)
- @Ymblanter: I'm sorry, my mistake. I'll make sure it won't happen again. --SimmeD (talk) 14:59, 22 May 2017 (UTC)
Your VFC installation method is deprecated
Hello SimmeD, we are aware that using the old installation method of VFC (via common.js, which you are using) may not work reliably anymore and can break other scripts as well. A detailed explanation can be found here. Important: To prevent problems please remove the old VFC installation code from your common.js and instead in your preferences. Thanks! --VFC devs (q) 16:24, 22 May 2017 (UTC)
Important message for file movers
A community discussion has been closed where the consensus was to grant all file movers the
suppressredirect user right. This will allow file movers to not leave behind a redirect when moving files and instead automatically have the original file name deleted. Policy never requires you to suppress the redirect, suppression of redirects is entirely optional.
Possible acceptable uses of this ability:
- To move recently uploaded files with an obvious error in the file name where that error would not be a reasonable redirect. For example: moving "Sheep in a tree.jpg" to "Squirrel in a tree.jpg" when the image does in fact depict a squirrel.
- To perform file name swaps.
- When the original file name contains vandalism. (File renaming criterion #5)
Please note, this ability should be used only in certain circumstances and only if you are absolutely sure that it is not going to break the display of the file on any project. Redirects should never be suppressed if the file is in use on any project. When in doubt, leave a redirect. If you forget to suppress the redirect in case of file name vandalism or you are not fully certain if the original file name is actually vandalism, leave a redirect and tag the redirect for speedy deletion per G2.
The malicious or reckless breaking of file links via the
suppressredirect user right is considered an abuse of the file mover right and is grounds for immediate revocation of that right. This message serves as both a notice that you have this right and as an official warning. Questions regarding this right should be directed to administrators. --Majora (talk) 21:36, 7 November 2019 (UTC)