Jump to content

Wikipedia talk:Cascade-protected items

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Protected edit request on 22 April 2020

[edit]

I'm requesting that the following pages please have their cascading protection removed:

  1. Wikipedia:Introduction/Tab1
  2. Wikipedia:Introduction/Tab2
  3. Wikipedia:Introduction/Tab3
  4. Wikipedia:Introduction/TabsBottom
  5. Wikipedia:Introduction/TabsTop

...Reason being is that Wikipedia:Introduction was recently repurposed with its former content being moved to Wikipedia:Introduction (historical). In response, all subpages of Wikipedia:Introduction are being adjusted/fixed to match the content at Wikipedia:Introduction (historical), considering that Wikipedia:Introduction is no longer the proper parent page for the subpages mentioned in this request. Steel1943 (talk) 20:53, 22 April 2020 (UTC)[reply]

Done. Jo-Jo Eumerus (talk) 08:45, 23 April 2020 (UTC)[reply]

Ceranium's stuff

[edit]

I assume "Ceranium's stuff" was meant to refer to Cenarium (talk · contribs) (referring to the historic User:Cenarium/Protected templates) but as you can see the username is misspelled. Please swap the "r" and the "n". Thank you. —Uzume (talk) 18:26, 21 June 2020 (UTC)[reply]

 Done — Martin (MSGJ · talk) 18:58, 21 June 2020 (UTC)[reply]

Padlocks

[edit]

It looks to me like all system messages have been migrated to the new-style padlocks. As such, I'd like to remove the old-style padlocks File:Padlock.svg and File:Padlock-blue.svg from this list. Any objections? Jackmcbarn (talk) 03:55, 5 October 2020 (UTC)[reply]

The first is linked from 684 pages and the second from 1277 pages. OTOH they look mostly like archives and userboxes? I don't think we need cascading protection for such cases. The first file exists on Commons and is upload protected, so I would say we don't need the local version at all. Jo-Jo Eumerus (talk) 08:23, 5 October 2020 (UTC)[reply]
Okay, removed from here, and I asked the original uploaders of those two files whether they still care about keeping local copies. Jackmcbarn (talk) 19:42, 8 October 2020 (UTC)[reply]

Category icon

[edit]

Can you replace File:Folder Hexagonal Icon.svg () with File:Symbol category class.svg (). While the link count states the folder icon has over 1.13 million file links, this is wrong and I can't imagine it is over 100k. The icon was replaced a while ago with "Symbol category class.svg" which currently has over 927k file links. Terasail[✉] 14:55, 22 April 2021 (UTC)[reply]

 Done I added the new one, lets wait for counts to update before pulling the old one. — xaosflux Talk 15:04, 22 April 2021 (UTC)[reply]
@Xaosflux: Thanks. Considering that the icon change was made over 10 weeks ago and the counter has not updated significantly. I think the only way that the true count will be displayed is with a bot that is run to WP:Ø edit the pages. (This is what I did to check that there were no template transclusions, but I don't have a bot account to run so I can't process that many pages) Terasail[✉] 15:11, 22 April 2021 (UTC)[reply]

Protected edit request on 14 August 2022

[edit]

Remove {{cite article}}, per WP:Redirects_for_discussion/Log/2022_August_3#Template:Cite_article. --BrownHairedGirl (talk) • (contribs) 18:55, 14 August 2022 (UTC)[reply]

Was done by Plastikspork. * Pppery * it has begun... 02:02, 15 August 2022 (UTC)[reply]
Thanks, @Pppery and @Plastikspork.
Plastikspork's edits removed the last 2 backlinks, so the ambiguous redirect is now gone. BrownHairedGirl (talk) • (contribs) 06:50, 15 August 2022 (UTC)[reply]

Protecting File:Treffpunkt.svg

[edit]
The image in question

I think File:Treffpunkt.svg should be uploaded and protected locally. At the risk of spilling the WP:BEANS, it is not even protected on Commons. This is currently used in {{centralized discussion}}, which is certainly a WP:HIGHRISK template. While that template is only semi-protected so editors can list discussions, the helper template that directly links to the image (Template:Centralized discussion/core) is template protected. The image is linked to more than 5,500 times, which is more than some of the images listed under #Other known high-risk images. Thoughts? HouseBlastertalk 21:52, 6 November 2022 (UTC)[reply]

Protected edit request on 9 November 2022

[edit]

Please remove File:Lock icon blue.gif from Wikipedia:Cascade-protected_items/content#Used_in_interface_and_message_boxes. It's not been in use for years, and it was deleted locally in 2017. --rchard2scout (talk) 11:00, 9 November 2022 (UTC)[reply]

 Donexaosflux Talk 19:11, 9 November 2022 (UTC)[reply]

Update Top 100 files and keep local copies of new entries.

[edit]

