Wikipedia talk:Twinkle/Archive 45

This is an archive of past discussions about Wikipedia:Twinkle. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Archive 40

←

Archive 43

Fine tuning categories

Hi! I've been working the AfD a bit and I'm unable to tag "Universities and colleges" instead of the generic "schools". I see that there are four cats on the " schools" delsort. I def dont want to do this manually :-) Any solution? Thanks, Vikram Vincent 16:55, 30 March 2021 (UTC)

@Vincentvikram I don't see any Wikipedia:WikiProject Deletion sorting/Universities and colleges. What are you referring to? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 12:58, 19 April 2021 (UTC)

1234qwer1234qwer4 On this link, https://en.m.wikipedia.org/wiki/Wikipedia:WikiProject_Deletion_sorting/Schools please scroll and look at the subcategories. VV 13:43, 19 April 2021 (UTC)

This seems like quite a rare (possibly unique) exception, and I think this is better solved by moving the subcategories to separate subpages (and transcluding them onto the main page, as done in multiple occasions already). I don't think the delsort script handles this correctly either. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 15:48, 20 April 2021 (UTC)

Link provided with the Sockpuppet warning is broken

When I gave someone a warning for being suspected as a sockpuppet I noticed that it gives a link to a page on Sockpuppet Investigations, however the link appears to be broken and instead displays as [[Wikipedia:Sockpuppet investigations/{{{1}}}]] instead of the actual link. Anyone know where this is supposed to take you? Blaze The Wolf | Proud Furry and Wikipedia Editor (talk) 20:24, 22 April 2021 (UTC)

Addon to the above: I noticed that it says "please respond to the evidence" before the link which means that I think it's supposed to link to the discussion of the sock which means it needed me to enter what the suspected Master account is. However it says (if known) next to the field and so I didn't enter the name of the master since I had no idea which account was the master. Blaze The Wolf | Proud Furry and Wikipedia Editor (talk) 20:26, 22 April 2021 (UTC)

CSD watchlist

Hi everyone. When tagging a page with CSD, my settings are that the page is watched temporarily but it's been permanently adding those pages to my watchlist. Sdrqaz (talk) 00:19, 23 April 2021 (UTC)

SPI report failing?

Could somebody take a look at this SPI report I filed with twinkle. It (apparently) failed to generate the right template code so the subst didn't get substituted. -- RoySmith (talk) 14:00, 23 April 2021 (UTC)

Oh, never mind. a left out some wiki-punctuation, which I guess broken the subst parsing. -- RoySmith (talk) 14:02, 23 April 2021 (UTC)

Nomination for merger of Template:POV

Template:POV has been nominated for merging with Template:Unbalanced. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:03, 1 May 2021 (UTC)

Template:Uw-notenglishtalk

{{Uw-english}} has recently been renamed to {{Uw-notenglishtalk}} per Wikipedia talk:Template index/User talk namespace#Requested move 19 April 2021. Twinkle should be adjusted accordingly. ~~~~
User:1234qwer1234qwer4 (talk) 14:52, 1 May 2021 (UTC)

Less bitey AfD notifications for non-xcon users

I was looking at Category:Welcome templates and happened upon {{WelcomeGNG}}, which I've never seen before and thought a huge improvement on our current {{Afd-notice}}. It's a genuinely friendly welcome (moreso than some of our Twinkle templates) that informs a new editor they've made an article that regrettably might not fit our current standards, but encourages them to keep working on the encyclopedia, and informs them about when and why we make separate articles. Is there a way for Twinkle to replace its current notification with this for newer (preliminarily defined as non-extended-confirmed) editors, perhaps also including a version for PRODs? Vaticidalprophet 23:27, 4 May 2021 (UTC)

I don't think that's an "approved" notice. That would be the first step, then it can be added to Twinkle. BilCat (talk) 23:55, 4 May 2021 (UTC)

@Vaticidalprophet: This appears specific for GNG/notability concerns. I'm much in favour of simplifying messages for new users, but here it seems like we'll have to add an extra checkbox. Maybe an option in the XFD window to "Use simpler AFD notify message (applicable for notability concern only)" when creator is non-xcon? However, we currently don't query the creator until user has submitted the nomination, so showing this option conditionally isn't that straightforward. – SD0001 (talk) 07:57, 5 May 2021 (UTC)

I think a better approach would be to modify the {{Afd-notice}} template to be more friendly, perhaps by borrowing elements from {{WelcomeGNG}}. But, as others noted, the template needs to be applicable to all cases, not just ones related to the general notability guideline. I would suggest that you start a discussion at the Afd-notice talk page. Oiyarbepsy (talk) 16:56, 5 May 2021 (UTC)

Twinkle glitch

Hello, Twinkle folks,

I found a glitch in the otherwise well-functioning Twinkle. I work at lot with CSD G13 stale drafts and when they are deleted with Twinkle, the program deletes the draft, the draft talk page and any redirects to the draft. But it doesn't delete redirect talk pages along with the redirects. Any way this oversight could be resolved?

The redirect talk pages do show up as broken redirects and are eventually deleted but it would be cleaner if the original Twinkle draft deletion deleted them at the same time. Thanks! Liz ^{Read! Talk!} 03:38, 17 April 2021 (UTC)

This is not a glitch or oversight, just a missing feature that no one has worked on. I have created #1382 on the issue tracker. – SD0001 (talk) 09:06, 17 April 2021 (UTC)

Thanks very much! Liz ^{Read! Talk!} 23:18, 6 May 2021 (UTC)

Proposed change to Twinkle user talk page notice for CSD C1

Hello,

About two years ago, I proposed a change to Twinkle notices for CSD C1 tagging. The problem is that empty categories are identified by a daily database report, they are tagged, then sit for 7 days and if they are still empty after a week, they are deleted. However, the current message is read by some editors as saying that the categories HAVE been empty for 7 days and are now being tagged as CSD C1 and will be deleted. Over the years, this has caused distress from some editors who state, "I just created this category yesterday, it hasn't been empty for 7 days and now you want to delete it!" But the 7 days starts with the tagging, we have no way of knowing how long a category has been empty without it since there isn't a permanent record of category contents.

So, in 2019 I proposed a change in the message we leave editors who categories get tagged to make this dynamic more clear but my proposal didn't generate any feedback so I didn't pursue things. I'm not even sure if I could just make this change myself or whether approval is necessary. But confusion still happens and so I thought I'd return and ask whether the wording on this notice could be adjusted to reduce editor distress when they receive it on their talk page. Liz ^{Read! Talk!} 23:35, 6 May 2021 (UTC)

I already did this with Special:Diff/1019505120 a while back. And, for what it's worth, the claim that we have no way of knowing how long a category has been empty without [the tagging] isn't true; VegaDark, back when they were active, used the history of Wikipedia:Database reports/Empty categories to determine how long a category had been empty (User talk:VegaDark#Ultra-Speedy deletions) * Pppery * _{it has begun...} 00:56, 7 May 2021 (UTC)

Request for option to not add article to watchlist if CSD deleting rather than tagging

Would it be possible to add an option where, if I'm deleting an article outright via CSD (rather than tagging it), it will not be added to my watchlist? ... discospinster _talk 15:10, 8 May 2021 (UTC)

AfD delsort

Wikipedia:WikiProject Deletion sorting/Awards should be added. Thanks. 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 14:50, 22 April 2021 (UTC)

This should be pretty easy to add. @SD0001 Can you file a patch? ~~~~
User:1234qwer1234qwer4 (talk) 14:53, 11 May 2021 (UTC)

Synthesis

Today, I discovered that the {{synthesis}} issue tag, concerning a common and distinctive type of original research, is not supported. Synthesis is the use of multiple sources to draw a conclusion not supported by any of them. –LaundryPizza03 (d c̄) 21:37, 26 April 2021 (UTC)

Can you please clarify what you mean by "not supported"? What do you wish to do involving that tag that you find yourself unable to do via Twinkle? DonIago (talk) 12:41, 27 April 2021 (UTC)

I cannot add the tag using Twinkle, as I can do with {{original research}}. –LaundryPizza03 (d c̄) 03:10, 28 April 2021 (UTC)

That's because {{synthesis}} hasn't been added to Twinkle yet. BilCat (talk) 05:32, 28 April 2021 (UTC)

This was the point of the original post. ~~~~
User:1234qwer1234qwer4 (talk) 12:00, 1 May 2021 (UTC)

I didn't think it had a point. BilCat (talk) 23:53, 4 May 2021 (UTC)

This is one of the most surreal discussions I have seen for a while; I thought it was perfectly obvious what LaundryPizza03 meant in the original post.

In any case, you can add this tag to Twinkle as a custom tag for yourself at WP:TWPREFS#tag under "Custom article/draft maintenance tags to display". Obviously this doesn't assist others who want to use the tag, but unfortunately, for various reasons, there is no active maintenance being done to the version of Twinkle in use on this wiki at the moment. You're welcome to put forward a pull request on GitHub if you know how. This, that and the other (talk) 09:46, 7 May 2021 (UTC)

Let me put it another way - the use of the template appears straightforward enough that it's not clear to me what the advantage would be of using it via Twinkle? I'd welcome some enlightenment on that front. DonIago (talk) 19:56, 7 May 2021 (UTC)

You could say the same for most of the templates in Twinkle's tag module. Evidently the module provides enough of a benefit for people to think it is worth using. This, that and the other (talk) 04:49, 11 May 2021 (UTC)

What advantage? Adding it without having to open the source code editor, AJAX. ~~~~
User:1234qwer1234qwer4 (talk) 14:58, 11 May 2021 (UTC)

Request undeletion at WP:REFUND

Tracked in github.com
Issue #1846

Hello!

It would be nifty to be able to request undeletions at WP:REFUND with Twinkle. Currently this is not possible. I was thinking that this would be an option for both deleted and current pages since sometimes, at least in the file namespace, I request revision undeletions when only part of a page has been deleted.Jonteemil (talk) 15:26, 17 May 2021 (UTC)

oldprod for BLPPROD

I noticed today that when a BLPPROD is added it adds {{oldprod}} to the talk page. If that BLPPROD is later removed and a user tries to add a Regular PROD, Twinkle will not allow it. It says that a previous PROD was found and terminates. This should not happen. A regular PROD can be used on an article that was previously BLPPROD'd. Oldprod should not be added when a BLPPROD is added. ~ GB fan 09:42, 13 April 2021 (UTC)

That's right. This has been brought up here a couple of times. If anyone can can file a patch on the github repository that would be welcome. – SD0001 (talk) 14:40, 14 April 2021 (UTC)

Is there anyone who has a github account that can request this change to Twinkle. This was also requested previously and never acted on, 1. Any help would be appreciated. ~ GB fan 11:27, 18 April 2021 (UTC)

I guess no one wants to help fix this problem. ~ GB fan 20:31, 3 May 2021 (UTC)

I opened #1402 on the issue tracker. – SD0001 (talk) 14:49, 18 May 2021 (UTC)

Just block the /64

Two requests:

I'd like this to be the default.
I'd like to have an option to make it the default (or vice versa).

I think the related essay is compelling for both, but having the preference would make me happy enough :^). Izno (talk) 16:43, 10 May 2021 (UTC)

This was 1352; just merged it now. – SD0001 (talk) 17:16, 18 May 2021 (UTC)

Help with contributing

Hi Twinkle devs, I'm currently trying to contribute, and I need some help testing and getting it to run. I'm working on the tagging module right now (git branch, specifically this dir), and I want to test it. I've created a new directory tag, split the tag objects into their own respective JSON files, and other things for which I'll create a new discussion on once I've been able to test. My problem is getting the json to be loaded into JavaScript, so they can be parsed in the new format before being shown in the popup. How can I do this? Thanks. SWinxy (talk) 23:02, 22 May 2021 (UTC)

Hi @SWinxy, this version of twinkle isn't in active development. While adding new templates is probably okay, for other significant code-level changes, it's unlikely anyone is around to review them. There's a more modern twinkle-enwiki repository which uses the i18n/l10n-supporting twinkle-core framework, to which we plan to upgrade some time in the near future. As for that repo, precise (and simple!) instructions for testing are available in the readme.

For the existing version of twinkle, testing is not at all straightforward. If you create additional files, that creates even more trouble. But none of these problems are applicable for twinkle-enwiki where you can use ES6 imports to inter-link different files. – SD0001 (talk) 05:54, 23 May 2021 (UTC)

Welcome template options

The welcome template options that are featured by default on Twinkle have a big effect on usage, so I think we ought to be offering up templates that do a good job being friendly and useful without overwhelming newcomers with tons and tons of links to complex pages. Keep in mind that it is always possible for an editor to add a custom template to their Twinkle module, so changes we make would not be prohibiting anything, just nudging by offering better defaults. Examining the current lineup, beyond the standard {{Welcome}}, we have:

{{Welcome-retro}} – I think it does a bad job, but it has a vocal constituency among statusquoists so I'm not going to fight its inclusion here for now.
{{Welcome-short}} – It's a nice concise message; I think we should retain it.
{{Welcome-cookie}} – It's an outdated fork of the main welcome, but the cookies are friendly, so I think we should retain it and hope we'll get consensus to wrapperify it someday so that it becomes synced.
{{Welcome-graphical}} – This has about 20 links, which is utterly overwhelming to any newcomer. For instance, it offers five different pages in the getting started section all attempting to be a starting introduction, without any guidance on where the actual best place is to start. This is guaranteed to result in choice paralysis, and good luck to any poor newbie who ends up at WP:The Missing Manual – what does it say about us that a literal book is what we suggest you need just to get started? I think it should be removed as a default option.
{{Welcome-menu}} – This template is even worse, with around 60 links. If a newbie so much as simply has a question they want to ask, this template responds "use {{helpme}}, or go to the Teahouse, or go to Questions and read the instructions there, or maybe Request administrator attention, or consider getting adopted, or there are the IRC channels, or maybe this talk page thing is what you want." That's an absurd and ridiculously unhelpful response; compare it to {{Welcome}}'s straightforward "get help at the Teahouse" button. This template should be removed as a default option.
{{Welcome-screen}} – The very first link in this template is to a historical welcome page that has since been redirected to our list of introduction pages (aka the awful ironically named Help:Getting started), which should tell you something about how well it's been maintained. It goes on to make faux pas like using jargon ("mainspace") and plugging the table of contents (who uses that?). It should be removed as a default option.

For those who yearn for a more expansive welcome template than the standard, I would suggest adding {{Welcoming}} as a replacement. It's got a nice design, helpful tips, and non-redundant links to the beginner-friendly tutorial series.

So in sum, let's remove {{Welcome-graphical}}, {{Welcome-menu}}, and {{Welcome-screen}}; editors who want to add them to their Twinkle can still do so, but they're bad templates and should not be promoted as default options. Replace them with {{Welcoming}}, a better choice. Do others agree? {{u|Sdkb}} ^talk 19:30, 11 May 2021 (UTC)

Notified: Wikipedia talk:Welcoming committee. {{u|Sdkb}} ^talk 19:32, 11 May 2021 (UTC)

Seem OK to me as long as we have a few options with no action buttons as we know they deter adults and are not accessible for all in mobile view.Moxy-

21:49, 11 May 2021 (UTC)

@Sdkb: {{Welcome-short}} is the one I tend to use - so I don't object to this change. I tend to dislike flashy welcome templates, they don't look genuine and often overwhelm more than help. Just text looks like a personal message and (I think) would encourage the user to reach out more often. Elli (talk | contribs) 04:10, 12 May 2021 (UTC)

I concur with these proposals. I've also, as mentioned, seen some other templates around I felt useful that aren't in Twinkle; I think there's a good case for {{W-informal}}, for instance. Vaticidalprophet 03:46, 13 May 2021 (UTC)

Support adding new templates, strong neutral on removing. While I personally don't like the big screen ones, if people like them, i don't see the big harm in keeping them in an as option. Also {{welcome-retro}} is one of the better welcoming templates, you can't just disagree with it without a reason. JackFromWisconsin (talk | contribs) 03:54, 13 May 2021 (UTC)
I linked over my opinion about the retro welcome to the discussion where its flaws were discussed in detail, so it's not at all "without a reason". But I'm not proposing here that we remove the retro welcome, so unless someone else wants to propose that, let's please not rehash that argument here. {{u|Sdkb}} ^talk 06:14, 13 May 2021 (UTC)

