Wikipedia:Interface administrators' noticeboard

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Xaosflux (talk | contribs) at 15:24, 31 October 2023 (→‎Inactive interface administrators 2023-10-28: d). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

    Welcome to the interface administrators' noticeboard

    This is the interface administrator noticeboard, for discussion of interface administrators and coordination of edits to the interface.

    Currently only interface administrators can undelete JS/CSS pages, if you have an uncontroversial undelete or deleted version retrieval request, please list it below.

    Any administrator can delete JS/CSS/JSON pages, for speedy deletions just use a CSD template on the page or its talk page.

    Individual requests for edits to interface or user JavaScript/CSS pages should continue to be made on their respective talk pages.

    0 interface-protected edit requests
    v·h
    Page Tagged since Protection level Last protection log entry
    Updated as needed. Last updated: 17:30, 19 February 2024 (UTC)


    Retired user populating deleted categories

    Please could the 5 instances of "members" be changed to "participants" in User:Kyoko/userpage.css following Wikipedia:Categories_for_discussion/Log/2023_October_1#Category:WikiProject_X_members? – Fayenatic London 08:12, 22 October 2023 (UTC)Reply[reply]

     Done. Diff. A css file is a weird spot for categories, but to each their own I guess. –Novem Linguae (talk) 15:07, 22 October 2023 (UTC)Reply[reply]
    These pages are being used to protect their user pages from modification via transclusion, to allow only themselves and what used to be admins to change it. I don't know exactly when or how the practice started.
    When the user is retired or otherwise long-term absent, it is usually better to substitute/copy the contents to the user page and to blank the CSS page. This allows routine project-wide maintenance such as this request to be done. Izno (talk) 18:46, 22 October 2023 (UTC)Reply[reply]

    A mass renaming of people in hundreds of WikiProjects from "members" to "participants" has taken place. A few of the old categories are still populated because users have embedded the old category name in .css pages that can't be easily edited.

    Can somebody with the right access go through the following (some categories have been deleted by the bot but still have entries) and fix the entries? Thanks in advance.

    Timrollpickering (talk) 10:13, 22 October 2023 (UTC)Reply[reply]

    @Timrollpickering, I will take a look at this, but could I ask you to move this request to WP:IANB? There is already a section there on the matter of these pages having these categories, and that is the right set of users anyway to action this request. Izno (talk) 19:03, 22 October 2023 (UTC)Reply[reply]
     Done Izno (talk) 20:40, 22 October 2023 (UTC)Reply[reply]

    OneClickArchiver old version is creating a mess

    First mentioned at Wikipedia:Village pump (technical)#WP:1CA "undefined". It looks like the old version of OneClickArchiver by arbcom blocked user Technical13 (User:Technical 13/Scripts/OneClickArchiver) has a bug that is creating a mess. It keeps creating archive pages named "undefined". List of pages. It looks like several editors still use the old version of the user script instead of the better, bug fixed version User:Evad37/OneClickArchiver.

    I think we should do something about this to stop the disruption. I think notifying a bunch of users and asking them to change user scripts is a bit labor intensive since it's so many users, and won't keep the problem from cropping up in the future. I think a more permanent solution would be blanking User:Technical 13/Scripts/OneClickArchiver.js, or BLARing User:Technical 13/Scripts/OneClickArchiver.js with something like importScript('User:Evad37/OneClickArchiver.js'); Thoughts? cc Awesome Aasim. –Novem Linguae (talk) 15:03, 24 October 2023 (UTC)Reply[reply]

    FWIW, User:Jo-Jo Eumerus/JS pages using old OneClickArchiver Jo-Jo Eumerus (talk) 15:30, 24 October 2023 (UTC)Reply[reply]
    @Novem Linguae How about start with mw.notify($("Warning: It seems you have a deprecated script installed. Please replace \"User:Technical 13/Scripts/OneClickArchiver.js\" with \"User:Evad37/OneClickArchiver.js\"")). Or better solution: Add an abuse filter to initially stop the creation of "undefined" archives, then tag the edit with "Possible malformed archive". There has been several years to migrate to the new script. We shouldn't be using a script that has been unmaintained for several years. Awesome Aasim 15:46, 24 October 2023 (UTC)Reply[reply]
    Here is some script code for abuse filter:
    action == "edit" & page_namespace != 0 & page_title rlike ".*\\/.*undefined.*"
    Might need further refinement.
    Action to take: disallow, then tag with "possible malformed archive". Awesome Aasim 15:51, 24 October 2023 (UTC)Reply[reply]
    If we get everyone off the old script, we won't need an edit filter. Edit filters are resource intensive and they probably shouldn't be the first tool we pull out of our toolbag.
    I don't personally like the mw.notify approach since that would bug a lot of people, when we can just do it automatically for them. But I would like to hear an experienced interface admin chime in about that. Maybe mw.notify is the necessary approach so that folks get to pick which user scripts they install and trust? –Novem Linguae (talk) 15:54, 24 October 2023 (UTC)Reply[reply]
    I would prefer to simply blank the script, I think, with a note explaining what's going on on the script's talk page (or in a comment on the script page itself). mw.notify is more of a nuisance than a viable information vector (people will just dismiss it and get annoyed, without reading it). And I also don't love the idea of redirecting to another userscript that people haven't chosen themselves. Writ Keeper  16:09, 24 October 2023 (UTC)Reply[reply]
    I've blanked it with pointers both to here and its replacement. Izno (talk) 16:46, 24 October 2023 (UTC)Reply[reply]
    Awesome. I added some comments and blanked the beta version as well.
    Resolved
    Novem Linguae (talk) 16:54, 24 October 2023 (UTC)Reply[reply]
    Next step is to fix those archives! Well, that was fast, as it was listed on Wikipedia:AutoWikiBrowser/Tasks#Cleanup_of_30_talk_page_archives_with_"undefined"_in_title. Now hope the undefined monster does not come back! Awesome Aasim 20:31, 24 October 2023 (UTC)Reply[reply]

    Inactive interface administrators 2023-10-28

    The following interface administrator(s) are inactive:

    — JJMC89 bot 23:18, 28 October 2023 (UTC)Reply[reply]

    FYI, removed :) — TheresNoTime (talk • they/them) 13:25, 31 October 2023 (UTC)Reply[reply]
     Donexaosflux Talk 15:24, 31 October 2023 (UTC)Reply[reply]