Wikipedia talk:Twinkle/Archive 44

Archive 40

←

Archive 42

Archive 43

Archive 44

Archive 45

Archive 46

→

Archive 48

Feature request: add nomreason to "old prod"

The PROD feature adds the {{old prod}} template to the talk page but it does not add |nomreason=. Please consider adding it, along with a toggle-switch to revert back to the current behavior if desired. davidwr/(talk)/(contribs) 14:48, 10 November 2020 (UTC)

Out of curiosity, why? If a page was PRODded and the PROD was removed, I don't really see how knowing the reason for the nomination is important, since it cannot be readded. Primefac (talk) 15:21, 10 November 2020 (UTC) (please ping on reply)

@Primefac: Knowing that someone prod'd and article for the same reason I am considering sending it to AFD can make the difference in a borderline case. Likewise, the combination of "nomreason" and a well-though-out "conreason" can make me think "oh, wait, I didn't see things from that point of view, no need to send this to AFD after all."

On the other hand, if I'm the only one who sees any utility to |nomreason=, perhaps it should be deprecated altogether, but that's a discussion for another talk page. davidwr/(talk)/(contribs) 17:08, 10 November 2020 (UTC)

Oh, didn't realize |nomreason= was a valid param. In that case, its possible non-use is because TW doesn't fill that in. As I said, it was mainly out of curiosity - if the template itself is designed to handle it, then it might be worth expanding TW's use to more fully utilize it. Primefac (talk) 19:44, 10 November 2020 (UTC)

Though the template supports it, it is unpopular -- there are folks who feel the whole template is clutter. See discussions 1, 2, 3. Adding the nomreason (which most of the time take up more space than the rest of the template) would aggravate those concerns. No other talk header template carries a full rationale text written by a single user that's going to stay there forever!

@Davidwr and Primefac: Would it be better to add a permalink to the template pointing to proded version? I am thinking of a |nomid= containing a revision id (populated by Twinkle), and a |condiff= param pointing to the diff showing the deprod (can be populated by a bot). – SD0001 (talk) 07:45, 11 November 2020 (UTC)

@SD0001: I like it in theory, but for consistency I would go with nomdiff, 2nddiff, and condiff as parameter names. I would also run it by Template talk:Old prod for a week to see if there are any objections. Make it clear that these parameters are optional and meant as a back-stop for script- and bot-edits which might not always "know" the reason that belongs in nomreason, 2ndreason, and conreason. Also since Twinkle DOES know the nomreason, there's no reason not to put it in {{old prod}} except perhaps length. Cutting the reason off after a certain length and using a new "nomdiff" parameter would solve this. For example if the real nomreason was "Because blah blah 100 words of more blah blah" the template could use |nomreason=Because blah blah a few words ... and a new |nomdiff= parameter could link to the actual diff so people could see the full reason. davidwr/(talk)/(contribs) 15:58, 11 November 2020 (UTC)

@SD0001, I was actually thinking that the other day as I was looking at it - a diff would be a lot better than filling it up with unnecessary prose. Of course, removing parameters would just require a template talk page discussion. Primefac (talk) 21:46, 11 November 2020 (UTC)

Opened Template_talk:Old_prod#Adding_permalinks/diff_links_to_template. – SD0001 (talk) 19:08, 17 November 2020 (UTC)

Adding Template:Uw-notenglishedit

Twinkle contains template:uw-notenglish, which is used for non-English new articles, and template:uw-english, for non-English talk page comments, but not template:uw-notenglishedit, for adding non-English content into an existing article. Could that latter template be included in Twinkle? When I encounter foreign-language edits, I am usually at a loss for what warning template to use. This template would be very useful. Thanks in advance for your comments. Extraordinary Writ (talk) 17:53, 17 November 2020 (UTC)

Extraordinary Writ, for now you can add it as a custom template via "Custom warning templates to display" in Wikipedia:Twinkle/Preferences. I agree though that it should be added as one of the defaults. Ionmars10 (talk) 18:29, 17 November 2020 (UTC)

Thanks, Ionmars10 - that's exactly what I needed. Hopefully it will be added as a default eventually. Extraordinary Writ (talk) 19:08, 17 November 2020 (UTC)

Adding Template:Uw-summary2

{{Uw-summary2}} has a distinctly different use case than {{Uw-summary}} – it's targeted at experienced editors who know how to use edit summaries but have gotten into a habit of not doing so, rather than new editors who are unaware of them. Could it be added to Twinkle? {{u|Sdkb}} ^talk 20:16, 4 November 2020 (UTC)

Yeah, I guess that makes sense. Weird to have two... ~ Amory (u • t • c) 22:12, 8 November 2020 (UTC)

Beside the point, but annoying parallelism issue where {{summary}} redirects to {{uw-editsummary}}, while {{uw-editsummary2}} redirects to {{summary2}}. Presumably one should be renamed! ~ Amory (u • t • c) 22:14, 8 November 2020 (UTC)

Amorymeltzer, boldly done. {{u|Sdkb}} ^talk 20:45, 17 November 2020 (UTC)

Could you program it so that it's possible to edit the summary field in Twinkle when welcoming users?

I am using Twinkle to leave customised welcome notes on the talk pages of users who have signed up for an online edit-a-thon on climate change. See for example here: User talk:Rickeyre. Someone has complained on my talk page (see here) that the edit summary field says "Welcome to Wikipedia!" instead of saying "Welcome to online edit-a-thon". Therefore my question: is it possible for you to make a change to Twinkle so that it becomes possible to change the edit summary content when using Twinkle with a customised welcome note? If it's difficult to do then don't worry about it. I thought I'd ask in case it's really easy. EMsmile (talk) 14:47, 18 November 2020 (UTC)

Support watchlist expiry for XFD

Please? :) See also WP:VPT#New Feature: Watchlist Expiry, currently deployed at MediaWiki wiki. --Izno (talk) 03:33, 18 November 2020 (UTC)

1090 – SD0001 (talk) 04:44, 18 November 2020 (UTC)

Yeah, I plan to. Some new stuff going up this weekend, then I'm gonna iron out any kinks in the PR SD linked. Hoping for day one (two?) availability. ~ Amory (u • t • c) 01:32, 20 November 2020 (UTC)

Discussion at Template talk:Bsr § Requested move 20 November 2020

 You are invited to join the discussion at Template talk:Bsr § Requested move 20 November 2020. * Pppery * _{it has begun...} 13:49, 20 November 2020 (UTC)

Special:Contributions ranges

Did a quick search: is there a reason TW doesn't load on Special:Contributions IP range pages? Special:Contributions/2600:8800:5E00:A76:21BE:18A1:807:3E8 sees the functions load but Special:Contributions/2600:8800:5E00:A76:21BE:18A1:807:3E8/64 does not. Same for Special:Contributions/24.237.208.166 and Special:Contributions/24.237.208.166/30. --Izno (talk) 16:19, 20 November 2020 (UTC)

775 – SD0001 (talk) 16:40, 20 November 2020 (UTC)

I think I have quick fix for this (to unblock Twinkle on the second phab:T206954 issue), but review may take time. I have already fixed phab:T211910 and will probably soon be merged. – Ammarpad (talk) 02:46, 21 November 2020 (UTC)

Blocking users from using Twinkle

See [1].

@Deepfriedokra and SebastianHelm: If this is an issue on other occasions as well, the most realistic way to accomplish this would be by creating a new user group and using an edit filter to disallow edits from users in that user group with the "twinkle" tag. — Alexis Jazz (talk or ping me) 00:20, 21 November 2020 (UTC)

I don't think we get new userrights created at this board. Primefac (talk) 00:23, 21 November 2020 (UTC)

This comes up now and again — some links in the archives — but the easiest way is indeed not to do that, but to build something in. There's no perfect solution that way, and indeed it was removed years ago because it was clunky and ineffective. The best answer is, as always, that if someone is misusing or abusing Twinkle, it's no different than misusing or abusing any other part of the project, and should be treated as such. ~ Amory (u • t • c) 00:44, 21 November 2020 (UTC)

For a small number of users you could integrate something in Twinkle itself indeed, but it'll probably be a bit clunky. A user group may indeed be overkill. Well, nevermind. — Alexis Jazz (talk or ping me) 00:57, 21 November 2020 (UTC)

@Alexis Jazz: No need for a new user-right. The WP:WikiProject Articles for creation scripts only run if your name is on this list which is fully protected. davidwr/(talk)/(contribs) 02:00, 21 November 2020 (UTC)

I think a better example would be WP:PERM/AWB for WP:AWB use; AfC is a WikiProject with an actual purpose.

That being said, I would strongly object to adding a PERM page for Twinkle (for many reasons). I'm with Amory on this one; if a user is abusing a tool, and they have been sufficiently warned about it, then block them. To be honest, though, a throwaway comment from DFO about "remove their TW access" doesn't really seem to be based on the case and hand or the issues brought up at that discussion. Primefac (talk) 12:40, 21 November 2020 (UTC)

I agree with Amory. "The best answer is, as always, that if someone is misusing or abusing Twinkle, it's no different than misusing or abusing any other part of the project, and should be treated as such". PERM/TWINKLE is just gonna create more and more backlogs. Numerous users who don't have Rollback rights use this tool to fight vandalism, and when there's a PERM for it, that's gonna make things more difficult. I would also object to it. ─ The Aafī on Mobile ^(talk) 20:46, 21 November 2020 (UTC)

{{salt}} template

Team: I was bold and changed the tone of {{salt}}; since tone changes are considered breaking changes, I am notifying users here. Feedback always welcome. UnitedStatesian (talk) 18:46, 22 November 2020 (UTC)

November 2020 Twinkle updates (2020-11-21) @4cba4ef

Some nice new features this time around! Now, when nominating a protected page for XfD, Twinkle will automatically submit an edit request on the talk page! You'll now also see redirect CSD options on pages tagged for RfD, and new warnings should always find an existing monthly header section (like Huggle). There are a number of other improvements and bug fixes are present as well; a brief summary of some of the more notable items are below. Changes not otherwise attributed were made by User:Amorymeltzer.

