Post your user script-related request or idea for a new user script (or gadget) as a new section below. Discussion in each section is encouraged. Note that most gadgets started out as mere user scripts. This page is intended for new user scripts, which affect the appearance of the site and may add additional functionality. Fully automated bots should be requested at Wikipedia:Bot requests instead.
All user script-related requests are welcome, whether they are for assistance writing an existing user script, desire for a new user script that does what you want, etc. Ideas for new user scripts are welcome too!
Before you request a script, please make sure it does not already exist. For a list of user scripts, see this list.
If you have been helped, please let us know, so that we may archive the request.
For accessibility purposes (see WP:DTT), all tables should have "row headers". It is annoying to copy/paste ! scope="row" |ad nauseam and a script to quickly add these to a selected column would be much appreciated. Thanks, Charlotte (Queen of Hearts • talk) 18:48, 11 September 2024 (UTC)[reply]
God I wish. It's a constant need at WP:FLC. It'd be awesome to highlight a column in visual editor or something and click an "add row headers" button and it would add ! scope="row" for cells without a span and ! scope="rowgroup" for ones with one. Hey man im josh (talk) 01:14, 24 January 2025 (UTC)[reply]
Might make more sense to build this into VisualEditor than to make it a user script. Consider filing a ticket on Phab for this and tagging it VisualEditor. Then of course drop the phab link here so myself and others can subscribe to it. –Novem Linguae (talk) 01:48, 24 January 2025 (UTC)[reply]
Is there a user script which allows people to easily propose and finish merges. The current process is prone to error and takes a long time to be finished. If there is one like it, that would be great in combating the backlog. Tavantius (talk) 21:24, 24 September 2024 (UTC)[reply]
Basically I want it to help create a merging discussion and if the discussion closes as merge, it'll help you copy-paste parts of the old article into the new article and do all the tagging as well. Tavantius (talk) 12:20, 26 September 2024 (UTC)[reply]
I'm still finding TV show articles that follow the form "Name of show was" despite MOS:TV having long established "Name of show is" as a standard. Could a bot be made to find cases of articles still using "was"? Maybe search for that word in the first sentence? Ten Pound Hammer • (What did I screw up now?)19:11, 28 September 2024 (UTC)[reply]
I don't think so – Quarry does not have access to page content, so queries which require checking wikitext cannot be answered with Quarry.jlwoodwa (talk) 00:24, 14 October 2024 (UTC)[reply]
Serial Number 54129: I've applied an update to this script, and fixed a couple of things along the way. There are still duplicate entries in the dropdown; that's more or less unavoidable since the duplicates are there in the original list itself. Let me know if you run into any issues. Writ Keeper⚇♔15:54, 10 October 2024 (UTC)[reply]
Would someone be interested in adopting this? Right now, there are only about 50 of us using it, but that's because it has a couple of unreliability issues.
Sometimes it just fails harmlessly, with no message to the user -- it just doesn't do anything at all.
Sometimes (pretty often) it fails slightly harmfully, putting the desired text in the wrong place (usually in a block notice where the example unblock request is presented).
It automatically submits the changed page, with no chance to preview.
I'm thinking that the second problem has to do with a check for "tlx|unblock" failing -- a regex issue? something to do with "chunkFiftyCharactersWide" being a wrong "chunk"? The first problem just needs an informative popup, but it would be nice to actually fix that problem. The third, I imagine, is where the "postWithToken" occurs; both the "accept" and "decline" should do the same thing "Show preview" does, i.e., show a preview.
I've worked on this user script before. If you can make me a list of bugs (oldid and description for each bug), I can probably find some time to take a look at it. The last time I worked on this I reorganized the code into a wikicode in -> wikicode out function and set up unit tests, so this shouldn't be terribly hard to work on. –Novem Linguae (talk) 22:28, 29 October 2024 (UTC)[reply]
Assume I'm ignorant. (And it's amazing what skills can vanish after 20 years of retirement from the profession.) I just listed the bugs/deficiencies above; oldid of what? --jpgordon𝄢𝄆𝄐𝄇22:46, 29 October 2024 (UTC)[reply]
I've been here two decades, I know exactly what an oldid is; you didn't specify the oldid of what. Try this one: [1]. It will fail as described in #2 above. --jpgordon𝄢𝄆𝄐𝄇15:14, 30 October 2024 (UTC)[reply]
What I was trying to say is the most useful format for me would be a list like this...
I forked the user script tonight and started refactoring the code to make it more readable, and kind of just refreshed my memory about how this user script works. You can install it at User:Novem Linguae/Scripts/UnblockReview.js if you want. Don't forget to turn off the old user script in your common.js so that the two don't clash. No bug fixes yet, but will work on this again soon. –Novem Linguae (talk) 05:14, 31 October 2024 (UTC)[reply]
Currently, there are two standard wikilink color options: blue if there is an article, and red if there is not. For those who wish to add this script, including myself, I would love to have a script that displays green wikilinks to denote Good Articles, and gold wikilinks to denote Featured Articles. The main purpose of this script would be to help users tell at a glance if an article has achieved one of these high status', without having to visit/click on the article. If not just for personal interest, this could be used to tell how close a topic is to becoming a Good or Featured Topic, and likewise to tell if a Good or Featured Topic should be delisted if a link suddenly loses its color.
@Johnson524: I had gone through a lot of trial and error to attempt to create this script, but then I discovered that User:Anomie/linkclassifier.js did the same thing and more. You can install that, and you'll get your desired effect by adding the following to your common.css:
A lot of the time, I have an article where an old version was better in some ways, but the newest version is better in other ways (e.g. after a mixed-quality edit spread across multiple sections). What I'd like is some way to take a diff between these two versions, and then paragraph-by-paragraph, select which paragraph I think is better (like I can already do with edit conflicts). Ideally in the visual editor, but it doesn't have to be, especially if there's some way to fold/hide templates and citations. – Closed Limelike Curves (talk) 03:19, 1 December 2024 (UTC)[reply]
I've seen it, and it's very good—90% of the way there. Basically all I'd need is a feature where if I have a diff, I can click a button that uses this interface to compare the two versions side-by-side. Right now, the script only shows differences from the current version. – Closed Limelike Curves (talk) 19:14, 1 December 2024 (UTC)[reply]
You could go to the old revision you want to compare against (by clicking its timestamp), click on "edit", and your edit box will be prefilled with the contents of the old revision. From there, just press "show changes". Aaron Liu (talk) 20:01, 1 December 2024 (UTC)[reply]
I'm not sure how possible this is, but it would be really nice to have a user script which adds a new icon to the top toolbar (where one's username is, notifications, watchlist, etc.) which could be customized using custom images + a custom link which it leads t 103.73.46.225 (talk) 10:40, 2 December 2024 (UTC)[reply]
Can someone make a version that combines the functionality of automatically retrieving the sources, like User:Polygnotus/Scripts/SourceTable does, with a simple interface where you can judge them. It should be usable for both NCORP stuff and non-NCORP stuff. Bonus points if you can generate the code, close the popup, save the page and then edit it again and keep going where you left off judging sources. Polygnotus (talk) 23:16, 6 December 2024 (UTC)[reply]
Please make MovedPlus.js add pages edited or moved by the script to the watchlist (or match the settings in Special:Preferences). @BilledMammal hasn't edited in almost a month or responded to requests on their talk page. Frost03:19, 10 December 2024 (UTC)[reply]
Wikipedia:Four Awards are really nice to receive, but unbearably tedious to award, as the record-keeping involves carefully noting dates, adding them to a really annoying table in a very annoying format, and doing other miscellanous tweaks. @Novem Linguae was kind enough to walk me through creating a design document for the concept - User:Premeditated Chaos/4A script idea. They're not free for a few months, but suggested I post it here in case anyone is interested in taking a whack at it. Thank you to anyone who looks, and feel free to edit that document or add questions on the talk page. ♠PMC♠ (talk)06:25, 11 December 2024 (UTC)[reply]
It's really the adding to the Records table with all the fiddly templates and dates that's the annoying part, which I'm not sure that template can really help with. ♠PMC♠ (talk)01:00, 13 December 2024 (UTC)[reply]
I'm here to ask for a script similar to User:BilledMammal/Move+, but where, if multiple pages are being RM'd, the first page on the "pages to move" list in the script's menu is always the first page in the RM, regardless of the title of the page where the RM has been made. This is to prevent the ordeal that took place here from happening again. JJPMaster (she/they) 15:23, 16 December 2024 (UTC)[reply]
@JJPMaster I think I can add this to my user tools script (see doc page here). Could you give me the following and I will try to implement it:
What namespace: based on what I'm understanding, article.
In steps, at least at the high level, what you would like it to do. I'm not sure I would be able to fork the script but I may be able to implement the features you request.
Namespaces: This tool would work in any namespace.
Steps:
There would be a button or some other indication that allows me to close an RM
I press it, and it allows me to choose between "Moved", "Not moved", and "No consensus", and also allow me to indicate if the page is being moved to a title other than what the RM proposal said
If there are multiple pages being moved, the title of the page will not be taken into consideration unless it is also included in the RM list; so as to avoid accidentally moving an entire WikiProject because an RM took place on its talk page
Afterward, it will add the {{Old move}} template to the talk pages of every article moved, and perform the moves
For Template:Interlanguage link, I'd love to have a script that will check the page for the following two common bad styles of linking: 1) a regular external link to another wik as found for example here, and 2) stuff like pl:Polska (often hidden under a pipe) and covert them to Ills. This shouldn't be that hard to code (I hope), but I am not seeing anything like that mentioned anywhere. Bonus for 1) thats might be harder to code - check for shortened URLs; I've seen some newbies use them too.. Piotrus at Hanyang| reply here13:10, 25 December 2024 (UTC)[reply]
Anyone attempting 2) should make sure to avoid conversion of [[:pl:Polska]] and [[:pl:Polska|Polska]] style links inside cs1|2 templates. {{ill}} must not be used in those templates.
@Trappist the monk, sounds like you're saying to avoid pl:Polska, Polska, and {{Ill}} in cs1|2 templates. Is that correct? If none of those, any recommendations for what to use, or avoid entirely?
No. What I wrote did not come out the way I wanted it – I've tweaked it a bit. What I wanted to say was: do not convert [[:pl:Polska]] and [[:pl:Polska|Polska]] links inside cs1|2 templates to {{ill}} templates. [[:pl:Polska]] and [[:pl:Polska|Polska]] are perfectly acceptable in cs1|2 templates.
@Novem Linguae See Wuliang Pagoda - Wikipedia (old rev, fixed since). Mind you, this is pretty rare, so if we cannot deal with that, that's ok. It's more of a 'perfectionist'-level fix.
@Michael Bednarek Right, but this should be a one tool with a two-step process. First, automatically fix the badly formatted links with a given target, then (optionally?) suggest the output that Cobaltcigs tool proviedes, for a review. Realistically, anyone using his tool wants want I propose we code, and probably vice versa too. Piotrus at Hanyang| reply here04:42, 26 December 2024 (UTC)[reply]
@Piotrus I somehow made typos while copying over the fixed script. It definitely should work now; I tested loading the script under safe mode (i.e. disabling everything else I have). Sorry for all the hassle. Aaron Liu (talk) 03:37, 28 December 2024 (UTC)[reply]
It looks like the exact same reason: When syntax highlighting is enabled, you need to use a different MediaWiki-provided API to edit the textbox. I'll check it out. Aaron Liu (talk) 14:36, 28 December 2024 (UTC)[reply]
@Aaron Liu Any progress? Would disabling the syntax highlighter fix things?
Sorry, I frankly forgot about this. IllWill is indeed the same issue, but DisamAssist works perfectly well for me. What problems do you encounter when you use it? Aaron Liu (talk) 03:18, 29 January 2025 (UTC)[reply]
The basic idea I had is to alternate the colors of links in the body of a page. This will hopefully look pretty and also solve the problem of distinguishing adjacent links from a single link with a space in it. I made a script to do this, but it could be taken a lot further if anyone else is interested in playing around with it.
Oops, this is in requests. I guess I should explicitly state I am looking for feedback, especially any JS pointers since I'm not too familiar with web development. Edit7hesadparts (talk) 15:44, 31 January 2025 (UTC)[reply]
Hello! A pain point for myself, and others who pursue FAs, is ensuring that the SFN & HARVNB templates is "p=" for single page (e.g., p. 4) and "pp=" for a citation spread across pages (e.g., pp. 4–6 or pp. 4, 6). I don't want to dictate outcomes here but I'd be very interested (as, I am sure, would all FA contributors) in something that makes this easier. Either by highlighting infractions or fixing it automatically. Would be cool to hear any thoughts. — ImaginesTigers (talk∙contribs) 18:46, 7 February 2025 (UTC)[reply]
I have looked through the areas I would expect to see that functionality included in (e.g., autoFormatter) and no, it doesn't. This request came out of an FAC discussion – I think someone would have told me if AWB was able to do it (unless the feature's been forgotten). But yeah I don't see it there sadly. — ImaginesTigers (talk∙contribs) 19:28, 7 February 2025 (UTC)[reply]
Hi ImaginesTigers, there actually is a script for this (a bloody nice bit of kit from Laboratoires Lingzhi), not only does it highlight pp. errors, but also alerts when publications are too early for ISBNs, need a pub. location, doi etc; in fact, all the stuff pernickety errors source reviewers highlight... i.e., it's where they find 'em ;) Serial(speculates here)20:02, 7 February 2025 (UTC)[reply]
Alright so I've been using User:Jeeputer/defconIndicator.js (super useful script by the way @Jeeputer) to check for vandalism information quickly in my toolbar, but I've been wanted to change it to show the pending changes backlog (like this). Problem is I haven't the slightest clue how to change user scripts, and I think Jeeputer's one uses ORES. Any thoughts are greatly appreciated, thanks! Sophisticatedevening(talk)23:42, 18 February 2025 (UTC)[reply]
@Sophisticatedevening: Hi. If you are familiar with Javascript, you can copy the code to your own userspace (i.e. a subpage) and tweak it to do what you want, otherwise I can expand the script to show the pending changes backlog too, or even create a new script for that purpose (the latter is preferred). JeeputerTalk08:06, 19 February 2025 (UTC)[reply]
Thanks for the response! Unfortunately my coding skills do not extend beyond basic html, so I'm not able to tweak it effectively myself. If you have the time to expand or create one, that would be super appreciated. Sophisticatedevening(talk)12:24, 19 February 2025 (UTC)[reply]
Can anyone create a script that can filter categories by namespace? If it be further sorted by the time of entry of an article into a category, it will be even better. These informations are already available in XML format (example), however that doesn't allow clicking or previews. Thanks! —CX Zoom[he/him](let's talk • {C•X})16:01, 13 March 2025 (UTC)[reply]
I can't build scripts, but can you elaborate on your request for the sake of editors who can? Are you talking about a search while sitting on a category page, and what kind of output are you expecting? Not knowing what you mean makes it hard to be sure, but I think that the Petscan tool might possibly do what you want. Mathglot (talk) 20:36, 3 April 2025 (UTC)[reply]
Hello. Can someone take over User:Lourdes/Backlinks.js, and make it work regardless whether one is in main or Draft space?
Inactive user Lourdes (talk·contribs) created this very handy (and very brief) script that adds a "Possible backlinks" link to the left toolbar which finds articles with possible backlinks for the current page. Works great in mainspace, but from a Draft, it creates a Cirrus search that uselessly targets draftspace, which articles will never do, so no results are returned. For example, for Draft:Free play, it creates search link "Draft:Free_play" -linksto:Draft:Free_play, and that obviously won't work. Can you fix it by chopping off the 'Draft:' prefix from the generated search link so it does?
As a possible additional enhancement, I think an added -intitle:<article name> term might possibly help refine the result set, as it eliminates articles right at the top of the search list that have the article name in the title of the search result. For example, compare these two searches:
The second link eliminates five results, returning 527 instead of 532, but they were all sitting at the top of results in the first link, so less cruft to scroll past in the second link. Not sure if this is enough of an improvement to merit doing, or if there's a downside to it – perhaps it would eliminate some good articles in some cases? See what you think. If it's not a clear improvement, then just adding Draft space support to the script would be a big improvement. Thanks, Mathglot (talk) 20:31, 3 April 2025 (UTC)[reply]
mw.loader.using("mediawiki.util",function(){letpgnm='"'+encodeURIComponent(mw.config.get("wgPageName").replace("Draft:",""))+'"'mw.util.addPortletLink("p-tb","https://en.wikipedia.org/w/index.php?title=Special:Search&search="+pgnm+"+-linksto%3A"+pgnm+"+-intitle%3A"+pgnm,"Possible backlinks","t-wdlh-check","View articles where possible backlinks may be created for the current page");});
Ponor, super, thank you! One slight housekeeping issue: if I host it, I may get bug reports or enhancement requests from others that I have no idea how to deal with, as I don't know javascript. Do you know someone who might agree to host it who can handle any issues? Or conversely, is there a kind of 'js commons' where people can maintain scripts in common without claiming ownership? I can always just let this request hang here for a while, hopefully a volunteer will turn up. In the meantime, I will install it as you suggested, at least to verify that it is working as expected. Thanks again! Mathglot (talk) 01:09, 4 April 2025 (UTC)[reply]
That can be your private script, nobody needs to know about it :D It's also a very simple one. If you or anyone else needs help with it - you know where to find me. In fact, you can paste the above code straight into your Special:MyPage/common.js, that does not need to be a stand-alone script at all! Ponor (talk) 01:24, 4 April 2025 (UTC)[reply]
Understood. Already copied it as a standalone, and made it clear in the summary that I can't help with it if someone as issues; but I also set it at CC0, so anyone can help themself. It's working fine, so once again, much obliged, and thanks again for the assistance! Mathglot (talk) 01:40, 4 April 2025 (UTC)[reply]
In the old WikiEditor it is pretty easy to define some custom buttons.
I have made proof of concept scripts that load a JSON file with custom buttons, and allow using any image instead of just these, both for VE and DiscussionTools.
For reasons beyond my understanding the WMF does not appear to be interested in actually providing this functionality.
I do not believe in JavaScript and I think it is morally wrong. Is there some JavaScript god here who can look at these proofs of concept and make something better (or less shit)?
I uploaded the code to Phabricator, links are on the right hand side.
Ideally as much of the WikiEditor toolbar customization options as possible would be supported. Ideally there would also be a script to generate the JSON.
Screenshot of script adding extra buttons to the New Topic Tool
Screenshot of script adding extra buttons to the ReplyTool
Screenshot of script adding an extra button to the Visual Editor
Screenshot of script adding extra buttons to the Visual Editor
@Nurginformed me of an error which affects both the version of Move+ created by @BilledMammal and @Polygnotus's fork (hosted in @Frost's userspace).
When using the 'Notify WikiProjects' function, and when notifying WikiProject New Zealand, an error occurs when a comment is left in the move discussion. Move+ leaves the code [[Wikipedia:New Zealand Wikipedians' notice board|ealand Wikipedians' notice board]], effectively removing the "New Z" from "New Zealand" in the comment.
See Special:Diff/1285364289 for BilledMammal's version making the error and Special:Diff/1285372599 for Polygotus's version making the error.
Is anyone able to fix the error and take on maintaining the script as BilledMammal hasn't edited in a number of months since the outcome of WP:ARBPIA5.
Ps, if someone does take it on, forking from BilledMammal's version would be in my opinion preferable, as that version doesn't add pages to the watchlist. TarnishedPathtalk10:38, 13 April 2025 (UTC)[reply]
@TarnishedPath I added const WATCHLISTPAGES = false; to the top. If you set it to true it watchlists pages. The original script just strips 15 characters which assumes the prefix is "Wikipedia talk:". Polygnotus (talk) 11:02, 13 April 2025 (UTC)[reply]
BilledMammal wrote: I hope to return later this year or early 2026 so hopefully they will be back soon. Which means that being a maintainer will not be a commitment for the rest of your life. Polygnotus (talk) 11:39, 13 April 2025 (UTC)[reply]
Yeah its great for lazy people like myself. When you have many references in an article it becomes near impossible to figure out which are duplicates without a script to help you. Polygnotus (talk) 11:10, 13 April 2025 (UTC)[reply]
Hello, I'm an NPP reviewer and I notice that some pages have been sneaky and have no {{reflist}} and <reference/> in the reference section. So, May I request a script where there will be warning either in the Page Curation Tool or in the top if a page does not have {{reflist}} or <reference/> in them. Thanks Warm Regards, Miminity (Talk?) (me contribs) 08:13, 16 April 2025 (UTC)[reply]
@Macaw*: I tested some of there is something I would like to change (maybe a bug). It shows up even when I'm just editing a section of a page, on redirect page and deleted pages. Much appreciated your work!! Warm Regards, Miminity (Talk?) (me contribs) 13:22, 5 May 2025 (UTC)[reply]
Being able to sort reflists by their provenance, such as by URI or other identifier, would be very handy for managing citations. Tools like CiteHighlighter and UPSD are all well and good for seeing what has already been assessed as reliable or not, but to assess anything that those two say nothing about, collation would massively reduce the cognitive load of searching for URIs etc., as well as the risk of missing a citation.
Being able to apply a categorisation before the sorting is applied would also be a massive help, to sort – for example – sources that the editor deems reliable in context from ones that are unreliable. EnronEvolvedMy Talk Page22:59, 26 April 2025 (UTC)[reply]
OK this is not real. But at the very least we need a user tool for selective citation (not all citations) conversion that doesn't require a lot of copy pasting and navigation. Countless times I have googled "Title Case Converter", copy paste a string, press a button, marvel at result, copy paste a string. This should be easier. If you write the actual conversion function with AI it will get the edge cases, such as dealing with : and other things, and generate a suite of test cases.
I am loooking for user scripts for user script development such as js syntax highlighting. Is there a list of them anywhere or could someone help me make one. Macaw*02:37, 6 May 2025 (UTC)[reply]
When you attempt to create a double redirect you are shown a warning that includes a suggested fix (i.e. if Foo is a redirect to Bar and you attempt to create a redirect to Foo, MediaWiki shows a warning recommending you change the target of your new redirect to be Bar).
In response to Wikipedia:Village pump (proposals)#Double redirect creation I opened phab:T393825 requesting a link or button to automatically implement the suggested fix. Comments on that task by the developer who implemented the warning suggest that this might be complex to implement as part of MediaWiki but that "This could definitely be implemented on-wiki via a JavaScript gadget though." Thryduulf (talk) 11:48, 13 May 2025 (UTC)
WP:GADGET#Proposals directed me to VPT, but Bugghost commented there directing me here. I have no idea which is the better location for this, but to keep comments in one location please pick one and close the other with a pointer. Thryduulf (talk) 22:44, 14 May 2025 (UTC)[reply]
Hello! Is there a user script that allows individual items to be marked as read (without opening it) straight from the watchlist? xRozuRozu • teacups18:11, 16 May 2025 (UTC)[reply]
Currently, you need to preview {{Ref info|style=float:right}} on the article, or place {{Ref info|style=float:right}} on the article's talk page, to gain any insight and display the citation statistics, e.g. for quark
I'd like a script that automatically displays it on all articles/drafts (perhaps with a toggle to hide it / enable it on other namespaces). Or, more likely, a customizable default that can be toggled in-article. Headbomb {t · c · p · b}09:30, 21 May 2025 (UTC)[reply]
@Headbomb: I didn’t make it show up floating on pages by default because I wasn’t sure where to place it; so, instead, it shows up as a dialog popup when you click the "show ref info" option. LMK if this is sort of what you wanted: User:DVRTed/refInfo.js. Regards, — DVRTed (Talk) 16:12, 27 June 2025 (UTC)[reply]
Does anyone know of any current scripts which can look at a discussion (usually drawn from an archive) and will outputs a list of unique non-IP editors who participated in the discussion like the following:
@[[User:Editor 1|Editor 1]], @[[Editor 2|Editor2]], ...?
If not is anyone able to write it? Whenever I've pinged previously involved editors to a discussion, I've done it manually reading through discussions, which is time consuming. TarnishedPathtalk08:39, 25 May 2025 (UTC)[reply]
I don't know if the script is failing or if it's just down to the lack of visual feedback? So I made it change from red to blue after it is clicked (sorry if that's confusing, I don't know if there's a way to have a popup in the mediawiki interface or something...) REAL_MOUSE_IRLtalk14:54, 25 May 2025 (UTC)[reply]
For pop-up dialogs, you can either learn Vue.js and use the dialog from Wikimedia Codex, or use the legacy OOUI with normal JavaScript. For feedback you can just use mw.notify(). Aaron Liu (talk) 18:10, 28 May 2025 (UTC)[reply]
Another approach would be to copy paste the wikicode into a website such as https://regex101.com and write a RegEx pattern that extracts the usernames. You probably don't need this advice since someone wrote a user script, but will mention anyway just in case. –Novem Linguae (talk) 04:50, 26 May 2025 (UTC)[reply]
Hello! Looking for a script that lets me press the keys <Control>+<Shift>+<R> to go to a random page without a short description of any type including auto created ones from templates like info boxes or from the short description template. Best wishes,Macaw*!16:30, 28 May 2025 (UTC)[reply]
@Macaw* It's pretty straightforward to make such a script (using the search results from -hastemplate:"Short description"), but I don't think there's an easy way to filter out pages with auto-generated short descriptions. @ me if that'd work for you. — DVRTed (Talk) 20:05, 24 June 2025 (UTC)[reply]
I see those templates that auto-generate short descriptions use {{Has short description}} to check if an article has a short description, and sometimes just {{Short description}}. If we filter both of them out, it seems like we get what we're looking for; i.e. -hastemplate:"Has short description" -hastemplate:"Short description". There might be some edge cases, but I've yet to find any. — DVRTed (Talk) 20:57, 24 June 2025 (UTC)[reply]
Every so often, I come across an IP that isn't disruptive in itself, but its range is blocked because the range was very disruptive. I could not have known that if the block log was not shown. But in the case, block hasn't yet been applied, it is very difficult to assess the amount of disruption coming from the range, because I can't create ranges on my own. A user script that works on every IP page by creating a list of IP ranges the current editor belongs in would be very helpful. It could link to the range contribs pages. Thanks! —CX Zoom[he/him](let's talk • {C•X})17:32, 28 May 2025 (UTC)[reply]