I have recreated the list of the top 100 files according to Special:MostLinkedFiles. Please replace Wikipedia:Cascade-protected items/content#The 50 most-used images and Wikipedia:Cascade-protected items/content#The 51-100 most used images with the equivalent sections in my sandbox. Along with this please also protect and create a local copy (With {{Keep local high-risk}}) of the new entries to this list, which are the following:

Terasail[✉️] 02:08, 27 February 2023 (UTC)[reply]

Hi Terasail, you could help out with this by uploading the local versions and then I will protect them. Are you up for that? — Martin (MSGJ · talk) 13:56, 2 March 2023 (UTC)[reply]
I might be wrong about this but I think you need to be an administrator to upload a local copy of a file. I can't use Special:Upload when there is a commons file, so unless you create a local copy another way I can't help you with this, I originally tried with File:MediaWiki Namespace.svg (Which you just created), but I just get told to use a different name to upload a file. Terasail[✉️] 14:01, 2 March 2023 (UTC)[reply]
Looking at Special:ListGroupRights, to create local files I would need the "reupload-shared" permission which is only given to admins, sorry about that. Terasail[✉️] 14:09, 2 March 2023 (UTC)[reply]
Okay, I had no idea about that! — Martin (MSGJ · talk) 16:02, 2 March 2023 (UTC)[reply]
Good thing is, that this sort of change shouldn't happen often. It just happens that the file list hasn't been touched in any meaningful way since the contents were moved from userspace. Terasail[✉️] 16:12, 2 March 2023 (UTC)[reply]
 Not done for now: Doesn't appear to have consensus at this time, and alternatives have been proposed. Izno (talk) 17:52, 11 April 2023 (UTC)[reply]

Protect on commons

[edit]
I think we should look at a better way of doing this. For example, something similar to how Wikipedia:Main Page/Commons media protection works — Martin (MSGJ · talk) 16:20, 2 March 2023 (UTC)[reply]
That could be an interesting idea, but would require discussion with commons? Since these would be longterm protections rather than short term, but getting a bot to do it could be interesting. My main concern with initally making the request is that there are files with over 200k uses that are completley unprotected and the second most used file is completley unprotected (don't tell anyone). Terasail[✉️] 16:38, 2 March 2023 (UTC)[reply]
I will enquire about whether it's possible. In the meantime, perhaps FunkMonk or Mitchazenia would help us out by protecting these on commons? — Martin (MSGJ · talk) 17:18, 2 March 2023 (UTC)[reply]
I don't really know much about this issue, I wonder if it would be better to ask someone who is both an admin on Wikipedia and Commons about this? FunkMonk (talk) 17:28, 2 March 2023 (UTC)[reply]
The technical ability shouldn't be dificult. A request to the bot operator to also get files from Wikipedia:Cascade-protected items/High risk files (Example page) in addition to the current page should do it. However the commons bot request only references getting main page files (Which will only be protected short term). And as this page proves, a majority of these files will not change over 5 years and would be equivalent to indefinate protection which would probably require some discussion on commons at a minimum. I don't see a discussion on enwiki as being necessary since high use files (somewhat) are already cascading and fully protected here. Terasail[✉️] 17:49, 2 March 2023 (UTC)[reply]
The Commons page to request protections on is commons:Commons:Administrators' noticeboard/Blocks and protections, and the policy that says that files used widely across projects can be protected is Commons:Protection policy#Upload protection. Jo-Jo Eumerus (talk) 15:58, 6 March 2023 (UTC)[reply]

File:Parlophone LP PMC 1202.jpg

[edit]

This file claims it's cascade protected by this page, but I can't find it here. Jo-Jo Eumerus (talk) 08:53, 11 June 2023 (UTC)[reply]

This page includes c:File:Vynil record.jpg which redirects to c:File:Parlophone LP PMC 1202.jpg. The handling of redirects on Commons is kind of weird, it often silently follows the redirect with no indication that there was one. Anomie 11:18, 11 June 2023 (UTC)[reply]
Ah, I see. That redirect doesn't seem to be that widely used (and neither its target) and it doesn't appear on the MediaWiki namespace, so I've removed it from here. Jo-Jo Eumerus (talk) 13:29, 11 June 2023 (UTC)[reply]

Protected edit request on 25 October 2023

[edit]

Please add {{#invoke:lockbox|lock|Template:Blocked text}} as this message is used in the MediaWiki interface (MediaWiki:Blockedtext). Awesome Aasim 01:11, 25 October 2023 (UTC)[reply]

 Not done I don't think this is necessary - the page is already fully-protected and isn't especially high-risk as fully protected pages go. * Pppery * it has begun... 01:42, 26 October 2023 (UTC)[reply]

Protected edit request on 27 October 2023

[edit]

Please change the shortcut on the subpage from WP:CASC (the main page) to WP:CPI/C (a shortcut I juts created for the subpage). Awesome Aasim 14:35, 27 October 2023 (UTC)[reply]

 Done * Pppery * it has begun... 14:46, 27 October 2023 (UTC)[reply]