Seems good to me, neutral on removing templates per Jack. I'm partial to {{welcome-retro}} and {{welcome-short}} as the least overwhelming of the welcome templates, but if other people prefer the larger ones I don't see much harm in keeping them. ~ANM🐁 T·C 04:00, 13 May 2021 (UTC)

Implementation request made here, noting the rough consensus above. {{u|Sdkb}} ^talk 06:33, 24 May 2021 (UTC)

Warning template filter no longer gets focused

Until a little while ago, the filter textbox for warning templates got automatically focused when I clicked the dropdown ("{{uw-vandalism1}}: Vandalism"). It no longer does, and I want the old behavior back. Is this a bug or an intentional change? Nardog (talk) 09:15, 19 May 2021 (UTC)

@Nardog: you mean that the optional message textarea should get focused on selecting a warning template from the dropdown menu? I don't think that ever used to happen. – SD0001 (talk) 13:08, 22 May 2021 (UTC)

@SD0001: No, the single-line textbox that shows up when you open the dropdown list and filters the list as you type. IIRC it got focused as soon as it appeared. Nardog (talk) 05:28, 23 May 2021 (UTC)

@1234qwer1234qwer4: You thanked me for this thread—can you attest to what I'm saying? Nardog (talk) 05:31, 23 May 2021 (UTC)

I get it now. This appears to a regression, yes. I checked out some old versions of twinkle dating back as far as 6 months. But they have the same issue. So I'm guessing some change in MW or browsers may be responsible. – SD0001 (talk) 05:36, 23 May 2021 (UTC)

@SD0001: I think I know what's not working. It's this line. Try running $('.select2-container').prev().data('select2').dropdown.$search.focus() while the filter box is visible. It doesn't work. But $('.select2-container').prev().data('select2').dropdown.$search[0].focus() does. For some reason, the jQuery .focus() doesn't work (neither does .trigger('focus')), but the vanilla DOM .focus() does. This sounds like a problem with jQuery upstream, but calling the DOM method directly would be a handy quick fix. Nardog (talk) 07:15, 24 May 2021 (UTC)

@Nardog I see that this works. Can you open a PR? Thanks! – SD0001 (talk) 15:05, 24 May 2021 (UTC)

@SD0001: Done, ICYMI. Nardog (talk) 11:19, 26 May 2021 (UTC)

It seems the reason behind this has already been found, but I can attest this, yes. ~~~~
User:1234qwer1234qwer4 (talk) 08:16, 23 May 2021 (UTC)

Thanks! Glad I'm not alone. Well, no, actually, we don't know what the reason is yet. Nardog (talk) 07:15, 24 May 2021 (UTC)

Error

~~Whenever I try any of the revert options, it comes up with the following message: Error:Aborted by user. ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{reply to|Qwerfjkl}} on reply)~~ 20:16, 18 May 2021 (UTC)

Please give more context. Also what device/browser are you using? Does this occur on one page or all of them? There have been no changes to twinkle in over 3 months, so if it's the latter that would be surprising. – SD0001 (talk) 03:53, 19 May 2021 (UTC)

Nevermind, I've released its because of the dialouge box that appears whenever I try to revert (i.e. Enter comment here:). ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{reply to|Qwerfjkl}} on reply) 16:21, 19 May 2021 (UTC)

@SD0001: Please.could you fix this problem by not using a dialog box to enter the comment for reverting. ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{reply to|Qwerfjkl}} on reply) 17:19, 23 May 2021 (UTC)

How else would you enter the comment for reverting? Besides you haven't really described what the problem is. – SD0001 (talk) 17:26, 23 May 2021 (UTC)

@SD0001: For technical reasons, I cannot view alert dialogue boxes, and they are automatically closed. ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{reply to|Qwerfjkl}} on reply) 20:15, 24 May 2021 (UTC)

Well, there's a active PR by TheTVExpert that replaces the prompt with simple window. – SD0001 (talk) 17:55, 26 May 2021 (UTC)

You can configure for which kinds of rollback the dialog box should be shown in your Twinkle preferences. ~~~~
User:1234qwer1234qwer4 (talk) 20:32, 23 May 2021 (UTC)

Nomination for deletion of Template:Uw-thumb2

Template:Uw-thumb2 has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Schierbecker (talk) 02:04, 27 May 2021 (UTC)

Typo found

Hi, I found a typo in the gadget. When you use the belated welcome template through Twinkle, between "[...]your contributions" and "Though you seem[...]", there is no period. Could you please fix that? Thanks, Zai talk 18:54, 1 June 2021 (UTC)

It's not a typo in the gadget itself, but rather in Template:Welcome-belated, which has some scary template syntax which someone seasoned may want to fix. (The typo can be seen on User_talk:Tobiasi0.) – SD0001 (talk) 14:34, 2 June 2021 (UTC)

Ah, ok. Thanks. Zai talk 18:57, 2 June 2021 (UTC)

Sorry - I tested my edit without substing and the bug only appears if you subst. The issue is that {{safesubst:<noinclude/>#parserfunction:{{templatecall}}}}, when substed, interprets {{templatecall}} as a literal string not as a template transclusion. Not sure why, although it probably relates to the order that different steps of the parser happen in. Previously the code had also been buggy but in the opposite direction, so that a full stop always appeared even when it was supposed to be suppressed. I have now fixed it properly with some more scary syntax. Thanks both. User:GKFX^talk 20:58, 2 June 2021 (UTC)

Non-english welcomes do not subst

hi, apparently twinkle's non-english welcomes (with the exception of the basic one) do not subst, and thus also doesn't automatically insert the signature as well. could this be fixed? thanks, ◎ | melecie | t 01:02, 4 June 2021 (UTC)

MelecieDiancie, I'm guessing the issue may have to do with WT:Welcoming committee/Welcome templates#Consolidation of foreign welcomes. Pinging Mathglot. {{u|Sdkb}} ^talk 02:14, 4 June 2021 (UTC)

@MelecieDiancie:, Thank you for alerting us to this problem. I'm pretty ignorant about Twinkle, but Sdkb is undoubtedly correct that it has to do with a recent change I made to consolidate the templates.

The change involved the creation of a new template, {{welcome-foreign}}, and the replacement of all the old templates, such as, say, {{welcomeen-es}}, with a redirect to the new one. Without knowing any details, there could be a two-pronged approach:

Include {{welcome-foreign}} in Twinkle, and use that. Ultimately, this should be the permanent solution. Not sure if I need to do anything to facilitate that, or if it's all up to some Twinkle-install gnome, or what.
Fix the Redirects, or something in the template code so that the redirects work when substed, for any Twinkle users who prefer to continue using them.

Just looking at the latter, I have a pretty good idea what the problem is (missing subst protection before the invocation of {{welcome-foreign}} from the redirect), but I need a test case. Can you tell me what template you used, e.g., {{welcomeen-fr}} or whatever), and I'll fix that one, and ask you to try again (you can send it to my Talk page if you want; in fact, that's a good idea). I've already made one simple change to the Spanish one ({{welcomeen-es}}), so if that one works for you from Twinkle now, then I can fix all of the other ones in short order.

Oh, one other question: you said parenthetically, "with the exception of the basic one"; what did you mean by that? Mathglot (talk) 03:31, 4 June 2021 (UTC)

Okay, I think found your edit: it was this one at User talk:187.202.98.79, which you then fixed up on the next edit, right? By chance, Spanish is the one template redirect that I fixed as a trial; if you try that same one on my page or your sandbox from Twinkle, I think it will work. Lmk. Mathglot (talk) 04:28, 4 June 2021 (UTC)

After some testing in my sandbox, I did a test at User talk:Sandbox for user warnings; you can find it in rev. 1026772464‎. Not sure if that's the same thing you were trying to do, but you can try it again there, and if you tell me it's good, then I'll fix the other ones the same way. Mathglot (talk) 05:14, 4 June 2021 (UTC)

Eager to help on this, but waiting for feedback. Can any other Twinkle user respond? If the current status is, "{{welcomeen-es}} working, all others (e.g., {{welcomeen-fr}}, {{welcomeen-nl}}, etc.) broken", then I know what to do. Assuming User:Sdkb is following. Mathglot (talk) 18:24, 4 June 2021 (UTC)

Adding safesubst to the wrappers is exactly what I'd assume needs to be done to fix this. I don't think you need to wait for further feedback here, just boldly add it. {{u|Sdkb}} ^talk 18:38, 4 June 2021 (UTC)

Thanks; will do. Mathglot (talk) 22:17, 4 June 2021 (UTC)

Done Mathglot (talk) 22:26, 4 June 2021 (UTC)

TwinkleGlobal

I think it would be reasonable to mention TwinkleGlobal in the "Use on other wikis" section. I boldly added it, but was reverted by Cassiopeia. Is there a reason I am missing not to mention it? Elli (talk | contribs) 01:05, 2 June 2021 (UTC)

Seems reasonable. I don't think we need a consensus for adding edits like that. – SD0001 (talk) 14:41, 2 June 2021 (UTC)

This is the first time I've come across it, and it's intriguing. Is there a reason that we need a fork for Twinkle to function globally? I'd think it would be better just for global functionality to come standard. I'm wary of forks because they inevitably go out of date unless they have a mechanism to automatically sync with their source, I'm not sure if this does. Courtesy pinging Xiplus who might be able to speak to this. {{u|Sdkb}} ^talk 19:51, 3 June 2021 (UTC)

It doesn't always keep to update with twinkle-enwiki. However, if you report a bug or feature request. I will reply it ASAP. Xiplus (talk) 01:55, 4 June 2021 (UTC)

Hey @Cassiopeia, is it really in the spirit of Not a Bureaucracy to demand seven days of discussion before someone posts a link to a related project? Oiyarbepsy (talk) 23:54, 4 June 2021 (UTC)

I've reverted the user. They haven't even participated in this discussion yet, and we've had no objections. BilCat (talk) 00:32, 5 June 2021 (UTC)

@Oiyarbepsy and BilCat: Then dont we the editors should have the spirit and why in the hurry not let other editors to commands, if any? I dont see different it this is delayed for a few more days. Cassiopeia^(talk) 02:23, 5 June 2021 (UTC)

Because no one else has a problem with adding it now. BilCat (talk) 02:53, 5 June 2021 (UTC)

Edit conflict when listing many files at FfD

Special:Diff/1026979918 when adding File:SalemKeizerVolcanoesCapLogo.PNG to Wikipedia:Files for discussion/2021 June 5. Presumably it has something to do with my rapid-fire FfD nominations. This could probably be prevented by using section=new? — Alexis Jazz (talk or ping me) 10:40, 5 June 2021 (UTC)

Nomination for deletion of Template:Uw-accessdate2

Template:Uw-accessdate2 has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Schierbecker (talk) 07:17, 8 June 2021 (UTC)

Nomination for deletion of Template:Uw-paid4

Template:Uw-paid4 has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Schierbecker (talk) 08:34, 8 June 2021 (UTC)

Warning-type

Currently there are no types of warning that can be given specifically for edit-warring, would this perhaps be a feature we could get? Vif12vf/Tiberius (talk) 18:17, 13 June 2021 (UTC)

Vif12vf, we are a little confused here: what do you consider as {{uw-ew}} {{uw-3rr}} and {{uw-ewsoft}}? Elizium23 (talk) 18:21, 13 June 2021 (UTC)

The problem is that the three warnings above do not appear in the list of warnings that twinkle may insert for you, otherwise I would have used them long ago. Vif12vf/Tiberius (talk) 18:24, 13 June 2021 (UTC)

Each one of these is classified as "Single-issue warnings" which is a category that you can select in the Twinkle warning menu. If you do not know which category to choose, you may use "All warning templates" option and the convenient search box to find your appropriate warnings.

This does take a little getting used to, until you are accustomed to which warnings are found where, but we think the categories are a good thing to keep us organized and the lists to a tidy size. Elizium23 (talk) 18:26, 13 June 2021 (UTC)

Support for template:split

Hi. Thanks a lot for such a great tool. May I add a wish to the list? Support for template:split, please. Thanks! fgnievinski (talk) 23:53, 7 June 2021 (UTC)

[resolved] Bug with uncontroversial requested moves

I've tried to use Twinkle to file uncontroversial requested moves (select "XfD" in the Twinkle menu, choose "RM", and check the "Uncontroversial technical request" box) a couple of times recently, but each time I get the error Adding entry at WP:RM/TR: failed to find target spot for the entry. The browser console has an error with the same message and the stack trace update @ VM197:466. Rublov (talk) 15:32, 16 June 2021 (UTC)

Rublov I added back an html comment and then it worked for me. I think this is fixed now. --Trialpears (talk) 15:41, 16 June 2021 (UTC)

Trialpears, it appears so. Thanks! Rublov (talk) 15:46, 16 June 2021 (UTC)

Proposed change to Template:R from domain name

Hi, I'm posting a message here because there there is a proposed change to the template, including changing its recommended usage. The template has a banner telling me to notify this talk page. (I don't know much about Twinkle or its development, so if this message was unnecessary, just remove it.) ―Jochem van Hees (talk) 16:27, 16 June 2021 (UTC)

Missing rcat templates

Hi. There seem to be several important rcat templates missing from the pop-up tagging window. I just noticed that {{R from non-neutral name}} wasn't there. Is there a way to add it? I normally use the search bar to find the one I want, so clutter isn't a problem. Thanks. --Sangdeboeuf (talk) 22:47, 18 June 2021 (UTC)

Welcome signatures

Unresolved

Would it be possible to individually enable/disable custom welcome template signatures? ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{reply to|Qwerfjkl}} on reply) 21:11, 13 June 2021 (UTC)

Qwerfjkl It could definitely be done in the welcome templates themself if we want the standard signature to be used for all welcome messages (or add a parameter to switch between standard and regular signature). Should also be possible to make changes to twinkle but I think that would be more difficult and wouldn't affect welcomes not done through twinkle. --Trialpears (talk) 21:21, 13 June 2021 (UTC)

I suggest both, as I only welcome users through Twinkle, as this limits the welcome templates I can use (without subsequently removing the duplicate signature), but many users just use templates without Twinkle. ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{reply to|Qwerfjkl}} on reply) 21:26, 13 June 2021 (UTC)

Qwerfjkl After some rethinking I have created {{subst:Default signature}} (shortcut {{subst:Dsig}}) which generates the default signature upon substitution. Pings work like normal and the wikitext generated is identical to doing it normally. The only problem is that if you don't substitute it you can get major problems with the next user to edit the page signature being displayed instead. If there's enough interest in using the template on a large scale that could be fixed by me making a bot that deals with unsubsituted uses. For twinkle it would now be simple to replace the normal signature with this. Trialpears (talk) 22:40, 13 June 2021 (UTC) This message was signed using {{subst:dsig}}

(talk page stalker) @Trialpears: I believe AnomieBOT already handles automatic substitution through the {{always substitute}} template through Category:Wikipedia templates to be automatically substituted. Alternatively, {{Require substitution}} seems to create an error in the template unless it's substituted, which I think might be a bit more useful for this template's purposes. OhKayeSierra (talk) 23:04, 13 June 2021 (UTC)

OhKayeSierra If AnomieBOT substituted it you would get AnomieBOTs signature which isn't what we want. {{Require substitution}} sounds better though. After some more testing it seems like pings only work properly if you already use the default signature, I will see if something can be done to trick echo, but otherwise it probably won't be possible to get pings working with twinkle either. Perhaps not necessary for the current application of welcome messages though. Trialpears (talk) 23:17, 13 June 2021 (UTC)

If I remember correctly, AnomieBOT substitution is actually smart enough to handle this case. Pppery (talk) 17:41, 14 June 2021 (UTC)

Yep, it is * Pppery * _{it has begun...} 18:00, 14 June 2021 (UTC)

Anomie I think it was a while since I told you how great your bots are! This is amazing!!

I highly doubt it's possible to get pings working normally since there appears to be a check for the custom signature to be present in the edit. Clever things like generating a signature but then not including it is also not working. It is however possible to put the custom signature inside {{void}} so it doesn't display but still generates pings. I'm not sure what's preferable, polluting wikitext or having non-functional pings. --Trialpears (talk) 19:07, 14 June 2021 (UTC)

@OhKayeSierra @Pppery @Trialpears Could someone implement the individual signature enabling/disabling? ― Qwerfjkl | 𝕋𝔸𝕃𝕂 (please use {{reply to|Qwerfjkl}} on reply) 18:23, 19 June 2021 (UTC)

