This is an archive of past discussions on 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.
@Star Mississippi: It should be checked by default on AfD subpages and you should leave it checked. Since you are leaving it checked, there may be another issue here. I will see about looking into this further soon. TheTVExpert (talk) 16:40, 18 March 2022 (UTC)
Latest comment: 2 years ago1 comment1 person in discussion
A proposed template change to alter the message emitted by template {{uw-translation}} is being discussed at Template talk:Uw-translation. This is completely backwards-compatible and there are no changes to any parameters, so won't break existing invocations. Your feedback is welcome at the discussion. Thanks, Mathglot (talk) 03:17, 20 March 2022 (UTC)
Twinkle doesn't recognize variant of multiple issues template
Latest comment: 2 years ago2 comments2 people in discussion
Hello! So on the article hill descent control system I used Twinkle to change the no sources template to a more citations needed template. That template and the advertising template were both inside of the template {{multiple}} which is a shortcut for the multiple issues template. However, when I used Twinkle, it apparently didn't recognize the multiple template as being the multiple issues template, so it added a new one and removed the templates from the multiple template and placed them inside a multiple issues template in this edit (disregard the "Newcomer task" tag, I simply found the article from looking through the recommended edits in my newcomer homepage), which resulted in the multiple template saying that there are no issues specified. ― Blaze WolfTalkBlaze Wolf#654500:24, 20 March 2022 (UTC)
The page =U= caused unexpected problems when attempting to file an RfD nomination for it, since {{rfd2}} cannot handle plain equals signs. Were this nomination submitted in Twinkle, it would have generated:
Latest comment: 2 years ago7 comments3 people in discussion
When I block a user for being a sockmaster, how can I change the default block length of 31h to indefinite?--Bbb23 (talk) 13:48, 21 March 2022 (UTC)
@Bbb23. Hey there. I wasn't able to reproduce this one. When I go to block and I select sockmaster as the reason, there is an "expiry" combo box that defaults to 24 hours, and it is changeable. Screenshot. Can you provide more details? –Novem Linguae (talk) 15:36, 21 March 2022 (UTC)
Oh I think I misunderstood you, you want to change the "default". Sockmaster and sockpuppet blocks are normally indefinite, right? Could probably just change Twinkle's code, if there's support for this. Are there any other block types in the list that might also need their default length changed? –Novem Linguae (talk) 15:43, 21 March 2022 (UTC)
Sockpuppets are almost always blocked indefinitely, and the default in Twinkle is indeed indefinite. The block length for a sockmaster varies from brief to indefinite. Regardless, I want the block length default for a sockmaster to be indefinite. I am not arguing for that as the default for all Twinkle users.--Bbb23 (talk) 15:46, 21 March 2022 (UTC)
Sounds like the requestor doesn't want us to change the default (I am not arguing for that as the default for all Twinkle users). And I think coding this as a user preference would have a poor complexity to value ratio. So I am leaning toward not creating a ticket for this one. –Novem Linguae (talk) 17:17, 28 March 2022 (UTC)
Incorrect XFD target
Latest comment: 2 years ago4 comments2 people in discussion
Hi, Twinkle's XFD tool automatically senses the type of page and targets a XFD nomination to AFD/RFD/TFD/MFD as appropriate. Now, Wikipedia:Soft redirect § Deletion says that soft redirects are subject to RFD, but on using Twinkle's XFD tool on a soft redirect page, it fails to recognise the soft redirect, instead it senses the namespace of the page and targets the XFD to TFD/MFD, and not RFD as per applicable rules. It would be great if this could be solved. Thanks! ---CX Zoom(he/him)(let's talk|contribs)13:18, 31 March 2022 (UTC)
Hey @CX Zoom. Thanks for reporting. I found some old tickets on this so looks like Twinkle has this feature, which would make this a bug. Can you provide a diff of where it's not working? Looking through your contribs, I found this, but that is probably the wrong diff since it is not a soft redirect. –Novem Linguae (talk) 19:23, 31 March 2022 (UTC)
An issue I was trying to fix was that Template:RMassist was adding blank lines at WP:RM/TR. One possible way to fix this is to remove the asterisk from the template and require users to manually enter an asterisk before {{subst:RMassist, which I did. But then you reverted the change to the RMassist template due to it resulting in Twinkle not adding the asterisk. Instead of removing the asterisk again, I have moved the asterisk to right after the <includeonly> tag in Special:Diff/1080726257, which is an alternative way to fix the blank lines issue. GeoffreyT2000 (talk) 02:19, 3 April 2022 (UTC)
Hi, in the redirect categorization box, when clicking the wikilink, it does not pass a ?redirect=no parameter to the url, and just loads the redirect target when clicked. Is there anything that could be done? Happy Editing--IAmChaos07:09, 12 April 2022 (UTC)
Hey there. I'm having trouble reproducing this one. Can you please give exact steps to reproduce? Also, what is a "redirect categorization" box? Is this the TW -> Tag feature, or something else? Thanks. –Novem Linguae (talk) 07:15, 12 April 2022 (UTC)
Yes, the tag feature on redirect pages. After tagging, when clicking the page link, it follows the redirect instead of remaining on page. When I say link, I mean the equivalent of the IP adress in this :commons photo. Sorry for the lack of clarity. Happy Editing--IAmChaos17:28, 12 April 2022 (UTC)
Latest comment: 2 years ago3 comments2 people in discussion
I added the {{update}} tag to the doc page because the images were out of date + some other incorrect info. Please feel free to improve/discuss/etc. interstatefive (talk) - just another roadgeek 02:19, 12 April 2022 (UTC)
Per the outcome of this RFC, could the patch discussed and implemented here please be reversed? Apparently our lack of consensus means that new entries need to return to being placed at the top. Thanks. Primefac (talk) 07:09, 12 March 2022 (UTC)
Novem Linguae, has the patch been applied? Logging of Tfd nominations is all over the place. New nominations are going at the bottom as opposed to the top. Or sometimes it goes in a random order. --WikiCleanerMan (talk) 15:04, 6 April 2022 (UTC)
Latest comment: 2 years ago3 comments3 people in discussion
I appreciate you re-adding Template:W-graphical back to the Welcome options. I was using the plate of cookies but it seems rather informal and I like to provide links to How to pages, the Help Desk and the Teahouse. I don't know if anyone uses Template:Welcoming which is enormous and can take up the entire User talk page. I think that one could be removed. Thanks again! LizRead!Talk!22:49, 14 April 2022 (UTC)
Hmm, That one kind of feels complementary to {{Thanks}} in terms of length. I have been using -retro, as it doesn't have the graphics like {{welcome}}, but does link to TWA. Happy Editing--IAmChaos06:55, 15 April 2022 (UTC)
Add {{Current related}} to tag feature
Latest comment: 2 years ago2 comments2 people in discussion
So I have been working through the NPP Feed for redirects. Usually I just open up twinkle throw a tag on, patrol it and move on. However, when I have a redirect that is an {{R from move,}} I am not able to patrol it from Twinkle, and have to use the curation toolbar directly. I don't know if it has to do with the rcat template being already in place, or it being a move instead of an edit in the history or some other thing I can't think of because I don't code... Anyway figured I'd see if anyone knew about that.
Steps to reproduce: Open an unreviewed redirect that was created by a page move, open the tag box on TW, the option to review the page is not present. Happy Editing--IAmChaos06:29, 20 April 2022 (UTC)
a) I'm not sure why but there are some criteria for speedy deletion where, even if the editor has check off "Please notify page creator if possible", Twinkle doesn't post a notification to the talk page of the page creator. If I had my way, notifications would be an opt-out feature instead of an opt-in feature but that's an issue for another day. The criteria where I know that notifications aren't posted is CSD G7 and there might be others as well. I can see why you omitted G7 because it would seem like it would only be used by the page creator to tag their own pages for deletion. But, in fact, this criteria is used by page patrollers to tag pages where the page creator has removed all or most of the page content. When I've gone to the tagging editor to remind them to post notifications, they state that they have this option checked, but Twinkle omits the notification. Removing content from a page is often done by new editors and I think it would be great if they could get a deletion notification to let them know that when they blanked the page, it was in fact deleted. I think talk page notifications are so important because editors do not have access to their Deleted Contributions list and they can be the only record they have of a page they worked on that has been deleted.
b) I'm not sure why, but when I delete pages with Twinkle, with the preferences I have selected, Twinkle deletes the page, the talk page and any redirect pages. But it doesn't delete any redirect talk pages. Frequently, editors don't create a redirect talk page so this is no problem but they do exist, especially if a page has been moved around. There are other tools to locate orphaned talk pages but it would be much simpler if Twinkle could just take care of these pages at the same time. I know that XFDCloser deletes redirect talk pages so there are some tools that manage to figure this out. I know I have brought up this issue here before so I apologize for repeating myself but maybe now there is a fix that could resolve this.
Hey Liz. Thanks for the suggestions. Just now I created a ticket for the first suggestion. I think that could be implemented by adding a G7 check box to the preferences page. I remember your second suggestion and in December 2021 I coded a working solution to the batch delete module that I was going to eventually port over to the CSD module. However it got stuck in code review. Folks requested changes and I haven't had the time to work on it lately. I'll add these two to my todo list and see what I can do. Feel free to ping me in a month or two if needed. Hope that helps. –Novem Linguae (talk) 00:30, 21 April 2022 (UTC)
Latest comment: 2 years ago2 comments2 people in discussion
When using the rollback feature of Twinkle and after it opens a user talk page, does it normally autofill/prefill anything on it or is it a customized feature that we can enable? --Bebiezaza (talk) 20:29, 27 April 2022 (UTC)
@Bebiezaza: It opens the user talk page and pulls up the warn/notify menu. (The one that pops up when you hit warn from a user/talk page). It just defaults to the automatic of that menu which is {{uw-vandalism1}}, but you can select any template from that menu before saving, or even close the menu to use one of the ones in the welcome menu, such as if the user does not have a talk page yet. Happy Editing--IAmChaos22:51, 27 April 2022 (UTC)
New parameter talk= for Template:Unbalanced
Latest comment: 2 years ago3 comments2 people in discussion
Hi, I tested out adding a "talk" parameter to link to a talk page section in Template:Unbalanced/sandbox at my user page User:Mathnerd314159/sandbox and it seems to work well. I was wondering if there was anything else to do before updating the live template? The template documentation mentions notifying Twinkle so I'm doing that here. --Mathnerd314159 (talk) 00:42, 3 May 2022 (UTC)
Hey there. I don't see {{Unbalanced}} in the list of tags in Twinkle. I've gone ahead and removed the notify Twinkle template from the documentation. If you think it is commonly used and would like it added, let us know. Thanks. –Novem Linguae (talk) 01:42, 3 May 2022 (UTC)
Recently I have been looking at a lot of biography pages without photos and the process of going to the talk page to add a "requested photo" template is annoying. It would be much nicer if I could do it within Twinkle. Gusfriend (talk) 07:15, 5 May 2022 (UTC)
When tagging redirects, it constantly bus me that you can't remove rcats by deselecting them - they appear deselected even if they are already on the page, and if you select any deselected rcat, Twinkle just skips them with a warning notice. ― Qwerfjkltalk15:29, 5 May 2022 (UTC)
Currently MediaWiki:Gadget-twinkleconfig.js uses the ombox class to let users know how Twinkle preferences work in the "backwards compat" case where someone has previously added their own preferences in local Javascript pages (i.e. circa a decade ago and later). At some point in the near but not quite yet future, I'll be moving ombox to TemplateStyles, so the use there will need to be modified.
I expect to split up each of the *mbox styles into separate TemplateStyles sheets, so ombox will be in its own page. (This is how we decided to do it at MediaWiki wiki.) Either the CSS will need to be loaded from that page (I see no reason mw.loader.load can't get those styles once they're on a separate page) or Twinkle will need to supply its own styles for those elements.
As a note, at some point in the further future the *mbox system will not be using a table for presentation, so the styles for the elements of interest will need to change somewhat again if the references to ombox remain here. Izno (talk) 00:16, 7 May 2022 (UTC)
That patch does not look complete. All of the styles related to *mbox will be moving, which includes the styles associated with mbox-image and mbox-text.
Separately, I am not sure of the purpose for having the -content style as a separate selector if this is the only set of styles associated with ombox in Twinkle. But that's up to you I guess, perhaps you expect to see more ombox uses in the future in morebits. Izno (talk) 01:15, 7 May 2022 (UTC)
The uses of ambox in the code select for the classes and are not used for output, so it's just the above-noted classes that need attention. Izno (talk) 01:55, 7 May 2022 (UTC)
A followon might consider two things: not using <big> (most big is usually in the realm of font-size 120-125%), and using flex instead of a presentation table. Izno (talk) 23:14, 14 June 2022 (UTC)
Double signature when {{WelcomeMenu}} is added using Twinkle
Latest comment: 2 years ago4 comments3 people in discussion
Hey there. So WelcomeMenu was removed, then re-added, and there's another discussion to remove it above. During the first removal, I think some people added it to their custom welcome templates to display (which is an option in Twinkle preferences). The default when displaying custom welcome templates is to automatically sign them. These diffs of @Deepfriedokra and Peaceray: above appear to be people using the custom welcome template still. Hope that makes sense. User:Deepfriedokra/twinkleoptions.js, User:Peaceray/twinkleoptions.js. –Novem Linguae (talk) 03:21, 9 May 2022 (UTC)
Latest comment: 2 years ago3 comments2 people in discussion
I'm not sure where to report this, but in the past few weeks have seen new behavior when using the TW "Warning" feature after reverting a vandal edit. When I examine a revision difference and press the red [vandalism] link, a new tab for the user talk page is created as usual. However when I attempt to issue a warning on the tlak page, the "linked page" field of the warning dialog is not populated with the reverted article title and I need to cut and paste it. This appears to happen when a new talk page is created (i.e. user has never received a warning or other message) and not for user talk pages that already exist. If it makes a difference I am using v99.0.1 64 bit version of Firefox.
If this is *not* the proper place to report this, can you direct me to the proper location?
Unable to reproduce on testwiki. Would you be willing to provide idiot-proof (Novem-proof?) steps to reproduce here on enwiki, specifying exactly what page it happens on, etc? :) Hint to developers: the pre-filed title appears to be passed via the ?vanarticle= part of the URL. –Novem Linguae (talk) 04:34, 5 May 2022 (UTC)
I've noticed a glitch while using Twinkle. Sometimes, when I reload the page after delivering a warning, Twinkle sends the user duplicate messages. It's happened to me twice within the past week (Special:Diff/1081965119, Special:Diff/1083260990). Not exactly sure how to reproduce the glitch as it tends to catch me offguard when it happens. Has anyone else experienced this? Helen(💬📖) 23:47, 17 April 2022 (UTC)
Ticket created. Does this happen just for IPs? Does this only happen for certain warnings or levels of warnings? Seems like this will be a hard bug to track down without steps to reproduce. –Novem Linguae (talk) 01:11, 18 April 2022 (UTC)
@Novem Linguae I may have a lead because it happened to me again today. Here’s what I believe happened: I hit submit on my warning message (so far it’s only been with IPs) and then quickly reloaded the page. Then I was met with some error message in green letters. After reloading the page, duplicate messages popped up. This may not be the exact way (I’m still working out how to trigger it every time), but it is a start. I’ll keep you posted if I notice anything else that may help. Helen(💬📖) 18:59, 18 April 2022 (UTC)
That helps. I added the error message to the ticket. The comment in the program code for that particular error message is "network or server error", so that could be another clue.
If you want, play around on https://test.wiki.x.io/ and see if you can get a "steps to reproduce" that works consistently each time.
Finally, try not refreshing the page for a couple seconds and see if that eliminates the problem. A lot of stuff in Twinkle will pop up a window where it does a bunch of stuff simultaneously but the tasks finish at different times, and if you interrupt that by refreshing too early, it could lead to glitchy behavior. I usually wait until everything says "done" and also wait a few seconds before I refresh. Hope that helps. –Novem Linguae (talk) 03:37, 22 April 2022 (UTC)
@Novem Linguae With your newest message in mind, I’ve cracked the case. Here are the steps to reproduce: hit ‘submit’ on the warning you are sending. Immediately afterwards, click on your contributions page. Then click the ‘back’ arrow on whatever device you’re using (for me, it’s a tablet)— the green error message will appear. Once the page reloads, duplicate warnings will pop up. Helen(💬📖) 14:46, 22 April 2022 (UTC)
I wasn't able to reproduce this. Perhaps I am not able to click "Contributions" fast enough to interrupt the warning process. Do you ever get this error if you don't click the back button? (In other words, is the back button a fundamental part of this bug?) –Novem Linguae (talk) 06:46, 10 May 2022 (UTC)
Remove TW from top of pages.
Latest comment: 2 years ago6 comments3 people in discussion
If you're asking if you can turn the Twinkle gadget off, sure. Go to Preferences -> Gadgets -> Browsing -> uncheck "Twinkle". Hope that helps. –Novem Linguae (talk) 00:27, 10 May 2022 (UTC)
No i don't want to turn off Twinkle, I just want to remove "TW" at the top of pages, I only use it for restoring revisions so I would don't want too see the flyout with options at the top. --Aaron106 (talk) 00:28, 10 May 2022 (UTC)
Probably no setting to turn that off. If you have an AdBlocker and it accepts custom filters, you could add this custom filter to your AdBlocker: wikipedia.org###p-twinkle –Novem Linguae (talk) 01:02, 10 May 2022 (UTC)
Aaron106, add #p-twinkle{display:none} to Special:MyPage/common.css. Or alternatively #p-twinkle H3 span{display:none} which removes the "TW" but leaves the downward arrow intact so the menu is still functional. — Alexis Jazz (talk or ping me) 07:58, 10 May 2022 (UTC)
Error in Twinkle menu position
Latest comment: 2 years ago3 comments2 people in discussion
Recently (a few days ago), the Twinkle menu position has moved a bit to the left, so all the selections are off the edge of the screen. ― Qwerfjkltalk09:32, 14 May 2022 (UTC)
Unable to reproduce. Are you talking about the TW menu when you unfold it, or the modal window that pops up? Can you provide a screenshot? –Novem Linguae (talk) 12:26, 14 May 2022 (UTC)
I sometimes close CfD discussions, and after closing and emptying the category, I tag them for CSD under G6, XfD. It then asks for a link (optionally) to the discussion, and when I input [[Wikipedia:.., it alerts me must start with Wikipedia: . It would be nice if the input could be wrapped in .replace(/^\[\[(.+)\]\]$/,'$1'). An even more minor issue is that it alerts me that there is another {{CfD}}-related template in the page, which I just ignore (and sometimes accidentally cancel the tagging). Qwerfjkltalk11:21, 2 May 2022 (UTC)
Latest comment: 2 years ago11 comments6 people in discussion
Last year, I opened a discussion here, with input from the welcoming committee, re-examining the default Twinkle welcome options. We reached consensus to remove several options with exceptionally poor design. After it was implemented, a few users of two of those templates noticed they were missing, asked for them to be restored, and had their request granted with little discussion. Neither the welcoming committee nor any participants from the prior discussion were notified, and while this was presumably a good faith oversight, it nevertheless should have invalidated the request, since a local consensus cannot overturn a properly widely advertised discussion. Given this, I ask that the restoration of these templates be reverted to remedy the procedural error, and that we continue discussion here as needed.
Copying my analysis of the two templates in question from the original discussion:
{{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.
To those of you using these templates, you are still welcome to do so via your preferences here, but I really encourage you to switch to better options, which were made default for a reason. 60 links may not seem overwhelming to you since you know where all of them go, but to a newcomer, I guarantee they will.
We should not be encouraging editors to dump an entire directory onto newcomers by making the templates that do so standard inclusions on Twinkle. The defaults should be our best options, not our worst.
I honestly don't remember the discussion (and don't appear in the cited archive). But FTR I wouldn't call for their return; I think some of the other welcome pages are already tending to be TMI for a new user. David Brooks (talk) 00:32, 1 May 2022 (UTC)
Sorry about readding. I assumed these were removed for disuse reasons, and when someone requested readd due to using frequently, I assumed it would be uncontroversial. Didn't know you guys were specifically trying to make it harder to use these particular templates. Anyway let's discuss it a bit and if there's still consensus I am happy to execute whatever is decided. TFD or RFC could also be good options, if needed. –Novem Linguae (talk) 00:52, 1 May 2022 (UTC)
I routinely use {{Welcome-menu}} to welcome new users. I have had many people thank me for the welcome & no one has complained. I realize that some editors may believe that 60 links is TMI, but I happen to think that it is a useful resource for newbies as long as they choose to leave it on their talk page. I have added the template to my preferences & will continue to use it. Peaceray (talk) 16:49, 1 May 2022 (UTC)
Some portion of newcomers will thank anyone who leaves any welcome message, and no one is likely to complain about a welcome's design immediately after receiving it, so that unfortunately doesn't tell us much. It'd be nice if there were some research that collected data about which welcomes tend to lead to retention, but in the absence of that, all we have to fall back on is usability principles. And they're pretty unequivocal that you don't want to immediately dump 60 links, including some pretty obscure ones (What makes Wikipedia:Mailing lists essential?), on a new user. {{u|Sdkb}}talk21:02, 1 May 2022 (UTC)
When I see a study indicating which welcome message is best at user retention, I will use that one. Right now, from what I remember, the most effective retention tool is to thank someone for their edits.
As far a usability, I believe the Welcome-menu to be well chunked, as per The Magical Number Seven, Plus or Minus Two. For those unfamiliar with chunking, it is a reorganization of material into a smaller groups when the number of items is more than seven, give or take one or two. Peaceray (talk) 21:29, 1 May 2022 (UTC)
Courtesy pinging @MMiller (WMF) just to double check if there are any studies on welcome template design—it'd be really helpful if the Growth team could commission one, or just provide any thoughts more generally on this topic.
Peaceray, The "policies and guidelines" section currently contains 21 items, so I wouldn't say it follows that principle. And more to the point, using five links where one will do (as is the case for e.g. the "getting help" section) is still terrible usability. I understand the temptation to give newcomers all the links they might need—it feels good to think you've provided someone with all they'll need to know—but that's unfortunately not how people learn. No one is going to read through (or even glance at) 60 links to massive policy pages before they start editing. When presented with that, they'll just go in blind and either get lucky or get bitten. Better welcomes like {{Welcome}} or {{Welcoming}}, by contrast, link to few enough (and beginner friendly enough) pages that editors may read them. {{u|Sdkb}}talk21:49, 1 May 2022 (UTC)
FYI, looks like we have around 28 people who added Welcome-menu to their custom welcome templates list last time we removed it. [2][3]. And 14 that added Welcome-Graphical. [4]. Because these templates are popular, might want to RFC this. We're currently in a cycle of remove them, someone complains, add them back, someone complains, which is not ideal. –Novem Linguae (talk) 03:33, 9 May 2022 (UTC)
Sounds reasonable, Novem Linguae; I'll open an RfC below. Looking through your links, though, most of them are from many years ago, so the actual numbers are much smaller. And agreed, Deepfriedokra—no one is trying to prevent anyone from using their preferred template, but defaults are powerful, so we should not be suggesting templates that are not our best by including them as default options. {{u|Sdkb}}talk23:51, 18 May 2022 (UTC)
Mismatched message?
Latest comment: 2 years ago3 comments2 people in discussion
No other hints unfortunately. I just did it how I usually do. I will keep an eye out for this in the future. I don't tag many pages with G6 I think, but also I don't normally look closely at the talkpage messages, I just check that it posted. Will update if I find anything else Happy Editing--IAmChaos19:04, 20 May 2022 (UTC)
Tag Request
Latest comment: 2 years ago2 comments2 people in discussion
Latest comment: 2 years ago4 comments2 people in discussion
I use Twinkle to do most of my page deletions, including PRODs and when I use it for PRODs, I use the unlink feature. This works MOST of the time but I'd say 1 out of 12 or 1 out of 20 times, nothing happens. I see "To orphan backlinks: click here to go to the Unlink tool" and I click on the link and it's inactive. Nothing happens at all. It is quite a chore to manually remove red links so the unlink tool is very handy. As I said, most of the time there is no problem but sometimes the link to unlink is just not active and clicking on it does nothing. Thanks. LizRead!Talk!23:08, 19 May 2022 (UTC)
Thanks for reporting. It might be throwing an error, which would abort the code without finishing at the spot of the error.
When this happens, have you tried going to the Twinkle menu and clicking Unlink? Does that work as a workaround or is that broken too?
The next time this happens, can you please reply here with the page title and not manually unlink, so I can investigate? Thanks. –Novem Linguae (talk) 08:37, 20 May 2022 (UTC)
Well, this is a little embarrassing but I use Twinkle throughout the day and night and I never noticed the separate "Unlink" option in the pull-down menu from the Twinkle tab. To delete a page, I just go to CSD on the pull-down menu, even for a PROD, and it has the PROD reason in the field for deletion rationale and after the page and any redirects are deleted, the Unlink option appears on the little screen. I'll try to Unlink option in the pull-down menu and see if it helps. This will work even after a page has been deleted? Funny how you use a tool thousands of times and you become an expert in those limited ways you use it without discovering other options that may exist. If that Unlink option works even without deleting a page first, I can see other ways it might be useful. LizRead!Talk!21:16, 23 May 2022 (UTC)
This will work even after a page has been deleted? I tested it on testwiki just now, unlink appears to work on non-existent pages. Give it a try :) But still keep an eye out for the bug and feel free to ping me the next time you see it. I'd like to squash the bug, but I will likely need a test case! –Novem Linguae (talk) 03:33, 24 May 2022 (UTC)
Isn't working
Latest comment: 2 years ago3 comments3 people in discussion
Hello friend. Please give enough information that I can reproduce the error. For example, what URL are you at when this happens? What did you click to open the customizing panel? Can you provide a screenshot of the error? –Novem Linguae (talk) 19:43, 25 May 2022 (UTC)
Latest comment: 2 years ago6 comments4 people in discussion
Hi folks, can I add one line to introduce TwinkleMobile script on Wikipedia:Twinkle main page? It can help some users using this tool on mobile. It has been used by dozens of users. Thanks. P.T.Đ (talk) 13:02, 26 May 2022 (UTC)
I just got a notification that a draft that I had supposedly created six months ago was speedily deleted. I don't recognize the draft, but I know that if I get a message about a draft that it thinks I created, I probably moved it from a sandbox to draft space six months ago, and then either declined it, or left it for another reviewer. What I notice is that no one else got the same message, and that it would have been useful if the originator of the sandbox draft was notified that their former sandbox draft had been deleted. Is it expecting too much intelligence to ask Twinkle to know what the provenance of a deleted draft was? Robert McClenon (talk) 17:26, 30 May 2022 (UTC)
Yes. There is no easy way to find out who wrote a page, so tools like Twinkle use the author of the first revision instead, even if that is a totally unrelated redirect. —Kusma (talk) 18:34, 30 May 2022 (UTC)
Hey Robert. Looks like this is an edge case where you moved a sandbox to draftspace, then the user later overwrote the redirect left behind in the sandbox with some new sandbox content that also got moved to draftspace. Since you technically did create the original redirect, you show as the second draft's author. This situation is rare but seems to make sense logically. I agree that it's not ideal but I don't see an easy way to fix it. Hope that explanation helps. –Novem Linguae (talk) 00:27, 31 May 2022 (UTC)
Twinkle consider the author of the first non-redirect version as the creator in case of AFD/PROD notifications. In case of CSD this feature was never implemented because CSD can apply to redirects too, so we're just using the author of the first revision - ideally we should use that fallback only for CSD criteria that are applied to redirects. – SD0001 (talk) 04:42, 31 May 2022 (UTC)
There is also G14, G5, G4, G3 which can apply to either redirects or non-redirects Happy Editing--IAmChaos22:00, 31 May 2022 (UTC)
Strange bug with Twinkle
Latest comment: 2 years ago7 comments3 people in discussion
I just noticed a strange thing that apparently has been happening with Twinkle for a long time that I just noticed....and I use Twinkle literally hundreds of times a day with expiring drafts. Whenever I opt to select "multiple" CSD criteria, Twinkle adds this to the list of reasons I have chosen in the notice it posts to page creators:
It contained a gallery in the userspace which consisted chiefly of fair use or non-free images. (See section U3 of the criteria for speedy deletion.) For legal reasons, we cannot allow non-free and copyrighted images to be used on user pages, and user pages containing galleries of such images may be eligible for speedy deletion.
I didn't select this reason! And now that I know it's content that is being added to each notice, I can't see that U3 even appears as an option to select in the Twinkle CSD box once you select "multiple" criteria. There are no "U" CSD reasons available because the pages I'm working with are in Draft space, not User space. It is never an appropriate reason, new editors don't add galleries to their drafts, it's not User space and the message states that they have to address this non-existent problem! Do you know why Twinkle would be inserting this reason into otherwise normal editor notices that I post? It's tiresome to have to keep going in and removing this paragraph in each notice and now that I'm aware of it, I see it happening every time I use "multiple" criteria. Thanks for any help you can supply. LizRead!Talk!04:26, 2 June 2022 (UTC)
And it if matters, it's always the same U3 criteria about galleries, it doesn't insert other criteria into the talk page notifications, just this one about galleries in User space. I'm sure the new editors have been puzzled by these warnings about galleries in their draft articles. LizRead!Talk!04:29, 2 June 2022 (UTC)
Okay, one last thing I noticed. Usually with these expiring drafts, I just delete them. But sometimes I forget to uncheck the "Tagging" option and the page is tagged for deletion instead. I just found that that if I tag a page with these two criteria, then neither the CSD tag on the draft page nor the talk page notice includes that U3 criteria. But if I go straight to deletion, and omit the tagging, then the U3 criteria is added to the talk page notice. Really weird. If you can figure this one out, cookies and beer are on me! LizRead!Talk!04:56, 2 June 2022 (UTC)
After about 20 minutes of testing, I think this is a downstream bug. Twinkle uses the wikicode {{subst:db-deleted-multiple|1=Draft:Maqbool ahmed sensei|2=G2|3=G11}}, which seems correct. So I think this is a bug with the template db-deleted-multiple. Twinkle's code base also doesn't have the text "u3" or "It contained a gallery in the userspace" anywhere in it, and this template does, so that's another big clue that the template is at fault. I'll make a post on the template's talk page, Template talk:Db-deleted-multiple. –Novem Linguae (talk) 05:23, 2 June 2022 (UTC)
Please ping me or drop a note on my talk page if it is not fixed. I didn't try to troubleshoot at all; I just hit it with a hammer, and the noise went away. – Jonesey95 (talk) 06:34, 2 June 2022 (UTC)
Abuse report info missing
Latest comment: 2 years ago4 comments3 people in discussion
"Anti-vandalism tools, such as Twinkle, Huggle, and rollback, should not be used to undo changes that are constructive and made in good faith.
If a change is merely "unsatisfactory" in some way, undoing/reverting should not be the first response."
However, there is no information on where to report that. How can I report seeing an instance of Twinkle being abused in that way? 176.62.33.75 (talk) 15:48, 6 June 2022 (UTC)
You could share a WP:DIFF here to get some second opinions. In general if it is an isolated incident, you could try talking to the user on their user talk page. If it's a pattern of behavior, you could escalate somewhere like WP:ANI. I don't recommend ANI for minor things though, there should be some kind of severe, actionable behavioral problem. –Novem Linguae (talk) 17:15, 6 June 2022 (UTC)
Should there be some clarification in that abuse section? I'm gonna go out on a limb here and say that using TW's good-faith revert option is acceptable in reverting good-faith edits. Furthermore, the standard TW revert, if accompanied by a suitable edit summary (which it prompts doing), is acceptable to be used for problematic edits that are not clear vandalism. It's my understanding that any revert without an edit summary, whether performed by the undo function, TW, RW, rollback, etc., implies the edit being reverted is vandalism. And there is at least one exception to that even, like mass revert of banned socks contributions. DB1729 (talk) 17:27, 6 June 2022 (UTC)
I also think that section comes off a bit strong. I'd be fine with you or someone boldly editing it if you think you can improve it. –Novem Linguae (talk) 17:31, 6 June 2022 (UTC)
When I tag an article for BLPPROD because it is an unreferenced BLP, I get a message saying that the tagging may not be applicable because the article is not in the category "Living Persons". That is true but stupid. An editor who creates an unsourced BLP in article space is unlikely to know what categories are, let alone to use them correctly. If the code is checking for the category, it would be more helpful, if it did anything, to ask if it should add the category to the article. Of course the reviewer tagging the article is more likely to know whether the subject is a living person than the originator of the article was. I suggest that either the message be eliminated, or it ask whether to apply the category.
By the way, if I tag the article as A7 instead, it doesn't check whether the article is in any of the applicable categories, and I don't think that it should, because A7, like BLPPROD, is applied to articles that were created by editors who don't know about and use categories. Robert McClenon (talk) 17:54, 12 June 2022 (UTC)
I tried to reproduce this on testwiki. I saw "Please note that only unsourced biographies of living persons are eligible for this tag, narrowly construed.", but it's embedded into something as a quick warning, and doesn't require any extra clicks. Is that what you're talking about, or something else? If something else, please post exact text (so I can search the code for it) or a screenshot. Thanks. –Novem Linguae (talk) 21:31, 12 June 2022 (UTC)
I'm positive I've seen the warning before (its a popup separate from the regular Twinkle box), but I can't reproduce rn, give me a second. Happy Editing--IAmChaos00:19, 13 June 2022 (UTC)
Hello! Twinkle's CSD tagging for {{db-g4}} and {{db-xfd}} should accept talk pages (in any namespace) as a link to the deletion discussion, per the guideline WP:XFD, as requested moves can be deletion discussions. Thanks! 🐶 EpicPupper(he/him | talk)20:53, 22 June 2022 (UTC)
Any interest in adding a preferences option to the Twinkle menu? It's currently buried 2 clicks away, either via opening a module and then clicking the preferences link at the bottom right, or by going to WP:TWINKLE then clicking on the hatnote. It's accessed often enough that I think having it be one click away makes sense. There's a ticket for this on GitHub but it has a "needs consensus" tag. Thanks. –Novem Linguae (talk) 14:40, 14 June 2022 (UTC)
Is there a way to generate the edit-warring report diffs without actually creating the report? Putting the diffs together for an editor on a single page is useful for a bunch of other reports as well, so if there is a way to generate the wiki-code for it quickly without actually creating a report at AN3 that would be super useful. nableezy - 16:46, 18 June 2022 (UTC)
Hey there. You could middle mouse wheel click the "Today at #:## AM" type links, which would open new tabs with those diffs loaded up. If you'd like something different, let's hammer out some details and I'll make a feature request. Details would include a diff of what it'd be useful for, how you want the output (Wikicode?), etc. I'd probably do it as some sort of button or link on the screenshotted screen. –Novem Linguae (talk) 17:39, 18 June 2022 (UTC)
Things like reports of the 1RR violation at AE or diffs used for an ANI report is what I was thinking of. Output would probably have to be wikicode or just saved to a configurable sandbox to modify as needed? Or even an option to generate EW report and not save it to copy and paste as needed. nableezy - 13:59, 19 June 2022 (UTC)
The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion.A summary of the conclusions reached follows.
There is consensus these templates should not be included as default options in the Twinkle welcome template menu. Users who may still wish to use them to welcome newbies may add them themselves to their personal twinkle tool using their custom Twinkle preferences. — Ixtal( T / C ) ⁂ Join WP:FINANCE! 21:39, 23 June 2022 (UTC)
{{Welcome-menu}} and {{Welcome-graphical}} are two of our oldest welcome templates; both were created in 2006 and have changed little since then. For many years, they were included the Twinkle welcome menu as default options. A year ago, I launched a proposal arguing that they were poorly designed and should be removed as defaults (I'll save the rationale for below to keep this section more neutral); it found consensus and the result was implemented. Twinkle allows editors to add custom welcome templates in their preferences menu, so editors who wished to continue using them were able to easily do so. Recently, a few users of those templates who were unaware of the custom option noticed they were missing and asked for them to be restored as defaults. The prior discussion participants were not notified, nor was welcoming committee, but the request was implemented out of process with minimal discussion. I raised this issue above, and an RfC was suggested to help settle the question more firmly. {{u|Sdkb}}talk23:53, 18 May 2022 (UTC)
Survey
No for both. As noted above, any editor is free to use any welcome template with Twinkle by adding it in their preferences. But defaults are powerful, and as welcomes are ultimately for the benefit of the newcomer being welcomed, the Twinkle menu should encourage editors to use our best options.These two templates are among our worst. Newcomers have consistently reported feeling that Wikipedia's guidance is an impenetrable, overwhelming labyrinth, and one of the most valuable functions of a good welcome template is to boil it all down to a streamlined launch ramp of the minimum essentials needed to get started productively. These templates don't do that, instead succumbing to the understandable but deeply flawed impulse to try to list out a quasi-comprehensive directory of every major page.{{Welcome-graphical}} has about 20 links, many of which (such as Wikipedia:Directories and indexes) are themselves lists that spiral out to hundreds of further pages. Many are also redundant. 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 to suggest that a literal book (from 2008) is what you need just to get started?{{Welcome-menu}} 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, particularly for someone who doesn't know how to differentiate between those options like we do; compare it to {{Welcome}}'s straightforward "get help at the Teahouse" button. {{u|Sdkb}}talk23:53, 18 May 2022 (UTC)
No. Ignoring the fact that these menus are out of date, the option to use them still remains available for those who wish to do so, they're just no longer the default option. This seems perfectly reasonable. Patr2016 (talk) 00:49, 19 May 2022 (UTC)
Yes. I do not feel it is Twinkle's role to tell editors which templates to use or not use. I feel Twinkle should include templates that are popular, and there is plenty of evidence that these two templates are popular. For example, a request with multiple participants to have it added back the last time we removed it, and the number of people that have added it to their Twinkle custom template list to basically undo the previous removal. [5][6][7] It's ironic because I agree with shorter welcome templates in principle, for example I always use {{Welcome-short}}, I just don't agree with putting up obstacles to accessing popular templates. I am concerned that there isn't enough support to TFD the templates in question, and that this is being used as a backdoor to deletion. Nothing personal if this RFC passes, I am happy to abide by the results, but those are my thoughts on the matter. –Novem Linguae (talk) 15:24, 19 May 2022 (UTC)
No. Twinkle shouldn't be suggesting these templates are generally and equally appropriate for use as a welcome for any and all new editors. If the templates are still available to use with custom TW preferences, then I see no problem with this proposal. DB1729 (talk) 15:56, 19 May 2022 (UTC)
No. thanks for the ping. These templates are not good for helping most users. I think that part has been made clear by the comments above. These are popular in part because they are defaults. By removing them as defaults, that can lead to welcomers picking other options that are more useful. - JackFromWisconsin (talk | contribs) 16:22, 19 May 2022 (UTC)
No Editors here raise good points, I don't feel the need to type forever to expand excessively. BUT agree with Liz that {{Welcoming}} should go. Happy Editing--IAmChaos16:51, 19 May 2022 (UTC) (edited 03:30, 20 May 2022 (UTC))
Yes I use Welcome-graphical as my default template as do other editors. It is far superior that the horrendous "Welcoming" welcome message which takes up half the new editor's user talk page. That one should go, I never see it used because it is so garish, over-sized and inappropriate. Welcome-graphical is just the right balance of providing links and useful information. Until it was added back, I had to use the cookies Welcome message which was not the message I want to convey, it's more appropriate for a children's website. This is not kindergarten where we are giving out cookies and hot chocolate. LizRead!Talk!23:05, 19 May 2022 (UTC)
@Liz{{welcoming}} should probably go too (never seen it before), but you can stil use {{welcome}}, the main welcome template, or {{welcome-retro}} which is what the cookies welcome is based on (but without the cookies). As Sdkb mentions you can also add custom welcome templates so you can still use graphical in Twinkle if you want. Galobtter (pingó mió) 03:08, 22 May 2022 (UTC)
Let editors make the choice they like. Our newest versions don't work well in mobile view so many lIke ones they know are viable.Moxy-23:21, 21 May 2022 (UTC)
A side note, but having mostly been away from editing for a couple years, one of the things I noticed when I came back was how much better the new welcome template is - I love it. @Sdkb is there a reason other welcome templates haven't been updated in a similar way? Sometimes I want to use something slightly more appropriate but I end up using {{Welcome}} cause it's so much more to the point. Galobtter (pingó mió) 01:14, 19 May 2022 (UTC)
@Galobtter, thanks, I'm glad you like it! The update was controversial enough that I'm not sure how successful you'd be trying to update others similarly. But one change we'll soon have the opportunity to make is finally getting rid of the "please remember to sign your comments with ~~~~" instruction, as it'll be unneeded with the new talk page project features. Rolling that out may be an opportunity to make broader improvements while we're at it. Cheers, {{u|Sdkb}}talk05:11, 19 May 2022 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Anybody want to help with writing code?
Latest comment: 2 years ago2 comments2 people in discussion
Anybody want to help with writing code? I've tagged 5 open tickets with "good first issue". These are super easy and mainly involve editing some configuration variables. The challenging part would be 1) compiling and running the development version so you can test your code (see tutorial here), and 2) if you've never used Git to make branches and submit pull requests before, that could be a pain. I'd be happy to answer any questions if you get stuck. I could probably write patches for about 20 of the open tickets, but I am currently limited on time, so would appreciate any help. –Novem Linguae (talk) 22:38, 23 June 2022 (UTC)
@Novem Linguae, if you want a bunch of very new people to try, you could try listing twinkle at mw:New Developers - honestly, I found just preparing for that to be a good exercise. Fair warning, though, they're very new and might not all stick around. Enterprisey (talk!) 00:32, 24 June 2022 (UTC)
Bug? CSD nomination not logged
Latest comment: 2 years ago3 comments2 people in discussion
Thanks, that should explain it. Well, I don't remember exactly but I nominated 3 pages within a 3 minute window, so that could be a possibility. —CX Zoom[he/him](let's talk • {C•X})21:46, 3 July 2022 (UTC)
AFD displaying success and failed messages despite succeeding
Latest comment: 2 years ago1 comment1 person in discussion
My Twinkle preferences are supposed to be set to watchlist pages that I've tagged for speedy deletion for three months ("watchSpeedyExpiry": "3 months",), but it keeps watchlisting them permanently. For instance, I G5'd Kanthe Gounden Chavadi today and it got indefinitely watchlisted. Is there something I'm doing wrong? Thanks in advance. Extraordinary Writ (talk) 19:43, 4 July 2022 (UTC)
Latest comment: 2 years ago5 comments4 people in discussion
Any objections to me writing a patch to log all Twinkle Javascript errors to a page onwiki? Would be helpful for debugging. I guess it's possible some folks might have privacy concerns so figured I'd check first. The info logged would be the Javascript error message, username, and diff probably. Would help with things like the #AFD displaying success and failed messages despite succeeding section above, which I was unable to reproduce but which was surely triggered by some sort of Javascript error. Thanks. –Novem Linguae (talk) 00:15, 6 July 2022 (UTC)
One thing to be careful about is not using some giant try/catch that then captures actual production issues. JavaScript errors these days are recorded in Logstash and reviewed regularly by the Performance team. I wouldn't want to suppress any errors they were supposed to see. As you know, JS errors can happen for any reason (network problems, something in MediaWiki's core JS modules, etc.). Similarly I suspect we might see a lot of noise, but perhaps you were intending on only logging certain things and not just anything. Typically when users report problems we send them to WP:JSERROR. Speaking of which, I think WP:CONSOLEERROR is a nice essay but I wonder if it be merged into the longstanding WP:JSERROR?
Roger that. The try/catch issue sounds solvable by catching the error, logging it, then re-throwing it. But I'll probably abandon this as going to VPT seems like a lot of work. I went ahead and merged the essays though. Thanks for sharing your expertise. –Novem Linguae (talk) 11:02, 6 July 2022 (UTC)
Worth noting that such a move would've been the first of its kind AFAIK, unprecedented for a gadget. ~ Amory(u • t • c)11:42, 6 July 2022 (UTC)
Error logging is difficult. Putting everything in try/catch wouldn't really catch anything useful as most errors take place in asynchronous contexts. (Not to mention that re-throwing errors removes stack trace data.) – SD0001 (talk) 20:15, 6 July 2022 (UTC)
Self-contradictory tag
Latest comment: 2 years ago2 comments2 people in discussion
Hello friend. Is this in regards to Twinkle Global? You should probably report these at meta:User talk:Xiplus/TwinkleGlobal. Also I do not understand your bug report. When you copy this to the Twinkle Global page, you may want to be more specific about what you are expecting to see and what you are actually seeing. You're talking about rollback so I thought you were talking about the red "Rollback" links that show up in diffs, but your two screenshots are of a contribs page. Hope that helps. –Novem Linguae (talk) 05:08, 12 July 2022 (UTC)
Latest comment: 2 years ago9 comments3 people in discussion
I have installed Twinkle both locally and globally, and I have noticed significant differences between those versions (local has significantly more features). Does anyone know why this is? – Ilovemydoodle (talk) 17:56, 7 July 2022 (UTC)
Perhaps Twinkle Global was forked from an earlier version of Twinkle Local, then development stopped. Can you provide a link to your global versíon of Twinkle and I'll take a look? What features are missing? –Novem Linguae (talk) 19:05, 7 July 2022 (UTC)
Doing some wiki archaeology, I'm going to guess these are the two diffs I need: WMTR code at time of error and input data: {{RMassist/core | 1 = We Make You ( EP) | 2 = We Make You (EP) | discuss = yes | reason = Extraneous spacing. | sig = –[[User:LaundryPizza03|<b style="color:#77b">Laundry</b><b style="color:#fb0">Pizza</b><b style="color:#b00">03</b>]] ([[User talk:LaundryPizza03|<span style="color:#0d0">d</span>]][[Special:Contribs/LaundryPizza03|<span style="color:#0bf">c̄</span>]]) 12:08, 15 July 2022 (UTC) | requester = LaundryPizza03}}. Testing on testwiki, be right back. –Novem Linguae (talk) 20:14, 15 July 2022 (UTC)
@John of Reading. Yeap, you're right. I just checked the code, Twinkle looks for ---- and enter on a new line.* -->, with .* being a wildcard. So the ---- that was deleted threw it off. I've gone ahead and written a patch that will not be quite as dependent on ----. Once it's deployed in a couple months, we'll be able to change that comment to whatever we like, as long as it stays one comment. (Two comments would throw it off.) –Novem Linguae (talk) 20:20, 15 July 2022 (UTC)
Notice: update to Template:Primary sources
Latest comment: 2 years ago4 comments2 people in discussion
@Novem Linguae:, I'm unfortunately rather ignorant about Twinkle, but maybe Sdkb or Wikmoz or Trialpears will know more about this. My guess is that you don't need to patch anything, because although this changes default behavior (adds new links that weren't there before), no previous invocation will break with any combination of params (valid or invalid) that didn't break previously (see test cases here). A breaking change, would be something like removing or renaming a named param, or switching the order of positional params, or interpolating a new one, or changing the behavior of a previously existing param. And this change doesn't do any of that. Hope this helps, and that one of the pingees (is that a word?) will be able to comment. Mathglot (talk) 08:26, 17 July 2022 (UTC)
Thank you so much i really appreciate. Are there any relevant boxes to click that will help a new editor like me? Uricdivine (talk) 19:30, 17 July 2022 (UTC)
Hey there. For TwinkleMobile, I'd recommend posting at their talk page, User talk:P.T.Đ/TwinkleMobile. Please give lots of details. What page were you on? What did you click? What did you expect to happen? What actually happened? Any screenshot? Hope that helps. –Novem Linguae (talk) 20:57, 17 July 2022 (UTC)
I've made a template, {{Mentor welcome}}, hoping to use Twinkles custom welcome template feature. However, when I go to a mentees talk page, I can't find the template in the welcome module. The template also disappears from the custom welcome template page when I refresh. I'm pretty sure the underlying problem exists between my behind and the computer monitor, but I have no idea how to troubleshoot it. Can anyone help? I dream of horses(Contribs)(Talk)00:15, 28 July 2022 (UTC)
I just added it to mine okay. Keep in mind you have to save both the custom welcome popup AND the twinkle pref page. Schazjmd(talk)00:23, 28 July 2022 (UTC)
Could implement this as a "Notice: More than 10 redirects will be orphaned if this page is deleted." message as the first comment in the AFD. I think this would need consensus though. –Novem Linguae (talk) 07:27, 18 July 2022 (UTC)
Wouldn't this be better for a bot since not all AFDs go through Twinkle? If this is done, it would be better to be uniform across all nominations. MB05:52, 20 July 2022 (UTC)
Maybe I missed something obvious, but why do we need to tag/mention the redirects to a page? When an AFD is closed, any admin worth their salt is going to be using the "also delete redirects" option; it doesn't really matter how many redirects are pointing at a page, as they will all be deleted anyway (and semi-automatically, if using something like WP:XFDC). Primefac (talk) 09:31, 21 July 2022 (UTC)
I think the point is that the incomming redirects could be a consideration in determining if an article should be deleted. MB16:50, 21 July 2022 (UTC)
Bug report in Discord: Does anyone else know why Twinkle seems to be leaving double warnings? I leave a single warning, and it makes 2 edits for some annoying reasonPadgriffin
Padgriffin, is this only happening with certain templates? Is this only happening when the user talk page doesn't already exist? Does this only happen when you visit the user talk page after a rollback? What skin are you using? Any other clues that could help me make this reproducible?
@Novem Linguae My skin is Vector legacy and the issue can be reproduced. It appears to happen when I attempt to exit the page (such as to Recent Changes) while Twinkle is warning the user, which triggers a "save failed" prompt despite actually succeeding, leading to double warnings. My browser is Firefox 103.0.1. PadgriffinGriffin's Nest04:49, 2 August 2022 (UTC)
Sounds like you're switching pages before Twinkle is done with its warning algorithm. Is the fix as simple as waiting a few more seconds until you see "done" in the popup?
Steps to reproduce: Open Twinkle warn menu > Submit warning > attempt to exit the page as the "retrieving page" message is on-screen to something that takes a bit longer to load (i.e. recent changes). Twinkle will then output "Save failed, retrying in two seconds", which results in duplicate warnings being made. PadgriffinGriffin's Nest07:07, 2 August 2022 (UTC)
Thanks for the steps. Was unable to reproduce, perhaps it's going too fast for me to navigate away at the right spot. When the error happens, are you navigating away from the page before or after you see "Warning complete, reloading talk page in a few seconds"? –Novem Linguae (talk) 07:41, 2 August 2022 (UTC)
Have you tried waiting for the "warning complete" message? Navigating away before that I would expect to be buggy, as it would interrupt Twinkle. Unless the "warning complete" message doesn't show for some reason, which would of course be a bug. –Novem Linguae (talk) 08:52, 2 August 2022 (UTC)
Yep, it's fine if I wait- the weird part is that I've been using Twinkle for years at this point like this (almost always triggering the "save failed" message) yet Twinkle has never done this prior to July 31st. PadgriffinGriffin's Nest09:04, 2 August 2022 (UTC)
I can reproduce it [12]. Step: 1. Submit warning > 2. Go to another page (for example clicking the logo). It make the API call be canceled > 3. Press ESC to stop page loading. It make js keep running, so the error handling code runs. Xiplus (talk) 09:34, 2 August 2022 (UTC)
Inconsistent tab display in Vector 2022
Latest comment: 2 years ago2 comments2 people in discussion
Twinkle's label is large and bold compared to other tabs in Vector 2022. It looks like the issue is the fact it uses a nav and h3 rather than div and label. Jdlrobson (talk) 16:01, 8 August 2022 (UTC)
Latest comment: 2 years ago3 comments2 people in discussion
I have been noticing problems with my twinkle, whene I enter page to warn (and other twinkle related things) a user my twinkle doesn't show. So I went to twinkle page and saw "is twinkle loading unreliably?" That I should remove this importScript('User:AzaToth/twinkle.js'); but it isn't in my own. Please what should I do?. UricdivineTalkToMe23:52, 8 August 2022 (UTC)
@Uricdivine. Hey there. 1) If you are loading Twinkle via importScript('User:AzaToth/twinkle.js'); in your common.js, I recommend removing that, then going to Preferences -> Gadgets, checking the box for Twinkle, then clicking "Save". 2) when I enter page to warn, is this right after a rollback? If so, wait a couple seconds until the "talk" link turns bold. Twinkle takes several seconds to load. Hope that helps. –Novem Linguae (talk) 10:21, 9 August 2022 (UTC)
@Novem Linguae Thanks for your reply and sorry for my very late own. I tried doing it but am a mobile user so importScript('User:AzaToth/twinkle.js'); isn't in my own. But the problem is still persisting and is getting worst. I have raised thr matter in wikipedia twinkle mobile tage page. UricdivineTalkToMe18:30, 12 August 2022 (UTC)
Suggestion for improving block module displayed text
Latest comment: 2 years ago2 comments2 people in discussion
I do realise this is a minor gripe, but is it possible to match up the "Template options" prompt with the actual template being used? For example, the {{uw-block}} prompt says "You have been blocked for..." ? followed by the prompt box, but the template code gives Your account has been blocked... because your username <reason from prompt box>, meaning I have to frequently rewrite my reason after preview. If this isn't possible, it's not the end of the world, but if there's a semi-easy fix I'd love for it to be implemented. Primefac (talk) 16:38, 14 August 2022 (UTC)
edit: forgot to note, the French wiki version of Clearstream is explicit about there being two Clearstream affairs. The first real, the second faked. This reality fails to make the translation. Given the absolute centrality of clearing houses such as Clearstream, this is no idle edit distinction - this English wiki page informs public discourse around existential corruption, on a global scale. It needs to more faithfully reflect origins e.g. extensive French press coverage, eg Denis Robert, et al. — Preceding unsigned comment added by Jasonbrown1965 (talk • contribs) 06:11, 22 October 2022 (UTC)
Jasonbrown1965. Hey there, and welcome to Wikipedia. To add a reference, try editing the page. There are two different editors: the wikitext editor and the visual editor. Make sure you're using the visual editor. Then click the spot you want to add a reference, and click "cite" in the toolbar. A little window pops up. Click automatic, paste a URL, then click Generate. Then click Insert. Then click Publish Changes. Hope that helps. –Novem Linguae (talk) 06:41, 22 October 2022 (UTC)
sanitized-css now gets prot templates and noincludes
Latest comment: 2 years ago4 comments2 people in discussion
Actually, for all 3 content models, I don't see a reason for noincluding the contents of the comments that add the protection template. What caused that to be the mode of addition? Izno (talk) 06:52, 18 August 2022 (UTC)
Ah, it's supposed to trigger off whether noinclude is selected in the GUI, but I didn't touch the option. Is it perhaps the default in the TE protection profile? That would explain that. It might make sense not to make that the default or relevant at all for these content models. --Izno (talk) 06:57, 18 August 2022 (UTC)
Latest comment: 2 years ago9 comments2 people in discussion
screenshot
Hello, am a mobile editor using twinkle. As of recent, I began noticing that twinkle has not been loading on most of the pages I visit. Please help UricdivineTalkToMe18:04, 17 August 2022 (UTC)
It may be helpful to look at your WP:CONSOLEERRORs before visiting that other talk page. WP:CONSOLEERROR is an essay I wrote on how to look for error messages. These error messages help software engineers find and fix bugs. –Novem Linguae (talk) 11:57, 18 August 2022 (UTC)
Novem Linguae, honestly, the reason I didn't want to try it first is because when I first tapped the link I saw things that only desktop and computer users can do. Unless as a mobile editor can I still report bugs?. UricdivineTalkToMe12:03, 18 August 2022 (UTC)
Latest comment: 2 years ago10 comments7 people in discussion
When warning someone, why is the additional message placed in italics, when the warning templates do not have that behavior? I could not find a setting to toggle that behavior, so I have to edit again to remove the italics, which is incredibly annoying. {{u|Bowler the Carmine}} (he/him | talk) 22:36, 14 August 2022 (UTC)
Would be easy to remove if there is consensus. I don't mind the italics though. Talk page watchers, does anyone else want this removed? –Novem Linguae (talk) 23:19, 14 August 2022 (UTC)
Sometimes when I add an extra message, I re-edit the talk page to either remove the italic or change it to bold to differentiate it from the templated text. When I read a templated warning on a talk page, I find it really easy to overlook the text in italic at the end; maybe that's just me. Schazjmd(talk)23:27, 14 August 2022 (UTC)
Yes, remove the italics. Let users decide for themselves what, if any, additional markup they'd like to include. (For me, personally, I usually want the added text to be bold.) MANdARAX XAЯAbИAM 00:10, 15 August 2022 (UTC)
Italics in warnings: I'm a keep, two people are a remove, two people were unclear what their preferences were in their comments. Any other opinions? –Novem Linguae (talk) 08:46, 18 August 2022 (UTC)
This problem would solve itself if we replaced the additional message by an option to edit the wikitext of the entire message. Editors could then add italics, bold or a flashing neon marquee as appropriate. It would also bring other benefits, such as allowing us to tailor text such as "you may have added/deleted/altered text in one or more articles or other pages" into something that looks as if it was written by a human without doing a separate follow-up edit. Certes (talk) 08:57, 18 August 2022 (UTC)
I am more in favour of resolving #1048/#1517. Let's allow folks to edit the full message – so that they can append text with whatever markup they like, or remove existing stuff from the template. This will remove the need for the additional message field. – SD0001 (talk) 13:58, 18 August 2022 (UTC)
Patrolling with Twinkle
Latest comment: 2 years ago6 comments3 people in discussion
Here is something that seems inconsistent. When reviewing/patrolling redirects, I use the curation tool. If I want to add a Rcat (and its one Twinkle knows about), I click on the Tag/Twinkle tab. I add the Rcat and mark it reviewed at the same time by clicking those two choices, then hit "Submit Query" one time (done in four clicks). If the redirect is auto-created from a page move, it already has a Rcat (R from move). If I go to Twinkle to add a second Rcat, there is no choice to mark it reviewed, so I have to go back to the curation tool and review it there (two steps, five clicks total). Not a big deal, I can still move pretty fast. But still, why is the option to review these redirects missing? It seems to be related to the move. MB03:33, 28 August 2022 (UTC)
It seems to happen with any redirect in the queue that is there due to a move. Right now, Tonggeun is the oldest redirect. MB04:44, 28 August 2022 (UTC)
@MB and Novem Linguae:I've tried to replicate this but I' still not sure what is meant by the 'move' situation. In any case, IMO it's a feature that should be in the Curation Tool. I've made an entry for it at here. Kudpung กุดผึ้ง (talk) 05:50, 28 August 2022 (UTC)
@Novem Linguae, do you have enough to go on. The above example won't work anymore because it was patrolled recently. Just find any unreviewed redirect in the queue that was created by a move. The next one is Star Movies India. MB16:43, 28 August 2022 (UTC)
Yeap I figured it out. It is this bug. Busy month for me (real life job stuff) so I may not be able to work on it right away. But it's in the queue. Thanks for reporting. –Novem Linguae (talk) 17:04, 28 August 2022 (UTC)
Unlink enhancement
Latest comment: 2 years ago2 comments2 people in discussion
When an article is deleted and backlinks are removed with the Unlink module, I presume it uses "What links here" to generate a list of articles linking to the target, and then scans the source code of those articles for [[target]] and removes the brackets.
If the link is in a hatnote, there are no brackets and Twinkle issues this message: Unlinking in page "pagename": Didn't find any backlinks on the page. After the article is deleted, there is a Redlink hatnote and the article gets added to the 8,000+ already in Category:Articles with hatnote templates targeting a nonexistent page for someone to clean up later.
If feasible, could Twinkle scan the source code for the target within a hatnote template (there are a lot of them) and if found, issue a message like "Target" is linked in "pagename" via a hatnote, this page must be manually edited to remove the link. The removal would be difficult to automate because sometimes the entire hatnote is removed and other times it is just modified.
Also note that the target could be both in a bracketed wikilink and a hatnote, so to be fully effective, hatnote scanning would have to be done in all cases, not just if no link is found.
If this is not possible, I guess changing the message to say Unlinking in page "pagename": Didn't find any backlinks on the page, the links are probable in hatnotes and must be removed manually might help. MB18:48, 5 September 2022 (UTC)
Latest comment: 2 years ago1 comment1 person in discussion
Based on this discussion, how easy would it be to drop the [[WP:CSD#G6|G6]]: code from Twinkle summaries when deleting via "XFD" option (in the dropdown) or when {{db-xfd}} is used? Primefac (talk)
Easy to code, but not great for maintainability. Coding exceptions to things can be a bit of a code smell as it adds complexity to an otherwise straightforward system. The relevant code is here. Let me know if you decide to move forward and I can create a GitHub issue. –Novem Linguae (talk) 10:32, 7 September 2022 (UTC)
Authority control
Latest comment: 2 years ago2 comments2 people in discussion
A selective bolding proposal at Uw-copyright-new may interest Twinkle users; your feedback requested
Latest comment: 2 years ago1 comment1 person in discussion
Template:Uw-copyright-new is a "gentle" variant of {{uw-copyright}} for new users. This is one of those single-use advice/user-warning templates that has a few bullet points of text between a header and footer; there are many others of that ilk; {{uw-coi}} comes to mind.
Via happy serendipity, an enhancement has been proposed that would allow the transcluder to do some simple style enhancements of the generated text, notably, bolding one of the bullet items, and perhaps a bit more. If the proposal is adopted and gains use, this could be a paradigm for updating other user warning templates in a similar manner, so getting the UX and functionality right for this initial use case could make life easier and possibly provide a consistent approach for other templates down the road. As a Twinkle user who may see such options popping up on this and/or other user warning templates in the future, your feedback would be welcome at Template talk:Uw-copyright-new#Adding bold style to bullet items or text. Thanks, Mathglot (talk) 22:08, 7 October 2022 (UTC)
Remove db-g13
Latest comment: 2 years ago2 comments2 people in discussion
The "Unlink backlinks" current description dialogue is confusing:
This tool allows you to unlink all incoming links ("backlinks") that point to this page. For instance, [[San Jose de Buenavista|link text]] would become link text and [[San Jose de Buenavista]] would become San Jose de Buenavista. Use it with caution.
The description does not mention that it will look for such backlinks in other articles and not on the page itself. My understanding was that the feature was to remove within the San Jose de Buenavista page all links redirecting to it. I had tried using the feature on San Jose de Buenavista with the intent to delink several table links within the Barangays section, like Atabay and Badiang, which is a redirect to the San Jose de Buenavista article. Upon clicking the "Unlink backlinks" link, the link checkboxes that Twinkle later showed did not make it clear to me what were supposed to happen to them; should these links within the San Jose de Buenavista article be delinked if they redirect to the article? I assumed it would remove the redirects so I clicked, and was surprised it unlinked all links of San Jose de Buenavista in all those articles which had their checkboxes checked. I already reverted the automated mass edits which I had misunderstood. I suggest adding a more specific dialogue description and mentioning redirects will help in avoiding similar potential mass edit mistakes:
This tool allows you to unlink all incoming links ("backlinks") from the checked pages below that point to this page.
I support this change. We use too much jargon that sometimes we forget how difficult it is to overcome that mountain of words. (Links to this article within this article are called selflinks.) - UtherSRG(talk)15:50, 18 October 2022 (UTC)
I feel that when reporting a user to WP:UAA, this option should be removed as UAA is not for usernames that only imply shared use. Either that or it should be merged with the option for a promotional username as I usually only see the 2 used together. ― Blaze WolfTalkBlaze Wolf#654516:42, 19 October 2022 (UTC)
Sorry if this is off-topic for Twinkle, but is there any advice anywhere on how to handle usernames which fall short of "blatant and serious violations of the username policy requiring an immediate block"? For example, what should I do with User:AmalgamatedWidgets? Certes (talk) 18:15, 19 October 2022 (UTC)
The little known noticeboard WP:RFC/NAME exists for reporting more complex cases of violation of the username policy. Usually that's where experienced users get dragged to. Not sure if that helps with new, promotional usernames but figured I'd mention it. –Novem Linguae (talk) 18:28, 19 October 2022 (UTC)
I think the reason why most people don't go there with experienced users is because usually if they're experienced and have the username, there are likely no issues with it. ― Blaze WolfTalkBlaze Wolf#654518:29, 19 October 2022 (UTC)
Latest comment: 2 years ago2 comments2 people in discussion
What happened to the option of adding stub tags to article in Twinkle? It used to be there but hasn't been for many years it seems (I haven't seen it at all since I started using this account, I only vaguely remember it with my previous account from 2017). Taking Out The Trash (talk) 01:55, 20 October 2022 (UTC)
Custom welcomes vs Default welcomes and signatures
Latest comment: 2 years ago3 comments2 people in discussion
For the default welcomes just the template is posted but for custom welcomes an extra signature is added. I thought I had reported before last time "W-graphical" was removed but I can't find it so maybe I forgot :/
As most welcome templates have a signature imbedded this just look odd — example.
By default I think the behaviour of default vs custom should be the same, although ideally an optional to add a signature or not on customs would be the best solution. Thoughts? KylieTastic (talk) 18:09, 19 October 2022 (UTC)
Latest comment: 2 years ago9 comments5 people in discussion
Hello, Twinkle folks,
I tried to leave my standard Welcome message and it was gone from the list of commonly used messages. It was called "graphical". Did you remove this for some reason? I must use it a couple of dozen times a day. I work with drafts and welcome dozens of new editors whose draft have gone stale. Could you please return it to the list of commonly used Welcome messages? I probably welcome more new editors than anyone outside of AFC reviewers so I'd like it to be there. Thank you. LizRead!Talk!19:28, 18 October 2022 (UTC)
Just look at any page of my Contributions and do a search for "Welcome" and you can see all of the Welcome messages I post (many also for the Teahouse). Unless a template has been deleted, I think some consideration is due those who use these features the most. I don't care for the other options that are available and I know other editors who welcome new users, especially those who review drafts, favor this template over the others as well so it's not just my preference. Please put it back. Thanks. LizRead!Talk!19:34, 18 October 2022 (UTC)
Hey @Liz. Yes we were forced to remove it because of an RFC. I apologize for the inconvenience.
Thanks for the ping/heads up, NL! @Liz, I see you participated in the RfC, but I know it can get hard to keep track. As a reminder, you're free to add it as a custom welcome in your Twinkle settings so that you can continue to use it, although I hope you'll take into consideration the reasons we removed it and choose a friendlier alternative for the newcomers you welcome. {{u|Sdkb}}talk01:18, 19 October 2022 (UTC)
Well I did not see the RfC but I was one who was annoyed last time it was removed. Just doing a rough query me and Liz who both use {{Welcome-graphical}} a lot are the 2nd and 4th twinkle welcomers. Also I note from the last complaintPeaceray the 3rd on the list complained about the removal. Us three make 835 twinkle welcomes and I've been on a semi break. On the other hand Sdkb has 4 uses! Also I have seen other AfC reviewers using "graphical" - but I cant remember who. A quick check of the others who said remove in the "RfC" had the following uses: 0, 0, 18, 0, 1 & 0. So basically we have those who don't use a tool determining the functionality for those that do use! I would also note that the Wikipedia:Welcoming committee has graphical in the main three listed {{Welcome}}, {{W-basic}} and {{W-graphical}} and suggests using Twinkle so now makes no sense. I did think about working out amongst all the actual uses which templates were used and how many each, but frankly I can't be bothered. KylieTastic (talk) 08:55, 19 October 2022 (UTC)
@KylieTastic: I've certainly welcomed way more than four newcomers, so I'd suggest your query needs some adjusting. I also have to strongly dispute your implication that I'm some outsider unqualified to work in this area — template design is one of my main focus areas, having worked on dozens of rewrites, as is newcomer help, being an active Teahouse host and the primary maintainer of the introductory tutorial series. The proposal was backed by widely recognized usability principles and was persuasive enough that we reached a consensus in a widely advertised RfC. {{u|Sdkb}}talk13:19, 19 October 2022 (UTC)
Hi Sdkb, to clarify the query is only welcomes via Twinkle and only in the recent edits table so ~last 30 days, and per those parameters you have four. I was not implying anything other than I actually said. My point was the RfC did not appear to come to the attention of many of the actual users ending up with just 7 people who had used Twinkle just 24 times to welcome in the last 30 days were telling 3 people with 835 twinkle welcomes in the last 30 days we're wrong. — I find welcomes are subjective, conditional and personal. I find {{Welcome}} personally non-helpful as Help:Introduction is already on the side bar and I welcome people after an AfC review so have already added a Teahouse invite and whilst I agree the Wikipedia:Task Center is a good link for someone very new who does not know where to start, I find not so appropriate for someone already submitting draft articles. I don't like {{welcome-retro}} as I don't like the invite to come to the welcomers talk page as I think the Teahouse is much more appropriate. {{welcome-short}} is friendly but again I do not find very helpful. {{welcome-cookie}} I just personally don't like the image or the disguised links to Help:Getting started (I think links should be obvious in a welcome) and again an invite to the welcomers talk page. {{welcoming}} is generally fine but I find the style of {{W-graphical}} easier to use and what I would prefer to have got. I don't think 20 links is too many as they are in clear groupings and only slightly more than {{welcoming}} which does not tell people to sign messages or use edit summaries something many new users need to be told about. Also {{W-graphical}} has a links to Help:Cheatsheet and Wikipedia:Five pillars that I think are very good additions. Although I agree it could be improved such as Help:Editing could be changed to Help:Introduction to editing with Wiki Markup/1 etc. I can perfectly understand why some prefer {{Welcome}} or {{welcome-short}} as a good basic welcomes but I can also see, as it is what I would have preferred, {{welcoming}} or {{W-graphical}}. Regards KylieTastic (talk) 14:51, 19 October 2022 (UTC)
That RFC is a load of BOLLOCKS. The arguments to remove it were based on irrelevant reasoning, and both are well used. Welcome graphical is the best we've got. I've had to fork other templates to make versions that are either all signed, or all unsigned, to allow the custom templates thing to work. Pfft. Had my whinge. Mako001 (C) (T) 🇺🇦 12:21, 22 October 2022 (UTC)
Latest comment: 2 years ago1 comment1 person in discussion
How safe is it to +2 the dependabot patches such as [14]? I notice that all the dependencies are "dev dependencies", so in theory it should be pretty safe. But we have no end to end tests so want to double check first. Thanks. –Novem Linguae (talk) 12:34, 26 October 2022 (UTC)
Default preferences
Latest comment: 2 years ago4 comments4 people in discussion
Hello! So I was recently made aware that the default Twinkle preferences are to not notify the user upon speedying a redirect for R3. Why? This makes absolutely no sense. You should always notify the user when speedying anything except for maybe G5. I think this should be changed so that the default is to notify the user automatically. ― Blaze WolfTalkBlaze Wolf#654513:13, 26 October 2022 (UTC)
The other day I tagged an empty category for deletion (C1). I distinctly remember seeing "Notify page creator if possible" box was checked in the pop-up before applying the tag. Soon after, I got this message from an admin.
I did a dry run test to confirm the box in the TW pop-up window was being ticked. Then I went into my Twinkle settings and discovered that notify creator for C1 was unchecked for some reason. I updated my settings and hopefully that fixes the problem.
The hover-over explanation in the pop-up window reads A notification template will be placed on the talk page of the creator, IF you have a notification enabled for the criterion you choose AND this box is checked. This is unexpected behavior.
Instead, the box in the pop-up should match your settings. In other words, if notify for C1 is disabled in settings, then the pop-up box should start out unticked. Then if the user ticks the notify user box to override their settings, Twinkle interprets this as the user wishes to override their settings and TW notifies the creator. Wouldn't this be more helpful and make more sense?
Also, why was notify for C1 disabled in my settings in this first place? I don't remember ever changing it. Shouldn't the default be to always notify the creator for any deletion nomination? --DB1729talk13:41, 31 October 2022 (UTC)
Hey there. Thanks for the ideas. This is actually two issues. Issue #1 is the unintuitive check box behavior. I agree that should be fixed and just now I made a ticket for that. Issue #2 is CSD C1 defaulting to not notify. I wrote a patch for that one and submitted it for approval. Hope that helps. –Novem Linguae (talk) 12:45, 2 November 2022 (UTC)
Thank you. After posting the above, I noticed the section Wikipedia talk:Twinkle#Default preferences. (The recent multiple complaints makes me wonder if something changed lately?) The op states You should always notify the user when speedying anything except for maybe G5. I agree with that and also add as an exception U1. There is no need to notify yourself.DB1729talk13:43, 2 November 2022 (UTC)
I cannot change the documentation because it is used in 77 other locations, and the /doc says to use |page=. I totally get your logic, but when I go to a template and need to customise it, I shouldn't have to look at its code to know why putting |page= (as the /doc tells me) doesn't work. Primefac (talk) 13:24, 2 November 2022 (UTC)
Another idea might be to code the template to accept both page and area. Perhaps this is easiest. Then we dont have to change Twinkle nor the documentation. Thoughts? –Novem Linguae (talk) 16:15, 2 November 2022 (UTC)
I think I'm probably the only person to have manually used the template; will leave be now that there's a new /doc. Primefac (talk) 17:14, 2 November 2022 (UTC)
Video tutorial
Latest comment: 2 years ago2 comments2 people in discussion
Advice of non-breaking changes to Uw-copyright-new
Latest comment: 2 years ago1 comment1 person in discussion
A new version of Template:Uw-copyright-new (as mentioned in the discussion above) with non-breaking changes has just been released. No changes should be required to the Twinkle installation, but if you wish to take advantage of the new features, please see the /doc page. Thanks, Mathglot (talk) 23:34, 8 November 2022 (UTC)
Twinkle links category without suppression on user talk page
Latest comment: 2 years ago3 comments3 people in discussion
In this COI notice[15] Twinkle linked a category on the user's talk page. This categorized the page, contrary to WP:USERNOCAT. Twinkle should automatically disable the category function on any category links by adding a leading colon, like I did manually here.[16] --DB1729talk02:45, 15 November 2022 (UTC)
Looks like some warning templates add a colon and some do not. Because some warning templates do add a colon, having Twinkle add a colon risks a double colon situation where this incorrect output is given: Hello, I'm Novem Linguae. I wanted to let you know that one or more of your recent contributions to [[::Test]] have been undone because they did not appear constructive. Anyway, I think it'd be best to fix these template-by-template. I'll put in an edit request at {{Uw-coi}}. –Novem Linguae (talk) 16:55, 15 November 2022 (UTC)
Twinkle is free sofwre?
Latest comment: 2 years ago5 comments4 people in discussion
Is it possible and/or advisable to add speedy deletion templates below #REDIRECT?
Latest comment: 2 years ago7 comments6 people in discussion
On redirect pages, is it possible and/or advisable to add speedy deletion templates below the #REDIRECT instead of above them? Putting the CSD templates above the #REDIRECT line breaks the redirect and causes the pages to show up in various error reports and categories that they should not appear in. Please see Template talk:Db-meta#Request for more information. – Jonesey95 (talk) 19:27, 15 November 2022 (UTC)
My first impression is that putting CSD and RFD templates above REDIRECT is preferrable, because we want them to be broken. If a page is up for CSD or RFD, we probably want editors to see this, rather than just being passed through to the target page. I'm open to being convinced otherwise though. –Novem Linguae (talk) 14:44, 27 November 2022 (UTC)
What works best for our readers? Probably a working redirect. On the other hand, if a redirect really deserves deletion, there may be no readers. Certes (talk) 17:19, 27 November 2022 (UTC)
But it is quite intentional that a redirect be "broken". The template displays a message asking for input on the discussion. And it gives a link to click on if the reader does not want to participate and just continue to the existing target. If there is really any serious thought about changing this, there should be a discussion, probably at WT:RFD, not here. MB18:45, 27 November 2022 (UTC)
I believe that this discussion largely stems from the db-meta discussion; since this section seems to be moving towards a consensus against change it probably makes sense to move back to the db discussion. Primefac (talk) 11:18, 28 November 2022 (UTC)
Adding rcat shell
Latest comment: 2 years ago11 comments4 people in discussion
In an edit like this, Twinkle just adds the rcat shell, with the summary "Addingrcat [sic] shell to redirect". Something like "Adding {{Redirect category shell}} to redirect" would be better. To reproduce: use Twinkle's tag function on a redirect. Just pressing 'done' gives an error, but it works if you select the rcats that are already on the redirect, to tag it with. — Qwerfjkltalk09:46, 26 October 2022 (UTC)
I have wondered if there was a way to add the rcat shell without adding a rcat. Could there be an option in the RCAT menu to just add it, so you wouldn't have go to the trouble of selecting an existing rcat? Alternatively, would it be better just to have a bot add this in the background to all redirects where it is missing? MB14:57, 26 October 2022 (UTC)
I've been using the workaround described above, but that doesn't quite do the job. For example, if the redirect has a tag "r from misspelling" and you select the same tag in Twinkle hoping to add the rcat shell, Twinkle adds the shell and "R from misspelling" - you get two tags due to the different capitalization. So it would be best to have an option to specifically add the rcat shell. I think this would be as simple as another choice in the tag list that said "{{Rcat shell}}: add Rcat shell to existing tags". Twinkle would just have to check that 1) the shell wasn't already present and 2) there are existing tags. If both conditions are met, add it. MB05:18, 4 December 2022 (UTC)
I created a ticket for the case insensitive thing. I agree with both these ticket ideas. Just need a volunteer to carve out time to write a patch, and possibly rewrite the old redirect detection code, which I hear is in bad shape. –Novem Linguae (talk) 01:22, 5 December 2022 (UTC)
That was just an example. The same thing happens with redirect rcats, like {{r from alternate name}} and {{r from alternative name}}. If the ability to add the shell is added, there would be no reason to select existing rcats and this whole issue of similar templates can just be avoided. This would only be an issue if you selected an existing one by mistake and the actual existing template was not exactly the same. I would think that would be so rare that it could be left to the user to just removed the dup manually. Definitely very low priority. MB01:33, 5 December 2022 (UTC)
Clarification of "no bot" message in documentation
@Paine Ellsworth, we are not talking about adding to all redirects (those without parameters). This is about adding when it is missing, i.e. there is one or more rcats already there but they are not wrapped in the shell. MB20:41, 26 October 2022 (UTC)
Adding the shell to a redirect that already has rcat templates in order to wrap those rcat templates within the Rcat shell sounds okay to me. We just don't want to have a bot add this in the background to all redirects where it is missing, nor use a bot or other automated process to add the rcat shell without adding a rcat if the shell has no rcat templates to begin with. P.I. Ellsworth , ed.put'r there20:56, 26 October 2022 (UTC)
db-error
Latest comment: 2 years ago3 comments3 people in discussion
I usually just choose the "G6: Housekeeping and non-controversial cleanup" option and write "created in error" in the text box. It would be nice to have a specific "created in error" option, though. – Jonesey95 (talk) 15:54, 14 December 2022 (UTC)
Latest comment: 2 years ago4 comments2 people in discussion
Hello, Twinkle folks,
I use Twinkle to delete pages and have been doing so in the same way for a few years now. Today, I'm getting a big red error message when doing so that says:
Building deletion summary: error "error" occurred while contacting the API. (null)
Sometimes I can delete the page if I refresh the page a few times but mostly I get a Twinkle box with this message in red. I use Twinkle every day for both CSD and PROD page deletions so it would be nice if it would get back to working in its usual efficient way. Thanks for looking into this. LizRead!Talk!18:09, 18 December 2022 (UTC)
Yes, everything is working fine now. I had thought it was a system problem, not a Twinkle problem, but that's where I saw the error message so I posted here. Thanks for the additional information. LizRead!Talk!20:37, 18 December 2022 (UTC)
Minor feature request: Jump to section from XFD edit summary
Latest comment: 2 years ago3 comments2 people in discussion
When creating a TFD, the TFD page is edited by Twinkle, with the edit summary, "Adding Template:WPBannerMeta/Archive 13" (see Special:Diff/1128892182). It should be modified to /* Template:WPBannerMeta/Archive 13 */ Adding [[Template:WPBannerMeta/Archive 13]], so that it creates a jump to section link which we can click on to go directly to the relevant section when looking at it from user contribs or page history, instead of having to searching in the entire page. The remaining edits made by Twinkle for a nomination already include a jump to section link in it, e.g., nominated page, user talk page notification, talk page of redirect target, so this would be more consistent. If possible, also modify the "Logging RfD nomination of Template:WPBannerMeta/Archive 13" summary of personal XFD log such that "RfD nomination" part links to the relevant section, in a similar manner to how "listing" does in above examples. Thanks! —CX Zoom[he/him](let's talk • {C•X})16:17, 22 December 2022 (UTC)
Template:More citations needed has been nominated for merging with Template:BLP sources. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. 🐶 EpicPupper (he/him | talk) 21:07, 4 April 2022 (UTC)
Courtesy link: Wikipedia:Twinkle/doc. I updated most of the images just now. See anything else that needs updating? Feel free to be bold and do it yourself if you want. –Novem Linguae (talk) 03:16, 12 April 2022 (UTC)
Done! Sorry for the delay. I was away from the computer over the past week. — MusikAnimal talk 18:35, 13 April 2022 (UTC)
Fixed the template for us. Please let us know if the error crops up again. Thanks all. –Novem Linguae (talk) 06:24, 2 June 2022 (UTC)
23:21, 21 May 2022 (UTC)
Thank you very much! I dream of horses (Contribs) (Talk) 22:03, 28 July 2022 (UTC)
UricdivineTalkToMe 18:04, 17 August 2022 (UTC)