• Each window now links to its preference pane for easier customization (#1178)
• xfd: Automatically submit an edit request when nominating protected pages (#1091)
  • Uses the new Template:Xfd edit protected
• speedy: Show redirect CSDs on redirects nominated for RfD (#1182)
• arv: Show a note if reported a user who is already blocked (#817 and #1184, by DannyS712)
• warn:
  • Append warning to an existing section, even if it's not the last (#1084)
  • Add {{uw-displaytitle}} (#1106, by Jackmcbarn)
  • Add {{uw-editsummary2}} (#1185, by TheTVExpert)​
  • Add uw-subtle series (1-4) (#536 and #1181)​​​​
  • Add {{uw-unattribcc}} as a single-issue notice (#1053, by Mdaniels5757)​
• block:
  • Default to current block information, and adds those settings as a new selection option (#1176)
  • Don't add expiry to template if it's a date, not a duration (#1172)
• tag:
  • Add an input for redirect page name for {{R avoided double redirect}} (#1164) (#1164, by TheTVExpert)
  • Add {{paid contributions}} (#1009, by unforgettableid)
  • Fix bugs in processing of existing tags (#1169, by SD0001)

This section should serve as a catching ground should anything not work properly or if any new bugs crop up, as well as for any feedback or suggestions. There were a lot of changes behind the scenes, so feel free to ping me. As always, input is welcome at the GitHub repo as well. Finally, if you're interested in helping out with Twinkle development, there's a helpful guideline for new contributors — check it out! ~ Amory (u • t • c) 15:38, 21 November 2020 (UTC)

Headings

Hello, I've been sending warning templates, recently though, new headings are being made for each new warning template I send like @User talk:SneekyBoy which has never happed before. Is this a bug or a new update? Jerm (talk) 04:07, 23 November 2020 (UTC)

Ah yeah, that's a bug. Should only have affected talkpages where the warning section was the first section, since I didn't account for 0 being false. Should be fixed now!​​ ~ Amory (u • t • c) 11:48, 23 November 2020 (UTC)

Duplication glitch

A glitch occurred when nominating a category for discussion (specifically, Category:Lists of fictional events). The first time failed because the user talk for the creator, Cydebot (talk · contribs), is protected, but the CfD was created. Then I tried again, and ended up CfDing it twice. –LaundryPizza03 (dc̄) 03:26, 23 November 2020 (UTC)

@LaundryPizza03: You nominated the Category, but the talk page notification failed, so you manually nominated it again? Is that right? If that's the case, Twinkle did what you asked it to, but there should be no need to do that just 'cause the notification failed. Was the error message confusing? ~ Amory (u • t • c) 11:51, 23 November 2020 (UTC)

Yes, apparently. –LaundryPizza03 (dc̄) 11:54, 23 November 2020 (UTC)

Discussion at Template talk:Condense § Requested move 10 November 2020

 You are invited to join the discussion at Template talk:Condense § Requested move 10 November 2020. * Pppery * _{it has begun...} 02:26, 10 November 2020 (UTC)

 Done ~ Amory (u • t • c) 11:57, 23 November 2020 (UTC)

AIV block warning

When submitting an AIV report on an IPv6, I was informed that it was already blocked in a rangeblock, which it is, however, the block is only a "partial block" against 8 unrelated pages, so I am not sure if Twinkle can have the smarts to notice this, but the warning was unhelpful in this case. Elizium23 (talk) 02:23, 22 November 2020 (UTC)

Opened a pull request to tweak the message for partially-blocked users. ~ Amory (u • t • c) 11:58, 23 November 2020 (UTC)

IP talk pages

Can Twinkle be made aware of likely-rapidly-changing-IP-addresses?

An editor in Australia pointed out that his ISP changes IP addresses rapidly and messages posted to those IP addresses are likely stale after a few hours or days.[2]

I can think of two ways to handle this:

• Use {{Age switch}} so the message "self-closes" or "self-collapses" after a few days or weeks.
• Keep a list of network blocks that are known to rapidly change, and use different messages on the talk pages of those IP addresses, or use a shorter "delay fuse" on the Age switch template.

davidwr/(talk)/(contribs) 00:33, 24 November 2020 (UTC)

Fails to issue warning

I have tried several times to issue a warning on the Sandbox for user warnings page, but failed to do so. A message box containing the text "User talk page modification: Retrieving page..." appears and forever hangs it there with no subsequent results. Mosesheron (talk) 13:43, 25 November 2020 (UTC)

​Bug! Fixed! Thanks for the report. ~ Amory (u • t • c) 11:49, 26 November 2020 (UTC)

Odd bug?

Hey all, I can't tell if this is a Twinkle bug or something different. I tried issuing a vandalism warning to this guy twice. I'm linking to what was on his talk page when I tried to warn him. The warning didn't go through, twice, and just sort of hung there as if it was waiting to process. When I deleted the non-existent template from his talk page, I was then able to process the warning. Cyphoidbomb (talk) 23:35, 24 November 2020 (UTC)

Sorry Cyphoidbomb, just saw this, but same issue as below and should be fixed! ~ Amory (u • t • c) 11:50, 26 November 2020 (UTC)

Headsup: there is an discussion about merging uw-vandalism1 into uw-disruptive1

Just as a quick headsup since the author appears to have forgotten to do so, there is an ongoing discussion at TFD about merging uw-vandalism1 into uw-disruptive1. Merry Christmas! Asartea ^{Talk Contribs!} 14:23, 3 December 2020 (UTC)

Change request: BLPPROD should not put Template:old prod on talk page

That template is to alert editors that the page is no longer eligible for a regular PROD.

Think of BLPPROD as a special case of "slow speedy deletion" similar to the "7 day speedy deletions" for files on the Commons. It's "speedy" because there is no discussion - at the end of 7 days either the page lacks a reference and it will be deleted, or there is a reference and someone forgot to remove the template. davidwr/(talk)/(contribs) 23:01, 5 December 2020 (UTC)

Temporary watchlisting behaviour

I'm trying out the new watchlist expiry options, so that if I use Twinkle to revert vandalism on some random article it is watchlisted for 90 days instead of forever. This is great, and should stop my watchlist growing without limit. However, I notice today that if I've previously chosen to watchlist a page indefinitely and then use Twinkle to revert vandalism there, the watchlisting is reduced to 90 days. I would prefer that this didn't happen. -- John of Reading (talk) 10:11, 7 December 2020 (UTC)

I absolutely agree. I've got some fixes up coming up in the queue (tomorrow?) as well as a larger rejiggering (PR 1242 if folks care), but it basically requires an extra query to do properly, and even then it's not quite perfect. But yes, this will be fixed soon. ~ Amory (u • t • c) 21:29, 13 December 2020 (UTC)

December 2020 Twinkle updates (2020-12-16)

Some good quality of life improvements this time around! Support for expiring watchlists was already available, but some kinks have been ironed out and improved to make it more useful. There are also some new watchlist preferences for the tag and page protection modules, allowing you to choose which types of pages to watch. CSD and XfD will both handle talk pages and non-wikitext pages better, and the protect and block modules now show more information. There are a number of other improvements and bug fixes are present as well; a brief summary of some of the more notable items are below. Changes not otherwise attributed were made by User:Amorymeltzer.

• Watchlist expiry:
  • Supported for all watchlist options in your Twinkle preferences
    • Options are: 1 week, 1 month, 3 months, and 6 months
  • Indefinitely watched pages will not be converted to an expiry
  • No defaults have been changed, but see the section above if you think they should.
• xfd:
  • Don't try to add edit request if page is already a talk (#1211)
  • Notify WT:TW/WT:AWB/WT:REDWARN automatically on TfD nomination (#1243, by Mdaniels5757)
  • Better handle content models for tfd and mfd nominations (#1208)
  • Fix RfD target page notifications for userspace nominations (#1232, by SD0001)
  • Adjust portlet tooltip to be more accurate for likely venue (#1193)
• tag:
  • Allow watching on per-venue basis (#1126)
  • {{Bsr}} renamed to {{Better source requested}} (#1199)
  • {{Condense}} renamed to {{Too many sections}}
• speedy:
  • Tag talkpage if unable to edit page (#1208)
  • Better handle content models when tagging (#1208)
• arv:
  • AN3: Don't follow redirects; always show resolution free entry field (#1195)
  • Note and soften message if user is already blocked (#1204)
• protect: Add options for watching protected/requested/tagged pages (#1133)
• protect/block: Show expiration of or timestamp for last action (if not currently restricted) (#1194)
• block: Add Horn of Africa DS topic (#1231)
• warn: Add {{uw-notenglishedit}} (#1196, by TheTVExpert)

This section should serve as a catching ground should anything not work properly or if any new bugs crop up, as well as for any feedback or suggestions. There were a lot of changes behind the scenes, so feel free to ping me. As always, input is welcome at the GitHub repo as well. Finally, if you're interested in helping out with Twinkle development, there's a helpful guideline for new contributors — check it out! ~ Amory (u • t • c) 11:00, 16 December 2020 (UTC)

Technical changes

We now have jsdocs for the Morebits library (#1190)! You can check them out at https://azatoth.github.io/twinkle/. There have been a lot of background changes to Twinkle and Morebits lately, an overview of changes to the morebits library for interested developers:

• Added unit tests for many functions (#1213)
• Enforce newer API error message format, defaulting to html (#1179)
• All Morebits and Twinkle uses of Morebits.wiki.api now use json rather than xml (#1224).
• Force loading of a page if a watchlist expiry is provided (#1242)
• userspaceLogger returns a promise (#1234, by SD0001)
• Morebits.status: Teach codify to parse HTML for status messages (#1179)
• Morebits: Add YYYYMMDDHHmmss format to Morebits.date constructor (#1200)
• Many fixes and improvements to Morebits.wikitext methods (#1240, #1239, #1214, #1225), and #1225)

~ Amory (u • t • c) 11:00, 16 December 2020 (UTC)

Tag redirect

Not sure if I did something wrong, but I tried to tag a redirect using Twinkle and it messed up by the looks of it. Here are the last three diffs: 3) Before 2) Twinkle 1) Manual Fix. Just asking here to confirm (or not) this is a bug before filing one at github. Feelthhis (talk) 04:17, 16 December 2020 (UTC)

I'm not sure if it's a bug or not, but the error is caused by the optional "|1=" parameter in Template:Redirect category shell, which Twinkle apparently doesn't recognize. BilCat (talk) 06:42, 16 December 2020 (UTC)

Yup, that looks like exactly it. Thanks for the report Feelthhis, I've pushed up a fix in the regex that should take care of it, might take a few minutes to go through. ~ Amory (u • t • c) 11:24, 16 December 2020 (UTC)

Amorymeltzer thanks for taking care of it and BilCat thanks for the testing. Feelthhis (talk) 11:28, 16 December 2020 (UTC)

Remove T3

Per Special:PermaLink/995058813#RFC:_should_WP:T3_be_deprecated?, T3 is no longer a valid CSD criteria, and should probably be removed from Twinkle. Primefac (talk) 01:03, 19 December 2020 (UTC) Gah, didn't realize I didn't need to make a separate post. But yeah, see the entry on the Templates for discussion page for {{db-t3}}. Primefac (talk) 01:10, 19 December 2020 (UTC)

Primed and ready! Should now be live. ~ Amory (u • t • c) 01:45, 19 December 2020 (UTC)

Ta. Primefac (talk) 02:12, 19 December 2020 (UTC)

Feature request: Apply 'multiple issues' without adding another tag

On an article with more than one tag already present, but not in {{multiple issues}}, if I try to use Twinkle without adding a further tag, it won't let me.

It would be good if Twinkle could apply {{multiple issues}} in such cases. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:16, 19 December 2020 (UTC)

Avoid redundant tagging

The following pairs of cleanup templates:

• {{COI}} and {{Autobiography}}
• {{More citations needed}} and {{One source}}
• {{More footnotes needed}} and {{More citations needed}}
• {{More footnotes needed}} and {{One source}}

should not be used on the same article (except where one or more of the templates are section-specific - e.g. {{One source|section|date=October 2020}}). Prior discussion is here.

I have asked for a bot to remove the first template in each of the pairs, but it would be good if Twinkle could also remove the redundant template (and remove {{Multiple issues}}, where appropriate) when it encounters such cases, and avoid creating such redundancy in future. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:48, 19 December 2020 (UTC)

Blocking twinkle

Hi, can somebody tell me what to do to block all twinkle generated messages and articles for deletion from my talk page?† Encyclopædius 17:17, 20 December 2020 (UTC)

Nomination for deletion of Template:Uw-attack

Template:Uw-attack has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Bsherr (talk) 17:27, 21 December 2020 (UTC)

File maintenance tagging not working

It says "Tagging file: Retrieving page" and the page never reloads. What happened? --Kailash29792 (talk) 08:36, 18 December 2020 (UTC)

@Kailash29792: Can you give more details: which page and which tag were you trying? Also, what browser are you using? – SD0001 (talk) 11:13, 18 December 2020 (UTC)

SD0001, Microsoft Edge. And the problems come on images. If you are still confused, I'll share a screenshot. Kailash29792 (talk) 11:26, 18 December 2020 (UTC)

@Kailash29792: At my end, I am able to add tags to images. The problem could be tag-specific; so which tag are you unable to use? – SD0001 (talk) 11:39, 18 December 2020 (UTC)

SD0001, Here. It stays stuck like this until I refresh the page. And the tag doesn't get added. Kailash29792 (talk) 12:03, 18 December 2020 (UTC)

The actual tag itself may be important for replicating on our end, so knowing exactly what you tried to add would help. Could you also show the output of your browser console (Items 6 of WP:JSERROR)? ~ Amory (u • t • c) 12:19, 18 December 2020 (UTC)

Amorymeltzer, it may be just anything. First I tried to add {{Orphaned non-free revisions}}, and later {{Obsolete}}, but both did not load. Maybe the issue is with my browser. I'll clear cache to see if it is fixed. If not, I'll come back to you. Kailash29792 (talk) 12:30, 18 December 2020 (UTC)

Hey Kailash29792 this should be fixed now, it was a dumb typo on my part, see more in #Redirect tagging getting stuck. ~ Amory (u • t • c) 01:27, 22 December 2020 (UTC)

Redirect tagging getting stuck

Recently, when trying to tag some redirects (e.g. trying to tag Frank R. Seaver with {{R from long name}}), Twinkle appears to be getting stuck. I click submit query, but then it just gets stuck on the "retrieving page..." portion, and when I give up and refresh the page, the edit has not been saved. Any idea what's causing this or how to fix it? {{u|Sdkb}} ^talk 22:30, 21 December 2020 (UTC)

I'm encountering the same thing trying to tag Wikipedia:BECAREFUL as {{r from shortcut}} and {{r to project namespace}}, so it appears Twinkle is fully broken for me on any redirect I try to tag. {{u|Sdkb}} ^talk 00:00, 22 December 2020 (UTC)

Sdkb, those both worked just fine for me. I suspect this might be the same as Kailash29792's issue above. I have a couple of theories, but without being able to replicate it, can't debug. Can you try another tag, then open up your browser console and paste what it says? Anything with morebits, twinkle, or friendly in the message, probably something with jquery.deferred. Your browser and version would also be helpful. ~ Amory (u • t • c) 00:51, 22 December 2020 (UTC)

Amorymeltzer, here's what I got:

load.php?lang=en&modules=jquery|jquery.ui&skin=vector&version=11ak3:51 jQuery.Deferred exception: Twinkle.getPref(...).indexOf is not a function TypeError: Twinkle.getPref(...).indexOf is not a function
    at Object.redirect [as onLoadSuccess] (https://en.wikipedia.org/w/load.php?lang=en&modules=ext.gadget.Twinkle&skin=vector&version=1szj2:438:140)
    at Morebits.wiki.page.fnLoadSuccess (<anonymous>:473:726)
    at Morebits.wiki.api.onAPIsuccess (<anonymous>:453:885)
    at mightThrow (https://en.wikipedia.org/w/load.php?lang=en&modules=jquery%7Cjquery.ui&skin=vector&version=11ak3:49:149)
    at process (https://en.wikipedia.org/w/load.php?lang=en&modules=jquery%7Cjquery.ui&skin=vector&version=11ak3:49:808) undefined
jQuery.Deferred.exceptionHook @ load.php?lang=en&modules=jquery|jquery.ui&skin=vector&version=11ak3:51
/beacon/event?%7B%22event%22%3A%7B%22mediaWikiVersion%22%3A%221.36.0-wmf.22%22%2C%22saveTiming%22%3A1013%7D%2C%22schema%22%3A%22SaveTiming%22%2C%22webHost%22%3A%22en.wikipedia.org%22%2C%22wiki%22%3A%22enwiki%22%2C%22revision%22%3A15396492%7D;:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

Does that help? {{u|Sdkb}} ^talk 00:56, 22 December 2020 (UTC)

Thanks — I've got to head to bed, but one more quick favor​: Can you enter Twinkle.getPref('watchTaggedVenues') and Twinkle.getPref('watchTaggedPages') in your console and tell me what you get in return for each? ~ Amory (u • t • c) 01:10, 22 December 2020 (UTC)

I entered those into the query after trying to tag a page where it got stuck. The first query returned this:

0: "articles"1: "drafts"2: "redirects"3: "files"length: 4__proto__: Array(0)concat: ƒ concat()arguments: (...)caller: (...)length: 1name: "concat"__proto__: ƒ ()[[Scopes]]: Scopes[0]constructor: ƒ Array()copyWithin: ƒ copyWithin()entries: ƒ entries()every: ƒ every()fill: ƒ fill()filter: ƒ filter()find: ƒ find()findIndex: ƒ findIndex()flat: ƒ flat()flatMap: ƒ flatMap()forEach: ƒ forEach()includes: ƒ includes()indexOf: ƒ indexOf()join: ƒ join()keys: ƒ keys()lastIndexOf: ƒ lastIndexOf()length: 0map: ƒ map()pop: ƒ pop()push: ƒ push()reduce: ƒ reduce()reduceRight: ƒ reduceRight()reverse: ƒ reverse()shift: ƒ shift()slice: ƒ slice()some: ƒ some()sort: ƒ sort()splice: ƒ splice()toLocaleString: ƒ toLocaleString()toString: ƒ toString()unshift: ƒ unshift()values: ƒ values()Symbol(Symbol.iterator): ƒ values()Symbol(Symbol.unscopables): {copyWithin: true, entries: true, fill: true, find: true, findIndex: true, …}__proto__: Objectconstructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()toLocaleString: ƒ toLocaleString()toString: ƒ toString()valueOf: ƒ valueOf()__defineGetter__: ƒ __defineGetter__()__defineSetter__: ƒ __defineSetter__()__lookupGetter__: ƒ __lookupGetter__()__lookupSetter__: ƒ __lookupSetter__()get __proto__: ƒ __proto__()set __proto__: ƒ __proto__()

The second query returned "false". {{u|Sdkb}} ^talk 01:16, 22 December 2020 (UTC)

Dumb bug/typo on my part, thanks for all that. Just pushed up a fix, might take a few minutes to propagate but you should be all set. Sorry about that. ~ Amory (u • t • c) 01:26, 22 December 2020 (UTC)

Awesome; thanks! {{u|Sdkb}} ^talk 01:49, 22 December 2020 (UTC)

Alert feature

Anyone else having problems checking talk pages when you give someone an alert? The check alert box says "A system filter has identified that you are trying to alert Badtitle/ApiErrorFormatter::getDummyTitle (contribs · logs · block log) to the existence of discretionary sanctions." and when you click on check talk page you go to User talk:Badtitle/ApiErrorFormatter::getDummyTitle: Revision history. Doug Weller talk 17:10, 23 December 2020 (UTC)

@Doug Weller: Twinkle does not have such a feature. You're actually using User:Bellezzasolo/Scripts/arb which is not a part of Twinkle. – SD0001 (talk) 17:20, 23 December 2020 (UTC)

SD0001, so I am. I forgot that I'd added that. Thanks. Doug Weller talk 17:52, 23 December 2020 (UTC)

Odd prod

Eddie891 issued me a Twinkle-generated prod notice for Joe Roche, which was created by David Straub, not me. I made exactly one very minor AWB edit to the article, in 2009, three and a half years after its creation. Any idea why Twinkle selected me to notify? MANdARAX • XAЯAbИAM 18:43, 2 January 2021 (UTC)

I received a similar notice from a normally careful editor. Something may be amiss with Twinkle. Certes (talk) 18:55, 2 January 2021 (UTC)

A recent bug was causing the 50th editor of the page (or the latest editor in case the page has <50 edits) to be identified as creator if the first revision was a redirect.  Fixed in 3dd033e. – SD0001 (talk) 20:21, 2 January 2021 (UTC)

Just saw this, so now pushed. ~ Amory (u • t • c) 21:49, 2 January 2021 (UTC)

Dbatch

Went today to delete a bunch of templates from the holding cell via dbatch, and much to my dismay the pages Twinkle pulls up are in no particular order! It used to be that they were all alphabetized, and this new non-layout is frustrating when I'm trying to find two dozen templates mixed in with a half-hundred other pages that I don't want to delete. Primefac (talk) 15:37, 20 December 2020 (UTC)

I'd say worth a report upstream. The XML API (which we were using until recently) as well as the JSON formatversion=1 API both order pages by namespace number and then alphabetically. But JSON formatversion=2 API (which we are using now) is ordering pages by the page ID instead – which is basically the order by date of creation, oldest pages first.

Can also be fixed with client-side sorting, of course. – SD0001 (talk) 16:41, 20 December 2020 (UTC)

Not sure how I'd do the second, given TW doesn't give me that option. Primefac (talk) 17:01, 20 December 2020 (UTC)

@Primefac: He meant that Twinkle could do it itself; I've thrown together a quick PR to do just that (apologies SD0001 if you were going to). ~ Amory (u • t • c) 17:51, 20 December 2020 (UTC)

That's what I figured, but I figured it wouldn't hurt to ask :-p Primefac (talk) 17:52, 20 December 2020 (UTC)

I'm not sure that it wasn't intentional. pageid is a reasonable thing to sort on, and doesn't run into language issues. ~ Amory (u • t • c) 22:43, 20 December 2020 (UTC)

This should now be fixed/changed. ~ Amory (u • t • c) 21:51, 2 January 2021 (UTC)

Citing wikimedia template

Is it ok that a Twinkle interface editor can add it to Tag? --🔥LightningComplexFire🔥 20:47, 30 December 2020 (UTC)

Because of the long list, it's good to indeed ask here before adding new template, since it's unclear how often a new template would get used. You can add custom templates in you Twinkle preferences, though! ~ Amory (u • t • c) 16:57, 3 January 2021 (UTC)

@Amorymeltzer: I added it to my custom list, but it doesn't load and I reloaded the cache twice. --🔥LightningComplexFire🔥 15:01, 6 January 2021 (UTC)

Never mind, I forgot to save it! --🔥LightningComplexFire🔥 15:06, 6 January 2021 (UTC)

Revert edit summaries

I just got a dressing down (followed by an apology) from an admin because of a Twinkle-based revert. I have made the same error several times. It seems that the wording of "‎reverted ... edit(s) by _" is quite similar to "reverted to revision ... by _" and can be easily mistaken for one another. Is it possible to change the wording? Possibly changing the wording of the latter to "restoring to ..."? Walter Görlitz (talk) 08:29, 6 January 2021 (UTC)

I'm neutral on this idea and think more input would be good, but I opened a PR. ~ Amory (u • t • c) 19:12, 8 January 2021 (UTC)

Spacing between reports at WP:UAA

See Wikipedia talk:Username policy#Spacing. I believe I can say that we have a consensus there that it would be a good thing if Twinkle added an extra line with an asterisk at the bottom when making a report. The page gets very hard to edit when it is backlogged, which happens on a near-daily basis. The original idea was to just add a blank line but apparently that is really not good for persons using screen readers. This would seperate the reports, making it easier to see where they begin and end, while not causing accessibility issues. 00:13, 24 December 2020 (UTC) — Preceding unsigned comment added by Beeblebrox (talk • contribs) 00:13, 24 December 2020 (UTC)

My reading of WP:INDENTGAP is indeed that that solution from RexxS works, but since there was no follow-up from Izno or Redrose64, yeah? ~ Amory (u • t • c) 21:54, 2 January 2021 (UTC)

Yes, that solution works. --Izno (talk) 22:06, 2 January 2021 (UTC)

@Izno, Beeblebrox, and Deepfriedokra: PR opened. Would something similar be useful at WP:AIV? ~ Amory (u • t • c) 17:10, 3 January 2021 (UTC)

Thanks! I'm not sure it's needed at AIV... but I haven't really worked that board in years. Beeblebrox (talk) 19:08, 3 January 2021 (UTC)

This should be live now ~ Amory (u • t • c) 19:13, 8 January 2021 (UTC)

new tag for file tagging

When tagging files, I suggest adding the tag Template:Userspace file, could have used it a few times. --TheImaCow (talk) 20:06, 3 January 2021 (UTC)

...like here. --TheImaCow (talk) 20:48, 8 January 2021 (UTC)

Watchlist error after rollback

This may be a bug: my Twinkle settings are set so that following a rollback the page is put on my watchlist for a week. However, Twinkle has repeatedly put those articles on my watchlist indefinitely. Before anyone asks, I have cleared the browser's cache.

Sdrqaz (talk) 21:50, 8 January 2021 (UTC)

Yup, bug. Should be fixed now! Thanks for the report. ~ Amory (u • t • c) 01:41, 9 January 2021 (UTC)

Much appreciated, Amory. Thought I was going crazy! Sdrqaz (talk) 15:33, 9 January 2021 (UTC)

A breaking change I made

Hello, fellow Twinkle users. I have added 2 commas to uw-multipleIPs. -Shift674-🌀 ^contribs 17:50, 12 January 2021 (UTC)

Shift674, a "breaking change" means a change which breaks or otherwise significantly changes the functionality of the template. Adding commas to fix grammar is not something that we need to notified about. Primefac (talk) 11:09, 13 January 2021 (UTC)

Add Twinkle buttons on Minerva

Can Twinkle buttons be added to the sidebar on Minerva? It would be something nice to have. Aasim (talk) 03:41, 14 January 2021 (UTC)

@Awesome Aasim: Minerva has a sidebar? – SD0001 (talk) 14:23, 14 January 2021 (UTC)

@SD0001: Aasim is likely referring to the hidden sidebar, the one that open when you click the hamburger menu. — Paper9oll (📣 • 📝) 14:37, 14 January 2021 (UTC)

@Paper9oll: Gotcha, that one! The more natural place to add script buttons, I think, is the 3-dots menu that appears next to the edit button (only in Advanced mobile mode). Recently, these areas have become accessible through mw.util.addPortletLink (phab:T231925), so supporting Minerva is definitely a possibility going ahead. The gadget as of now is not loaded for the mobile domain at all – can be fixed by adding targets=desktop,mobile in the gadget definition. – SD0001 (talk) 15:19, 14 January 2021 (UTC)

Missing Contributions log entry

I used Twinkle (CSD) today to initiate a G8 speedy deletion for the flagged broken redirect Hillside, California (disambiguation). The bot Fastily completed the request at 16:07 UTC, on 10 January 2021, but I see no entry in my user contributions log for the edit I made to the disambiguation page.

Not sure if this is a Twinkle or MediaWiki concern (found nothing in this Project's Talk page archives about it) but thought I'd start here for some feedback. Thank you! — WILDSTAR^talk 19:06, 10 January 2021 (UTC)

When a page is deleted, all revisions of the page are deleted, and will no longer be visible except to administrators. You have around 145 deleted edits.

As for Twinkle, if you want to save a record of pages you nominate under CSD, you can enable a userspace log in your Twinkle preferences, see Wikipedia:Twinkle/Preferences#speedy. Similar logs exist for PROD and XfD nominations.

Also, Fastily is not a bot ;) ~ Amory (u • t • c) 00:50, 11 January 2021 (UTC)

Amorymeltzer, just tested that on our MW. I had never noticed it before... but you are absolutely correct!  :) Thank you! — WILDSTAR^talk 05:01, 11 January 2021 (UTC)

Amorymeltzer, "Fastily is not a bot" Are you sure? :) S Philbrick(Talk) 19:06, 16 January 2021 (UTC)

Change Watch this page to temporarily watch this page

A common situation is the need to delete an article so that another article can be moved there. That requests uses the template {{Db-move}} and I mistakenly thought my proposal should be directed there, but it appears that it is a twinkle action using that template so I will try reposting my request here.

When requesting the deletion of articles so that another article can be placed there, the request invokes a template {{Db-move}}, which has an option to:

Watch source page and target page

Which is checked by default.

When I process one of these requests, I routinely uncheck that box. I feel a little guilty doing this because on rare occasions, some issue arises and it might have been better to have it in my watchlist. However, my watchlist is a bit out of control, and I don't need to add thousands of entries where I don't particularly care about edits to the article, other than edits that might relate to this particular move. Any such edits are almost certain to happen within days of the move. I trust you can guess where I'm going with this. If the default were changed to "temporarily watch source page and target page for one month" I wouldn't mind having it checked as almost anything I care about will show up in my watchlist within a few days, and then the entry will drop out of my watchlist at the end of the month. Now that developers have created the temporary watchlist option, I propose that the default be changed to one of the temporary options. I don't have strong feelings about the length of time; a week would be fine, and I picked a month just to be on the safe side. if most editors want these entries permanently in their watchlist so be it, but my guess is that would be rare enough that those editors could manually change the temporary option to permanent.

I do see the suggestion to post this at git hub but I'd like to get consensus here before requesting it on the chance that I'm missing something and it's not a good idea.

I'm also proposing it in connection with this very narrow situation, but it occurs to me that the use of the temporary watch might apply to other situations as well.--S Philbrick(Talk) 19:03, 16 January 2021 (UTC) Addendum — I just noticed Wikipedia_talk:Twinkle#Watchlist_error_after_rollback which suggests to me that I have control over whether it's permanent or temporary in my watchlist so I will look into that.--S Philbrick(Talk) 19:08, 16 January 2021 (UTC) I didn't realize I could control this, so my request is moot. I'm striking out rather than removing, on the chance that I'm not the only one who didn't know that.--S Philbrick(Talk) 19:12, 16 January 2021 (UTC)

Redirect tagging doesn't include {{R to subpage}}

Pretty much title. I'd like to be able to speedily tag redirects with {{R to subpage}}, but I can't, it just isn't in the list. If I need to post this to GitHub, I can do that too. Elliot321 (talk | contribs) 22:26, 12 January 2021 (UTC)

I've found it's missing others too, like {{R for convenience}}. Elliot321 (talk | contribs) 22:59, 12 January 2021 (UTC)

​Currently, the list Twinkle offers is populated with the contents of Template:R template index. That template intentionally doesn't include all possible Rcats (although I'm not sure on the "decision" process) which IMO is a fine proxy for Twinkle since having to include every possible Rcat gets unwieldy. ~ Amory (u • t • c) 12:43, 13 January 2021 (UTC)

What redirect tags should Twinkle include?

As noted above, Twinkle's redirect tagging module includes all items in Template:R template index, which is supposedly all of the functional rcats but not all rcats. I haven't counted how many more that'd be, but is having too many a concern? What should the criteria be? ~ Amory (u • t • c) 21:39, 17 January 2021 (UTC)

Template:Welcomelaws and 'problem user' welcome templates

Twinkle categorizes user welcome templates into general and 'problem user', for users whose early edits appear potentially disruptive or otherwise problematic. For the most part, what group a template is placed in seems fine. However, Template:Welcomelaws is placed with the 'problem' templates, which I'm not a fan of. Welcomelaws strikes me as the best template for most new users -- it's friendly, comprehensive, and runs through everything a new editor needs to know in a way not quite as big an infodump as many of the other attempts at a comprehensive welcome template. Is there any particular reason Welcomelaws is categorized alongside the vandal, spammer, and POV/COI templates? Vaticidalprophet (talk) 21:33, 17 January 2021 (UTC)

I always presumed the logic was "If you are suggesting some read, be aware of, and follow the rules, they probably need it." There are friendlier/more welcoming/pure "welcome" templates. ~ Amory (u • t • c) 21:42, 17 January 2021 (UTC)

CSD nomination box error

When one nominates an article for speedy deletion, and selects the "multiple criteria" box, the "Custom rationale with {{db}}" option disappears. I assume this was meant to be the other way round - {{db}} should only be used with other csd criteria. Thank you for your time. Opal|zukor^(discuss) 14:10, 7 January 2021 (UTC)

@Opalzukor: This is most likely because {{db}} is not supported by {{db-multiple}}. TheTVExpert (talk) 15:35, 7 January 2021 (UTC)

Thought I had replied to this, but yes, that's exactly the reason. ~ Amory (u • t • c) 21:43, 17 January 2021 (UTC)

Watchlist expiry default options

I've just pushed some code that should enable the new watchlist expiry coming next week. What I wanted to ask, however, was whether or not some of the defaults should change. Here are the current unchanged defaults:

• ARV: Add sockpuppet report pages to watchlist (indefinitely)
• Image: Add image page to watchlist when tagging (follow site preferences)
• Image: Add user talk page of initial uploader to watchlist when notifying (follow site preferences)
• PROD: Add article to watchlist when tagging (indefinitely)
• Rollback/revert: When reverting a page, how long to watch it for (indefinitely)
• CSD: When tagging a page, how long to watch it for (indefinitely)
• Tag: Add page to watchlist when tagging (indefinitely)
• Tag: Add talk pages to watchlist when starting merge discussions (indefinitely)
• Warn: Add user talk page to watchlist when notifying (indefinitely)
• Welcome: Add user talk pages to watchlist when welcoming (indefinitely)
• XFD: Add the nominated page to watchlist (follow site preferences)
• XFD: Add the deletion discussion page to watchlist (follow site preferences)
• XFD: Add the daily log/list page to the watchlist (where applicable) (no)
• XFD: Add user talk page of initial contributor to watchlist (when notifying) (follow site preferences)
• XFD: Add the redirect's target page to watchlist (when notifying) (follow site preferences)

At the moment, Twinkle will use expiry options of 1 week, 1 month, 3 months, and 6 months. Should any of these be changed to one of those values? In particular I can see PROD, XfD, and CSD making liberal use of them, but what do people think? ~ Amory (u • t • c) 19:15, 28 November 2020 (UTC)

There's also a suggestion I've made to add options to the rpp/pp module to watch requested pages, watch tagged pages, and (for sysops) watch protected pages. What would folks think those should be set to? ~ Amory (u • t • c) 19:30, 28 November 2020 (UTC)

I would probably favor 1 month for XFDs, maybe 1 month for PROD and delayed CSDs, and 1 week for immediate CSDs. I think these maximize the likelihood someone will see a relisting or recreation. I'm not sure if the split on CSDs is practical.

For page protections, it would be cool for the default watch time to be protection length + a week or something.

These thoughts might be generalized to: "watch until a week or so after when follow-up activity is most-likely to occur". --Izno (talk) 19:51, 28 November 2020 (UTC)

The CSD split is, indeed, not practical, but 1 month for all ain't gonna hurt much. 1 month/1 month/1 week was roughly what I figured, but you've a good point on the delayed ones. I'm intrigued by your idea for protections, maybe I'll mull that down the line. Of course, indefinite protections are least likely to need indefinite watching... ~ Amory (u • t • c) 20:48, 30 November 2020 (UTC)

I've suggested that editors be allowed to change their default expiry periods in general. (We currently have only "add forever" and "don't add".) Any solution for Twinkle might bear in mind the possibility of something like this being implemented. Certes (talk) 20:11, 28 November 2020 (UTC)

As a user, I'd expect "follow site preferences" to do just that. Might require work down the line, but will cross that bridge if/when we get there. ~ Amory (u • t • c) 20:49, 30 November 2020 (UTC)

So would I. The problem is that the site preference can only be set to "don't watch" or "forever", and there are no plans to change that (it was omitted from the implementation that's about to be rolled out). Certes (talk) 21:43, 30 November 2020 (UTC)

I can't decide whether vandal reverters would prefer a shorter default watch period for rollback/revert... ~ Amory (u • t • c) 20:51, 30 November 2020 (UTC)

Proposed changes to default watchlist behavior

I'd like to propose some simplistic changes to the defaults above, basically moving most watchlist defaults to 1 month. There's been minimal input, so I'm wary of messing folks up too much, but I think something'd be welcome and helpful. The changes are in bold below:

• ARV: Add sockpuppet report pages to watchlist (indefinitely)
• Image: Add image page to watchlist when tagging (1 month, not follow site preferences)
• Image: Add user talk page of initial uploader to watchlist when notifying (1 month, not follow site preferences)
• PROD: Add article to watchlist when tagging (1 month, not indefinitely)
• Rollback/revert: When reverting a page, how long to watch it for (1 month, not indefinitely)
• CSD: When tagging a page, how long to watch it for (1 month, not indefinitely)
• Tag: Add page to watchlist when tagging (1 month, not indefinitely)
• Tag: Add talk pages to watchlist when starting merge discussions (1 month, not indefinitely)
• Warn: Add user talk page to watchlist when notifying (1 month, not indefinitely)
• Welcome: Add user talk pages to watchlist when welcoming (3 months, not indefinitely)
• XFD: Add the nominated page to watchlist (1 month, not follow site preferences)
• XFD: Add the deletion discussion page to watchlist (1 month, not follow site preferences remain at follow site preferences per below)
• XFD: Add the daily log/list page to the watchlist (where applicable) (no)
• XFD: Add user talk page of initial contributor to watchlist (when notifying) (1 month, not follow site preferences)
• XFD: Add the redirect's target page to watchlist (when notifying) (1 month, not follow site preferences)
• Protect: Add when requesting protection (indefinitely)
• Protect: Add when tagging with protection template (follow site preferences)
• Protect: Add when protection (follow site preferences)

Obviously I'd love some input and feedback on this​​ as this is just me spitballing. I previously posted at VPT, I dunno if another notice should be placed. There are other venues that might be worth pinging. ~ Amory (u • t • c) 22:39, 19 December 2020 (UTC)

• @Amorymeltzer: You've obviously thought this through carefully and all of that sounds reasonable. Default watching is limited to forever or not at all; if that changes then we should revisit these settings. Certes (talk) 23:29, 19 December 2020 (UTC)
• XFD: Add the deletion discussion page to watchlist (1 month, not follow site preferences) I'd suggest indef. Deletion discussion pages are unlikely to get edits after 1 month, so unwatching it then is pointless. If someone were to file a DELREV after a month or vandalise it years later, those would be good things to find on a watchlist. – SD0001 (talk) 05:01, 20 December 2020 (UTC)

  Agreed; any given XFD, once it's closed, is rather unlikely to be edited (so it's not like it's going to be spamming our notifications), but having that notification is good (I would even add RFAs into that category for the same reason) mainly in cases of vandalism. Primefac (talk) 10:37, 20 December 2020 (UTC)

  Fair points indeed; changed back to follow site preferences, which it was before. ~ Amory (u • t • c) 00:54, 21 December 2020 (UTC)

• Be bold. Only thing is, if you're going to integrate this for a non-default watch (which is indefinite), you maybe need to tell people that watching these pages will watch them temporarily by default somewhere in the documentation. --Izno (talk) 21:33, 20 December 2020 (UTC)

  Sorry Izno, I'm having trouble parsing what you mean by integrate this for a non-default watch (which is indefinite). I think you're saying the above changes should be noted in the module itself? ~ Amory (u • t • c) 00:54, 21 December 2020 (UTC)

  Somewhere where it's advertised that pages are watched should be something that says "this is only a temporary watch; change your prefs over here". Maybe enough people will get it from the half-star, but it's kind of a radical change of behavior for old-timers (maybe in a couple years such a reminder could be removed). Could be documentation, could be in Twinkle itself. --Izno (talk) 02:15, 21 December 2020 (UTC)

  (Sorry for belated reply Izno, but that time of year(s)...) I'm not sure where to put such a thing. where might you suggest? I've tried to advertise this (VPT) but clearly minimal interest. Most watching prefs aren't noted visibly in the dialogs; I dunno that we want to clutter the dialogs by adding a line to note that the default has/will change. I suppose it wouldn't be the end of the world if it's a limited engagement, but that obviously has limited benefits for less-frequent users. ~ Amory (u • t • c) 21:25, 2 January 2021 (UTC)

  I was just thinking something like Wikipedia:Twinkle/doc#Default watchlist options as the simple-stupid. --Izno (talk) 22:09, 2 January 2021 (UTC)

  👍 ~ Amory (u • t • c) 21:44, 17 January 2021 (UTC)

Rollback feature requests

Just a few wishes, probably as options, in order of priority:

1. Don't reload the page when rolling back from article history - I have the option set for contribs, I wish I could have it for history. It would speed things up a lot, since it takes several seconds and it's almost never what I want to do.
2. Rollback links in the watchlist - I can use standard rollback, but for non-vandalism I prefer Twinkle's (not marking "minor" etc.). The time saved by not having to go to another page would more than make up for any slowness in loading the watchlist. #1 would also apply here.
3. "Rollback (AGF)" links in contribs and history pages - the extra few seconds of having to go to a diff page means I don't use "AGF" as often as I'd like. An alternative would be to add a checkbox to the standard rollback edit summary box, to add the AGF text.
4. A selection of canned/custom edit summaries - I have a list of standard ones that I copy and paste (most popular: "Unsourced and unexplained change that contradicts the existing source"). I wish this could be built in to the edit summary box.
5. A pony - would also be nice to have.

--IamNotU (talk) 15:04, 1 January 2021 (UTC)

I used Twinkle to deliver you a pony on your talk page.[3] Please take good care of it. davidwr/(talk)/(contribs) 🎄 18:45, 1 January 2021 (UTC)

Awesome! --IamNotU (talk) 21:07, 1 January 2021 (UTC)

On #2, Twinkle isn't active on the Watchlist for speed/performance reasons. I think the major issue is actually the rollback module itself — the watchlist can be/is slow as is, and the rollback links are delayed, so I imagine it'd be a performance nightmare. Then again, I suppose it'd be similar to RecentChanges... ~ Amory (u • t • c) 12:42, 14 January 2021 (UTC)

On item 1: IamNotU, what are you usually trying to do after reverting the history? ~ Amory (u • t • c) 21:44, 17 January 2021 (UTC)

Amorymeltzer, About #1, if I'm on an article history page and doing a rollback, I'd prefer to just stay on the history page, like I can with contrib pages if I set the Don't reload the page when rolling back from contributions or recent changes option. I'd like that option to also apply to article history (and watchlist), so I'd just get the little notification box in the upper right, and stay where I am. I don't need to go look at the article, I know what I just did (usually:). I'll want to head back where I came from, more often to my watchlist or a contribs page than the article.

On #2, I wouldn't mind if it impacted the performance of the watchlist, because it would speed up the workflow a lot more, since I wouldn't have to go to the diff, article's history, or the user's contribs page, and then back to the watchlist, like I do now. My rollbacks tend to be more about good-faith mistakes or sockpuppetry, I'm not a heavy vandalism fighter; I have real rollback but I don't use it that often. Twinkle's works better for me, even though it's slower. I tried some of the scripts that give edit summaries for real rollback, but none of them seemed to work as well, and I don't like that it marks everything minor. --IamNotU (talk) 23:06, 17 January 2021 (UTC)

FYI: change to Welcomeen-fr

Just a heads-up that a change to Welcome template {{Welcomeen-fr}} in this edit adds a new optional param to the template. This is completely backwards compatible, so I don't consider it a "breaking change", but am posting here anyway as a courtesy. Mathglot (talk) 21:24, 18 January 2021 (UTC) Same thing with {{welcomeen-es}}. Mathglot (talk) 17:22, 19 January 2021 (UTC)

How do I tag non drafts and articles

Like talks? I'm not talking about WikiProject tags... --🔥LightningComplexFire🔥 17:01, 19 January 2021 (UTC)

@LightningComplexFire: Currently, articles, drafts, redirects, and files can all be tagged. Tagging talk pages is not currently available, but @SD0001 did write the code for it two years ago, however it was never merged in. TheTVExpert (talk) 19:57, 19 January 2021 (UTC)

FYI: new optional "reason" parameter in {{Original research}}

An optional "reason" parameter has been added to the {{Original research}} template. This isn't really a breaking change, but leaving a courtesy message here regardless. Elliot321 (talk | contribs) 19:58, 20 January 2021 (UTC)

I'm gonna be changing some templates

Including edit filter and speedy deletion notices. Shinyedit^bonjour. 01:55, 21 January 2021 (UTC)

Notifications when starting SPI

Is it possible for there be an option to only notify the suspected sockpuppet and not the sockmaster? This is useful if the sockmaster has already been blocked for socking and it’s not 100% certain yet that the suspected sockpuppet is one. SK2242 (talk) 06:40, 22 January 2021 (UTC)

You can set the notification to appear or not as you feel appropriate. I don't think it's something that needs to be automated further. Primefac (talk) 12:15, 22 January 2021 (UTC)

Do not display [restore this version] button if a historical version is identical to the current version

1. Go to USER:IN/.
2. View the history of this page.
3. Try using Twinkle to restore to my made the edit at 3:40 AM (UTC).
4. When it restore, Twinkle will be presented with the following statement:

Grabbing data of the earlier revision: Revision we are reverting to is identical to current revision, stopping revert.
I think that isn't necessary. That can be done by controlling the source - that is, do not show [restore this version] button.--Did you know? Alcremie's 1000th edit was made very close to the 20th anniversary day of Wikipedia. 11:32, 20 January 2021 (UTC)

Support as per IN. — Paper9oll (📣 • 📝) 11:57, 20 January 2021 (UTC)

@IN and Paper9oll: This could potentially be doable, however, it would most likely make the button take longer to show up when it is needed. TheTVExpert (talk) 18:54, 20 January 2021 (UTC)

@TheTVExpert: Around how much longer will it take, my guess is around 2 seconds more? Or maybe instead of hiding the button, make the link/button state to be unclickable instead. Of course, not all users would prefer longer waiting time of 2–5 seconds (this would of course depends on the internet speed) hence maybe can make it available as optional feature. — Paper9oll (📣 • 📝) 06:57, 22 January 2021 (UTC)

Don't think this is much of an advantage. But if this is being done, be sure to fetch and compare only the SHA1s of the revisions, not the whole texts. – SD0001 (talk) 07:58, 22 January 2021 (UTC)

Agree, seems like a non-issue. Wait a half-second for it to search the diffs and compare, or wait a half-second and find out the rollback is pointless. Either way, you're wasting time, but if we do nothing we don't waste more in testing/implementing. Primefac (talk) 12:17, 22 January 2021 (UTC)

Agreed, don't think it's worth it; it's likely to be a fair bit longer on page load, too. ~ Amory (u • t • c) 17:21, 22 January 2021 (UTC)

Preview function

The preview function, that is quite handy and found in all of the welcome and warning templates (afaik) is oddly missing from the SharedIP templates (and all of it's the subs, such as DynamicIP, StaticIP, Edu, Gov't, etc.) Was that deliberate? Is it possible to add that function to those templates? (am I even asking in the right place?) Any help with this would be appreciated. Cheers - wolf 10:15, 24 December 2020 (UTC)

@Thewolfchild: Definitely the right place! Dunno about intentional, but it could be added if folks find useful. I opened an issue to track it. ~ Amory (u • t • c) 17:14, 3 January 2021 (UTC)

@Amorymeltzer: how about just adding it, or giving me template editor and I'll add it, then we can trial it, and go from there? - wolf 21:12, 12 January 2021 (UTC)

I think you're a bit confused — this isn't anything to do with the templates, it's with Twinkle's code itself. At any rate, TheTVExpert just opened a PR for it, which I'll try to review when I get a moment later this week. ~ Amory (u • t • c) 00:27, 13 January 2021 (UTC)

No, I came here as a result of the individual templates. I tried asking on another page but didn't get a response. I then tried here because there is more traffic. (And viola, I got a reply!) Thank you for your efforts, hopefully we can get something done - wolf 08:08, 13 January 2021 (UTC)

@Amorymeltzer: looking at the github link you noted, it appears the request was added, but it's still not on the template, is there a delay? Thanks again for your assistance - wolf 13:32, 22 January 2021 (UTC)

I have not had the time to review the latest code in the PR. I intend to do so today. ~ Amory (u • t • c) 17:22, 22 January 2021 (UTC)

Now live. ~ Amory (u • t • c) 18:16, 22 January 2021 (UTC)

@Amorymeltzer:, that's great, thanks for getting that added. Cheers - wolf 18:36, 22 January 2021 (UTC)

Custom tags

When searching for tags, the user-defined ones are listed under the last regular section instead of under the "Custom tags" section, as they are without search. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:28, 24 January 2021 (UTC)

Yes. No headers are shown while searching. – SD0001 (talk) 17:35, 24 January 2021 (UTC)

I mean this. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 18:08, 24 January 2021 (UTC)

Oh, I see. That is a bug. – SD0001 (talk) 10:26, 26 January 2021 (UTC)

Pipes in RfD nominations

When I RfD'd a page via Twinkle, instances of pipes were replaced by {{subst:!}}, which breaks any templates with parameters in the nominator's rationale. I was able to confirm that this is specific to Twinkle; the preview function parses pipes correctly. It is possible that other queries in Twinkle are affected. Example diff. –LaundryPizza03 (dc̄) 01:05, 26 January 2021 (UTC)

The issue is specific to templates used inside ref tags as substitution doesn't work in them. – SD0001 (talk) 10:29, 26 January 2021 (UTC)

Annoying error message

Every time I load a new page on Wikipedia, I get a pink warning that says "Could not parse your twinkle preferences." Is there anything I can do to make this go away. It is getting annoying. Thanks. Scorpions13256 (talk) 20:10, 26 January 2021 (UTC)

Go to your preferences and disable Twinkle. Sorry. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 20:12, 26 January 2021 (UTC)

I don't want to do that because I use it for RCP. Do you have any idea what could be causing this? Scorpions13256 (talk) 20:21, 26 January 2021 (UTC)

Sorry, I was a bit sarcastic. Do you see any errors in the browser console? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 20:24, 26 January 2021 (UTC)

@Scorpions13256: It was likely caused by this diff. TheTVExpert (talk) 20:28, 26 January 2021 (UTC)

I just figured that out myself the second before you notified me. What a coincidence. Is there anything I can do? Scorpions13256 (talk) 20:29, 26 January 2021 (UTC)

Scorpions13256, it's likely because you're importing User:Scorpions13256/twinkleoptions.js directly in your personal script page, User:Scorpions13256/common.js. The twinkleoptions.js file is for Twinkle to use itself, you shouldn't ever import it directly. If you remove that line from your common.js, I think you can safely remove the edit Jon made. ~ Amory (u • t • c) 21:05, 26 January 2021 (UTC)

Done. Everything is back to normal. Thank you all for your help. Scorpions13256 (talk) 21:25, 26 January 2021 (UTC)

PROD: Prevent creation of discussion pages

Hi, I very often propose files for deletion and then it always creates {{Old prod}} on the talk page. Is there any way to add an option that prevents this/that you can turn this off? I have already created over 400 unnecessary talkpages, and for the few files that are not deleted, you can also read in the page history that the file was once suggested for deletion. --TheImaCow (talk) 06:20, 26 January 2021 (UTC)

Not to ask the impertinent question, but who cares? If the page is deleted, the talk is deleted along with it, and if the page isn't deleted, the {{old prod}} has successfully been added to the talk page to inform users of the existence of an old prod. I see no downside. Primefac (talk) 11:18, 26 January 2021 (UTC)

I care. When I want to move files to Commons, I go to Category:Unused Files and always middle-click a row of files to open them (i.e., in a new tab). The files, with which you can do nothing, or are not free, are proposed for deletion ... and if there is then in addition to the 3 other edits (notification, the actual tag, log entry) also the creation of a talk page, then it simply takes too long for me. But not only would it take too long for me, I find these "Old Prod" tags on files talks quite unnecessary in themselves. For articles with many revisions it might be helpful, but for files that only very rarely have more than 10 edits? You click once on the "History" tab and see that immediately. On the other hand, is there anyone who also looks at the file disscusion pages, if there are any? I think not. And also, I don't want to spam my edit count higher with such unnecessary edits.

Long story short: Takes too long, is unnecessary, and spams up the edits. --TheImaCow (talk) 05:21, 27 January 2021 (UTC)

But I thought the points was that Twinkle was doing it automatically - if you do nothing, it does it for you (from a "clicks" perspective, turning off a checkbox actually increases the number of clicks you make). If you're doing it manually, then I'm not sure why you're posting here. Primefac (talk) 11:56, 27 January 2021 (UTC)

Opting out of old prod tagging (if there had been such an option) won't actually reduce the total time taken. This is because Twinkle schedules things such that old prod tagging takes place at the same time as notifying the creator. Making the entry to your userspace log takes place after the creator is notified. Hence the latter two are the sort of like the rate-determining steps. – SD0001 (talk) 13:41, 27 January 2021 (UTC)

refunds to "your user page"

I wrote about this issue here. I haven't surveyed other Twinkle templates, but the language in {{Welcomeauto}} has been there a very long time. I was proposing that we write that the restoration of a deleted page would be placed in "your user space" rather than "your user page". It's a pretty small thing, but used often enough that I wanted to get some consensus before making it all by myself. — jmcgnh^{(talk) (contribs)} 08:50, 27 January 2021 (UTC)

That makes sense from my perspective. Cyphoidbomb (talk) 17:34, 27 January 2021 (UTC)

Note to see steps for multiple/bundled XFD discussions

Twinkle doesn't seem support creating bundled XFD discussions, but doesn't indicate that on the XFD interface, would it be worth adding a notice like ("If nominating multiple Xs for the same discussion see WP:MULTIAFD/WP:TFDHOWTO/WP:RFDHOWTO/etc.") At User_talk:GenQuest#Lanka_Premier_League_AfDs the nominator evidently thought that this was possible, which led to duplication, busywork, and breaking the XFDCloser script. ---- Patar knight - ^chat/_{contributions} 17:43, 28 January 2021 (UTC)

I really appreciate many of Twinkle's wonderful features, but multi-XfD (and multi-RM) is the enhancement I'd most like to see. I know it wouldn't be easy. Certes (talk) 19:04, 28 January 2021 (UTC)

Uncontroversial RMs

Twinkle failed to create an RM/TR nomination on Foreign involvement in the Syrian Civil War with the error "Adding entry at WP:RM/TR: failed to find target spot for the entry". 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 19:09, 29 January 2021 (UTC)

@1234qwer1234qwer4: This edit may have fixed the problem. Can you try it again? -- John of Reading (talk) 19:21, 29 January 2021 (UTC)

Thanks, that was it. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 19:29, 29 January 2021 (UTC)

Don't display [rollback (AGF)] || [rollback] || [vandalism] buttons on the latest version of the diff page if there is only one contributor to the page

1. Go to special:diff/1001178118.
2. Click [Rollback] button.
3. When the Twinkle rollback, it will display the following text:

Grabbing data of earlier revisions: No previous revision found. Perhaps IN is the only contributor, or that the user has made more than 50 edits in a row.

I think that isn't necessary. That can be done by controlling the source - that is, do not show [rollback (AGF)] || [rollback] || [vandalism] button. By the way, did you know? Alcremie's 1000th edit was made very close to the 20th anniversary day of Wikipedia. 15:33, 30 January 2021 (UTC)

As above, this would be fairly unwieldy and slow things down. I suppose it'd be less apparent on diffs, but it would delay things loading. ~ Amory (u • t • c) 01:30, 1 February 2021 (UTC)

Nomination for deletion of Template:Uw-ttraidblock

Template:Uw-ttraidblock has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Aasim (talk) 02:05, 1 February 2021 (UTC)

Nomination for deletion of Template:Uw-ewpovblock

Template:Uw-ewpovblock has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Aasim (talk) 02:08, 1 February 2021 (UTC)

I have created block templates.

You are welcome. ThePersistentAddition (talk) 17:12, 27 January 2021 (UTC)

And they have been TFD'd. I recommend consensus before you create a block template, suggest in the village pump. Aasim (talk) 09:32, 1 February 2021 (UTC)

Feature request

Hey you hard-working volunteers, thanks for Twinkle!

Had a feature request: Is it possible when using the Twinkle > Warn > search field, for the search feature to look through all templates by default and find the one you need? Currently, if you're looking for the COI template (random example), you have to either know to search through the single-issue notices page, or scroll all the way to All warning templates and run the search on that. Seems to me that a search tool should search everything. Thanks for your hard work! Cyphoidbomb (talk) 17:33, 27 January 2021 (UTC)

A workaround would be to configure "all templates" as the default group at Wikipedia:Twinkle/Preferences#warn. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 17:43, 27 January 2021 (UTC)

Just tried it. The downside there is that the layout of templates that I've become accustomed to over the years has changed, and the neat headings have disappeared as well. Cyphoidbomb (talk) 17:53, 27 January 2021 (UTC)

Cyphoidbomb, this should now be live, thanks to TheTVExpert! ~ Amory (u • t • c) 16:15, 31 January 2021 (UTC)

Cool, thanks TheTVExpert! Is this something I have to turn on? It doesn't seem to work for me just yet. Cyphoidbomb (talk) 17:05, 31 January 2021 (UTC)

Sorry, Cyphoidbomb, I meant that the group of "All templates" should now show the headers in the order expected. If you set that to your default, you can search for any template but still also see the headings you wanted. ~ Amory (u • t • c) 17:58, 31 January 2021 (UTC)

Amory I now see the change, although I was getting used to having L4 be my default warning. Curses! I appreciate the adjustment. That said, I still think the search field should encompass all standard warnings/notices, but perhaps an argument for another time. Regards to all, Cyphoidbomb (talk) 02:22, 2 February 2021 (UTC)

I hear ya, but counterpoint: someone who wants to give a level 3 warning and doesn't want their search results polluted with other options outside the level they've already selected. That's why the menu option with every template was created, for the broad search. ~ Amory (u • t • c) 12:22, 2 February 2021 (UTC)

TfD problem

This has been on my mind for some time, but can Twinkle stop inserting an extra line when nominating a template for TfD? See e.g. this, this, or this for what I'm talking about.

That is, rather than

{{Tfm/dated|...}}
ORIGINAL TEMPLATE CONTENT

can it be

{{Tfm/dated|...}}ORIGINAL TEMPLATE CONTENT

or perhaps

{{Tfm/dated|...}}<!--
-->ORIGINAL TEMPLATE CONTENT

(provided the bot or script used to remove the banner could correctly remove <!-- --> as well)?

The line break could be particularly disruptive e.g. when the template is used inside <ol>...</ol> made by #. I assume the same applies to other types of banners such as SD, in which case </noinclude> should be immediately followed by the first character of the template content without a line break. Nardog (talk) 12:35, 2 February 2021 (UTC)

Many templates start with {| which must be at the start of a line. Otherwise the whole table code is displayed instead of rendering the table. There is also other code which must be at the start of a line. In some cases it is produced by transcluding another template so it may be hard to detect for Twinkle. Always omitting a newline would do more damage than always including it. Wikipedia:Templates for discussion#Listing a template says: "If the template nominated is inline, do not add a newline between the Tfd notice and the code of the template." The newline is the default recommendation. PrimeHunter (talk) 12:57, 2 February 2021 (UTC)

Twinkle tries to be smart: if it detects p .Inline-Template it defaults to inline (and likewise .infobox' for infobox). Perhaps some additional clarification on the meaning of the menu options would be helpful? ~ Amory (u • t • c) 13:10, 2 February 2021 (UTC)

Ah, that's true. Clarification sure could help, but I think a separate checkbox would be even better (e.g. "Suppress line break after tag (recommended for inline)"). I also wonder why |type=disabled isn't available in the dropdown; I submit that it should be. Nardog (talk) 13:31, 2 February 2021 (UTC)

@Nardog and PrimeHunter: For TfDs twinkle offers a "deletion tag display style" option. If set to "standard" or "sidebar/infobox", a newline is added. If set to "inline template" or "tiny inline", no newline is added. This option usually has to be selected by nominator, but is auto-set in cases mentioned by Amorymeltzer. – SD0001 (talk) 13:30, 2 February 2021 (UTC)

FFD notices

Are there plans in the works for Twinkle to add optional FFD notices to either the talk pages where files are used or to captions (where applicable). This is the optional part of the WP:FFD Instructions, Step 3. Give due notice. The documentation suggests that there are no extra FFD options to handle this. -2pou (talk) 22:12, 8 February 2021 (UTC)

Nomination for merging of Template:R from template shortcut

Template:R from template shortcut has been nominated for merging with Template:R from shortcut. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Aasim (talk) 10:12, 9 February 2021 (UTC)

IP user notification

When I realised I created an XfD notification at User talk:203.143.10.132 for a user whose last contributions were in 2005, I was quite amused; however, a regular Wikipedia reader might now be confused rather than amused. I think Twinkle should notify IPs whose last contributions were more than half a year ago. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:53, 9 February 2021 (UTC)

Update to Twinkle menu — Devs read here

This is for folks from other projects who maintain their local forks of Twinkle who may be bullets on their Vector menus today. Similar to last June, things were changed a bit. The fix (see PR and diff) is to simply add the mw-portlet class to the constructed menu's outer class. ~ Amory (u • t • c) 18:50, 9 February 2021 (UTC)

BLPPROD tagging should not add Old prod template to talk pages

Twinkle currently appears to add the {{Old prod}} template to talk pages when an article is tagged as BLPPROD. However, this is incorrect behaviour, per WP:BLPPROD: "a prior declined BLPPROD nomination does not block an article from being nominated for standard PROD and vice versa." --Paul_012 (talk) 12:57, 10 February 2021 (UTC)

I still think the template is valuable to have, for showing talkpage readers the history of the page. I don't think Twinkle should be changed. UnitedStatesian (talk) 13:13, 10 February 2021 (UTC)

@UnitedStatesian: The solution would be a different template. I'm with Paul 012, it's confusing to have a template whose primary purpose is to remind users that a page is now PROD-ineligible when that is not the case. davidwr/(talk)/(contribs) 13:50, 10 February 2021 (UTC)

Nomination for deletion of Template:Expert needed

Template:Expert needed has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Ten Pound Hammer • ^{(What did I screw up now?)} 22:27, 9 February 2021 (UTC)

• As noted in the TfD, "Template:Example" seems to be a bug in Twinkle. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 22:32, 9 February 2021 (UTC)
  • @TenPoundHammer: Unrelated to the TfD, but what happened to get the "Template:Example" do you know? Do you remember what the steps were when you nominated the page? ~ Amory (u • t • c) 11:01, 10 February 2021 (UTC)
    • @Amorymeltzer: I don't know. I just did it like any other Twinkle nomination, and it did this. I think it's because the template is fully protected that Twinkle spazzed out. Ten Pound Hammer • ^{(What did I screw up now?)} 23:00, 10 February 2021 (UTC)
      • Twinkle should be able to handle that, though, so I'm curious how it ended up happening. ~ Amory (u • t • c) 18:56, 11 February 2021 (UTC)

Change to wording of Template:Undisclosed_paid with language saying that the payer may not be the subject of the article

Per the instructions at Template:Twinkle_standard_installation:

If you plan to make breaking changes to this template, move it, or nominate it for deletion, please notify Twinkle's users and maintainers at Wikipedia talk:Twinkle as a courtesy, as this template is used in the standard installation of Twinkle. Thank you!

The change to Template:Undisclosed_paid is the addition of the sentence:

The payer may have been the subject of the article, or a competitor, rival, associate, independent entity, etc.

So that it looks like:

Further discussion could be at Template_talk:Undisclosed_paid#Proposal_to_add_language_to_the_template....

Jjjjjjjjjj (talk) 04:08, 12 February 2021 (UTC)

January 2021 Twinkle updates (2021-01-31)

A number of more minor improvements this time around. Most notably, most watchlist defaults have been changed to take advantage of expiring watchlist behavior. A number of bugs have been fixed; a brief summary of some of the more notable items are below. Changes not otherwise attributed were made by User:Amorymeltzer.

• Watchlist behavior:
  • Set most watchlist defaults to 1 month expiry (#1249)
• All windows: add link to Twinkle talk page (#1212, by TheTVExpert)
• tag:
  • Hide subheadings on quick filter (#1288, by TheTVExpert)
  • Fix rcat matching when 1= is explicitly used (#1246)
• warn:
  • Add headers for "All Warning" template group (#1290, by TheTVExpert)
  • move {{uw-agf-sock}} from singlewarn to singlenotice (#1265)
• arv: Add a blank newline after UAA entries (#1263)
• revert and rollback: Change 'Reverted to revision' edit summary to 'Restored revision' (#1271)
• speedy: Remove T3 (#1217)
• shared: Add preview (#1275, by TheTVExpert)
• block:
  • Adjust default expiry for copyright blocks to be indefinite for registered users (#1278, by ToBeFree)
  • AP2 amended to post-1992 (#1284)
• unlink:
  • Link the listed pages (#1254)
  • Properly show what will happen to all links (#1248)
• unlink/batch: Sort lists of pages by namespace then title (#1251)
• batch:
  • Show arrow links for batchprotect and batchundelete (#1254)
  • Show image uploader/editor info, like batch delete (#1253)
• welcome: Fix welcome-short parameter syntax (#1269, by TheTVExpert)
• prefs: fix typo: proteting -> protecting (#1285, by The Earwig)
• morebits:
  • Fix handling of circular redirect page load (#1274)
  • lookupCreation: fix bug from JSON conversion (by SD0001)

This section should serve as a catching ground should anything not work properly or if any new bugs crop up, as well as for any feedback or suggestions. There were a lot of changes behind the scenes, so feel free to ping me. As always, input is welcome at the GitHub repo as well. Finally, if you're interested in helping out with Twinkle development, there's a helpful guideline for new contributors — check it out! ~ Amory (u • t • c) 16:12, 31 January 2021 (UTC)

@Amorymeltzer would you mind adding the most important bits to the next issue of Scripts++ if you have time? I missed this for the January issue unfortunately DannyS712 (talk) 01:57, 3 February 2021 (UTC)

​It's actually on my todo list whenever I make this post, but I didn't think anything here was really worth mentioning this time around. In hindsight, maybe the watchlist behavior would have been good to include? ~ Amory (u • t • c) 12:15, 3 February 2021 (UTC)

Yeah, thats what I was thinking, as well as possibly the copyright block default expiry, the preview in shared, and the revert and rollback summary change DannyS712 (talk) 13:55, 3 February 2021 (UTC)

 Done ~ Amory (u • t • c) 12:44, 13 February 2021 (UTC)

Twinkle XFD redirect template bug

When nominating a redirect page for deletion, twinkle adds the Template:afd1 to the page the redirect page links to.Manabimasu (talk) 04:55, 14 February 2021 (UTC)

@Manabimasu: I believe you're referring to Wikipedia:Articles for deletion/Regressive conservatism? From what I can tell, you selected the AfD option on the Regressive conservatism redirect, when you wanted to select Redirects for discussion. Is that right? I can clean up the AfD if you like, but I think that's what happened. ~ Amory (u • t • c) 16:05, 14 February 2021 (UTC)

​ thanks for the info. You can clean it up.Manabimasu (talk) 22:09, 14 February 2021 (UTC)

 Done See Wikipedia:Redirects for discussion/Log/2021 February 14#Regressive conservatism ~ Amory (u • t • c) 22:31, 14 February 2021 (UTC)

New user warning template Uw-medrs

New template {{Uw-medrs}} is released and available for use. There has been previous discussion of this template at WT:MED where it was mentioned that developers here should be notified. From the discussion, it is not yet clear whether this will evolve into a set of multi-level templates or not. For now, it has no numeric suffix, with the assumption that it is single-level. Further discussion either here (if Twinkley topic) or at Template talk:Uw-medrs, if more pertinent to the template itself. Thanks, Mathglot (talk) 04:14, 15 February 2021 (UTC)

Edits made using WP:Twinkle

I've been trying to see if there is a way to change the "tag: twinkle" that is affixed to any edit made using twinkle, but it doesn't seem that's possible. Is there any way to change or remove that? —FORMALDUDE^(talk) 08:22, 15 February 2021 (UTC)

What valid reason is there to remove the tag? --Izno (talk) 08:25, 15 February 2021 (UTC)

Indeed, there is no way. Previously it was possible to edit the attached summary, but that was done away with in favor of a unified tag. ~ Amory (u • t • c) 00:38, 16 February 2021 (UTC)

Notifying deceased users

As per this, could it be implemented that users with {{deceased}} on their talk page don't get notified of a nomination? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 13:06, 28 January 2021 (UTC)

It would probably be better for Twinkle to obey some kind of Category:Wikipedians who opt out of message delivery or similar, and deceased editors to have that placed on their page (or {{deceased}} to include it), rather than Twinkle accounting for particular templates directly. ProcrastinatingReader (talk) 13:09, 28 January 2021 (UTC)

@ProcrastinatingReader: So, should we create a separate category like Category:Wikipedians who opt out of Twinkle notifications? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:45, 9 February 2021 (UTC)

Category:Wikipedians who opt out of message delivery has 3,954 pages built up over years. It might be better to just use that. ProcrastinatingReader (talk) 16:48, 9 February 2021 (UTC)

I thought about that, but Twinkle notifications are quite different, as they concern a specific user (the page creator) rather than all users at once. I am thinking about opting out of message delivery, but would rather not opt out of XfD notifications. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:51, 9 February 2021 (UTC)

I've got something in the works that will allow for this, and was planning on using categories rather than templates. Things like {{deceased}} and {{retired}} put/can put folks into Category:Wikipedians who opt out of message delivery, so that'd be a reasonable thing to piggy-back on/two-birds-one-stone kinda thing. I'd be inclined to say a separate category wouldn't be ideal. ~ Amory (u • t • c) 15:53, 10 February 2021 (UTC)

Twinkle messages are directed to a single user whereas that category is for mass messages (not targeted to a specific user). Quite different. Plus, we should support the ability to turn off messages from specific modules only. This is a better done via a template using hidden external links (similar to {{no talkback}}), so that they can be efficiently queried without needing to have multiple templates or categories. – SD0001 (talk) 16:45, 10 February 2021 (UTC)

Except of course for the examples I just gave. I'm fine with using a dedicated template (I've got both written atm) but it won't avoid having multiples. It would enable limiting specific modules, so that'd be a cool feature; hadn't thought of that. ~ Amory (u • t • c) 17:07, 10 February 2021 (UTC)

Not sure what you mean. The template could be included in those other templates. If we're fine with having multiples, then it deosn't matter if they're temlpates or categories. But the beauty of the external link trick is that we could aim for a single template: {{no twinkle}} (disable all) --> gives notwinkle.com?modules=csd|prod|xfd, {{no twinkle|csd}} (disable just csd) --> notwinkle.com?modules=csd. Then query prop=extlinks for notwinkle.com and parse the module list. – SD0001 (talk) 20:10, 10 February 2021 (UTC)

Yes, I'm agreeing with you on that. I was saying that to only use that would mean the presumptuous editing of retired or deceased users' talkpages. Both can exist, yes, but both have to exist. At any rate, more when PR. ~ Amory (u • t • c) 21:30, 10 February 2021 (UTC)

Worth noting {{deceased}} / {{retired}} are usually placed on user pages, rather than user talk pages which are usually what contain Category:Wikipedians who opt out of message delivery. So it'll have to check user pages too, probably. ProcrastinatingReader (talk) 00:05, 14 February 2021 (UTC)

{{deceased}} is always placed on the talk page as well. For {{retired}} too it should be (and usually is) placed on the talk page as well though it depends on the user. – SD0001 (talk) 10:59, 16 February 2021 (UTC)

Template:Needtrans updated

Fyi: Template:Needtrans has been updated to be more robust for the use of param |language=. Thanks, Mathglot (talk) 08:39, 18 February 2021 (UTC)

Nominations at MFD have no newline

When nominating a page for deletion at WP:MFD with Twinkle, it seems to omit a newline between the page information and the nomination statement, and other times it doesn’t seem to be omitted. See the two discussions for February 15, 2021. Both were nominated using Twinkle, but one of them has a newline, and the other doesn’t. This can cause scripts like WP:XFDV to not work, because omitting the newline causes the script to parse the nomination statement as “undefined”. GMXping! 16:15, 16 February 2021 (UTC)

This appears to be the result of some recent edits to {{mfd2}} by Awesome Aasim... The template ought to add a newline automatically. – SD0001 (talk) 20:12, 19 February 2021 (UTC)

Can poke this tomorrow and fix it if nobody wants to grab it first. ƒirefly ( t · c ) 20:39, 19 February 2021 (UTC)

P.S. The reason my nomination has a newline is that I fixed it manually - unfairly blaming Twinlke at the time! ;) ƒirefly ( t · c ) 20:42, 19 February 2021 (UTC)

PorkchopGMX and SD0001 I noticed as well and promptly reverted, attempted in the sandbox, and then fixed it. Feel free to sentence me to the village stocks if it merits it. :)

What I was trying to do was make it easier to nominate multiple pages with the MFD2 template (by adding a "first" parameter) because sometimes you need to do that. There was no dedicated template to do that, so I went ahead and added that functionality in. After a few technical hurdles it should be working now. Feel free to fix it up even further if it is still not working. Aasim (talk) 21:48, 19 February 2021 (UTC)

Cola before links

I know this is veery unimportant, but as Twinkle already has so many minor but helpful things, I am still suggesting that a colon be added before a link not only in the posted text, but also in the edit summaries. This is to prevent incorrect linking of subpages: Special:Diff/1006788316, Special:Diff/1006788323. Thanks. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 10:18, 16 February 2021 (UTC)

@1234qwer1234qwer4: Indeed. Sounds like a good first task. Feel free to file a patch. – SD0001 (talk) 20:03, 19 February 2021 (UTC) My bad, patches still welcome for the phab task I guess :) – SD0001 (talk) 09:58, 20 February 2021 (UTC)

Sorry, thought I replied to this 1234qwer1234qwer4, but Twinkle already prepends the colon to both those edit summaries; indeed, Twinkle has for years done so for any link that could be to a user page to avoid pings. Seems like a MW bug? Unless I'm misunderstanding you... ~ Amory (u • t • c) 22:11, 19 February 2021 (UTC)

@Amory: Yep, I see the source code of your edit summary in my email notification and this confirms it is indeed a MediaWiki bug. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 22:13, 19 February 2021 (UTC)

See phab:T273860, Wikipedia:Village pump (technical)/Archive 187#Is linking to articles beginning with a slash impossible in summaries?. Nardog (talk) 08:09, 20 February 2021 (UTC)

Add AGF links everywhere?

Should all Twinkle rollback/revert links display all three types (AGF, rollback, vandalism)? Right now, they're only on diff pages, whereas Contributions, history, and Recent Changes have two (rollback, vandalism). ​I'm in favor of doing so, but wanted other folks' opinions. ~ Amory (u • t • c) 16:41, 20 February 2021 (UTC)

Actually, would it be possible to deactivate separate buttons instead of the whole module? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 17:34, 20 February 2021 (UTC)

As in, you want preferences to disable a type of link entirely? ~ Amory (u • t • c) 15:25, 21 February 2021 (UTC)

Yes. I realised I'm pretty much using only regular rollback, and the other links just clutter the corresponding pages. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 15:27, 21 February 2021 (UTC)

Arbitration Requests buddy

Hi, I'm not sure who can adjust this but I tried giving an editor a sanction warning about Cryptocurrencies using Twinkle Arbitration Requests buddy but couldn't find it listed. In fact, none of the General/Community sanctions are listed (you can find them at Template:Gs/alert).

Also, Gamergate is listed four times on the drop-down menu for Discretionary Sanctions. It would also help if the items were alphabetized and there was a scroll on the right hand side...the pop-up box extends beyond the right-side of a normal laptop screen so it is cut off. Maybe the box could be resized to allow two lines of text, rather than one loooooong string of characters. Thank you! Liz ^{Read! Talk!} 03:31, 21 February 2021 (UTC)

@Liz: That's User:Bellezzasolo/Scripts/arb, which isn't part of Twinkle, it's maintained by Bellezzasolo (who has hasn't been particularly active lately). It hasn't been updated in a year or so. ~ Amory (u • t • c) 15:23, 21 February 2021 (UTC)

@Liz and Amorymeltzer:, the reason for the lack of GS is a change to the format of {{Gs/topics}}. I've published a quick fix for that one. As regards scrolling, I'm not sure how to do that easily, but you should be able to drag the window to the left side of the screen, which will probably let you read them! ∰Bellezzasolo✡ Discuss 18:42, 21 February 2021 (UTC)

New maintenance tag: No reliable sources

Others editors recently expressed a maintenance tag for articles that have no reliable sources in them. I went and generated such a tag, as follows:

What does it take to get this incorporated into Twinkle so that NPP users can have easy access to it? Am I asking in the right place? A loose necktie (talk) 02:32, 21 February 2021 (UTC)

A loose necktie, I'm not sure this tag is a good idea; editors argue over what's reliable and what isn't all the time. Adam9007 (talk) 02:38, 21 February 2021 (UTC)

I suppose that is true. It is meant to be used in those cases where the sources are clearly unreliable (facebook, blogs, etc.). If an article had a source whose reliability was in doubt, the tag shouldn't be used there. But NPP gets a lot of pages that contain nothing that anyone would consider reliable, and for those articles, this tag might be useful. A loose necktie (talk) 02:49, 21 February 2021 (UTC)

@A loose necktie: Twinkle has {{Unreliable sources}} and {{Unreferenced}}, which cover the cases, yes? ~ Amory (u • t • c) 15:20, 21 February 2021 (UTC)

Agree. {{No reliable sources}} should be redirected to {{Unreliable sources}}. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 15:22, 21 February 2021 (UTC)

There was some discussion here and here that there was a need for a distinct template by those who have a use for it. The need for such a template seems to be real, not contrived. A loose necktie (talk) 06:49, 22 February 2021 (UTC)

No, they're not the same. An article that has no reliable sources is not the same as one which has sources, some of which are unreliable, nor is it completely unreferenced. Not a comment on whether it would be useful to add to Twinkle, just that it shouldn't be redirected. Black Kite (talk) 06:58, 22 February 2021 (UTC)

I wasn't suggesting it, but an article with "no reliable sources" either has "no sources" or "all sources unreliable" so the already-present tags cover the two more specific cases. I'll note that {{unreliable sources}} has a parameter to toggle to toggle "some" and "some or all" in the message. ~ Amory (u • t • c) 11:36, 22 February 2021 (UTC)

In Twinkle, you can't add a parameter to "unreliable sources", so there is no method to change it to "some or all sources are unreliable" (ignoring whether, if you know that all sources are unreliable, it isn't better to state this unequivocally instead of the wishy-washy "some or all"). So at the moment, if I see it correctly, it is impossible to directly use Twitter to tag an article as having "no" reliable sources. Fram (talk) 11:52, 22 February 2021 (UTC)

It's not "impossible", as Twinkle users can manually add tags so that they are available for their own use. BilCat (talk) 19:43, 22 February 2021 (UTC)

Ah, I didn't notice the switch. Fair enough then, though I don't think the template is completely useless. Black Kite (talk) 19:46, 22 February 2021 (UTC)

I understand the motivation to suppress the development of redundant templates, but doesn't it also make sense to develop and utilize a new template if it works better than existing ones in certain common contexts and is faster and easier to use than manually modifying parameters of a "square peg" template going into a "round hole" situation? Just seems like a no-brainer to me. A loose necktie (talk) 20:41, 22 February 2021 (UTC)

Nomination for merging of Template:In use

Template:In use has been nominated for merging with Template:Under construction. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. JsfasdF252 (talk) 17:09, 27 February 2021 (UTC)

March 2021 Twinkle updates (2021-03-02)

A big improvement to the block module for sysops: you can now just block the /64! It's been live for a while, so hopefully admins have been able to make use of it. Other big changes include a new preference to watch user pages after a CSD notification, rollbacks will treat consecutive edits from the same IPv6 /64 range as the same user, and a tidier talkback menu. A number of bugs have been fixed as well as laying the groundwork for future updates; a brief summary of some of the more notable items are below. Changes not otherwise attributed were made by User:Amorymeltzer.

• Generic:
  • Ensure we extend, never shorten, a watchlistexpiry (#1301)
  • Better spacing between checkboxes and text (#1331)
  • Better messages on Twinkle preferences load failures (#1313, by SD0001)
  • Better messages when looking up page creator (#1339)
• arv: Remove duplicate sockpuppets from report (#1341)
• block:
  • Add checkbox to just block the /64 (#1266)
    • Leave template on the page of the current IP even when blocking a /64 (#1323, by GorillaWarfare)
  • Reword {{uw-efblock}} reason to say 'Repeatedly triggering' rather than 'Deliberately triggering' (#1327)
  • Show the length of the last block if it expired naturally (#1291)
• csd: Add preference to watchlist user page on notification (#1286)
• revert and rollback: Revert consecutive edits by the same IPv6 /64, treating them as the same user (#1266)
• protect: Allow admins to mark page protections that were requested at RfPP (#1293, by GorillaWarfare)
• tag:
  • COI: Add area for automatically starting a discussion on the talkpage (#1191)
  • {{R from template shortcut}} merged with {{R from shortcut}} (#1333, by TheTVExpert)
  • Fix message after successful tagging (#1340)
• talkback: Simplify menu a bit, reducing redundant talkback items (#1328)
• warn:
  • Fix bug in section insertion when non-Level2 headings are present (#1308)
  • Change reference to "level 2 heading" to "talk page section" (#1294, by GorillaWarfare)
• xfd: Fix RfD message in {{Xfd edit protected}} (#1305)

This section should serve as a catching ground should anything not work properly or if any new bugs crop up, as well as for any feedback or suggestions. There were a lot of changes behind the scenes, so feel free to ping me if anything isn't working. As always, input is welcome at the GitHub repo as well. Finally, if you're interested in helping out with Twinkle development, there's a helpful guideline for new contributors — check it out! ~ Amory (u • t • c) 19:18, 2 March 2021 (UTC)

Technical changes

There have been a fair amount of background changes, in particular the addition of Morebits.ip utilities and better error handling in a few places. As always, you can check out the jsdocs for the Morebits library at https://wikimedia-gadgets.github.io/twinkle/.

~ Amory (u • t • c) 19:18, 2 March 2021 (UTC)

Uw-agf-assign

I've added a new template, {{Uw-agf-assign}}. Could this be added to twinkle? -- RoySmith (talk) 02:47, 9 March 2021 (UTC)

Feature request - Common Warnings

There are currently 4 warnings listed in the "Common warnings" section of the Warnings table: {{uw-vandalism1}}, {{uw-disruptive1}}, {{uw-test1}}, and {{uw-delete1}}. However, the only one of these that I use on a daily basis is the Vandalism warning. I actually use {{uw-unsourced1}} as much if not more than any other warning, probably combined.

So my feature request is two-fold:

1. Would it be possible to add {{uw-unsourced1}} to the "Common warnings" section?

Or

1. Would it be possible to allow Twinkle users to choose their own 4-5 warnings to be placed in the "Common warnings" section? (Ie. User-customizable.)

I'd ultimately like the second one, but I'd settle for the first in the short term. I understand other users might prefer a different warning there, which I why I suggested user-customizable common warnings, probably as a long-term option.

Thanks. BilCat (talk) 09:41, 9 March 2021 (UTC)

DSA using Twinkle

I don't know if idea has been done before, but I think Twinkle goes hand-in-hand with delivering Discretionary Sanctionas Alerts. When using it, it will subst the DS template, turning into this:

This is a standard message to notify contributors about an administrative ruling in effect. It does not imply that there are any issues with your contributions to date.

You have shown interest in (a) GamerGate, (b) any gender-related dispute or controversy, (c) people associated with (a) or (b), all broadly construed. Due to past disruption in this topic area, a more stringent set of rules called discretionary sanctions is in effect. Any administrator may impose sanctions on editors who do not strictly follow Wikipedia's policies, or the page-specific restrictions, when making edits related to the topic.

For additional information, please see the guidance on discretionary sanctions and the Arbitration Committee's decision here. If you have any questions, or any doubts regarding what edits are appropriate, you are welcome to discuss them with me or any other editor.

🔥LightningComplexFire🔥 15:35, 3 March 2021 (UTC)

I think this is a good idea. 🔥LightningComplexFire🔥 15:35, 3 March 2021 (UTC)

I think this is a great idea, and had been meaning to suggest it myself for some time. I think it would fit best as a new option in the Talkback tool. ― Tartan357 ^Talk 15:52, 8 March 2021 (UTC)

Makes sense to me. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 15:54, 8 March 2021 (UTC)

Belezzasolo has a module for it (can't be bothered to look up the link right now), though if I recall correctly it's been a while since it was updated. ^{SubjectiveNotability} _{a GN franchise} (talk to the boss) 15:57, 8 March 2021 (UTC)

That'd be User:Bellezzasolo/Scripts/arb; there's a brief mention of it above at Wikipedia talk:Twinkle/Archive 44#Arbitration Requests buddy. Dunno that Twinkle needs to sherlock it. ~ Amory (u • t • c) 12:08, 9 March 2021 (UTC)

I think this fits the scope of Twinkle; this could be merged like Friendly was. @Bellezzasolo ping. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 12:11, 9 March 2021 (UTC)

Bug: SPI reporting

I've noticed a bug that's appeared in two SPI cases I've opened using Twinkle. Twinkle only places the sockmaster's username in the links for the Editor interaction utility and the Interaction Timeline, and does not include the suspected sockpuppets. See [4]. ― Tartan357 ^Talk 15:50, 8 March 2021 (UTC)

AFAIK, that's due to how Template:SPI report works, in particular through Wikipedia:Sockpuppet investigations/SPI/Blank report template header, which is how the puppeteer name is added to a new, blank report. I don't think including the template includes a way to indicate the puppeteer? ~ Amory (u • t • c) 12:17, 9 March 2021 (UTC)

Abuse section

In discussion with some other users I've been trying to clarify appropriate use in the 'Abuse' section, but the wording has not been polished very well -- so feel free to improve this section further. The goal is to improve the wording so it doesn't sound like simply including a minimal edit summary (such as mere Tag) automatically justifies any "lazy" undo of constructive, good faith contributions which merely needed a little improvement. (Unfortunately, it seems that whenever I find the laziest type of deletions of constructive contributions I find it has come from a Twinkle user, so appropriate usage needs to be clarified better.) DKEdwards (talk) 21:55, 7 March 2021 (UTC)

DKEdwards, I think you're looking at this a bit too narrowly. Bad reverts aren't a problem with Twinkle, they're a problem with the user - they could have reverted you using the Undo button, by manually undoing your edit, using Huggle, Redwarn, even the old old "open the previous edit and save it" revert. I don't think putting extra warnings in the Twinkle docs are going to solve the issue. ^{SubjectiveNotability} _{a GN franchise} (talk to the boss) 16:13, 8 March 2021 (UTC)

You're right of course that this is not a "problem with Twinkle" or the majority of its uses (although there might be more that could be implemented in twinkle to discourage abuse). But as I mentioned, when I do find people doing especially lazy reverts of non-vandalism, I keep finding that they did it using Twinkle (using it incorrectly). Twinkle isn't the root cause of the problem, but there is probably some correlation between users who have the impulse to make lazy rushed reverts, and users who are attracted to tools to automate their fast work. Automation demands an above-average vigilance to proper use. I really do believe that it chases off good faith editors when their legitimate work is reverted with less effort than it took for them to make the contribution. The effort to create and destroy should be more balanced, even if that means requiring edit summaries be in full sentences (or whatever it takes!) In addition to the general guidance for all editors, I think it may be helpful to have very *specific* reminders to users of tools that are seen to be abused too frequently. Then it's possible to e.g. forward them the link to a policy note that is an exact match to what they have been doing, and that it is not proper use. I'm open to whatever *works* to remind people to not abuse tools, but I don't know all the tools and for some reason Twinkle is the only one I keep seeing people misuse. (But yes, this isn't meant to blaspheme Twinkle!) DKEdwards (talk) 20:39, 8 March 2021 (UTC)

Sort of seems like you want to repeat what's said at WP:QUO, WP:ROWN, WP:RV, etc.? I'd think it'd be better to link there since they'll always be more comprehensive. ~ Amory (u • t • c) 12:24, 9 March 2021 (UTC)

Twinkle error

I attempted to warn a spammer with a final (and then only warning) but am unable to do so and keep getting "User talk page modification: Failed to save edit: There is no section 3." is this a new change? My reading of it is that it won't take because 4im/4 needs to come after 3, but I'm not sure? 4im definitely shouldn't require a 3 or sequential warnings. CUPIDICAE💕 15:33, 11 March 2021 (UTC)

It seems so far to only be happening on this user talk. CUPIDICAE💕 15:35, 11 March 2021 (UTC)

@Praxidicae: That is a very unusual page. Twinkle may have miscounted the sections because there is an example ==References== heading hiding inside <pre>...</pre> tags. -- John of Reading (talk) 16:04, 11 March 2021 (UTC)

Huh! Is it because of the template? CUPIDICAE💕 16:07, 11 March 2021 (UTC)

@Praxidicae: Yes. I've edited {{W-FAQ}} to use different markup that will not be so confusing. If that edit sticks, future uses of that template will work OK. It won't solve the problem on pages where the template has already been placed, such as the one you mention. -- John of Reading (talk) 16:20, 11 March 2021 (UTC)

Notification of TfD

Please see Wikipedia:Templates_for_discussion/Log/2021_March_19#COI_article-space_templates. XOR'easter (talk) 15:25, 20 March 2021 (UTC)

Remember what to report/warn about

On Special:Contributions, can't Twinkle remember the page and revisions of the last rollback so that they will be automatically filled in with when the user opens ARV, Warn or Wel? Or, perhaps better yet, remember rolled-back users/pages/revisions in cookies for a short period of time so they will be filled in with when ARV, Warn, or Wel is opened on any page associated with one of the users? Nardog (talk) 16:21, 17 March 2021 (UTC)

Sorry Nardog, I'm having trouble understanding what you're asking for. What do you mean by "remember?" ~ Amory (u • t • c) 16:51, 20 March 2021 (UTC)

@Amorymeltzer: That the ARV, Warn or Wel form will be automatically filled in with the information (page name/revision IDs) about the last revert you did of that user when you open it, even when "Open user talk page..." is turned off or when the form was not opened through a window automatically opened by Twinkle. Nardog (talk) 17:01, 20 March 2021 (UTC)

Redirect tagging bug

For some reason, Twinkle inserted two vertical bars before the redirect shell. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 12:57, 19 March 2021 (UTC)

Mmm, nice find. Twinkle wasn't treating the preexisting tags as a regex, and the | for the parameters was throwing things off. Should be fixed now. ~ Amory (u • t • c) 17:12, 20 March 2021 (UTC)

Article maintenance tagging - Group inside 'multiple issues' bug

First of all, I would say it is so nice to have a gadget like 'Twinkle' & I have been using it always.

I just want to bring to your notice that I use 'Twinkle' for adding the {{Cleanup bare URLs}} which has many a times group the bare URL tag inside 'multiple issues' even though I had unchecked the group box provided at the bottom. It is a bug that needs to be addressed. Check this & this edits.

Please do the needful at earliest.

Thank You! -Ninney (talk) 02:21, 18 March 2021 (UTC)

@Ninney This seems plausible, but in your case, why did you add the tags even though you fixed the URLs just after that? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 13:04, 19 March 2021 (UTC)

Just a small misunderstanding. Why should I tag the article & then fix the URLs in the first place when I can directly fix it?

I read a lot many articles on wiki & if I find any bare URLs I simply use Twinkle & tag them. There are very few good editors (like @Derek_R_Bullamore, @MarnetteD and @CommanderWaterford) who are indirectly part of the cleanup clique working tirelessly & endlessly helping articles getting rid of bare URLs. They are the ones fixing it.

I personally think that while tagging the Bare URLs tag it should not be inside multiple issues (MI) since they get fixed within a day by the above editors using reFill 2 or any other tool.

Check this particular edit, where even though I had unchecked the group box, the tag went inside the MI & the editor had to remove it from the MI & then fix the 25 bare references using reFill 2. How cumbersome it will be for the cleanup team to always remove the tag from the MI group & then use the tool for fixing the references?

I had tried various combinations on separate occasions - first unchecking the check box for MI & then marking the tag OR by first selecting the tag & then unchecking the check box but could not identify the issue as it works smoothly sometimes & that is when I thought of reporting it here.

All the best! -Ninney (talk) 03:01, 20 March 2021 (UTC)

I requested that Twinkle NEVER group this tag inside MI here about a year ago. MB 03:19, 20 March 2021 (UTC)

It is uncommon to have an exception like that. Why not just make the template display "(reFill)" (with a link) at the end of the text when grouped into the multiple issues template? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 11:14, 20 March 2021 (UTC)

I agree, this could and should be handled on the template's end. Nardog (talk) 17:29, 20 March 2021 (UTC)

Note that the fact that Twinkle apparently ignored the unchecked "group inside multiple issues" box is still a bug. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 20:16, 20 March 2021 (UTC)

New welcome message?

It would be really great if there was a welcome message essentially saying "Your user page is not a social media profile page". I find the biggest mistake that new editors make is putting a lot of personal information on their user page that would be perfectly okay on social media but is not appropriate for Wikipedia. So if there was a welcome message that talked about user pages or linked to that policy page, I'm sure it would get used a lot. Not sure who addresses these comments about Twinkle but thought I'd just put it out there in case someone decides to add it to the list. Liz ^{Read! Talk!} 02:03, 23 March 2021 (UTC)

@Liz I mean, there are warning templates like {{uw-socialnetwork}} or {{uw-userpage}}. A new template proposal is probably not a problem of Twinkle. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 12:29, 23 March 2021 (UTC)

Template parameters in XfDs bug

Twinkle should use "1=" and the like for unnamed parameters where arbitrary page names are possible, since page titles may contain equals signs. See Wikipedia:Miscellany for deletion/Template:State of Green=Creating User:Greenfuturedk for an example. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 20:18, 8 March 2021 (UTC)

1234qwer1234qwer4, was there an error here? ~ Amory (u • t • c) 16:49, 20 March 2021 (UTC)

@Amorymeltzer "Example (edit | talk | history | links | watch | logs)​". 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:52, 20 March 2021 (UTC)

Ahh I see. That's not Twinkle, it's Template:Mfd2. Twinkle provides |pg=pagename but it looks like {{Mfd2}} doesn't for the {{pagelinks}} template, ie, Mfd2 does {{pagelinks|{{{1|{{{pg}}}}}}}}. ~ Amory (u • t • c) 17:21, 20 March 2021 (UTC)

@Amorymeltzer I assume my edit fixed it? Not sure why you didn't implement it. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 17:57, 25 March 2021 (UTC)

Nomination for merger of Template:R from historic name

Template:R from historic name has been nominated for merging with Template:R from former name. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. {{u|Sdkb}} ^talk 18:01, 25 March 2021 (UTC)

Rcat parameters

I suggest Twinkle allow for including the "of" parameter in redirect templates that support it. I'm not sure I can list all of them, but here are some examples:

• {{R from long name}}
• {{R from short name}}
• {{R from abbreviation}}
• {{R from initialism}}
• {{R from acronym}}
• {{R from plural}}
• {{R to plural}}
• {{R from alternative spelling}}
• {{R from misspelling}}
• {{R from alternative capitalisation}}
• {{R from miscapitalisation}}.

𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 18:06, 25 March 2021 (UTC)

Improved edit summary for PRODs?

Right now, when adding a {{proposed deletion}} tag with Twinkle, the edit summary is "Proposing article for deletion per WP:PROD." When the rationale provided is short (say, less than 200 characters), can that be included in the edit summary as well? User:力 (power~enwiki, π, ν) 04:57, 27 March 2021 (UTC)

re Article on Frank McCoppin 1834-1897 born Clonterm, Longford, Ireland.

Please explain why in this article he is described as a Scottish national hero when he was born in Ireland?? He is my 3 x Grt Uncle and as such is included in my family tree. Is this an error calling him Scottish when you have him listed as born in Clonterm, Ireland? You have his picture and details listed on this page stating that he was born in Clonterm,Longford, Ireland (1834-1897). Dustysocs (talk) 06:27, 3 April 2021 (UTC)

@Dustysocs: How is this related to Twinkle? If you're not happy with how the article is written, you can either exercise WP:BOLD or create discusison on WP:TEAHOUSE or WP:HELPDESK. This is not the right place to ask this question. — Paper9oll (🔔 • 📝) 06:33, 3 April 2021 (UTC)

XFD previews

I can't scroll the preview of AFD nom to see it all. Is it just me? Usedtobecool ☎️ 03:21, 2 April 2021 (UTC)

@Usedtobecool it works fine for me. By any change are you using a mobile device or some old browser? – SD0001 (talk) 13:21, 3 April 2021 (UTC)

No, Windows 10, Google Chrome Version 89.0.4389.114. I just tried on Edge, and it worked. So, obviously it's just me. I'll troubleshoot myself. Thanks for looking, SD! Best, Usedtobecool ☎️ 13:28, 3 April 2021 (UTC)

Notifying deceased users

As per this, could it be implemented that users with {{deceased}} on their talk page don't get notified of a nomination? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 13:06, 28 January 2021 (UTC)

It would probably be better for Twinkle to obey some kind of Category:Wikipedians who opt out of message delivery or similar, and deceased editors to have that placed on their page (or {{deceased}} to include it), rather than Twinkle accounting for particular templates directly. ProcrastinatingReader (talk) 13:09, 28 January 2021 (UTC)

@ProcrastinatingReader: So, should we create a separate category like Category:Wikipedians who opt out of Twinkle notifications? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:45, 9 February 2021 (UTC)

Category:Wikipedians who opt out of message delivery has 3,954 pages built up over years. It might be better to just use that. ProcrastinatingReader (talk) 16:48, 9 February 2021 (UTC)

I thought about that, but Twinkle notifications are quite different, as they concern a specific user (the page creator) rather than all users at once. I am thinking about opting out of message delivery, but would rather not opt out of XfD notifications. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 16:51, 9 February 2021 (UTC)

I've got something in the works that will allow for this, and was planning on using categories rather than templates. Things like {{deceased}} and {{retired}} put/can put folks into Category:Wikipedians who opt out of message delivery, so that'd be a reasonable thing to piggy-back on/two-birds-one-stone kinda thing. I'd be inclined to say a separate category wouldn't be ideal. ~ Amory (u • t • c) 15:53, 10 February 2021 (UTC)

Twinkle messages are directed to a single user whereas that category is for mass messages (not targeted to a specific user). Quite different. Plus, we should support the ability to turn off messages from specific modules only. This is a better done via a template using hidden external links (similar to {{no talkback}}), so that they can be efficiently queried without needing to have multiple templates or categories. – SD0001 (talk) 16:45, 10 February 2021 (UTC)

Except of course for the examples I just gave. I'm fine with using a dedicated template (I've got both written atm) but it won't avoid having multiples. It would enable limiting specific modules, so that'd be a cool feature; hadn't thought of that. ~ Amory (u • t • c) 17:07, 10 February 2021 (UTC)

Not sure what you mean. The template could be included in those other templates. If we're fine with having multiples, then it deosn't matter if they're temlpates or categories. But the beauty of the external link trick is that we could aim for a single template: {{no twinkle}} (disable all) --> gives notwinkle.com?modules=csd|prod|xfd, {{no twinkle|csd}} (disable just csd) --> notwinkle.com?modules=csd. Then query prop=extlinks for notwinkle.com and parse the module list. – SD0001 (talk) 20:10, 10 February 2021 (UTC)

Yes, I'm agreeing with you on that. I was saying that to only use that would mean the presumptuous editing of retired or deceased users' talkpages. Both can exist, yes, but both have to exist. At any rate, more when PR. ~ Amory (u • t • c) 21:30, 10 February 2021 (UTC)

Worth noting {{deceased}} / {{retired}} are usually placed on user pages, rather than user talk pages which are usually what contain Category:Wikipedians who opt out of message delivery. So it'll have to check user pages too, probably. ProcrastinatingReader (talk) 00:05, 14 February 2021 (UTC)

{{deceased}} is always placed on the talk page as well. For {{retired}} too it should be (and usually is) placed on the talk page as well though it depends on the user. – SD0001 (talk) 10:59, 16 February 2021 (UTC)

I am restoring this topic, as it seems it has not been resolved yet. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 08:25, 9 March 2021 (UTC)

My proposal: Create Category:Wikipedians who opt out of template messages, which can then be added to the {{deceased}} and {{retired}} templates, as well as allowing any active editors to use it as well. The title ensures that the category can be used by all semi-automatic processes, and not just Twinkle. Oiyarbepsy (talk) 16:46, 17 March 2021 (UTC)

@Oiyarbepsy So, when do we create the category? Do we wait for the change described by Amory below? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 17:58, 25 March 2021 (UTC)

I proposed a new Morebits class for processing user information, which includes the ability to do this. ~ Amory (u • t • c) 16:50, 20 March 2021 (UTC)

@Amorymeltzer I don't understand what morebits is - would it be able to do things that a category couldn't? Oiyarbepsy (talk) 19:36, 25 March 2021 (UTC)

@𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰, I've created the category, see discussion section below. Oiyarbepsy (talk) 19:55, 3 April 2021 (UTC)

Missing redirect tag

I noticed that {{R from non-neutral name}}, which I use often, is not listed in Twinkle's redirect tagging tool. Can it be added? ― Tartan357 ^Talk 01:11, 2 April 2021 (UTC)

@Tartan357 You can manually add it for yourself at WP:TWPREFS. I am not sure what is generally seen as the minimal number of transclusions for an rcat to be added to Twinkle. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 21:17, 5 April 2021 (UTC)

AfC Reviewer Deletion Notification Template

Hello,

I have a suggestion.

Any time an article is XfD/PROD/CSD that was accepted through AfC, the accepting reviewer gets a notification. I would make the templates myself, but I don't know how to use templates. What do people think of this?

Noah ^💬 20:39, 9 April 2021 (UTC)

Sounds like a good idea; it should also be possible for Twinkle to fetch the reviewer through the parameter in the {{WikiProject Articles for creation}} template. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 21:13, 9 April 2021 (UTC)

SDZeroBot has an AfD notifier that contacts users based on their additions; it might be possible for SD0001 to go off the edit summaries (or tags, if someone were to get an AFCH tag) and set up an opt-in for such notifications. Primefac (talk) 11:38, 10 April 2021 (UTC)

Seems like a good idea, but an expiration may be in order, say, after two years, no notifications Oiyarbepsy (talk) 03:53, 11 April 2021 (UTC)

Yes this seems better done using a bot – especially when it needs to support expirations and be opt-in / opt-out. – SD0001 (talk) 10:42, 11 April 2021 (UTC)

Can't set custom warning templates

No matter what I do, it always disappears when I reload the page. Yes I am hitting the save changes button. Snowmanonahoe (talk) 01:03, 11 April 2021 (UTC)

@Snowmanonahoe: What always disappears when you reload? I see that User:Snowmanonahoe/twinkleoptions.js is currently red link so the preferences didn't get saved. Does the form at WP:TWPREF give any when you try to save? – SD0001 (talk) 06:58, 11 April 2021 (UTC)

No, it's successful. It also works when I try to save other settings. Snowmanonahoe (talk) 13:40, 11 April 2021 (UTC)

@SD0001 I got it. It turns out I had to hit save changes twice, once on the custom warning popup and again at the bottom. Thanks. Snowmanonahoe (talk) 13:42, 11 April 2021 (UTC)

CfD anchors

Currently, for RfD, the bullet point in the nomination automatically contains an anchor with the redirect title, easening merges by leaving links intact. Could something similar be implemented for CfD nominations? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 10:18, 6 April 2021 (UTC)

@1234qwer1234qwer4 I think this is placed by a template, so I suggest you ask at Categories for Discussion. I don't think changes to Twinkle are required for this. Oiyarbepsy (talk) 07:25, 11 April 2021 (UTC)

@Oiyarbepsy Thanks, it appears this is the template {{Cfd2}} and all others listed in the documentation. I've started Wikipedia talk:Categories for discussion#Nomination anchors now. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 07:42, 13 April 2021 (UTC)

Protected edit request on 14 April 2021

Add the rcat {{R to project namespace}} to WP:TW ― Qwerfjkl|✉   21:05, 14 April 2021 (UTC)

 Done — xaosflux ^Talk 23:27, 14 April 2021 (UTC)

Twinkle

I am.. slightly embarrassed to say this but whatever twinkle is it makes me think of like some sort of junk food ie a dessert of some sort... probably zingers.. the question is why is it called twinkle? Caleb Jones Safley (talk) 01:26, 15 April 2021 (UTC)

Good question! Twinkle used to be called Twinklefluff, and AzaToth (Twinkle's creator) explains here that the latter name came from a random name generator. 120.150.121.92 (talk) 08:06, 15 April 2021 (UTC)

Adding a new report

Hi, how to add a new report to an old SPI case? For example, i want to add a new report to this case. TheBirdsShedTears (talk) 10:53, 15 April 2021 (UTC)

There are a few different ways. If you are on the user's talk page, use Twinkle's "ARV" dropdown to file the SPI from their talk. If you are on WP:SPI itself, there is a box in the (collapsed) "How to open an investigation:" notice that will allow you to file a new report. Primefac (talk) 13:24, 15 April 2021 (UTC)

Removing Undisclosed paid

I hope that you will help me to delete this template because he's the co-founder of one of the largest corporations in Armenia and is a well-known entrepreneur in the international business community (having worked with established brands like PAUL and Marriott) and he's been covered by Armenian as well as international media a lot and his name is being referred to in a lot of important outlets, which basically means he's not an unknown person by any means.Twinkle --JohnMcCarthyDS (talk) 13:15, 15 April 2021 (UTC)

JohnMcCarthyDS, I believe you are in the wrong place, as this page is for discussion of one of our semi-automated tools. You might want to try the talk page of the article in question, or the Teahouse, to further discuss these issues. Primefac (talk) 13:25, 15 April 2021 (UTC)

Thank you --JohnMcCarthyDS (talk) 13:37, 15 April 2021 (UTC) Primefac 13:25, 15 April 2021

Thank you --JohnMcCarthyDS (talk) 13:40, 15 April 2021 (UTC) Primefac  13:25, 15 April 2021

Notification of Arbitration

Can Twinkle add Template:Arbitration CA notice to its TB section? Thanks, NotReallySoroka (talk) (formerly DePlume) 03:33, 16 April 2021 (UTC)

Nomination for deletion of Template:Expand language

Template:Expand language has been nominated for being moved from articles to talkpages. You are invited to comment on the discussion at the entry on the Templates for discussion page. Elli (talk | contribs) 11:19, 16 April 2021 (UTC)

Bug when PRODing a file which has Template:Deleted on Commons

When trying to propose a file for deletion with this template, you get "Page already tagged with a deletion template, aborting procedure", but this is not a deletion template, it is simply a maintenance tag to alert other editors that this file was deleted on Commons and may have issues, or it may just be that it is compliant with our policies but not with Commons policy. Dylsss^{(talk contribs)} 23:02, 15 April 2021 (UTC)

The regex here needs a fix. – SD0001 (talk) 13:13, 16 April 2021 (UTC)

UserBoxen Delete

I tried to nominate four user boxes to MfD as one ought. Twinkle performed almost everything correctly, but the deletion notice, the full one, was transcluded to any user page the box was on.

That confused me sufficiently to self close my nominations and renominate (incorrectly) at TfD. While it feels weird that userboxen go to MfD, Twinkle knows this when one tries to nominate to TfD. So please could the folk who understand these things look at the userboxen deletion process from end to end? Fiddle Faddle 07:20, 14 April 2021 (UTC)

I seem to recall that there is a box on Twinkle to "noinclude the nomination on transcluded pages" when you nominate a page for XfD, that should have prevented the issue. Primefac (talk) 14:03, 14 April 2021 (UTC)

@Primefac I think one issue is that I never saw it, assuming it to have been present. Another issue is that I would not realise, first time, that I needed it.

I'm reasonably experienced here, yet I managed to embarrass myself. I'd like to seek to make it harder for others to embarrass themselves. I got as far as "Well, I'm not trying that again!" Fiddle Faddle 22:13, 14 April 2021 (UTC)

Heh, fair enough. I honestly couldn't remember if that box showed up for all XfDs or just for TfD nominations, which is why I was somewhat wishy-washy in my reply.

Another thought, should you accidentally do such a task again, would be to add the <noinclude>...</noinclude> tags yourself, thereby saving the hassle of un-nominating and re-nominating.

As a third thought, I'm starting to think that we should just not have UBX in the Template: namespace for the sole reason that it causes this sort of confusion. I'm not sure Twinkle can ever be "smart" enough to know if something is a userbox or not when nominating a template. Primefac (talk) 13:22, 15 April 2021 (UTC)

Twinkle detects titles beginning with "Template:User_" as userboxen and suggests MfD for them but there's no "deletion tag display type" option for MfD as for TfD. There's still the "wrap in noinclude" option that would have prevented the issue as you say, but it isn't checked by default. Not sure what if anything needs to be done here. – SD0001 (talk) 03:36, 17 April 2021 (UTC)

So that is what the "wrap in no include" is for. I've never dared use it because I had no idea what it did 🤪 I was worried about embarrassing myself! So I managed that embarrassment anyway, at a later date and in a different way

I think the thing that need to be done is to improve that message, perhaps? But how verbose that could get! Or allow UBX to be nominated at TfD! Fiddle^Timtrent Faddle^{Talk to me} 08:29, 17 April 2021 (UTC)

The TW menu appears but on clicking them nothing happens

This is in tewiki.

The "TW" menu appears normally in all the namespaces. When any of the menu items like warn, CSD, XFD etc are clicked, nothing happens - no dialog appears. Only a # is added to the URL. This has happened after doing the following activity.

• Imported the latest version of "Gadget-morebits.js" page from enwiki. This was done because of the following problem:
  • Wile on any User talk: page, when TW --> warn is clicked, it showed the dialog with two drop-down list boxes (which is normal behavior). But, when selection is changed in the main drop-down, the list in the second drop-down is not changing (which is not normal). The list of second drop-down always remained same (the default list), no matter whichever is selected in the main drop-down. This problem was "noticed" after
    • - An extensive localisation was done on the "Mediawiki:Gadget-Twinkle.js‎" file. But I am not sure if the problem was there before localisaion.
  • To solve this issue I imported the latest version of Gadget-morebits.js.
• After that, the TW tab disppeared. So, I reverted to the old (last import) version of Gadget-morebits.js.

This time, the TW tab appeared, but none of the menu items is working.

Appreciate a quick help to solve this problem. Thanks in advance. __ Chaduvari (talk) 05:45, 16 April 2021 (UTC)

Browsers: Checked it on Chrome Version 89.0.4389.128 and Edge Version 89.0.774.77

Skin used: Vector

Thanks __ Chaduvari (talk) 05:09, 17 April 2021 (UTC)

@Chaduvari: If nothing happens on clicking the TW menus, that's usually due to a JS error which you can see in your browser console (press Ctrl+⇧ Shift+J to open).
I have been working on a new version of twinkle that's easy to localise and keep updated, created per a WMF grant. Sorry that you were not aware of this before you worked on localising the existing version. https://github.com/wikimedia-gadgets/twinkle-starter has the instructions on setting up. This is a new project so there may be a few issues. Let me know if you try it and encounter any issues. – SD0001 (talk) 06:28, 17 April 2021 (UTC)

@SD0001,

Alas! How I wish I had seen your project before spending 10 days and translating so many strings! (In fact, I was praying to God, that I may be soared the thought of upgrading Twinkle to solve the issue, which will lead me to redo the localisation altogether). Anyway, my immediate task is to restore the Twinkle first. Then I am ready to spend as much amount of time as required to relocalise it.

I checked the browser console as you suggested. On an article page, when I clicked "CSD", I got the following report in the console window. Can you please see if this helps resolve the issue..

load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:60 Uncaught TypeError: mw.util.wikiGetlink is not a function

at SimpleWindow.addFooterLink (load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:60)

at Function.twinklespeedyInitDialog [as initDialog] (load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:374)

at twinklespeedyCallback (load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:373)

at HTMLLIElement.<anonymous> (load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:68)

at HTMLLIElement.dispatch (load.php?lang=te&modules=jquery|jquery.ui&skin=vector&version=11ak3:69)

at HTMLLIElement.elemData.handle (load.php?lang=te&modules=jquery|jquery.ui&skin=vector&version=11ak3:66)

addFooterLink @ load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:60

twinklespeedyInitDialog @ load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:374

twinklespeedyCallback @ load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:373

(anonymous) @ load.php?lang=te&modules=ext.gadget.Twinkle&skin=vector&version=1uh3h:68

dispatch @ load.php?lang=te&modules=jquery|jquery.ui&skin=vector&version=11ak3:69

elemData.handle @ load.php?lang=te&modules=jquery|jquery.ui&skin=vector&version=11ak3:66 Chaduvari (talk) 08:09, 17 April 2021 (UTC)

Another observation:

On the article page, "Last" menu is working fine. I was able to go to the diff page. And on the diff page, "Since", "Since mine", and "current" are also working fine.__ Chaduvari (talk) 10:17, 17 April 2021 (UTC)

@Chaduvari Change all instances of mw.util.wikiGetlink (3 usages in te:మీడియావికీ:Gadget-morebits.js) to mw.util.getUrl.

If the bulk of your work was translating strings, then you're in luck! The translations would be needed for twinkle-core too. – SD0001 (talk) 10:24, 17 April 2021 (UTC)

@SD0001, Great!! It is working now. Thank you very much for the support. __ Chaduvari (talk) 10:47, 17 April 2021 (UTC)

And, @SD0001, I have seen your project on git hub. But I do not have a clue on -

1. how to import the same into Tewiki. and
2. where to do the translations

If you can guide me on this, I will discuss with the tewiki community and take necessary action.

Also, can you please help me with the following issue:

Wile on any User talk: page, when TW --> warn is clicked, it showed the dialog with two drop-down list boxes (which is normal behavior). But, when selection is changed in the main drop-down, the list in the second drop-down is not changing (which is not normal). The list of second drop-down always remained same (the default list), no matter whichever is selected in the main drop-down. Can you guide me what to do solve this issue. Chaduvari (talk) 10:52, 17 April 2021 (UTC)

As the readme says, click the "Use this template" button to create a github project, say "twinkle-tewiki". Clone the project and use a code editor like VS Code to add configurations and localisations for your project (does require little bit of JS familiarity, though you could take enwiki's customisations and modify those as well). Then use the command "grunt build" from the terminal which compiles all the files into a single JS file, that you can copy-paste to the on-wiki gadget page. Feel free to connect via email or Discord where this would be more convenient to discuss.

As for the warn bug, change line 786 of morebits.js to text = mw.util.escapeRegExp(text);. – SD0001 (talk) 11:17, 17 April 2021 (UTC)

Thanks @SD0001, the drop downs re working fine now. __ Chaduvari (talk) 13:27, 17 April 2021 (UTC)

"Help received" etc. tags are required

Not sure if there are any, but this page needs "Help received" "Help awaited" etc. tags which can be used in individual sections. Thanks. __ Chaduvari (talk) 23:12, 17 April 2021 (UTC)

Use on other wikis

Hi! On Wikipedia:Twinkle/Localisation there are tips on how to make Twinkle work on other wikis. I'm terrible at javascript but as far as I can see then the section Wikipedia:Twinkle/Localisation#Disabling_Modules is not updated? I think Amorymeltzer made some changes in the way modules are imported? --MGA73 (talk) 20:50, 17 April 2021 (UTC)

There've been a fair number of changes to that; that page is largely out of date. If you're trying not to include specific modules, the current way is simply not to load them through the gadget definition. ~ Amory (u • t • c) 10:08, 18 April 2021 (UTC)

There's now the twinkle-starter project that can be used to sanely localise twinkle. I've roughly updated the page to that effect. – SD0001 (talk) 10:52, 18 April 2021 (UTC)

Misspelling

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

The dropdown box for prepared messages has a misspelling under Behavior in Articles. Line 7, {{uw-nor#}} Adding original research, including unpublished syntheses of sources. That should be spelled synthesis of sources. Thanks.—JlACEer (talk) 19:49, 18 April 2021 (UTC)

...unless it's plural. Certes (talk) 19:57, 18 April 2021 (UTC)

...which is quite obviously the case. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 19:59, 18 April 2021 (UTC)

Yup, it's plural. BilCat (talk) 20:00, 18 April 2021 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Notification opt outs

Twinkle developers: I've created Category:Wikipedians who opt out of template messages. As discussed in the section above, please revised Twinkle so that it does not place notifications if either the user page or user talk page is in that category. Thank you, Oiyarbepsy (talk) 19:18, 3 April 2021 (UTC)

The category is not needed. There's a big patch by Amory as linked in the section above that'll make it possible to opt out of template messages in a more specific way (allowing for turning off specific types of notifications, etc). – SD0001 (talk) 15:37, 14 April 2021 (UTC)

@SD0001 I asked @Amory for an explanation and never got one, so maybe you understand this? What exactly will this patch do and how will it work? And how long until it is live? Oiyarbepsy (talk) 15:50, 14 April 2021 (UTC)

It will enable users to place a template on their talk page to indicate their notification opt-out preferences. Something like {{no twinkle}} to opt out of all twinkle notices and {{no twinkle|csd|prod}} to opt out of only CSD and PROD notices. {{Deceased}} and {{Retired}} are also handled in some way. Its author is no longer active so I'll look into getting it merged by the end of this month. – SD0001 (talk) 16:16, 14 April 2021 (UTC)

Many admins and patrollers use Twinkle. Are you saying that editors can opt out of warnings for disruptive behaviour? Because I can assure you that the first thing I will be doing if I am prevented from dropping a caution / warning / block notice / on a usertalkpage, is removing the template from that user's page so that it doesn't happen again. Black Kite (talk) 17:06, 14 April 2021 (UTC)

Just to be clear, a CSD/PROD option is fine (in fact any option that didn't hit the uw- template family would be), as is handling the retired/deceased templates. But a total opt-out from Twinkle warnings would simply be disruptive. Black Kite (talk) 17:16, 14 April 2021 (UTC)

No. It's largely a moot point now, but what I wrote would allow opting out of only xfd, csd, image, prod, and tag notifications. ~ Amory (u • t • c) 17:35, 14 April 2021 (UTC)

This was never even considered. The section above was specifically about automatic notifications, not ones you select specifically for a user. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 13:00, 19 April 2021 (UTC)

@SD0001 I'm okay with using templates, but they should be software-neutral and should not have Twinkle in their name. There are various other bots and programs that also send out template messages, and they should be covered by the same opt-out system. For example, a person that doesn't want a notice from Twinkle almost certainly doesn't want a notice from the Disambiguation Link bot either, nor do they want the AFD notices produced by your bot. There's a reason that the category I created used the generic term "template messages" in the title and not Twinkle. Oiyarbepsy (talk) 17:20, 14 April 2021 (UTC)

Technically twinkle will look only for a hidden external link on the page (which would be emitted by {{no twinkle}}). If and when a general purpose opt-out template is created the same external link can be embedded inside that template (or {{no twinkle}} itself could be used inside that template), and twinkle will follow it. – SD0001 (talk) 17:57, 14 April 2021 (UTC)

Inviting translations

A fork of Twinkle that supports internationalisation and localisation is now on translatewiki.net. Your help in translating messages to different languages would be very much appreciated! You can also contribute by writing message documentations (language=qqq). This will help in porting Twinkle to other wikis. Thanks. – SD0001 (talk) 17:13, 19 April 2021 (UTC)