Nomination for deletion of Template:Book-prod

Template:Book-prod has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. --Trialpears (talk) 19:32, 19 June 2021 (UTC)

No edit summary explanation for revert?

I'm new to Twinkle and just tried my first vandalism revert. I am disappointed that the edit summary does not include an explanation for the revert. Please consider having the program drop [[wp:RVV|rv/v]] (rv/v) into edit summaries for vandalism reverts. Butwhatdoiknow (talk) 17:46, 21 June 2021 (UTC)

Butwhatdoiknow, please see #Feature request? Elizium23 (talk) 21:42, 21 June 2021 (UTC)

Thanks. Butwhatdoiknow (talk) 22:48, 21 June 2021 (UTC)

Feature request

When I use Twinkle to revert vandalism using the "Vandalism" button, it does not include "Vandalism" in the revert edit summary, as seen here. Would it be possible to automatically include "Vandalism" in the edit summary? I believe this would be very useful. Thanks. BilCat (talk) 18:27, 3 June 2021 (UTC)

BilCat, it actually used to work this way, and the devs decided that it was not conducive to civility to accuse editors of vandalism this way. It will suffice to leave an appropriate warning on the user talk page to this effect. Elizium23 (talk) 02:29, 5 June 2021 (UTC)

How does that make any sense? I'm going to warn the user for vandalism anyway, so I am already accusing them of vandalism. The way it is now, no one can tell why the user was reverted. How is that better? BilCat (talk) 02:41, 5 June 2021 (UTC)

BilCat, please see Wikipedia talk:Twinkle/Archive 32#Please remove the "vandalism" summary. for the discussion that led up to this. Elizium23 (talk) 02:47, 5 June 2021 (UTC)

Thanks, but I'm going to try RedWarn, as its developers aren't afraid of telling the truth in edit summaries. BilCat (talk) 02:51, 5 June 2021 (UTC)

All bot/script operators need to follow consensus. No sense in attributing that to fear. HighInBC ^{Need help? Just ask.} 02:55, 5 June 2021 (UTC)

How am I not following consensus? I made no changes to Twinkle, I simply made a request. BilCat (talk) 03:04, 5 June 2021 (UTC)

(edit conflict) Oh, the user who "complained" has been blocked for 8 years now, just 3 months after making the complaint. This is hilarious. LOL. BilCat (talk) 03:01, 5 June 2021 (UTC)

I ask the developers to either (a) reconsider their prior decision to leave what amounts to a blank edit summary (result being, as BilCat says above, "no one can tell why the user was reverted") - perhaps making the text be "see reverted user's talk page for reason" - or (b) rename the button from "Vandalism" to "revert without explanatory edit summary." Butwhatdoiknow (talk) 22:55, 21 June 2021 (UTC)

I would suggest an edit summary like "unconstructive" or something, which matches the warning of our initial vandal templates. Oiyarbepsy (talk) 00:32, 22 June 2021 (UTC)

Infinite Block Template to IP Address User

I placed indefinite block template on User talk:49.149.136.70. How can he be blocked because he is still editing even with the template on. — Preceding unsigned comment added by 124.106.226.215 (talk) 10:46, 24 June 2021 (UTC)

The template only displays a message about a block. The actual block is a separate function of the MediaWiki software, and can only be put in place by administrators. -- John of Reading (talk) 10:57, 24 June 2021 (UTC)

Protection template broke template display

I've just protected this template using TW. In this edit it added the {{pp-dispute}} icon, and that broke the display of the page. It seems to require a line break after the closing /noinclude to display properly. I've no idea where to go to fix that, but I'm sure someone here will know. Thanks, Justlettersandnumbers (talk) 10:27, 22 June 2021 (UTC)

In general for templates, a newline should not be added as that breaks the formatting. This template, however, begins with table syntax which only works when on a newline – so for this template a newline should be there. Twinkle can only do so much to guess whether to add a newline or not. I guess it's easy enough to realise the mistake and fix it manually for edge cases like these. – SD0001 (talk) 11:15, 24 June 2021 (UTC)

Breaking MOS:ORDER when grouping into multiple issues

This edit through Twinkle to add a maintenance template and group it into {{multiple issues}} caused the {{confused}} hatnote to be bumped below the warning templates, where it was previously (per MOS:ORDER) above them. --Lord Belbury (talk) 16:56, 25 June 2021 (UTC)

It's because {{confused}} (which is a redirect) is not there on the regex twinkle uses to find hatnote templates. Might be worth adding ... – SD0001 (talk) 07:15, 26 June 2021 (UTC)

Nomination for deletion of Template:AN3 report

