Wikipedia talk:Twinkle

WT:TW

This is the talk page for discussing improvements to the Twinkle page.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Tips for writing good bug reports and feature requests:

Include the affected article name and a diff.
Include a screenshot.
For bugs, include the exact steps to reproduce the bug. Bugs need to be reproducible.

We will use this information to create a ticket on GitHub, which is our todo list for volunteer developers. For most tickets, expect them to take a long time (months). They will need to attract the interest of a volunteer developer, then go through code review, then get merged to master, then get deployed.

Twinkle has detailed documentation located at WP:TW/DOC.

Archives

Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
11, 12, 13, 14, 15, 16, 17, 18, 19, 20
21, 22, 23, 24, 25, 26, 27, 28, 29, 30
31, 32, 33, 34, 35, 36, 37, 38, 39, 40
41, 42, 43, 44, 45, 46, 47, 48

Other archives

Friendly talk archives: 1, 2, 3, 4, 5

Old Bugs page; archive 1, 2, 3, 4, 5

Old RFA page; archive 1, 2

This page has archives. Sections older than 30 days may be automatically archived by when more than 30 sections are present.

Template:Db-t5

Tracked in github.com
Issue #2094

Please add the new Template:Db-t5. Gonnym (talk) 07:40, 3 December 2024 (UTC)[reply]

Just bumping this so it doesn't get lost. Primefac (talk) 21:15, 5 January 2025 (UTC)[reply]

@Novem Linguae can the various pull requests (including this) be merged? Gonnym (talk) 09:26, 22 January 2025 (UTC)[reply]

I don't have time right now to review all 20 of them, but can try to take a look at the Db-t5 one. The delay with PRs is that they require manual testing, which is laborious. But breaking Twinkle for 50,000 people and then fixing it is even more laborious, so we're stuck with manual testing for each PR :) –Novem Linguae (talk) 11:49, 22 January 2025 (UTC)[reply]

I don't know how to test this here (is there a beta version of Twinkle that can be imported?), but looking plainly at the code and the discussion seems correct. There is no need for notifications. Gonnym (talk) 11:55, 22 January 2025 (UTC)[reply]

I ran into a case where I needed db-t5. –LaundryPizza03 (d c̄) 21:51, 16 February 2025 (UTC)[reply]

Auto detect the CSD tag while viewing history

Sometimes when processing CSD tags, such as U1 (user request for sub page in their user page), G7 (user request to delete a page they were the sole contributor to), and G5 (no substantial edits except for socks), I have to check the history of the page. From the history page, it won't detect what the CSD tag on the page is like it would if I was simply viewing the tagged article and pressed the CSD button (autofilling in the deletion rationale). It'd be a lot more convenient for me, and I'm sure other admins who process CSD requests, if we didn't have to go back to the article to have the rationale from the CSD tag autofill. Hey man im josh (talk) 13:57, 30 January 2025 (UTC)[reply]

I'll second that (it would be nice), genuinely don't know if that sort of thing is possible though. Primefac (talk) 21:14, 3 February 2025 (UTC)[reply]

Third party --> Independent sources

Please note that the Template:Third party switched over to Template:Independent sources per WP:DONTSAY3RDPARTY. The redirect was preserved, but the wording of Twinkle could be changed for consistency.

jps (talk) 18:38, 30 January 2025 (UTC)[reply]

Store warnings list and other data separately

If there's agreement that it should be added I'll create an issue on GitHub.

Basically, my suggestion is to move the config (such as warning lists, CSD templates) to separate files like RedWarn/Ultraviolet does, e.g. Wikipedia:RedWarn/Default Warnings, Wikipedia:Ultraviolet/configuration.json. Doesn't have to be on-wiki. ~ Rusty ^meow ~ 22:33, 9 February 2025 (UTC)[reply]

Can you talk a bit about the advantages of this approach? Using User:Rusty Cat/twinkleoptions.js as an example, I'm not really seeing that this JSON file is too big or hard to read the way we're doing it now. –Novem Linguae (talk) 22:45, 9 February 2025 (UTC)[reply]

@Novem Linguae: I meant the data currently stored in JavaScript files on GitHub, like the warnings list. I feel like it could make updating or localizing Twinkle easier. ~ Rusty ^meow ~ 00:45, 11 February 2025 (UTC)[reply]

Yeah, it can be good to not mix types in the same file (mixing JS and JSON, in this case). Some downsides though would be 1) yet more MediaWiki files needed, and Twinkle already uses like 20, 2) deploy script might need changing, and 3) having all code needed for a Twinkle module in that module is a decent way to organize things.

This isn't a no, but these are my initial thoughts.

Some good candidates for extraction would be the default config, welcomes, maintenance tags, warnings, and probably others that I'm forgetting. There's probably a lot of JSON data sprinkled around in Twinkle. –Novem Linguae (talk) 01:10, 11 February 2025 (UTC)[reply]