Template:AN3 report has been nominated for deletion (by someone else, who didn't post a notification here). You are invited to comment on the discussion at the entry on the Templates for discussion page. * Pppery * _{it has begun...} 21:14, 28 June 2021 (UTC)

Twinkle added a redirect after the categories

I used the Tag feature with Twinkle to add the {{R with possibilities}} tag to a redirect that has a draft in review. I then was notified by User:Redrose64 that the tags should go before the categories. Here is the diff of what I did, or actually what Twinkle did at my command: https://wiki.riteme.site/w/index.php?title=Victoria_De_Angelis&type=revision&diff=1030612603&oldid=1025117024&diffmode=source

I created a GitHub account, but it isn't obvious to me what repository or project or whatever to use, without having it give me the training. I am, among other things, a retired software tester, and should be able to follow instructions on using a bug logging tool, so can someone tell me where to put the bug report? (Or can someone put it in for me and show me what they did?) Robert McClenon (talk) 20:50, 27 June 2021 (UTC)

@Robert McClenon: I can't do anything to address your substantive issue at this time, but I did update the GitHub link in the header box. Is it any clearer now? This, that and the other (talk) 08:06, 29 June 2021 (UTC)

Twinkle for KS Wikipedia

Hello, Can please someone help me in getting the twinkle at Ks Wikipedia. The translation will be done by me later. Please import it to KS Wikipedia. _signed,Iflaq ^(talk) 11:40, 1 July 2021 (UTC)

Automatically patrolling the "article" created when RfD'ing a page

When you tag a page with {{subst:rfd}}, it gets sent to the "article" queue of Special:NewPagesFeed. Fairly often, when I RfD something, I soon see it come up in the page curation log. For whatever reason, it's possible to self-patrol such "articles", so lately I've taken to patrolling them myself, but that requires going back after I'm redirected to the RfD page. Since I often file multi-redirect RfDs, that can add up to a lot of clicks. Which makes me wonder—for patrollers and sysops, could Twinkle give the option of automatically patrolling that left-behind "article"?

(One could probably make the case for a bot doing this for all users [after verifying that the RfD has actually been filed], but that's a separate matter.) -- Tamzin (she/they) | o toki tawa mi. 05:31, 29 June 2021 (UTC)

Tamzin, isn’t there already a bot which does similar things? One of DannyS712’s fleet? firefly ( t · c ) 07:21, 29 June 2021 (UTC)

Hmm. I've never had anything other than a redirect patrolled by a DannyS712 bot. And there's definitely times I've RfD'd a page without any human ever coming along to patrol the "article" before the RfD closed. -- Tamzin (she/they) | o toki tawa mi. 07:52, 29 June 2021 (UTC)

Tamzin, ahhh that may well be what I'm thinking of. I can certainly see a case for auto-patrolling such "articles", as there's no need for them to clog up the curation queue. Probably needs a discussion somewhere reasonably well-travelled (WT:RFD?)... firefly ( t · c ) 08:03, 29 June 2021 (UTC)

This can certainly be done and sounds like a good idea. I have opened 1426 on the issue tracker if someone wants to take a shot at the implementation. – SD0001 (talk) 17:09, 5 July 2021 (UTC)

Twinkle CSD setting

Hello, folks,

I was just informed that when an editor tags a page for CSD G7 ("Author requests deletion, or author blanked"), even if the editor checks the box to "Notify page creator", Twinkle doesn't post a notification on the talk page of the page creator. This can cause problems with new editors who do not realize when they blank a page that it will be deleted and because of Twinkle, they don't get a notification that their page will be or was deleted.

Can you change this so an editor can override this by checking the box that says "Notify page creator"? It would help to not have to then go post notifications or, worse, the new editor not knowing what has happened to their draft. Thank you. Liz ^{Read! Talk!} 03:50, 6 July 2021 (UTC)

@Liz: The first step would be to create a template message that might be posted in this case. Category:CSD warning templates has no message for G7. -- John of Reading (talk) 06:38, 6 July 2021 (UTC)

How to use twinkle

Can you pls tell me how to use twinkle while recent changes patrolling Thank you. (This is me Jarvis (talk) 07:03, 9 July 2021 (UTC))

Semi-protected edit request on 10 July 2021

This edit request to Wikipedia:Twinkle has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

My suggested changes are: Adding the steps on how to use it with the User Warning Sandbox (UWSB). 2600:1702:41C0:4F70:A9AD:E16F:F0BD:C9F8 (talk) 21:28, 10 July 2021 (UTC)

Not done for now: please establish a consensus for this alteration before using the {{edit semi-protected}} template. Warning User talk:Sandbox for user warnings isn't any different than warning any other user. OhKayeSierra (talk) 23:38, 10 July 2021 (UTC)

Nomination for deletion of Template:Pp-move-indef

Template:Pp-move-indef has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. ProcrastinatingReader (talk) 12:06, 16 July 2021 (UTC)

IP ranges not supported

I can't report IPv4 ranges to WP:AIV, despite vandalism frequently spanning multiple IPs. I don't know if this is true for IPv6 or any of the other WP:APV systems. –LaundryPizza03 (d c̄) 15:50, 18 July 2021 (UTC)

Twinkle's code actually supports reporting IP ranges to AIV. However, this will only work when/if phab:T206954 is implemented in mediawiki. – SD0001 (talk) 04:19, 23 July 2021 (UTC)

WP:RPP

(Urgent) Hi, Twinkle fails to add page protection requests. Received message "Wikipedia:Twinkle/Fixing RPP". Kindly fix the issue. Thank you. Cassiopeia^(talk) 02:40, 31 July 2021 (UTC)

Twinkle Tag category

Isnt template: {{Self reference cleanup}} worthy to be included in Twinkle's section: ′Add or remove article maintenance tags′ ? --Gpkp [u • t • c] 07:19, 31 July 2021 (UTC)

RPP bug

Request for page protection is being put in the wrong place. Don't know what's changed, but my latest request for page protection was placed in the wrong spot [1] (below the comment "DO NOT PUT NEW REQUESTS HERE. GO TO THE SUBPAGE ABOVE" and had to be moved by Cyberbot I [2]. There are multiple similar moves of Twinkle protection requests. Meters (talk) 07:26, 17 July 2021 (UTC)

Hmm... looks like someone recently added that comment line to the protection request page and Twinkle doesn't know about it. Meters (talk) 07:31, 17 July 2021 (UTC)

And I am at least 50% sure some requests are being lost. In this edit, Cyberbot I "moved" two requests, but they appear to have just been deleted. Firefangledfeathers (talk) 06:13, 18 July 2021 (UTC)

Cc @Cyberpower678: ↑ – SD0001 (talk) 13:19, 18 July 2021 (UTC)

Same here. Notified the owner. –LaundryPizza03 (d c̄) 00:20, 19 July 2021 (UTC)

I still don't know what happened to the Armenian page request in my diff, but the Neom request in LaundryPizza03's diff was moved to /Increase (by bot), declined, and archived (by bot). Firefangledfeathers (talk) 03:56, 22 July 2021 (UTC)

I am also unable to do any RPP via twinkle. It is producing the error Wikipedia:Twinkle/Fixing RPP. ––FormalDude ^talk (please notify me {{U|FormalDude}} on reply) 05:07, 29 July 2021 (UTC)

Same here. Can someone please look into this soon? Thanks! BilCat (talk) 07:29, 29 July 2021 (UTC)

Very annoying timing. I've got trouble with an LTV who keeps page jumping and this bug is making it incredibly difficult to request page protection. REDMAN 2019 (talk) 10:51, 29 July 2021 (UTC)

Same here. The error message says I have to contact the Twinkle Gods. Twinkle Gods, hear our prayers! –Austronesier (talk) 12:31, 29 July 2021 (UTC)

@Austronesier: Our Twinkle God, which art in the Internets, hallowed be thy work. Thy free time come, thy update be done, [...]. In all seriousness, the temporary stopgap measure of a bot moving the Twinkle comments until Twinkle can be updated to comply with the new format is far less annoying than having to now do it manually... Cheers, RandomCanadian (talk / contribs) 18:49, 30 July 2021 (UTC)

As I was saying, and as you can see from the recent edits by Special:Contributions/Hind_ji, the current solution is not user-friendly for those of us who aren't familiar with this... RandomCanadian (talk / contribs) 20:16, 30 July 2021 (UTC)

Same problem, can't request rpp via Twinkle. ZaniGiovanni (talk) 12:08, 30 July 2021 (UTC)

@ZaniGiovanni, RandomCanadian, Austronesier, Redman 2019, BilCat, and FormalDude:, I just made this edit to Twinkle. This should temporarily get it back to a working state while the devs work on a proper fix. Can anyone confirm? —CYBERPOWER (Around) 10:03, 31 July 2021 (UTC)

Cyberpower678, Yes it works!! Thank you very much. ––𝗙𝗼𝗿𝗺𝗮𝗹𝗗𝘂𝗱𝗲^(talk) 10:06, 31 July 2021 (UTC)

Cyberpower678, thanks also. I didn't use RPP until early this morning, so I had forgotten about the issue until now. BilCat (talk) 20:59, 9 August 2021 (UTC)

Watching tagged pages

In Special:MyPage/twinkleoptions.js, I have set watchTaggedPages to yes, but whenever I tag a file with {{opaque}}, it is only watched for one month. Shouldn't it be watched indefinitely? --Stefan2 (talk) 21:06, 15 August 2021 (UTC)

Bug report: Collapse top and collapse bottom in XfD log

If an XfD nomination includes the {{collapse top}}/{{collapse bottom}} templates, it will not display properly in the XfD log because the latter needs to go on its own line, but doing so will also break the list. (Example: 2 entries are misplaced inside the collapsible at the bottom.) –LaundryPizza03 (d c̄) 07:33, 18 August 2021 (UTC)

Stuck "Saving page" when CSD tagging

When Twinkle is CSD tagging for me, it keeps getting stuck on the "Adding entry to userspace log: Saving page..." step. Is User:Jeff G./CSD log too long? If so, how do you suggest I archive or truncate it? — Jeff G. ツ 16:23, 9 August 2021 (UTC)

@Jeff G. 100kb doesn't sound big enough to actually cause issues. Can you check if the console has any errors (see Wikipedia:JSERROR point 6)? – SD0001 (talk) 16:38, 9 August 2021 (UTC)

@SD0001: If only I had access to the console. Puffin Browser Pro (v4.7.3) on my iPad 3 seems not to have one. The process works in Chrome there and on my Win10 laptop. — Jeff G. ツ 21:58, 15 August 2021 (UTC)

@SD0001: I tried it again today and it worked (although it took 18 seconds on the 2nd attempt). — Jeff G. ツ 12:46, 24 August 2021 (UTC)

Template-protected edit request on 24 August 2021

This edit request to Wikipedia:Twinkle/Preferences has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Fix the short description per WP:SDFORMAT (remove 'the' and '.'). Qwerfjkl talk 12:08, 24 August 2021 (UTC)

Done firefly ( t · c ) 12:17, 24 August 2021 (UTC)

@Firefly Hi, you don't seem to have removed 'the' (it's been converted to lowercase instead). Can you fix this? ― Qwerfjkl talk 17:53, 24 August 2021 (UTC)

Qwerfjkl, woops - done. firefly ( t · c ) 18:50, 24 August 2021 (UTC)

Twinkle requests leading to the wrong place

This has been going on for a few months now. When making a request for page protection, reporting users, etc. the edit gets reverted and is moved to a subpage as you can see here. The invincible message even says that you should put a request on the subpage and not the main page (""). Could you guys please fix this? Cheers - Wretchskull (talk) 08:15, 5 September 2021 (UTC)

This was already fixed in the github repo by TheTVExpert (1430). But the change hasn't been deployed on-wiki. – SD0001 (talk) 11:52, 5 September 2021 (UTC)

Changes to uw-minor template

There is a discussion on changes to the wording of {{uw-minor}} at Wikipedia talk:Template index/User talk namespace#Template:Uw-minor rewrite. SpinningSpark 07:59, 8 September 2021 (UTC)

New message

Hello,

I use Twinkle many times a day to delete pages, mostly draft pages, and today, I started getting a message, in bright red, on the box that appears after a page is deleted that states:

"Deleting talk page: Cannot delete the page because it no longer exists"

It's not unusual for draft pages not to have talk pages and this notation hasn't appeared before. It's not helpful information so it would be nice if this feature could be removed. Admins don't need to be informed about the absence of a talk page when when they delete a page. Liz ^{Read! Talk!} 20:14, 2 September 2021 (UTC)

I found I can avoid these annoying red messages if I uncheck "Also delete talk page" in the deletion box which, in my set-up, was checked by default. Just an extra step in the deletion process but it can add up when you are deleting a lot of pages. I'd prefer for there not to be notices to tell me what is NOT there. Liz ^{Read! Talk!} 22:23, 2 September 2021 (UTC)

Fixed in 1440. – SD0001 (talk) 19:04, 4 September 2021 (UTC)

Git Sync

@MusikAnimal: Can you sync the wiki version to the latest GitHub version? The last sync was around March. The above fix, TheTVExpert's RPP upgrade, and a number of other bug fixes have been merged. Some i18n-related morebits changes also occurred back in April/May, but everything has been tested as of now – have checked the basic functionality of all modules. – SD0001 (talk) 20:07, 4 September 2021 (UTC)

@SD0001 Sure thing. Can you refresh my memory on where the docs are for the sync.pl script? I'm getting errors when I try to use it. If all else fails I can sync the files manually. — MusikAnimal ^talk 21:33, 7 September 2021 (UTC)

@MusikAnimal: https://github.com/wikimedia-gadgets/twinkle/blob/master/DEVELOPER.md#synchronization-using-syncpl – SD0001 (talk) 04:19, 8 September 2021 (UTC)

Done There were a lot of unsynced changes, but so far I'm not seeing any issues. — MusikAnimal ^talk 16:09, 8 September 2021 (UTC)

September 2021 Twinkle update

Per the discussion above, the Twinkle gadget pages have been updated (for the first time since March).

Please report any and all issues or abnormal behaviour here as they could be due to the recent changes.

Also, Twinkle isn't being actively maintained as of the last few months. Some policy changes such as the deprecation of BOOKPROD are yet to be reflected in Twinkle. If you want to help out with maintenance, see the contributing guidelines – we have a new dev-script to make testing changes easier. – SD0001 (talk) 04:12, 9 September 2021 (UTC)

Allow adding "reason" parameter to db-g2

Template {{db-g2}} supports parameter |reason=, so it would be nice if Twinkle allowed adding it via text field, as it already does for WP:G6, for example. —⁠andrybak (talk) 13:38, 11 September 2021 (UTC)

Lots of templates have lots of parameters, but Twinkle only supports the commonly used ones. A reason param isn't usually needed for test pages; so having this even as an optional field isn't really a good idea IMO – as that would make it look as if entering a reason is recommended. One can of course edit the page manually to add the param. – SD0001 (talk) 07:04, 13 September 2021 (UTC)

I need help

I h Supreme baby (talk) 10:40, 16 September 2021 (UTC)

Supreme baby This page is for discussing the operation of the Twinkle feature only, and is not for general help seeking. You may ask for help at the Teahouse. 331dot (talk) 11:08, 16 September 2021 (UTC)

Add the option of type=disabled to TfD

Add the option of type=disabled to TfD which is supported by the template, see Template:Template for discussion#Disabled. Gonnym (talk) 09:49, 21 September 2021 (UTC)

@Gonnym As of now, pretty much the only way to have changes done in twinkle is to file a PR. – SD0001 (talk) 13:17, 21 September 2021 (UTC)

Ok, will do. Thanks! Gonnym (talk) 13:36, 21 September 2021 (UTC)

@SD0001, I think we should at least set the automatic archiving threshold here higher in that case. ~~~~
User:1234qwer1234qwer4 (talk) 17:54, 23 September 2021 (UTC)

Twinkle

So, I use Twinkle throughout the whole day for my work and I got to one page where I put in a custom reason for deletion which Twinkle reject for unknown reasons. But the message I got back was:

*Building deletion summary: Unable to generate summary from deletion template

*Asking for reason: you didn't give one. I don't know... what with admins and their apathetic antics... I give up...

I thought I knew Twinkle pretty well at this point but I didn't know it had a sense of humor and moments of despair. Thanks for the laugh! Liz ^{Read! Talk!} 23:50, 27 September 2021 (UTC)

Twinkle has a few Easter eggs sprinkled here and there. The one I've known the longest is when you try to add a Talkback template to your own talk page; you will receive a message saying "Is it really so bad that you're talking back to yourself?", which earned a chuckle from me. —k6ka 🍁 (Talk · Contributions) 13:29, 29 September 2021 (UTC)

The code for the Easter egg you mentioned can be found here. —k6ka 🍁 (Talk · Contributions) 13:38, 29 September 2021 (UTC)

Bug: preview of CfD/S has trailing brackets

Steps to reproduce:

Go to Category:Writer by nationality navigational boxes
Click on TW → XFD
Select "Deletion discussion venue: CfD/S (Categories for speedy renaming)"
Click "Preview" below the "Reason" input box.
Observe the preview

Actual result: preview ends with (UTC)[]. Here, "(UTC)" is part of the timestamp in the signature.

Expected result: preview ends with (UTC). —⁠andrybak (talk) 15:28, 2 October 2021 (UTC)

The issue is occurring with all previews throughout Twinkle, not just for CfD/S. I think it's because of DiscussionTools adding the brackets though it doesn't add the reply button that was supposed to come in between. – SD0001 (talk) 16:25, 2 October 2021 (UTC)

Reported upstream at phab:T292345. – SD0001 (talk) 16:53, 2 October 2021 (UTC)

"prod" doesn't work when {{deleted on Commons}} is present

Twinkle will not mark files containing {{deleted on Commons}} for proposed deletion because the file is "already tagged with a deletion template." {{deleted on Commons}} only indicates that the file has been deleted on Commons and has nothing to do with status of the local file. I'm pretty sure this is unintentional. Ixfd64 (talk) 20:02, 2 October 2021 (UTC)

This can be fixed by adjusting the regex here. – SD0001 (talk) 10:40, 7 October 2021 (UTC)

Twinkle did not group tags

Hello, in Special:Diff/1046045935, the tags were not grouped despite "Group inside {{multiple issues}}" being enabled. ~~~~
User:1234qwer1234qwer4 (talk) 17:51, 23 September 2021 (UTC)

Filed as 1449 on the issue-tracker. – SD0001 (talk) 03:30, 8 October 2021 (UTC)

A near-total overhaul of the tag module was done for the twinkle-core/twinkle-enwiki project, which I think would prevent such issues. But of course, due to reasons that are more political than technical, we're still using the legacy twinkle ... – SD0001 (talk) 05:07, 8 October 2021 (UTC)

bnWP Twinkle error

bnWP twinkle gadget stopped working. It says ‘Failed to retrieve edit token.’ Not just bnwiki, same on simple. Does anyone have any idea why the problem is happening? bnWP TW source —MdsShakil (talk) 14:13, 9 October 2021 (UTC)

You are using a very old version of morebits (bn:মিডিয়াউইকি:Gadget-morebits.js). The old method of retrieving edit tokens used there was recently removed in MediaWiki. – SD0001 (talk) 15:06, 9 October 2021 (UTC)

Token handling in enwiki version of morebits was updated last year. You can see the diff here and try applying it to your version. – SD0001 (talk) 15:10, 9 October 2021 (UTC)

morebits was updated by Jayprakash12345, now it's working but we plan to upgrade overall. Thanks for your help

—MdsShakil (talk) 13:59, 10 October 2021 (UTC)

Using {{Edit protected}} for protected page and {{Edit request}} for requested edits

Hi. I'm here to propose that a change should be made in MediaWiki:Gadget-twinklexfd.js. I think that the Twinkle gadget should use {{Edit protected}} for protected page and {{Edit request}} for requested edits.
I'm a partial blocked user from mainspace. I use Twinkle gadget for CSD and AfD. For the block, I can't make edits on mainspace. So when I use CSD and XfD option, Twinkle adds a short message and a {{Edit protected}} template on the nominated page's talk page. I've been also warned for doing this.
I hope the correction should be made. Thanks. || Tajwar.thesuperman ^💬 18:08, 9 October 2021 (UTC)

@Tajwar.thesuperman: Your requested edits are not COI edits either. So, Twinkle should instead use {{Edit partially-blocked}} for AfD nominations by users partially blocked from the Article namespace or a single page they would want to send to AfD anyway. GeoffreyT2000 (talk) 18:51, 9 October 2021 (UTC)

@GeoffreyT2000 Yeah. Please correct this. Thanks. || Tajwar.thesuperman ^💬 18:54, 9 October 2021 (UTC)

@Tajwar.thesuperman: So then,

{{subst:Xfd edit protected|page=Nominated page|discussion=Discussion page|tag=<nowiki>{{subst:afd|help=off}}</nowiki>|type=partially-blocked|reason=I am partially blocked}}

(using the two new parameters I have added) should be used for partially blocked users making AfD nominations using Twinkle. GeoffreyT2000 (talk) 19:55, 9 October 2021 (UTC)

@GeoffreyT2000: Well. Do I need to add it somewhere else? Or it will add automatically? || Tajwar.thesuperman ^💬 04:34, 10 October 2021 (UTC)

@Tajwar.thesuperman: I have made a Github request at https://github.com/wikimedia-gadgets/twinkle/issues/1452. GeoffreyT2000 (talk) 14:19, 10 October 2021 (UTC)

Requested edit to a module

Instructions at Template:Requested move require you to be notified as a courtesy of any changes to the template (or module), and there is presently an edit request at Template talk:Requested move#Badly worded default for reason= parameter that may need your input and monitoring. Best to all! P.I. Ellsworth - ed. ^put'r there 03:39, 14 October 2021 (UTC)

Request to undelete my article and verify it

Hi, I'm Itswajidshaikh00, and I would like to request the undeletion of this draft deleted under CSD G13. Please restore the page so that I can make edits to it. Thank you. https://wiki.riteme.site/wiki/Draft_talk:Wajid_shaikh Itswajidshaikh00 (talk) 11:18, 22 November 2021 (UTC)

@Itswajidshaikh00. Hey there. I recommend posting your inquiry at WP:REFUND. –Novem Linguae (talk) 11:25, 22 November 2021 (UTC)

Why (and how) is Twinkle posting from my bot account?

I have used twinkle to flag two pages for speedy deletion, and both times the edits came from my bot account. While my bot account had recently accessed the API via a tool running on toolforge, and I had made an edit from my bot account using a private browsing window, that private browsing window had since been closed, and the browser window I was using at the time said I was logged in as "Ahecht" at the top. How is Twinkle able to post as something other than the currently logged in user? --Ahecht (TALK
PAGE) 17:29, 12 November 2021 (UTC)

Twinkle can only post as the currently logged-in user, but that is not necessarily the one whose username you see at the top. It can change if you log out and log in as the bot in another tab, for instance. Twinkle would never edit under IP addresses, as the API requests use the assert=user check, but currently the assertuser= check is not set, that would ensure that the logged-in user hasn't changed.
DId you see the "edit token expired, fetching new token..." message?
Also, when the page reloaded after action complete, which was the account signed in? – SD0001 (talk) 18:42, 12 November 2021 (UTC)

I did get a "fetching new token" message, but when the page reloaded I was still logged into my Ahecht account. Pages I edited manually after using Twinkle were also using the correct account, but then when I used Twinkle again it posted from the bot account. I think somehow the API was logged in separately from the browser itself. I opened the console and did a new mw.Api().postWithToken( 'csrf', {action: "logout"} ) and logged back in, which seems to have fixed it. --Ahecht (TALK
PAGE) 22:08, 12 November 2021 (UTC)

Spam blacklist

I unknowingly included a link to a site on the Spam blacklist in an AfD nomination using Twinkle. As a result, no nomination page was created, but other actions, such as adding the nomination to today's log and notifying the page creator, were performed anyway. In order to redo the nomination, I had to revert those actions first to prevent duplication, and of course type my nomination statement again. Not terrible, but certainly annoying. Could Twinkle not be made to not perform any action at all if one action is not allowed? Lennart97 (talk) 13:37, 15 November 2021 (UTC)

@Lennart97: This could potentially be fixed. But did you have to type the nomination again, or did you get the Your deletion rationale is provided below, which you can copy and paste into a new XFD dialog if you wish to try again message? – SD0001 (talk) 14:30, 15 November 2021 (UTC)

If that's what normally happens, then most likely it happened here too without me noticing, thinking it was part of a long unimportant error message, although I can't be sure... sorry! :) Lennart97 (talk) 14:51, 15 November 2021 (UTC)

Twinkle not leaving CSD notices on user pages when CSDing redirects for some criteria

When using Twinkle in my browser, CSD notices are not being given to relevant users on their talkpages when I nominate a redirect for speedy deletion. This occurs even when the "Notify page creator if possible" is checked to notify the creating user. I have the page creation script enabled as well. — Mikehawk10 (talk) 23:54, 19 October 2021 (UTC)

@Mikehawk10: Which criteria, specifically? – SD0001 (talk) 08:23, 20 November 2021 (UTC)

By default, CSD notices are not sent for R2, R3 and R4 criteria. See WP:TWPREFS#speedy where you'll find that those checkboxes are unchecked. These preference options take precedence over the "Notify page creator if possible" option in the CSD screen. – SD0001 (talk) 08:29, 20 November 2021 (UTC)

Request to remove the SPI notification checkbox

Tracked in github.com
Issue #1473
Resolved

Notifications are rarely advisable at SPI, and the SPI team has quietly discouraged them for some time. There are rare times when someone's participation is needed, usually if there's strong evidence but a possible AGF explanation, but that should be a carefully studied decision. In practice, when that does happen, it's usually done with a custom message rather than a templated message (example by me, example by a CU). Despite the "use your judgment" tooltip above the notification checkbox, many users (including very experienced ones) still check it by default, presumably on the premise that if it's required for AN, ANI, etc., it's also advisable for SPI. But at SPI, unlike any of these other venues, users should only be filing if good-faith explanations have been exhausted; there is not the notion of working with the subject of the filing to improve, as there is at other venues. Most filings are against repeat offenders who, if notified, often troll the comments and harass the clerks and admins.

Again, there may be some cases where a notification is indicated, but by removing the checkbox we'd force people to put some more thought into that decision to notify. Special:Search/~"An editor has opened an investigation into" shows countless cases of experienced users notifying users who have been blocked or banned for years, suggesting that people tick this box out of habit rather than with due consideration to the circumstances. Both times that I've brought this up with a user, they've told me they thought they were supposed to notify. (Across ~300 filings I've clerked so far, I believe I've notified in three, all with custom notifications, and I think that's about standard for clerks, CUs, and admins who regularly patrol SPI.) -- Tamzin^{[cetacean needed]} (she/they) 17:51, 19 November 2021 (UTC)

Cross-posted to the clerks' noticeboard. -- Tamzin^{[cetacean needed]} (she/they) 17:51, 19 November 2021 (UTC)

Yeah, I agree with this assessment. --TheSandDoctor ^Talk 17:58, 19 November 2021 (UTC)
Sounds good to me. I'm all for simplifying user interfaces, especially when it's been shown that an offered option mostly leads to incorrect use. -- RoySmith (talk) 18:07, 19 November 2021 (UTC)
Also notified: WT:SPI. – SD0001 (talk) 11:48, 22 November 2021 (UTC)
Agreed. I believe the last thing we want to do is to give the offender a heads-up that they're being investigated. Aloha27 talk 12:21, 22 November 2021 (UTC)
Support removal due to mostly incorrect use. If people desire to use it they could always place it manually. Dreamy Jazz ^{talk to me | my contributions} 16:13, 22 November 2021 (UTC)
I've used it very productively in one case. However, once it's used incorrectly, the notification is the toothpaste that won't go back in the tube. Support removal. Cabayi (talk) 19:43, 22 November 2021 (UTC)
I wrote a patch for this that was accepted today. Should be all set. This functionality will be removed in the next release of Twinkle. –Novem Linguae (talk) 21:13, 24 November 2021 (UTC)

redirect which may not be needed in uw-joke1

in the uw-joke1 template, the "certain degree of freedom" section links to a redirect, I'm not sure if that's particularly needed. Example on a user talk page. It links to this redirect, which is an alternative capitalisation of the actual title of the page it's linking to, and I'm not sure if its necessary. Not really a big issue, just something I noticed.

DirkJandeGeer (щи) 12:24, 30 November 2021 (UTC)

@DirkJandeGeer: Since you've mentioned it, I've edited {{uw-joke1}} to bypass two redirects. This isn't really a Twinkle issue; Twinkle just places the template on a user talk page, and doesn't care what the template actually says. -- John of Reading (talk) 12:43, 30 November 2021 (UTC)

Many thanks, I was trying to figure out how to edit it but I saw a notification saying I should post something on this talk page first, now I know for next time.

Thanks for the help, DirkJandeGeer (щи) 13:38, 30 November 2021 (UTC)

Discussion at Wikipedia talk:Template index/User talk namespace § Customizing warning headers for Twinkle

You are invited to join the discussion at Wikipedia talk:Template index/User talk namespace § Customizing warning headers for Twinkle. {{u|Sdkb}} ^talk 20:57, 30 November 2021 (UTC)

Retooling the Vandalism revert button

Hi, I have a suggetion for changing the "Vandalism" revert button to something else. At present, the "Vandalism" button reverts a series of edits, has no option for adding an edit summary, does not automatically give an explanation in the summary, but does open the user talk page for adding warnings. (The automatic summary "Vandalism" was removed several years ago.)

I'd like to suggest that this be changed to add a edit summary, but not open the user's talk page. This would basically be a straight rollback, and could be called "Rollback No Warning" or something else. This would be useful in cases where a rollback is desired, but warning the offending user is unnecessary for whatever reason. Thanks. BilCat (talk) 20:43, 30 November 2021 (UTC)

@BilCat Adding an edit summary but not opening the user's talk page is what the "Undo" button is for. --Ahecht (TALK
PAGE) 21:28, 30 November 2021 (UTC)

Not if there's more than one edit. That's my point. BilCat (talk) 21:31, 30 November 2021 (UTC)

@BilCat Undo works just fine for more than one edit. For example, try the undo button at http://wiki.riteme.site/w/index.php?title=Wikipedia%3ASandbox&type=revision&diff=1058001342&oldid=1058001285 (assuming no one else has written to the sandbox in the meantime). --Ahecht (TALK
PAGE) 22:04, 30 November 2021 (UTC)

They have. BilCat (talk) 22:08, 30 November 2021 (UTC)

Isn't there already a 'Rollback' button for this purpose? When I use it, I get a warning first, then a prompt to enter an edit summary. I am then taken to the user's talk page, but this is a setting that can be changed in Twinkle prefs. Firefangledfeathers 22:13, 30 November 2021 (UTC)

Yes, there is, but I am taken to the user's talk page. In most cases that's what I want to happen, but not in all cases. BilCat (talk) 22:19, 30 November 2021 (UTC)

Looks like that's something that you could change in Twinkle preferences. I appreciate the Vandalism button. When I use it, I know my edit will be marked minor with no additional edit summary, which I know communicates a reversion of vandalism. And I like to add an appropriate template warning to the user talk. Firefangledfeathers 22:24, 30 November 2021 (UTC)

It's an either/or option, so I'd like a separate button for each. I'd also prefer that it add "Vandalism" automatically, but I'm in the minority on that one. (I don't use it incorrectly, but apparently other users did, and so Vandalism was removed from the summary.) BilCat (talk) 22:31, 30 November 2021 (UTC)

G10 notice should link to the page, no?

See Special:Diff/1058050271. I'm taking this here because both the template and Twinkle would need to be changed, I imagine. Enterprisey (talk!) 06:34, 1 December 2021 (UTC)

I always assumed that was intentional, since the name of the article is often an attack itself. Meters (talk) 06:49, 1 December 2021 (UTC)

Yes, it's intentional as attack page titles are often libellous. In fact, the code has a lot of hacky special cases like this just to prevent G10 page names from leaking anywhere – even in the edit summary and the CSD log. – SD0001 (talk) 12:01, 1 December 2021 (UTC)

TwinkleMobile

Hello everyone, I'm from viwiki. Yesterday, I made a script which enables Twinkle on mobile view (Minerva skin). If you want to use this script, please see how to install it on this page: User:P.T.Đ/TwinkleMobile. I don't know English, so I can only write basic sentences. Thanks. P.T.Đ (talk) 19:57, 28 November 2021 (UTC)

TwinkleMobile portlet link in AMC mode
TwinkleMobile portlet link not in AMC mode
TwinkleMobile dialog
Twinkle dialog on mobile
TwinkleMobile dialog when there are no tasks

Thanks for the note @P.T.Đ. This looks excellent. Ideally, we should integrate minerva support into the gadget. I'll open a github issue for that. Sidenote: you should probably use the Toolforge CDN instead of cdnjs for loading an external library to comply with the wikimedia privacy policy. – SD0001 (talk) 15:58, 1 December 2021 (UTC)

Thanks @SD0001. I used Toolforge CDN for external library. I made this because some viwiki users want to use Twinkle on mobile. If Twinkle is updated for using on mobile (and the gadget supports mobile view, loads scripts with ResourceLoader), I will disable this script. P.T.Đ (talk) 22:44, 2 December 2021 (UTC)

Opened #1483 on the issue tracker. – SD0001 (talk) 17:09, 5 December 2021 (UTC)

Missing template in warning series

Tracked in github.com
Issue #1350
Resolved

For some reason the {{uw-attempt4im}} template (only warning for deliberately triggering the edit filter) isn't included under the "Only warning" menu under Twinkle's warn module. I've been using the template via a manual edit substitution, but this should be added to the module. Taking Out The Trash (talk) 16:37, 8 December 2021 (UTC)

I patched that one here a week or two ago. It will be fixed in the next release. –Novem Linguae (talk) 17:15, 8 December 2021 (UTC)

Can't use Twinkle for edit warring reports

I've tried twice across different days already, but every time I fill out the edit warring report nothing happens when I press accept, the window just stays open as if I never clicked it and no report gets placed. Megaman en m (talk) 06:44, 8 December 2021 (UTC)

@Megaman en m. I was unable to reproduce this on test wiki. Can you give additional information? 1) The exact data you were typing into the form / exactly how you filled out the form. You can screenshot if you want. 2) After Twinkle hangs, open your browser's developer tools window (F12 hotkey on Google Chrome desktop), click on Console, and provide a screenshot. This is where Twinkle error messages are likely to be. Example. Thanks. –Novem Linguae (talk) 07:02, 8 December 2021 (UTC)

Here it is, it also prompts me if I want to send it even though I haven't given a warning to them yet, to which I say yes, then this happens. (There actually is a warning given by someone else, but it doesn't register that.)--Megaman en m (talk) 09:27, 8 December 2021 (UTC)

Did I provide enough information?--Megaman en m (talk) 03:52, 9 December 2021 (UTC)

@Megaman en m. Hey there, thanks for the details. 1) Can you also give the user's name? 2) Can you give the URL of the warning diff? 3) Had you clicked the button yet in the above screenshot? I was expecting to see a Twinkle error but I don't see it, makes me wonder if you had clicked submit yet. Thanks. –Novem Linguae (talk) 05:06, 10 December 2021 (UTC)

Username: Buffalo8

https://wiki.riteme.site/w/index.php?title=Intelligence_quotient&diff=prev&oldid=1059043427

https://wiki.riteme.site/w/index.php?title=Intelligence_quotient&diff=prev&oldid=1059052718

https://wiki.riteme.site/w/index.php?title=Intelligence_quotient&diff=prev&oldid=1059065076

https://wiki.riteme.site/w/index.php?title=Intelligence_quotient&diff=prev&oldid=1059229146

Also I would like to point out that right now I can't even load the intelligence quotient page when trying to report him with Twinkle, even after trying all the spelling and capitalization differences (It just says "none found"). And yes, I did click the submit query button back then, several times across several days, it just hangs there like nothing happened. Pretty sure I pressed it as well when I made that screenshot. So unless there's a hidden loading time that lasts up to a minute, it's just not working for me. I can however use the vandalism report tool on Twinkle without issue.--Megaman en m (talk) 08:11, 10 December 2021 (UTC)

Alright, confirmed, I was able to reproduce it. For some reason, for the combination of AIV->AN3, username Buffalo8, page Intelligence quotient, the API query is not returning any revisions, so the "user's reverts" section in the modal window is empty. @SD0001, at first glance, does anything look wrong with this API query that is used in twinklearv.js -> getAN3Entries() that would cause it not to return any revisions? Direct link: https://wiki.riteme.site/w/api.php?action=query&format=json&prop=revisions&rvprop=sha1%7Cids%7Ctimestamp%7Cparsedcomment%7Ccomment&rvlimit=500&rvend=2021-12-08T09:25:38.390Z&rvuser=Buffalo8&indexpageids=true&titles=Intelligence%20quotient Thanks. –Novem Linguae (talk) 09:41, 10 December 2021 (UTC)

@Novem Linguae looks like rvend is being set incorrectly. – SD0001 (talk) 12:47, 10 December 2021 (UTC)

Megaman en m. Alright, so after more investigating... the reason that the revisions wouldn't show up after a few days is that Twinkle only grabs revisions from within the last 48 hours. This is probably by design, to prevent stale AN3 reports. I hacked in some code to bypass that and then I attempted to warn the subject using the exact same info you filled into the form, and it worked for me. So I'm unable to reproduce. I undid my warnings, but if you want I suppose you could restore them and edit your name in place of mine. I'm out of ideas, sorry we couldn't get you a more satisfactory resolution. –Novem Linguae (talk) 07:27, 11 December 2021 (UTC)

Changing TFD behaviour

Tracked in github.com
Issue #1486
Resolved

Per this discussion which has seen no dissent, could we please have Twinkle place new TFD nominations as a new section at the bottom of the appropriate TFD log page? Primefac (talk) 21:27, 11 December 2021 (UTC)

Hey @Primefac. I wrote a patch for this just now. If approved, it will be included in the next Twinkle release. –Novem Linguae (talk) 00:43, 12 December 2021 (UTC)

Thanks! Primefac (talk) 09:13, 12 December 2021 (UTC)

Twinkle's delete function

Tracked in github.com
Issue #1382

Hey, I have so many comments about Twinkle which I use throughout the day. But right now, I'd like to ask why, when admins use Twinkle to delete pages, it will delete the article, the article talk page, any redirects to the article, but not the talk page of the redirects to the article.

Luckily, we have bots that pick up mistakes like this and deliver them in reports at some point during the day/night but it would be simpler if Twinkle would just delete the redirect talk pages while it's deleting all of the other related pages. Thanks. Liz ^{Read! Talk!} 06:36, 13 December 2021 (UTC)

Hey @Liz. I think there's an open ticket for this one from April. It just needs code. I'll see if I can carve out some time to code it. –Novem Linguae (talk) 06:45, 13 December 2021 (UTC)

Patch submitted for the batchdelete module. [3][4] –Novem Linguae (talk) 12:33, 13 December 2021 (UTC)

Yes, I thought I probably had brought it up before. Is it because there isn't a direct link from the redirect talk page to the article that is being deleted like there is from the talk page and the redirect page? Thanks for working on it. Liz ^{Read! Talk!} 18:19, 14 December 2021 (UTC)

CSD U3

Tracked in github.com
Issue #1490

Twinkle's CSD tagging function on user pages still lists an option for criterion WP:U3, which was deprecated in July 2021. –LaundryPizza03 (d c̄) 21:15, 14 December 2021 (UTC)

@LaundryPizza03. Patch submitted. Thanks for reporting. –Novem Linguae (talk) 02:48, 15 December 2021 (UTC)

2015th nomination

Tracked in github.com
Issue #1493

I was a bit bemused when I came across Wikipedia:Articles for deletion/The Basement (2015th nomination). Apparently, Twinkle noticed the AfD at Wikipedia:Articles for deletion/The Basement (2014) (which was about an article at The Basement (2014)) and figured it was the 2014th nomination of The Basement. When The Basement was nominated for deletion yesterday, Twinkle incremented the count by one, and we thus have the 2015th nomination. Not sure what can or should be done about this: I just wanted to point it out in case someone more technically adept than me has any ideas. Extraordinary Writ (talk) 01:25, 17 December 2021 (UTC)

Sounds like a bug. Ill take a stab at writing a patch when I'm at a computer. –Novem Linguae (talk) 02:55, 17 December 2021 (UTC)

Got it. Patch submitted. Please see link above. –Novem Linguae (talk) 15:46, 17 December 2021 (UTC)

Thank you! Extraordinary Writ (talk) 18:28, 17 December 2021 (UTC)

Welcome messages added above "Talk header"

Tracked in github.com
Issue #1494

Hi, Liz pointed out on an issue on my talk page that amounts basically to if a talk page has a {{Talk header}} at the top already then the welcome message added by Twinkle (assuming you have "Place welcomes above existing content on user talk pages" set) is added above this. I can see the point that this is maybe not the best logical order, although I'm personally also happy just seeing the welcome and {{Talk header}} as one big header.

The reason this happens a lot is that the AFCH tool, that AfC uses, automatically adds {{Talk header}} to blank talk pages when posting the review notifications (accepts, decline or reject). Then if I, or others, then add a welcome, which I do to both give help and reduce the bite of any decline/reject, it is placed above the "header".

So the question is do others think that if Twinkle is set to "Place welcomes above existing content on user talk pages" is should still place after any existing {{Talk header}} (and possibly other templates), and if yes then would it be possible to change the order? Cheers KylieTastic (talk) 13:41, 18 December 2021 (UTC)

Hey KylieTastic. Patch submitted. Thanks for reporting. –Novem Linguae (talk) 16:42, 18 December 2021 (UTC)

Cheers Novem Linguae KylieTastic (talk) 16:45, 18 December 2021 (UTC)

How to add Turkish Welcome Greeting?

I noticed that the following templates exist but are not in the Twinkle. Additionally I noticed that Oriya (Odia) and Romanian were in Twinkle but not listed in WP:WELCOME-FOREIGN which I've changed just now.

Arabic: {{subst:welcome-foreign|lang=ar}}
Farsi:: {{subst:welcome-foreign|lang=fa}}
Hausa: {{subst:welcome-foreign|lang=ha}}
Hindi: {{subst:welcome-foreign|lang=hi}}
Turkish: {{subst:welcome-foreign|lang=tr}}
Urdu: {{subst:welcome-foreign|lang=ur}}
Vietnamese: {{subst:welcome-foreign|lang=vi}}

I tried to find appropriate place to change this, but figured asking would be the best. Thanks! ~ 🦝 Shushugah (he/him • talk) 16:06, 20 December 2021 (UTC)

You can add custom welcome templates from WP:TWPREF#welcome "Custom welcome templates to display". – SD0001 (talk) 18:17, 20 December 2021 (UTC)

Redirect format

Tracked in github.com
Issue #1497

Hi! A minor issue I noticed: Twinkle tags redirects in the format:

#REDIRECT [[Example]]
{{Redirect category shell|
{{R to example}}
}}

I think there should be another newline (i.e. two in total) after
#REDIRECT [[Example]] i.e.

#REDIRECT [[Example]]

{{Redirect category shell|
{{R to example}}
}}

― Qwerfjkl talk 12:39, 24 December 2021 (UTC)

@Qwerfjkl. Patch submitted. Thanks for reporting. Happy holidays. –Novem Linguae (talk) 13:39, 24 December 2021 (UTC)

Add Template:Thanks to IP welcome messages

Tracked in github.com
Issue #1498

I don't often use {{Welcome-anon}}, because it seems kinda silly to expect that someone might be interested in delving into all our resources when they haven't yet expressed enough interest to even register an account. I think {{Thanks}} is much better suited for communicating with IPs who make constructive contributions, so I'd like to suggest we add it to the Twinkle IP welcome messages. Thoughts? {{u|Sdkb}} ^talk 19:43, 29 December 2021 (UTC)

Notified: Wikipedia talk:Welcoming committee. {{u|Sdkb}} ^talk 19:44, 29 December 2021 (UTC)

Sdkb. Patched submitted, see tracking box for link. Happy holidays. –Novem Linguae (talk) 02:53, 30 December 2021 (UTC)