Dark mode error

On diffs, when using dark mode, the [Restore this revision] links are hard to read. Can a change to implement dark mode compatibility be implemented? Justjourney (talk) 03:00, 13 February 2025 (UTC)[reply]

I meant [Restore this version] in my last comment. Justjourney (talk) 03:01, 13 February 2025 (UTC)[reply]

Rollback options

I've been using Twinkle for years and recently became a New Pages Patroller which required me to make a few changes to my Twinkle preferences. Ever since then, I've lost my Twinkle rollback functions (AGF rollback / Normal rollback / Vandalism rollback) and cannot for the life of me work out how to get those links back. Does anyone know how these are switched on/off via my Twinkle preferences? Now I'm only seeing the standard "undo" revert option (on the diff page) that everyone sees. Rodney Baggins .talk. 12:44, 14 February 2025 (UTC)[reply]

@Rodney Baggins: In your Twinkle settings (TW > Config), search for "Show rollback links on these pages" and tick "Diff" there. -- John of Reading (talk) 13:14, 14 February 2025 (UTC)[reply]

@John of Reading: That's brilliant, thank you so much! I guess I'd have found it myself eventually but got a bit blinded by the massive sea of options and didn't have time. No idea how it got unchecked in the first place. Cheers, Rodney Baggins .talk. 16:53, 14 February 2025 (UTC)[reply]

Could Twinkle Move/ECP a page on nomination

at Wikipedia_talk:Deletion_policy#Move_protection_for_articles_at_AfD I asked if this could be done via Twinkle. Any insight? (and of course general thoughts on the question welcome. Star Mississippi 19:17, 15 February 2025 (UTC)[reply]

Removing list entry instead of unlinking

Hello. When Twinkle unlinks backlinks to a deleted page, in some cases, the entire list entry should be removed, not just the double brackets. Namely, if the link is in a navbox or sidebar, in a See also section, or on a disambiguation page. I believe this function is built into XFDcloser (see WP:XFDC#Unlinking backlinks). Here is an example of Twinkle not doing this automatically and creating a problem (another one), and here is one where XFDcloser does things correctly. If possible, Twinkle should replicate that behavior. Thanks. InfiniteNexus (talk) 21:50, 16 February 2025 (UTC)[reply]

Incomplete XfD log on template merge TfD nomination

When one makes a template merge TfD nomination, the creator of both templates receive a notification. Yet, in the userspace XfD log only person is mentioned as having been notified instead of both. Example: Notification to person 1, Notification to person 2, Diff in XfD log. —CX Zoom[he/him] ^{(let's talk • {C•X})} 17:51, 28 February 2025 (UTC)[reply]

Request for "Linked page" box for uw-editsummary2

When I use Twinkle to apply uw-editsummary, I get a nice box asking for a "Linked page". When I apply uw-editsummary2, I do not get that box, but it would be helpful. I always have to go back to the editor's talk page and add a link to the page in question, so that they are not getting a blanket "you did something undesirable" message. How can that "Linked page" box be added to uw-editsummary2? Thanks. – Jonesey95 (talk) 19:52, 28 February 2025 (UTC)[reply]

The template itself doesn't support a linked page, probably because it's intended to be used when an editor chronically doesn't leave edit summaries, so there's no need to call out a specific example. If you feel the template's behavior should be changed to allow for calling out a particular page, I think you should probably start a discussion at the Talk page for the template. DonIago (talk) 20:40, 28 February 2025 (UTC)[reply]

Twinkle cannot handle Lua module redirects

Attempting to send a Lua module redirect to RfD fails with "Adding deletion tag to redirect: Failed to save edit: Lua error at line 1: unexpected symbol near '{'." The suggestion at WP:TFDHOWTO is to tag the doc page. I think this is what Twinkle should be doing for RfDs too but there is a caveat. Sometimes the doc page is also a redirect to the target's doc page. For example Module:Rail -> Module:Adjacent stations and Module:Rail/doc -> Module:Adjacent stations/doc. I'm not quite sure how that should be handled.

On a related note, trying to add an rcat with the tag module also fails, this time with "Tagging redirect: Failed to save edit: Lua error at line 3: '}' expected near 'category'.". In my opinion, this should be fixed by adding the tag to the doc page, as described in WP:Categorization#T and as I've been doing manually when creating module redirects (see Module:Footballbox collapsible and its doc page as an example). However, again, this assumes the doc page itself is not a redirect. Nickps (talk) 17:45, 3 March 2025 (UTC)[reply]

On second thought, adding the RfD notice to the doc page doesn't really work because it would not disable the redirect. Perhaps a better approach would be to add it to the module page itself using Module:Module wikitext. Nickps (talk) 04:22, 4 March 2025 (UTC)[reply]