@Novem Linguae, much thanks, and happy holidays to you, too! Cheers, {{u|Sdkb}} ^talk 03:01, 30 December 2021 (UTC)

PROD reasons cannot be recovered for reuse if the article has deletion tags on the talk page

If you try to PROD an article, that has deletion tags on the talk page, then not only does the Script stops but it also does not allow the recovery of the PROD reason that was typed. The scripts says "Looking up page creator: Done, found Arslanmulk Checking talk page for prior nominations: Previous XfD template found on talk page, aborting procedure".

The logical next step in such case is XFD, but the reason generally remains the same. The Script should show the user whatever he typed and allow him to reuse the PROD reasoning that was typed before. Venkat TL (talk) 13:47, 1 January 2022 (UTC)

Thanks for the feature request. I've noticed this too and I filed a very similar feature request here in March 2021. Appears to have consensus, just needs code. –Novem Linguae (talk) 19:22, 1 January 2022 (UTC)

Failed to notify user talkpage of CSD

Hello. I speedy nominated User:Queenbesties/sandbox/Queen Besties as CSD G11. While it tagged the userpage properly, Twinkle failed to send a notification to the user about the CSD with Template:Db-spamuser-notice. Twinkle gave me the following error:

Failed to save edit:

[4a2c0caa-6364-4aa4-933e-30ff2f4d257d] Caught exception of type Wikimedia\Rdbms\DBQueryError

Because of this, I manually used the CSD warning template on the user's talkpage. I should note the talkpage was originally not created before my CSD notification. This is the first time I ran into this issue of not being able to notify an user on their talkpage with Twinkle for a speedy deletion. Does anyone know why this is the case? Thanks! --MrLinkinPark333 (talk) 21:56, 1 January 2022 (UTC)

That's an error originating from MediaWiki itself which Twinkle can't do anything about. I have been encountering a similar DBQueryError in one of my bot tasks for the past 2 weeks, for which I filed phab:T298010 but unfortunately no one seems interested in looking into it. – SD0001 (talk) 05:54, 2 January 2022 (UTC)

@SD0001: Thanks for letting me know. Now I know if I run into this issue again, it's not Twinkle. Thanks! --MrLinkinPark333 (talk) 17:57, 2 January 2022 (UTC)

Astrology in Delsort

Hi, Praemonitus was suggesting me to include Astrology in the deletion sorting. Due to reasons unknown to me, Astrology does not show up in the Twinkle option when nominating articles on AfD. The manual instructions are here: Wikipedia:WikiProject Deletion sorting/Astrology.

To reproduce the problem, Goto Urmila Devi Dasi or any existing article and click XfD on Twinkle. In the AfD window, Choose deletion sorting categories. Type Astro. You will only find Astronomy and not Astrology. (Problem)

I dont understand why Astrology is missing there, when it exists. Is it just me or are you seeing the same? May be some sort of update is needed. Venkat TL (talk) 19:20, 5 January 2022 (UTC)

@Venkat TL: You can add it to Wikipedia:WikiProject Deletion sorting/Computer-readable.json which is set to be used in the next release of Twinkle. TheTVExpert (talk) 19:51, 5 January 2022 (UTC)

@TheTVExpert thanks for the link. Added now. Venkat TL (talk) 19:58, 5 January 2022 (UTC)

Wrong user notified about PROD

Can you please check why this admin was notified instead of the actual page creator. [5] Venkat TL (talk) 19:17, 5 January 2022 (UTC)

@Venkat TL: This was because the admin was technically the creator of the first non-redirect version of the article which is who gets notified. TheTVExpert (talk) 20:15, 5 January 2022 (UTC)

@TheTVExpert ok. Thank you for checking and explaining. Venkat TL (talk) 20:24, 5 January 2022 (UTC)

Feature request

Hi, is it possible to introduce the Advanced Reporting & Vetting (ARV) options to the "compare revisions" page, when we are comparing a certain user's edits to those made before them? This will help auto-detect page oldids and make reporting easier. Thanks! ---CX Zoom(^he/_him) (^{let's talk}|_contribs) 13:18, 13 January 2022 (UTC)

Rollback IPv6 edits only compares part of address to determine they are consecutive

I was trying to roll back a single change using the AGF option: the diff is here (subsequent edits have been made, which changes the repro but not significantly). It was made by 2600:1700:4200:2B40:10D:75C6:25CD:86BE. But Twinkle thought there had been two changes in a row, as the previous one was by 2600:1700:4200:2B40:909B:D433:7089:DEE1. I don't know how v6 addresses are constructed; is it really possible to suggest they were the same user? David Brooks (talk) 03:40, 15 January 2022 (UTC)

And I just realized I goofed: the top 4 edits also worked as a repro (the 3 most recent IPs the same and the 4th different) until I went and made my own edit on top. But I'm sure you get the point. David Brooks (talk) 03:54, 15 January 2022 (UTC)

This is intentional; see User:TonyBallioni/Just_block_the_/64 for context. Writ Keeper ⚇♔ 04:20, 15 January 2022 (UTC)

Understood, thanks. Since in the example the two edits were fundamentally different and 4 months apart, I guess I'll be alert to this fortunately rare case, and revert the old-fashioned way. Asking Twinkle to set a maximum timestamp gap would presumably cause difficulties in how to define the maximum. David Brooks (talk) 15:56, 15 January 2022 (UTC)

Actually, now I've slept on it, consider this a feature request: if an edit from the same IP is more than delta-T before its successor, stop looking for "same user" edits. Either it's probably a different individual, or the previous edit may well be benign and unlikely to have been spotted by now anyway. After all, the usual revertible behaviors are usually batched within a few minute. I'm open to the setting of delta-T (a week should be plenty?) and I realize it may be difficult to find a live repro. David Brooks (talk) 16:32, 16 January 2022 (UTC)

Twinkle on Igbo Wikipedia

Hi! I had wanted to activate twinkle on Igbo Wikipedia but found out it was not listed. What do I do? Olugold (talk) 21:49, 18 January 2022 (UTC)

Add Template:Deprod-reprod to TW?

Tracked in github.com
Issue #1502

Saw this talk page post, figured I should bring the suggestion here. Signed, IAm Chaos 01:33, 19 January 2022 (UTC)

This one was harder than expected becuase we'd probably also want to add code that makes the "linked page" field required for only this template. I opened a ticket. –Novem Linguae (talk) 15:25, 20 January 2022 (UTC)

Thanks! Signed, IAm Chaos

U3

Tracked in github.com
Issue #1490

The speedy deletion criterion U3 was repealed back in July 2021, but you can still nominate pages for deletion with this criterion using Twinkle. See this for what happens when you do this. —GMX^{^{(on the go!)}} 19:37, 27 January 2022 (UTC)

@PorkchopGMX: This is set to be removed in the next release of Twinkle. TheTVExpert (talk) 19:49, 27 January 2022 (UTC)

Dropdown menu broken?

When I logged on to Wikipedia today, I noticed that the dropdown menu for Twinkle seems to be broken, and all the list's items are splayed out in their own section (see screenshot). Anyway to fix this? —Tenryuu 🐲 ( 💬 • 📝 ) 21:41, 3 February 2022 (UTC)

Came here to report the same, on Edge and Chrome. David Brooks (talk) 23:32, 3 February 2022 (UTC)

An interface admin edited the code today without going through code review. Perhaps it's related. Diff. –Novem Linguae (talk) 23:46, 3 February 2022 (UTC)

@Novem Linguae: This seems to be it. See here. @Tenryuu and DavidBrooks: are you using vector–2022? TheTVExpert (talk) 00:08, 4 February 2022 (UTC)

@TheTVExpert: I am. David Brooks (talk) 00:21, 4 February 2022 (UTC)

@TheTVExpert: Yeah, I'm using the new Vector skin. If it's an accidental code mishap I'm sure it'll be fixed soon. —Tenryuu 🐲 ( 💬 • 📝 ) 00:38, 4 February 2022 (UTC)

It still works for me on Vector legacy ~~Firefox 96.0.2. The interface change looks harmless. Perhaps Edge and Chrome (which share a codebase) have changed.~~ Certes (talk) 00:24, 4 February 2022 (UTC)

I've reverted Special:Diff/1069711330 for now as Twinkle apparently does not (yet) support the Vector 2022. I wasn't even aware until today that we're now treating the new Vector as a different skin. This will surely break many scripts and gadgets. — MusikAnimal ^talk 01:04, 4 February 2022 (UTC)

Confirmed the "More" dropdown is working again for me. David Brooks (talk) 01:27, 4 February 2022 (UTC)

The "More" dropdown menu is fixed. Thanks! —Tenryuu 🐲 ( 💬 • 📝 ) 01:45, 4 February 2022 (UTC)

Hi User:MusikAnimal. Sorry about that... was trying to avoid this breakage :)

The new Vector skin has a different key but apart from that it should work identical, so I think my change had the right idea but failed to update all the references to vector so they also check vector-2022.

I don't know much about Twinkle though so would be great if someone else who is more knowledgeable could make the next attempt:) Jdlrobson (talk) 02:14, 4 February 2022 (UTC)

Note Twinkle was working earlier today but got broken while I fixed https://phabricator.wikimedia.org/T300814

Previously we were hacking Vector 2022 so that mw.config.get('skin') returned 'vector' to avoid this. Jdlrobson (talk) 02:16, 4 February 2022 (UTC)

User:MusikAnimal I've managed to get Twinkle loading in a dropdown menu on Farsi Wikipedia for both Vector's with several edits. It also needed a change to MediaWiki:Gadgets-definition (https://fa.wikipedia.org/w/index.php?title=%D9%85%D8%AF%DB%8C%D8%A7%D9%88%DB%8C%DA%A9%DB%8C%3AGadgets-definition&type=revision&diff=34059182&oldid=33972671)

I'd rather an admin here made the appropriate changes to English Wikipedia next time round as I've not had the most luck this week :)

Sorry again for the disruption. No harm intended. Jdlrobson (talk) 02:40, 4 February 2022 (UTC)

@Jdlrobson Had this been announced in meta:Tech/News we would have fixed it already (speaking for Twinkle and MoreMenu specifically, since there are close eyes on those gadgets). The code also needs to be updated in the respective remote repositories, which again we would have done in preparation had we known this change was coming. But no worries, we of course know you mean no harm! :) I'll get to work on updating Twinkle on GitHub now and deploy the changes in shortly thereafter. Thanks, — MusikAnimal ^talk 02:51, 4 February 2022 (UTC)

This week didn't go to plan. :( My original hope was that we could avoid the hassle of gadget developers having to edit their gadgets by hacking the skin to pretend it was normal vector but as T300814#7674241 points out that wasn't my best idea and was a little ill thought so I had to scramble to find some kind of solution to fix live edit preview which was apparently breaking a lot of editors workflows.

Thanks for working on the fixes with such short notice. It's appreciated. Jdlrobson (talk) 03:08, 4 February 2022 (UTC)

No problem, and sorry if I was at all harsh in my wording. I understand now that this wasn't a planned change so you wouldn't have known to warn us via Tech News. Everything should be working now in Vector 2022. Best, — MusikAnimal ^talk 04:55, 4 February 2022 (UTC)

Release soon?

Hey @SD0001. Happy holidays. The Twinkle gadget is 24 commits behind master. Any interest in doing a release soon? How's that work, do we just need to ping MusikAnimal to run the release script? –Novem Linguae (talk) 14:59, 22 December 2021 (UTC)

@Novem Linguae Yes, let's get 1460 merged first, then you can ping MusikAnimal for running the deploy script after running some sanity tests of the modules or code paths that have been changed, ideally in a different browser than the one you normally use. Almost all changes have been tested by at least two people so hopefully there won't be any bugs. Testing with IE 11 may also be a good idea, not because I think people still use IE, but because if it works in IE it will pretty well work in all other browsers. Happy holidays! – SD0001 (talk) 18:41, 22 December 2021 (UTC)

That does not appear to be moving.... should everything else continue to be held up for this? KylieTastic (talk) 12:17, 12 January 2022 (UTC)

I'm having a bit of trouble motivating myself to install IE11, test a bunch of stuff I already tested, and finish the mentioned patch. Rather than waiting for my time and motivation to increase, might be better to just release what we have, and deal with any bugs as they're reported. I defer to SD0001 though. –Novem Linguae (talk) 03:11, 27 January 2022 (UTC)

@SD0001 @Novem Linguae I see there are a lot of unsynced changes. Preferably nothing should be merged in the repo unless it's safe to be deployed, I think... but anyway I'm glad I ran the script with the --dry flag first and noticed this discussion. I'm going to manually sync the more urgent changes for #Dropdown menu broken? now. Just ping me when you feel everything is safe to deploy. Best, — MusikAnimal ^talk 04:50, 4 February 2022 (UTC)

@MusikAnimal Everything is safe to deploy. We haven't had the time to do sanity testing, but I merged all of Novem's changes after testing, and they've tested it as well. So I don't think there's a chance anything significant is broken. Minor bugs if any can be taken up as and when reported. – SD0001 (talk) 05:43, 4 February 2022 (UTC)

Okay, with your word,

Done! — MusikAnimal ^talk 06:01, 4 February 2022 (UTC)

Problem with unlinking backlinks

Tracked in github.com
Issue #1503

Hello, Twinkle folks,

I use Twinkle to do most page deletions and I've found problems recently when I try to remove backlinks. For example, I just deleted a PROD, Cyber Seduction: His Secret Life, and after deleting the page I tried to remove the backlinks and just got big, red error messages and "Unlinking backlinks: Done (0/31 actions completed successfully)". And when I checked, "What links here", I found over 30 pages that still had links to the deleted page that were not removed.

I mainly use the Unlink feature with PRODs because the majority of my page deletions are draft pages and they usually have no backlinks. This problem happened to me a few days ago so I handled it manually and I thought it was just a fluke so to run into it again right now makes me wonder if there is some sort of bug. I deleted some PRODs earlier today and had no problem so it's a sporadic problem. Thanks. Liz ^{Read! Talk!} 01:41, 25 January 2022 (UTC)

Howdy @Liz. After some testing, I was able to replicate this on test wiki, and I've determined this is because there is a colon in the name of the page. It thinks that "Cyber Seduction:" is the namespace, so it is trying to delete links to "His Secret Life". It's not a super easy fix, I'll have to give this some thought, so I created a bug report. Thanks for reporting. –Novem Linguae (talk) 03:27, 25 January 2022 (UTC)

Alright, I thought of a way to fix this. Patch submitted for approval. –Novem Linguae (talk) 04:24, 25 January 2022 (UTC)

A belated thank you for figuring this out, Novem Linguae. Such a simple explanation but one that would never have occurred to me. I guess that is why the problem only happened occasionally. Thanks for submitting the patch. Liz ^{Read! Talk!} 00:47, 5 February 2022 (UTC)

Proposed change to the sock list in Template:SPI report

Tracked in github.com
Issue #1509

Please see Template talk:SPI report § Proposed change to sock list. While not per se a breaking change in terms of how it would affect Twinkle, the proposal comes coupled with a proposed change to Twinkle's usage of the template. (If there's consensus to implement the template change, I can file the PR for the Twinkle side.) -- Tamzin^{[cetacean needed]} (she/they) 04:49, 5 February 2022 (UTC)

Button style proposal

I think the buttons that appear on the screen will be more beautiful this way.
File: MediaWiki:Gadget-morebits.css

body .ui-dialog.morebits-dialog .ui-dialog-buttonpane button {
	float: none;
	margin: .2em 0 -.1em;
	color: #fff;
    background-color: #36c;
    border-color: #36c;
    padding: 6px;
    line-height: 1;
    border-style: solid;
    position: relative;
    font-weight: bold;
    text-decoration: none;
    text-align: center;
    cursor: pointer;
    display: inline-block;
    box-sizing: border-box;
    vertical-align: middle;
    font-family: inherit;
    font-size: inherit;
    white-space: nowrap;
    user-select: none;
    border-radius: 3px;
}

𝗩𝗶𝗸𝗶𝗽𝗼𝗹𝗶𝗺𝗲𝗿 ℣ 16:12, 5 February 2022 (UTC)

Twinkle placing new WP:TFD nominations at wrong location on daily page

See here. Twinkle is placing new nominations for WP:TFD at the bottom of the daily page instead of at the top of the page. I've noticed that WikiCleanerMan has been doing their due diligence to fix the nominations' locations on the page(s) (but I'd imagine they'd rather have this issue fixed so they don't have to fix the nominations' locations anymore.) Steel1943 (talk) 01:55, 5 February 2022 (UTC)

@Steel1943. Hey there. It's intentional, please see Wikipedia talk:Twinkle/Archive 45#Changing TFD behaviour. I'd recommend letting it do its thing, and if there's a big backlash we can revert it after trying it out for a bit. –Novem Linguae (talk) 02:59, 5 February 2022 (UTC)

Thanks for the link to that discussion. ~~However, the change goes against the instructions at WP:TFDHOWTO, specifically the part listed at "II: List the template at Tfd.:~~

~~Add this text at the top, just below the -->:~~
~~For deletion: {{subst:Tfd2|template name|text=Why you think the template should be deleted. ~~~~}}~~

~~For merging: {{subst:Tfm2|template name|other template's name|text=Why you think the templates should be merged. ~~~~}}~~

~~If the template has had previous Tfds...~~

@Novem Linguae: Since the change in Twinkle goes against the long-standing instructions at TFD, this change in Twinkle needs to be reverted unless there is consensus for the change at TFD as a whole. In other words, I find the change in Twinkle controversial (I suppose I'm the "backlash") and am requesting it be reverted; I saw the WP:SILENCE claim in the discussion chain, but I didn't edit in all of 2021, so I would not have had a chance to dispute it. (Also, pinging Primefac as the initiator of the discussion that was linked.) Steel1943 (talk) 03:50, 5 February 2022 (UTC)

For the record, the discussion I found regarding this can be found here. (The discussion has since been archived.) ~~And I'll be fair on this; I cannot support this change unless Anomie's bot starts transcluding the daily subpages in ascending order instead of descending order.~~ Steel1943 (talk) 03:55, 5 February 2022 (UTC)

@Anomie:, feel free to disregard what I said above; apparently, I didn't understand how the WP:TFD page is laid out. Also, to everyone else: Please disregard the rest of this as I'll work on making the changes to accommodate the changes. Steel1943 (talk) 04:00, 5 February 2022 (UTC)

Per the linked discussion, I have performed the following series of edits to update the instructions at WP:TFD.~~, as well as the order which the last 7 daily subpages are listed in order to conform with the discussion.~~ (Pinging WikiCleanerMan to make them aware of the discussion and the changes.) Steel1943 (talk) 04:12, 5 February 2022 (UTC)
I undid my changes to the daily subpage listings after realizing there was no reason/consensus to do that per the discussion to make the changes, as well as the precedence set with doing "listing at bottom of daily subpage, have days listed in descending order" at WP:FFD. Steel1943 (talk) 04:19, 5 February 2022 (UTC)
The reason for this change is explained here. Top-posting means that sometimes clicking on a section edit link results in editing the wrong section. It happens to me multiple times per week. – Jonesey95 (talk) 06:29, 5 February 2022 (UTC)
@Jonesey95: For what it's worth, I saw and mentioned that discussion earlier in this section; rereading it resulted in me updating the TFD instructions since the instructions were still directing nominators to post new nominations at the top of the daily subpage. Steel1943 (talk) 11:09, 5 February 2022 (UTC)
I notice that a surprisingly small number of TFDs are actually via Twinkle. Looking at the history of today's log, 12 out of 15 are manual adds, 2 out of 15 are via Twinkle, and 1 out of 15 are relists via the XFD Closer script. There's also the TFD documentation, and AnomieBot also pulls in code from somewhere with a comment to put new entries at top/bottom. Someone already updated the documentation and AnomieBot to say "bottom". Anyway, to fully implement this change, we will also need to put in a patch request for XFD closer, and also train users to do manual adds at the bottom (perhaps via moving their TFDs when they put them in the wrong place and pinging them). I await more responses before making a decision on reversion. At this point I feel that getting 3 people objecting on this page would be enough to revert and then have an RFC about it. I'd also like to hear from Primefac. –Novem Linguae (talk) 14:35, 5 February 2022 (UTC)
Yeah, apologies about the TFD page, I thought I had updated everything when the change was made. We should be encouraging manual editors to start using Twinkle (if only from the "less hassle" angle) but it's also possible they might not even know about the change. I'll see about finding an IntAdmin to update XFDC. Primefac (talk) 14:38, 5 February 2022 (UTC)
Those non-Twinkle stats are surprising to me. It's such a time-saver and greatly limits errors. – Jonesey95 (talk) 14:55, 5 February 2022 (UTC)
- For the record, I don't object anymore; the inconsistencies were my main issue, but after the instruction update I performed, everything (that I can think of) seems to be consistent now. Steel1943 (talk) 15:08, 5 February 2022 (UTC)

Steel1943, you don't need to ping three times, I'm aware of the discussion from your first ping. The same issue happened on the February 5, 2022 Tfd. I just think this is more of a glitch that happens on occasion. I don't use twinkle as for me it's just better to do it manually, which, yes can be a pain, but it makes a better effort when it comes to my editing habits and avoids glitches. The only glitch when doing it manually would be an edit conflict but it's easy to fix when you start over to avoid any hiccups later or at that moment. --WikiCleanerMan (talk) 16:47, 5 February 2022 (UTC)

(I pinged you whenever there was a change in the way the conversation was going, and I was not aware if you had read the conversation when I pinged each time, so I didn't want to leave you out of where the duscussion was.) Steel1943 (talk) 17:05, 5 February 2022 (UTC)

What the conversation above is stating that per discussion, putting the discussions at the top of the page is not current procedure; current procedure is to put the discussions at the bottom of the page. Steel1943 (talk) 17:21, 5 February 2022 (UTC)

The Tfd's for February 7, 2022, are now being placed going from top to bottom. This is going to make things harder because the way and like it has been for so many other regulars at Tfd is to go from bottom to top where the first nomination goes first on top, then the second nomination goes right above it. This needs to be reverted. --WikiCleanerMan (talk) 20:51, 7 February 2022 (UTC)

Survey

Moved to Wikipedia talk:Templates for discussion § RfC: Should new nominations be placed at top or bottom of daily subpage?

Discussion at Wikipedia talk:Manual of Style/Layout § Template:Improve categories

You are invited to join the discussion at Wikipedia talk:Manual of Style/Layout § Template:Improve categories. –Novem Linguae (talk) 01:19, 18 February 2022 (UTC)

Welcome-menu template missing from the latest iteration of the drop-down welcome menu

Tracked in github.com
Issue #1513

{{Welcome-menu}} is missing from yesterday's change in the drop-down welcome menu. Can we please add it back in? The welcome menus are one of the major things that I use Twinkle for, & I almost exclusively use the Welcome-menu option for newly registered editors. It is painful having to drop in {{subst:WelcomeMenu}} manually! Peaceray (talk) 20:01, 4 February 2022 (UTC)

@Peaceray: It was removed per this discussion. You can add it back in your Twinkle preferences. TheTVExpert (talk) 20:20, 4 February 2022 (UTC)

I was wondering why the welcome messages I use every day were missing. Liz ^{Read! Talk!} 00:44, 5 February 2022 (UTC)

I'm happy to add it back in if people use it. Any others to add back besides welcome-menu? –Novem Linguae (talk) 00:51, 5 February 2022 (UTC)

I use the welcome variants when it seems appropriate, usually when I can AGF. Happy to use Preferences though. David Brooks (talk) 00:57, 5 February 2022 (UTC)

(ec)That would be awesome if you could add back a few. All I know about the one I use is that it states it has 20 links to policy pages. It looked like it was going to kind of be a pain in the ass to go through all of the templates to locate and manually add back the templates I frequently use.

I have also wanted to add to the Twinkle drop down warning messages the one about Wikipedia not being a social media site...I see editors posting that one on the talk pages of a lot of young, new editors. I run into a lot of new editors creating "profile pages" so it really fits their situation. But I guess my request doesn't help much if I don't give you a link to the template I'm referring to. I'll tray to track that down. There are a helluva lot of templates though! Liz ^{Read! Talk!} 00:59, 5 February 2022 (UTC)

I see the one I always use is called {{Welcome-graphical}} but some other editors didn't like it at all which I guess is why it was removed. I found it useful as it provided a balance of policy pages and "How to get started" links. Liz ^{Read! Talk!} 01:03, 5 February 2022 (UTC)

Alright, welcome-menu and welcome-graphical. Works for me. Any others? Should we revert all the ones that were removed, or just focus on welcome-menu and welcome-graphical? –Novem Linguae (talk) 01:36, 5 February 2022 (UTC)

Patch submitted. –Novem Linguae (talk) 01:40, 18 February 2022 (UTC)

Userbox was listed at TFD instead of MFD

Tracked in github.com
Issue #1516

I nominated a userbox for deletion. Userboxes got to MFD not TFD. Twinkle placed it at TFD (See this). Surprisingly, a similar userbox which I nominated shortly after was properly listed at MFD (see this). -- Whpq (talk) 15:40, 18 February 2022 (UTC)

Twinkle detects userboxes by looking for Template:User in the title. Luckily I think most userboxes follow this convention. For the few that don't, you can still manually select MFD when nominating. Anyway, I have created a feature request in case anyone wants to work on this. I think programatically, we'd have to pull the wikicode of the page and look for {{Userbox. –Novem Linguae (talk) 17:57, 18 February 2022 (UTC)

Ok/ That's good to know. -- Whpq (talk) 18:46, 18 February 2022 (UTC)

Preview / Optional message

Tracked in github.com
Issue #1517

I find Twinkle's preview and optional message very useful when warning editors. Would it be even better to present the proposed edit in a wikitext editor so that it can be customised? I think this just means pre-loading the "optional message" (renamed as something like "suggested message") with the boilerplate wikitext, and adding it to the user talk page as-is rather than prepending the boilerplate. Certes (talk) 23:10, 18 February 2022 (UTC)

What kind of customizations are you thinking? I'm having trouble of thinking of customizations that wouldn't already be covered by the optional message field. Feel free to share a diff. –Novem Linguae (talk) 23:17, 18 February 2022 (UTC)

A few examples from commonly used templates:

one or more of your recent contributions to Example have been undone – I might want to link to the contribution(s) or at least reword "one or more" so it reads less like a boilerplate template to be ignored
An edit that you recently made to Example seemed to be a test and has been reverted – if the tester reverts themself, I'd omit the implication that someone else reverted
there is a Manual of Style that should be followed – I'd link to relevant section(s)
you made an edit concerning content related to a living (or recently deceased) person – might come across more credibly if I seemed to know whether the person was still alive

I can edit these later, or simply add clarification at the end, but I think both good-faith editors and vandals respond better to a human than to a bot, and such tailoring makes the messages seem more human and relevant. Certes (talk) 00:35, 19 February 2022 (UTC)

Ah, that makes sense. Ticket created in case someone wants to work on it. –Novem Linguae (talk) 00:49, 19 February 2022 (UTC)

Add Db-afc-move to CSD menu

Tracked in github.com
Issue #1510

Feel free to move this to a more suitable place if I am wrong to make the request here. It would be nice to have Template:Db-afc-move, which is a request that falls under CSD G6 (see Wikipedia talk:WikiProject Articles for creation § Template:Db-afc-move), added to the CSD menu. 15 (talk) 17:12, 19 February 2022 (UTC)

I created a ticket for this a couple days ago. Feel free to join the discussion on GitHub. –Novem Linguae (talk) 17:34, 19 February 2022 (UTC)

Doesn't recognize existing month heading when day supplied

I think I noticed this before, but check the current version of User talk:Mrmorchan. I don't know what tool (if any) puts the day number in the section heading, but Twinkle didn't recognize it. Note the day number is from my POV (and UTC's) tomorrow because the editor is in Australia, which may be a problem for Twinkle's logic. @Brandon.b2005: how did you generate that first section? David Brooks (talk) 20:12, 23 February 2022 (UTC)

Looking at the page history, and at Special:Diff/1073638012, Brandon.b2005 (talk · contribs) did not use twinkle, or in fact any semiauto tool that has a tag appended to it. So I would imagine that he typed it out. Happy Editing--IAm Chaos 21:54, 23 February 2022 (UTC)

I agree. The edit summary indicates he typed it. If so, this situation is probably not very common and in my opinion probably doesn't need a ticket. Thanks for keeping an eye out though. –Novem Linguae (talk) 22:55, 23 February 2022 (UTC)

@DavidBrooks, IAmChaos, and Novem Linguae: Good morning everyone, you're correct, I issue warnings manually using the templates here. As I'm in Australia, my timezone may be a day ahead of yours. Would you like me to use only the month and year in section headings in future? Thank you. Brandon.b2005 (talk) 00:32, 24 February 2022 (UTC)

Hi, No need to worry about timezones, enWP runs on UTC. Generally tools like Twinkle, RedWarn, Huggle will recognize sections that are Month, Year, so for anyone using any of those three tools doing that would be helpful. Happy Editing--IAm Chaos 00:35, 24 February 2022 (UTC)

Short answer: Yes, that'd be helpful, if you don't mind my friend. We have some automated warning tools, and they work best if the heading is in the format == February 2022 ==. Thanks so much. –Novem Linguae (talk) 01:04, 24 February 2022 (UTC)

Thank you both. I'll take note of this when I'm issuing warnings in the future. Have a great day and apologies for any inconvenience caused by this section headings issue. Brandon.b2005 (talk) 03:50, 24 February 2022 (UTC)

There's still an edge case when Brandon-down-under posts a warning on March 1, and the rest of us follow up on February 28. I don't know what the tools would do then, but it's just amusing to think about, not fatal! David Brooks (talk) 04:27, 24 February 2022 (UTC)

Haha. Wait until new years', the timezone difference between 31 December and 1 January is too strange to think about as it would affect the logic regardless of what date format the section heading is written in. Brandon.b2005 (talk) 05:01, 24 February 2022 (UTC)

Double signature

Tracked in github.com
Issue #1513

Tracked in github.com
Issue #1511

I added the {{Welcome-menu}} template via my Twinkle preferences. However, when I use it, my signature gets added twice: once in the middle of the message after "Happy Editing!" and then again after the entire message (see here for an example). I'm assuming that this is because the template itself has ~~~~ in the message itself and that Twinkle automatically adds the signature at the end. Can this be fixed? Thanks. Jauerback^dude?/_dude. 15:08, 24 February 2022 (UTC)

Hey there. This pull request should fix {{Welcome-menu}} once it gets merged and deployed (you can delete welcome-menu from your custom templates at that point). The bigger issue is covered in this ticket. Hope that helps. –Novem Linguae (talk) 15:30, 24 February 2022 (UTC)

Great. Thanks! Jauerback^dude?/_dude. 15:55, 24 February 2022 (UTC)

Merge

Tracked in github.com
Issue #1522

Hello! So recently I proposed to Channel articles for merging into their specific section at Wii Menu. I noticed that when I propose the merge to a specific section, the link to the merge discussion ends up like Talk:Articlename#Section#Proposed merge of Articlemerge into Articlename#Section which doesn't take you to the appropriate section on the talk page. When you start a merge discussion, would it be possible for Twinkle to not make the link Talk:Articlename#Section if it detects that the merger is merging one article into a specific section of the other article? ― Blaze Wolf^Talk_{Blaze Wolf#6545} 18:20, 24 February 2022 (UTC)

Can you please provide the exact steps to reproduce? Were you using the merge to or merge from tag, and what article were you on? I need enough info to reproduce this on test wiki. Thanks. –Novem Linguae (talk) 00:52, 25 February 2022 (UTC)

@Novem Linguae: I'm fairly sure it was merge to (which Twinkle automatically adds merge from to the target page I'm fairly sure). The article I"m merging is Nintendo Channel. If You still need the exact steps after this then I'll do my best to explain them. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 00:58, 25 February 2022 (UTC)

Alright, I wrapped my head around this one. Ticket created. When I get time to fix it, should be an easy one. –Novem Linguae (talk) 01:13, 25 February 2022 (UTC)

Alright sounds good. The same thing happened when I had proposed Internet Channel into Wii Menu#Internet Channel, which Panini fixed (albeit with me being confused because it seemed like they were modifying the merge discussion to be different, when they were just fixing). ― Blaze Wolf^Talk_{Blaze Wolf#6545} 01:18, 25 February 2022 (UTC)

New features request

Tracked in github.com
Issue #716

Tracked in github.com
Issue #1521

Twinkle is now currently available in Vector and MinervaNeue (named TwinkleMobile), i want to request that Twinkle should be available in all skins because of the popularity Vitaium (talk) 00:17, 24 February 2022 (UTC)

How many skins are there installed on enwiki that would need support? Do you have a specific skin in mind to do first? –Novem Linguae (talk) 01:06, 24 February 2022 (UTC)

There are 4 skins installed in Wikipedia, they are Vector (desktop/PC), MinervaNeue (mobile), MonoBook, and Timeless. Vitaium (talk) 00:13, 25 February 2022 (UTC)

Looks like there's already a ticket for MonoBook here. I created a ticket for Timeless here. –Novem Linguae (talk) 00:28, 25 February 2022 (UTC)

I closed the ticket for Timeless just now. Twinkle is already included in Timeless. –Novem Linguae (talk) 01:31, 25 February 2022 (UTC)

@Vitaium Are you referring to User:P.T.Đ/TwinkleMobile? This is not an official version of Twinkle. You will need to reach out to the author (P.T.Đ) directly to request changes to it. — MusikAnimal ^talk 01:24, 25 February 2022 (UTC)

OS block?

Tracked in github.com
Issue #1525
Resolved

Maybe I'm missing something obvious, but in the block options there is {{checkuserblock-account}} but not {{OversightBlock}}. I feel like it used to be there, am I misremembering? Primefac (talk) 16:48, 26 February 2022 (UTC)

Appears to be a bug. {{OversightBlock}} in the code but is not showing for some reason. I'll make a ticket, and probably submit a patch next week. –Novem Linguae (talk) 19:07, 26 February 2022 (UTC)

Too many pre-made reasons, it slips off the back? :-p Primefac (talk) 19:10, 26 February 2022 (UTC)

Did that Phab ticket about renaming oversighter to suppressor go through? Might be that. –Novem Linguae (talk) 19:20, 26 February 2022 (UTC)

Oh... that would probably do it. Primefac (talk) 19:21, 26 February 2022 (UTC)

It is. ~ Amory (u • t • c) 19:22, 26 February 2022 (UTC)

I've hotfixed it in the live version with a pointer to the Github issue. I trust Amory or MA will take care of it before pushing the repo live. Izno (talk) 19:47, 26 February 2022 (UTC)

Great. Can someone test the hotfix and let us know if it works? –Novem Linguae (talk) 19:58, 26 February 2022 (UTC)

Live version works. Primefac (talk) 20:13, 26 February 2022 (UTC)

Twinkle loading unreliably?

Twinkle is not always loading on all enwiki pages. Is there a way to solve this problem? Thanks. Rusty4321 ^{talk contributions log} 21:09, 25 February 2022 (UTC)

If available, please provide a list of pages Twinkle isn't working on. –Novem Linguae (talk) 00:27, 26 February 2022 (UTC)

cmt - I have noticed on many pages that it says reverting to default settings. I load a lot of pages and also have recently been trying a lot of userscripts, so I can't give a list of pages and also may have some conflicts with other programs. So in all, my 2c probably doesnt help, but I have always had it load on pages. Happy Editing--IAm Chaos 01:04, 26 February 2022 (UTC)

I don't have a list of pages, but Twinkle will load on page reload. Rusty4321 ^{talk contributions log} 22:52, 27 February 2022 (UTC)

Unable to investigate or fix until I can reproduce it. Need a page this happens consistently on, or some other hint. –Novem Linguae (talk) 00:07, 28 February 2022 (UTC)

Deleted template shown?

Tracked in github.com
Issue #1530

Under the Create protection part of Twinkle, there is a Generic ({{pp-create}}) option, even though {{pp-create}} was deleted 2.5 years ago. Someone may want to fix that. Thanks. ---CX Zoom(^he/_him) (^{let's talk}|_contribs) 12:35, 28 February 2022 (UTC)

I see it in the code, but I am having trouble finding it in the popup window. Can you give detailed steps to reproduce please? For example, 1) visit this article, 2) click this, 3) click that. Thanks. –Novem Linguae (talk) 13:53, 28 February 2022 (UTC)

Twinkle doesn't try to transclude it anywhere. It's just the drop-down menu that shows it, though I believe, it should be removed. The location: Any red-link page → Twinkle RPP → Type of protection (drop-down menu appears) → Create protection (section) → Generic ({{pp-create}}) option. ---CX Zoom(^he/_him) (^{let's talk}|_contribs) 14:43, 28 February 2022 (UTC)

Patch submitted for approval. Thanks for reporting. –Novem Linguae (talk) 15:39, 28 February 2022 (UTC)

Minor punctuation issue with {{Welcome-retro}}

Twinkle's version of {{welcome-retro}} is missing a period at the end of "Thank you for your contributions" unless the optional "linked article" parameter is specified. —GMX^{^{(on the go!)}} 17:36, 3 February 2022 (UTC)

@PorkchopGMX (on the go) @PorkchopGMX. Hey there. Thanks for reporting. Can you provide a diff so I have a better idea of what to fix? Thanks. –Novem Linguae (talk) 01:43, 18 February 2022 (UTC)

Here's a diff. This is a problem with Template:Welcome-retro. I've made a post on their talk page. –Novem Linguae (talk) 13:47, 28 February 2022 (UTC)

@PorkchopGMX. Should be fixed. Let them know at Template talk:Welcome-retro#Missing period if you see any further issues with this one. Thanks for reporting. –Novem Linguae (talk) 21:47, 28 February 2022 (UTC)

Suggestion for improvement

Tracked in github.com
Issue #1520

I am a mobile user and I am using Twinkle. When I warn an editor after rollback, the editors talk page will be open in a new tab. Can you please fix it, open an editors talk page in the same tab, like RedWarn does, TIA. —Ctrlwiki (talk) 00:03, 22 February 2022 (UTC)

Thanks for the suggestion. Ticket created on GitHub. –Novem Linguae (talk) 05:13, 22 February 2022 (UTC)

Please make this an optional (opt-in) setting, I generally do not leave warnings and I do not want to deal with extra unnecessary navigation. If this is going to be mobile-only, then ignore me, as I do not use it. Primefac (talk) 07:42, 22 February 2022 (UTC)

My request is just simple. After a rollback, automatic open the reverted editors talk page to warn, but in the same tab. Because the current one is, after a rollback, the reverted editors talk page is automatically open to warn, but in another tab. There is no option for the first one I mentioned. That's it. If you are gonna make it as an optional, it's ok. Just add that in Twinkle. —Ctrlwiki (talk) 10:39, 22 February 2022 (UTC)

If this happens, I'm in the side of opt-in or mobile-only. I often want to return (control-tab or, if I'm feeling dexterous, shift-control-tab) to the main page to check History for related damage if it feels warranted. I'll add this comment to the ticket. David Brooks (talk) 15:22, 22 February 2022 (UTC)

Definitely should be opt in only. Having a seperate tab is WAY easier for keeping track of what I'm doing, but that may just be the ADHD talking trying to stay organized. Happy Editing--IAm Chaos 18:54, 22 February 2022 (UTC)

I want the editors talk page will open in the same tab after rollback. Cause what happening now, after rolling back an edit, a notice will show up "Pop-up blocks (always show)", if I don't click the always show, you can't warn the user, and if I click always show, you can warn the user in another tab but chrome will allow pop-ups, which I do not want. I want to warn user but I don't want the Chrome allow pop-ups so that's why I think allowing me to warn user in the same tab after rollback will fix the problem I mentioned above. Using RedWarn, after rolling back, a warn menu will show up, and I can warn the user in the same tab. That is what I want in Twinkle, if you are going to make it as an optional, it's ok. —Ctrlwiki (talk) 00:41, 23 February 2022 (UTC)

For what it's worth, none of us above are disagreeing with you that this is a reasonable feature requests, it's just that none of us personally want it forced upon us, hence our various "opt-in" comments. You do not need to convince anyone because no one is opposed! Primefac (talk) 09:47, 23 February 2022 (UTC)

I've just explained my reasons for my suggestion, don't be mad, firstly, I did not convince anyone. —Ctrlwiki (talk) 10:40, 23 February 2022 (UTC)

@Ctrlwiki If you click "always show" in Chrome it only will allow popups from Wikipedia, not from all websites. --Ahecht (TALK
PAGE) 13:23, 23 February 2022 (UTC)

Ya I know. But still don't want it. I do not know if they can remove that notice, and never show up again, and why the tool need to allow pop-ups just to be able to warn. Except for that, I don't want also to open the user talk page after rollback in another tab. If they can't make it as an option—another suggestion is to automatically open warn menu after rollback edits so warning an editor will be easy, no need to open the users talk page. If you're going to ask if why don't I use RedWarn instead of Twinkle, it is because Twinkle is faster than RedWarn for me. —Ctrlwiki (talk) 14:19, 23 February 2022 (UTC)

IMO, Chrome calling a new tab a "popup" is misleading. I spent a while searching for a new toplevel window, which is what the term always meant to me (or a fake one within the currently active web page, of the type that currently litters our online experience - no, I don't want to take a survey!). But I doubt making that distinction will matter to the current debate: the objection seems to be to opening the new tab. David Brooks (talk) 19:58, 23 February 2022 (UTC)

There seems to be no user who objected to my suggestion. What's the update, I hope you add this feature, because no one is against it. Even make my suggestion optional, no problem. —Ctrlwiki (talk) 12:56, 1 March 2022 (UTC)

Features for Twinkle need to be programmed, and that means someone needs to be program it. As indicated at the top of this section, the issue has been flagged as an improvement on github and when someone gets around to coding it, will be added to the live version. Primefac (talk) 14:57, 1 March 2022 (UTC)

Honestly, my read of this discussion is that only one user wants this feature, and others will tolerate it if they can easily opt out of it, but in general others don't want it. Could argue that this didn't really achieve consensus. –Novem Linguae (talk) 18:48, 1 March 2022 (UTC)

I would also appreciate this feature. ― Qwerfjkl talk 19:26, 1 March 2022 (UTC)

@Novem Linguae: Why did you say that they don't want this feature. this feature is not a default option, it will be made an additional option. In fact, other twinkle users don't know about this discussion. And maybe, many of them, who are also mobile users, will appreciate this feature. Because when this feature is still not made, opening the talk page in another tab caused a lag on the mobile. Unlike desktop, twinkle on mobile (using desktop view) is literally difficult to use. And what is the reason why others don’t like this feature? —Ctrlwiki (talk) 23:46, 1 March 2022 (UTC)

I have another request if you really don't like my first suggestion. what if, the warn menu opens after reversion, and then warn, so there is no need to go to a user's user talk page just to warn. Maybe no one will object to that, because that was already done in RedWarn. Just make it optional as well. —Ctrlwiki (talk) 23:56, 1 March 2022 (UTC)

Question about special characters and possible proposal

Tracked in github.com
Issue #1533

Hello. When I initiated this RFD using Twinkle, I wanted to insert additional arrow → characters to help explain the current situation. I didn't see that option available so I instead typed =>. An editor then changed those to arrows afterwards. As far as I could tell, while Twinkle will automatically generate the arrow symbol at the top of an rfd, its edit window does not have the capability to insert additional special characters like the way we can in the standard edit window.

Maybe I didn't try very hard, so my question: Is the CharInsert menu accessible from a Twinkle edit window? If no, is it feasible to add this feature? --DB1729 (talk) 22:48, 3 March 2022 (UTC)

Ticket created. –Novem Linguae (talk) 23:34, 3 March 2022 (UTC)

Just type →: → ― Qwerfjkl talk 14:52, 4 March 2022 (UTC)

Twinkle breaks WP:UAA

Tracked in github.com
Issue #1534

Hello! So just recently, someone reported a user to UAA with Twinkle and something broke while reporting causing this to happen (the editor fixed it themself). I have no clue what's causing this or why but I'd figure I'd post this here so maybe someone could figure out what's going on. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 21:14, 7 March 2022 (UTC)

Hello! I was gonna report this myself as the user who made that edit. I think this is caused by attempting to report someone just after an edit is made to the page, and as a result Twinkle accidentally blanks the page. EDM fan 2 (talk) 21:24, 7 March 2022 (UTC)

@EDM fan 2: I reported it because this is the 2nd time I've seen this happen. I would've let you do it if I had known you were gonna report it. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 23:02, 7 March 2022 (UTC)

I just tried submitting a report and Twinkle seems to be loading the page, adding the report to the end, and then submitting the whole thing as the text. Perhaps using appendtext would be less error-prone? Suffusion of Yellow (talk) 23:20, 7 March 2022 (UTC)

Thanks for reporting. Ticket created. I was unable to reproduce on testwiki. Can you provide more details about exactly what you entered into the form? I assume AIV->UAA, username=GALE (Agency), checkboxes=Promotional username? –Novem Linguae (talk) 04:10, 8 March 2022 (UTC)

I made a report earlier today and as far as I can tell it seems fine. Just noting. - FlightTime (open channel) 04:13, 8 March 2022 (UTC)

@Novem Linguae: Probably. I myself haven't encountered the issue but I've seen it twice. My guess is it's what EDM fan 2 described, Twinkle reports the user right after someone else does causing that. ― Blaze Wolf^Talk_{Blaze Wolf#6545} 14:00, 8 March 2022 (UTC)

Rename category

Tracked in github.com
Issue #1536

When requesting that a category be speedily renamed, please could Twinkle check that the proposed new name does not exist? The editor should do this, but it's easy to forget if you don't normally work in that area. (I've just withdrawn a request and replaced it by a deletion request for the erroneous duplicate name.) Certes (talk) 15:06, 9 March 2022 (UTC)

Sounds reasonable. Ticket created. –Novem Linguae (talk) 15:34, 9 March 2022 (UTC)

Deploy

Hey @MusikAnimal. When you get a chance, would you be willing to run the Twinkle deploy script? There's a bug fix in there for a bug that is likely to affect Twinkle on Thursday. Thanks. –Novem Linguae (talk) 13:39, 9 March 2022 (UTC)

Novem, I assume this THURSDAY issue is what's causing TW to look like it's been taking steroids for the last two years and is playing King Kong on top of my navbar? Primefac (talk) 19:54, 10 March 2022 (UTC)

There was just a section started at VPT, a bunch of other words are appearing as well for me, not just twinkle. Happy Editing--IAm Chaos 19:57, 10 March 2022 (UTC)

Not Novem Linguae, but yes this is the cause. There is a patch on GitHub that will fix this, but it has not been deployed yet. TheTVExpert (talk) 20:03, 10 March 2022 (UTC)

Alright, we ran the deploy script a few minutes ago, should be fixed. Please let us know if any further issues.

@Primefac. No more steroids for Twinkle. 💪💪 lol –Novem Linguae (talk) 20:26, 10 March 2022 (UTC)

Looks good, ta. Primefac (talk) 20:58, 10 March 2022 (UTC)

Sorry I was late to deploy! I didn't realize there was a backwards compatible fix, so I was waiting for wmf.25 to land on group 2 first (I had to make the same fix for meta:MoreMenu). A pity we weren't notified via Tech News :( — MusikAnimal ^talk 21:25, 10 March 2022 (UTC)

Slight error when warning a user for having a "bot username"

Tracked in github.com
Issue #1537

When you report someone for this reason, it allows you to provide a "linked article". I was curious, so I tested it in the sandbox for user warnings. However, it doesn't link an article but tells you another reason why the username violates the username policy, so I ended up with a sentence stating "In addition, it Article". The "Linked Page" should definitely be reworded to "Additional reason for username policy violation" or something along those lines, because it's not a linked page, and saying it is one is quite confusing. InterstateFive (talk) - just another roadgeek 17:19, 11 March 2022 (UTC)

Sandbox link –Novem Linguae (talk) 17:52, 11 March 2022 (UTC)

Diff

What is the Diff in Twinkle placed at the bottom of the Turn of selected modules, what happens when you check it? —Ctrlwiki (talk) 22:46, 16 March 2022 (UTC)

It is the Diff module, which adds the "Last", "Since", "Since mine", and "Current" options to the Twinkle menu. The first of which is available on all pages, while the other three are available only on diff pages. TheTVExpert (talk) 00:27, 17 March 2022 (UTC)

What happens if I disable this? Will the revert options and restore revision options disappear in diffs? —Ctrlwiki (talk) 08:21, 17 March 2022 (UTC)

No, they are part of the Revert and rollback module. Disabling the Diff module only gets rid of the aforementioned options in the Twinkle menu. TheTVExpert (talk) 12:31, 17 March 2022 (UTC)