Wikipedia talk:Twinkle

Active discussions

Twinkle violating MOS:ORDER - needs correctionEdit

Please see this edit. In this edit, Twinkle put a {{Pp-blp}} tag above a {{Short description}} template, which is in violation of MOS:ORDER, since {{Short description}} is #1 and {{Pp-blp}} represents #3. Steel1943 (talk) 21:49, 23 June 2020 (UTC)

Hi Steel1943, Unrelated to Twinkle but the date format script does the same thing, I've noticed tons of articles that have shortdesc either second or third as opposed to first,
Would be nice if a bot could reorder these :), –Davey2010Talk 22:00, 23 June 2020 (UTC)
@Davey2010: That edit you referenced ... wow, the date script put in a tag that is #5 on MOS:ORDER, but put the tag above both #1 and #4! Steel1943 (talk) 22:04, 23 June 2020 (UTC)
Wow, That certainly is surprising, What's more surprising is that I didn't even know MOS:ORDER existed until now!, Anyway pinging Ohconfucius who may or may not be aware of MOS:ORDER, I've amended the order :), Thanks, –Davey2010Talk 22:16, 23 June 2020 (UTC)
Yeah, Twinkle's not great about this. The tag module handles it pretty well, but the others (protect, xfd, prod, csd) don't pay much attention. In their defense, the whole short description thing is a pretty new phenomenon as far as Twinkle is concerned. I'll try and think about this when I get a chance. ~ Amory (utc) 11:03, 24 June 2020 (UTC)
Gave it a go for Twinkle: ~ Amory (utc) 15:07, 6 July 2020 (UTC)
Should be done now, for the most part anyway. ~ Amory (utc) 15:46, 19 July 2020 (UTC)

Feature request: make template search easier to accessEdit

Wouldn't it be great if the warnings dialog that comes up first had a search box that was immediately visible? It's a waste of time to go through pull down menus to get to the templates search. ThatMontrealIP (talk) 20:11, 25 June 2020 (UTC)

Sorry, I'm not really understanding what you're asking for. Are you saying you want the search box to be already selected when the menu loads? ~ Amory (utc) 01:14, 27 June 2020 (UTC)
@Amorymeltzer: yes, It would be great to be able to search all templates without the current process (having to click the template menu, then select all templates, then click another pull down and search in that box). I'm suggesting having a plain old search box that applies to all templates immediately visible. Maybe I am missing something but I always have to go through the above process to search all templates. For example I might think "ah, COi is where, oh ok it's under single-issue notices" then I click single issue notices, then I search for COI. It could instead be a single step with an immediately available search box. Am I doing it wrong?ThatMontrealIP (talk) 00:03, 30 June 2020 (UTC)
Well, for starters, you can choose which dropdown group is the default option in your twinkle preferences. You can select all templates if you like. There's also an option to combine the two singlet menus, you can also choose that as your default, or indeed any of the others. Having it open with the cursor set in the search area is something to consider, though. I think I could support that. ~ Amory (utc) 01:33, 30 June 2020 (UTC)
@Amorymeltzer: Thanks for the quick reply and the tip! I like what you are saying about the cursor being immediateley in the all-template search.ThatMontrealIP (talk) 01:35, 30 June 2020 (UTC)
I second this. It would be nice if the search box was above the dropdown rather than inside it. Nardog (talk) 16:33, 30 June 2020 (UTC)
This should be the case now — the template select is still below the menu, but it should be the focus upon menu loading. ~ Amory (utc) 15:46, 19 July 2020 (UTC)

Add Template:Uw-sigdesign to Twinkle's "Warn/Single-issue notices" functionEdit

...Just as the header states, can Template:Uw-sigdesign be added to Twinkle's "Warn/Single-issue notices" function? Asking since I've wanted/needed to use that template on new users' talk pages a few times now... Steel1943 (talk) 17:05, 15 July 2020 (UTC)

@Steel1943: I assume you've already added it through your "Custom warning templates to display:" section of your Wikipedia:Twinkle/Preferences page, and simply feel it's useful for other users too? The way you worded the question made it seem like you hadn't. - BilCat (talk) 02:43, 19 July 2020 (UTC)
@BilCat: Nope, I didn't even know the "Custom warning templates to display:" section existed until I read this message. But sure, let's go with stating this warning message should exist in Twinkle by default. 😉 Steel1943 (talk) 03:12, 19 July 2020 (UTC)
Ah, ok. There are several custom fields in the Twinkle preferences, and they're very useful for warning, tags, etc. that aren't there already. I probably wouldn't use the warning you've suggested, but I wouldn't oppose it being added if other users found it useful. - BilCat (talk) 03:50, 19 July 2020 (UTC)

Twinkle should check talk page for redirects before adding templatesEdit

I recently prodded an article that apparently had the talk page redirected to another article, but Twinkle followed the redirect added the prod template to the wrong article. I think it should check for redirects first before adding templates (this happened at Moonstone (comics)). --Piotr Konieczny aka Prokonsul Piotrus| reply here 01:32, 19 July 2020 (UTC)

Merged all files but not working in mlwikiEdit

I have recently merged around 5 files related to Twinkle in mlwiki. At first, it showed an error 'morebitsWikiApiUserAgent is not a function', which was resolved by updating morebits.js file. As of now, Twinkle is showing errors: 'Uncaught TypeError: Twinkle[module] is not a function' and 'jQuery.Deferred exception: Twinkle[module] is not a function TypeError: Twinkle[module] is not a function'. I would like to know whether anybody have a solution to this problem. Adithyak1997 (talk) 05:41, 19 July 2020 (UTC)

Adithyak1997, was everything working beforehand? I'll be honest, I wouldn't have thought that using mw.loader.load would work, and my quick tests suggest that indeed it doesn't. What's probably happening is that the Twinkle loading function from Twinkle.js is running before the mw.loader.load can pull in the source from enwiki, so you're ending up with an error. The enwiki pages are actually about to get updated today, which I think might solve that your issue; the order is likely to be different, but a quick test suggest it should work. You would have to update Twinkle.js as well as the Gadget definition, or you can just import the current versions locally. ~ Amory (utc) 10:59, 19 July 2020 (UTC)
Everything didn't work good previously. There were many issues when using Twinkle but small functionalities like AfD worked correctly. Then came the issues related to Twinkle menu, which was resolved by Jayprakash12345. Problems like arv is not a function and fluff.init is not a function also existed which led me to take the post of an interface admin (temporary) there. Extra things created by me were addition of select2 and addition of pagestyles. Adithyak1997 (talk) 11:07, 19 July 2020 (UTC)
Okay that makes sense. I'd be willing to bet that the only ones that worked were ones that were locally present (not loaded via importScript or mw.loader.load), is that, right? I'll ping you when I push the changes here if you like. ~ Amory (utc) 11:13, 19 July 2020 (UTC)
Adithyak1997, the section below has the new style of pages. If you update your Twinkle.js and Gadget (MediaWiki:Gadgets-definition), does that solve things? ~ Amory (utc) 14:35, 20 July 2020 (UTC)
Previously, I updated all the things to the main file. Inorder to avoid further issues, I have reverted all the merging. I will try creating all the required pages into my sandbox and will update as directed by you. Since I am a little busy now, I will try to update within a week. Adithyak1997 (talk) 14:43, 20 July 2020 (UTC)


Criteria X2 for content translation tool articles is being deprecated. I don't think twinkle supports X2 but since the template is tagged as used by twinkle I'll play it safe and drop a message here. --Trialpears (talk) 08:17, 19 July 2020 (UTC)

Thanks and yup! I'm not sure if Twinkle ever did, tbh, but yeah, no issues here! ~ Amory (utc) 10:20, 19 July 2020 (UTC)

July 2020 Twinkle updates, features, and behaviors (2020-07-19) @2b6f9a7Edit

A lot of bug fixes this time around, as well as some major refactoring on the backend thanks to SD0001. Some of the more notable improvements are a massive increase in the number of redirect tags available, automatic selection of the template menu in the warning menu, and a ton of fixes to endorsing PRODs. There are a number of other improvements and bug fixes; a brief summary of some of them are below. Changes not otherwise attributed were made by User:Amorymeltzer.

  • Multiple:
    • Respect MOS:ORDER for hatnotes and shortdesc in PROD, CSD, XfD, tag, and protect modules (#1022)
      • Also updates the list of hatnote templates Twinkle watches out for
    • Don't follow cross-namespace redirects when notifying users (PROD, XfD, CSD, warn, block) (#915, by SD0001) (see also #1017 and #1016)
    • Bold action completed messages (#1038, by SD0001)
    • Better display of long numbers (#988, by Huji)
  • tag:
    • Add all redirect templates with >500 transclusions (#1002)
    • Disallow conflicting file tags (#1000)
    • Fix issue in whitespace matching preexisting rcats (#995)
  • speedy:
  • prod:
    • Fix a number of bugs around endorsing (#973)
    • Require confirmation if an empty reason is provided (#1006)
    • Don't include empty reason in log (#972)
  • warn:
    • Automatically focus on the template selection menu (#1023)
    • Add outing to uw-pinfo label to aid in searching (#1031) (#1024, by JJMC89)
    • Fix a couple bugs in custom warning edit summaries (#1026)
    • Fix bug in autolevel not elevating level for singlewarn (#1028)
    • Fix bug where autolevel message wouldn't display (#1014)
  • revert and rollback:
    • Don't add "Restore this revision" links to revdel'd history revisions (#982)
    • Fix skipping of trusted bots (#994)
  • xfd: Fix xfd log numbering (#981) (#977, by Mdaniels5757)
  • block:
  • unlink: Alert/return if no pages selected, show more accurate interface message (#998)

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

Is anyone else no longer seeing the ability to issue user warnings to their Talk pages? DonIago (talk) 15:44, 19 July 2020 (UTC)
@Doniago: Give it a few minutes: when the gadget pages get updated, it takes a few minutes for the ResourceLoader to field the new files. I think it should be all clear now, so let me know if it's still an issue (quick test worked for me). ~ Amory (utc) 15:50, 19 July 2020 (UTC)
Looks good now! Just a timing issue. :) Thanks! DonIago (talk) 16:04, 19 July 2020 (UTC)

Issues with tagging (consolidated)Edit

@GSS, ProcrastinatingReader, LaundryPizza03, Steel1943, Chris troutman, Timtrent, and Grey Wanderer: Sorry for all the issues you (and presumably others) are facing. I've consolidated the sections here, and put up a tracking issue on GitHub, to try and organize some thoughts. I've now reverted all of the changes made recently (with one notable exception) so do please let me know whether you are or aren't still seeing the same issues (you may have to refresh your cache). For those of you who can load checkboxes, can you check what happens if you open, close, then open again the tag module? I can't replicate any of the issues anymore so I'll take any reports, details, error messages, anything! Really sorry for all the hassle. ~ Amory (utc) 17:24, 25 July 2020 (UTC)

It's working fine for me now, on all articles. I've checked on some with existing tags, some without, including the list I added earlier in this section. Sorry, I'm not sure what you mean by what happens if you open, close, then open again the tag module -- it behaves as expected, I suppose? No debug messages in console or anything, if that's what you meant? ProcrastinatingReader (talk) 17:29, 25 July 2020 (UTC)
That's indeed what I meant, thank you. ~ Amory (utc) 17:40, 25 July 2020 (UTC)
Thank you for your efforts Amorymeltzer, I tried on Apollo 11 and a few others and it's now working perfectly. GSS💬 17:29, 25 July 2020 (UTC)
Amorymeltzer, Only had a chance to check it once. Put a single cleanup tag on with success. Good luck with finding the issue when you roll the changes 'back' forwards! You can bet it'll be obvious and hiding in plain sight Fiddle Faddle 19:06, 25 July 2020 (UTC)

Just FYI to all, I restored the changes (with the fixes) a little over an hour ago. Let me know if any issues arise or persist, you may need to clear your cache. ~ Amory (utc) 19:22, 26 July 2020 (UTC)

Error on tagEdit

When I click "Tag" I now see an empty list (no checkboxes), on all articles. Browser console has: Uncaught TypeError: Cannot read property 'indexOf' of null

at this line:

ProcrastinatingReader (talk) 18:52, 19 July 2020 (UTC)

ProcrastinatingReader, Works for me. Adam9007 (talk) 19:34, 19 July 2020 (UTC)
Facing the same issue since last night. GSS💬 07:53, 20 July 2020 (UTC)
@ProcrastinatingReader and GSS: Do either or both of you still see this issue? I suspect there was a timing/caching issue. If you do still see the error, what page and what tags were you trying? ~ Amory (utc) 14:33, 20 July 2020 (UTC)
Amorymeltzer, I do. It happens on any page, and no tag in particular, I just can't see any tags. Looks like this: (that was at Apollo 11) ProcrastinatingReader (talk) 23:24, 20 July 2020 (UTC)
Can you replicate it and show any errors that you see in your browser console (see WP:JSERROR)? And, if you don't mind, what browser are you using? ~ Amory (utc) 00:16, 21 July 2020 (UTC)
Amorymeltzer, sorry I'm not sure what you mean by replicate (as in reproduce? if so, yes, this happens to me on every article)
The error is in my original message, the line it refers to is that highlighted line (L 560) in friendlytag.js. Here's a full trace:
::::::Uncaught TypeError: Cannot read property 'indexOf' of null
::::::    at makeCheckbox (load.php?lang=en&modules=ext.gadget.Twinkle&skin=vector&version=80fli:376)
::::::    at Object.<anonymous> (load.php?lang=en&modules=ext.gadget.Twinkle&skin=vector&version=80fli:383)
::::::    at Function.each (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets|jquery.ui&skin=vector&version=1rtpe:5)
::::::    at doCategoryCheckboxes (load.php?lang=en&modules=ext.gadget.Twinkle&skin=vector&version=80fli:383)
::::::    at Array.<anonymous> (load.php?lang=en&modules=ext.gadget.Twinkle&skin=vector&version=80fli:384)
::::::    at Function.each (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets|jquery.ui&skin=vector&version=1rtpe:5)
::::::    at Object.<anonymous> (load.php?lang=en&modules=ext.gadget.Twinkle&skin=vector&version=80fli:384)
::::::    at Function.each (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets|jquery.ui&skin=vector&version=1rtpe:5)
::::::    at HTMLSelectElement.Twinkle.tag.updateSortOrder (load.php?lang=en&modules=ext.gadget.Twinkle&skin=vector&version=80fli:383)
::::::    at friendlytagCallback (load.php?lang=en&modules=ext.gadget.Twinkle&skin=vector&version=80fli:376)
ProcrastinatingReader (talk) 00:22, 21 July 2020 (UTC)
Thanks, I'll try and look into this — I can't replicate it in any of chrome/firefox/safari on my end, so I'll do what I can. ~ Amory (utc) 00:33, 21 July 2020 (UTC)
Uncaught TypeError: Cannot read property 'indexOf' of null
    at makeCheckbox (load.php?lang=en&modules=ext.gadget.Navigation_popups%2CTwinkle&skin=vector&version=11zsw:542)
    at Object.<anonymous> (load.php?lang=en&modules=ext.gadget.Navigation_popups%2CTwinkle&skin=vector&version=11zsw:549)
    at Function.each (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets|jquery.ui&skin=vector&version=1rtpe:5)
    at doCategoryCheckboxes (load.php?lang=en&modules=ext.gadget.Navigation_popups%2CTwinkle&skin=vector&version=11zsw:549)
    at Array.<anonymous> (load.php?lang=en&modules=ext.gadget.Navigation_popups%2CTwinkle&skin=vector&version=11zsw:550)
    at Function.each (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets|jquery.ui&skin=vector&version=1rtpe:5)
    at Object.<anonymous> (load.php?lang=en&modules=ext.gadget.Navigation_popups%2CTwinkle&skin=vector&version=11zsw:550)
    at Function.each (load.php?lang=en&modules=jquery%2Coojs-ui-core%2Coojs-ui-widgets|jquery.ui&skin=vector&version=1rtpe:5)
    at HTMLSelectElement.Twinkle.tag.updateSortOrder (load.php?lang=en&modules=ext.gadget.Navigation_popups%2CTwinkle&skin=vector&version=11zsw:549)
    at friendlytagCallback (load.php?lang=en&modules=ext.gadget.Navigation_popups%2CTwinkle&skin=vector&version=11zsw:542)
MoreMenu.messages.en.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
MoreMenu.user.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSED Failed to load resource: net::ERR_CONNECTION_REFUSED
MoreMenu.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
and this is what errors I see at Apollo 11. GSS💬 12:45, 21 July 2020 (UTC)
@GSS: I strongly believe it's an issue on your side. From the last 4 lines of your latest comment, I think its an issue with your network connection. Please check whether you can reproduce the same when using some other internet connection. Sorry if my reply is unrelated. Adithyak1997 (talk) 13:16, 21 July 2020 (UTC)
In this case it's not related, but it's certainly something weird going on that could be exacerbating any issues for sure! ~ Amory (utc) 13:54, 21 July 2020 (UTC)
@GSS: Okay I could replicate it on TietoEVRY, so this was super helpful, thanks! I've just pushed a fix (sorry, delayed by ancient laptop + yogurt explosion, thankfully not together), should take effect within a minute or two. ~ Amory (utc) 13:53, 21 July 2020 (UTC)
Amorymeltzer, issues are persisting for me. eg at Barbra Streisand. I'm getting exactly the same issue as before. ProcrastinatingReader (talk) 13:52, 23 July 2020 (UTC)
All good now, it looks like! Maybe just caches or something delayed the fix for me. -- thanks for the patch :) ProcrastinatingReader (talk) 09:54, 24 July 2020 (UTC)
Amorymeltzer, hmm. I'm testing on my other Mac (using Chrome) and I still get the issue. I assume the patch was this. I've hard flushed my caches and ensured this is the version being loaded in Chrome, but I still get the error. On Safari, I don't get any error. Hence, I'm thinking some kind of cache error, but since the version of the file on my end matches with the update I'm not sure it'd be that. Any suggestions? ProcrastinatingReader (talk) 16:11, 24 July 2020 (UTC)
ProcrastinatingReader, well, if you're not sure and were still seeing it (before about an hour ago), you could try copying the text of that revision and pasting it into your browser console. That should create a new tag menu button, and clicking on that would be a way of testing the exact version. ~ Amory (utc) 17:33, 25 July 2020 (UTC)

Bug report: Duplicate tagsEdit

When I used Twinkle to tag an article that already had a tag at the beginning and wrap them in {{Multiple issues}}, it added each of the new tags twice (Special:Diff/968926473). –LaundryPizza03 (d) 10:25, 22 July 2020 (UTC)

That's no good. I've been a bit busy so haven't been able to test too deeply, but I can't seem to replicate this. I'll try and look a little deeper tonight or tomorrow when I get a moment, but what browsers are you folks using? (steel IIRC you're on ff?) ~ Amory (utc) 13:00, 23 July 2020 (UTC)
I'm on Chrome. The error only happens when the "multiple issues" box is checked, even if they were already present. Chris Troutman (talk) 13:30, 23 July 2020 (UTC)
  • In my example above, I didn't check the "multiple issues" box, and still had duplicate tags put on the article. Steel1943 (talk) 15:14, 23 July 2020 (UTC)
Amorymeltzer, Mac and Safari. Happens repeatably for me when the MI box is checked. Fiddle Faddle 15:09, 23 July 2020 (UTC)
It has been happening to me for weeks. Using safari. Grey Wanderer (talk) 00:47, 24 July 2020 (UTC)
Grey Wanderer, how sure are you about weeks? That's an interesting point not noted above, which could help me narrow things down. Do you have a diff of it happening before July 19th? ~ Amory (utc) 01:19, 24 July 2020 (UTC)
My memory must be suspect. Indeed the oldest diff I can find is on July 19th. Grey Wanderer (talk) 02:18, 24 July 2020 (UTC)
    • Yeah, that's my intent once I get back to a machine (approx 4 hours). I'll set aside some time today and tomorrow to try and look at these (means I won't be doing reviews...) but I can't replicate any of 'em anymore so it'll be difficult (race?). — Preceding unsigned comment added by Amory (talkcontribs) 11:31, 25 July 2020 (UTC)

Okay so I think I figured this one out! It looks like my solution for welcoming on IE 11 issue below should take care of it. So that's one down for now... ~ Amory (utc) 19:07, 25 July 2020 (UTC)

Can't welcome with IEEdit

Since the latest update, I can't issue welcomes when using Internet Explorer. Attempts to do so just produce {{subst:undefined}} and my signature. (Everything else, including issuing warnings, seems to work fine.) Now, I realize that fixing this might be low priority, given IE's status. I use other browsers for other purposes, but for what I do on Wikipedia, IE is by far my preferred browser. Is there anything that can be done? Thanks, MANdARAX  XAЯAbИAM 08:10, 22 July 2020 (UTC)

I see you've been testing, but can you try again with IE and paste the output from your browser console? That'd be helpful. I assume the preview doesn't work either? Also, what version of IE are you using? ~ Amory (utc) 09:55, 22 July 2020 (UTC)
You assume correctly that the preview doesn't work. I've got IE 11.959.18362.0.
Go to page:
DOM7011: The code on this page disabled back and forward caching. For more information, see:
HTML1300: Navigation occurred.
JQMIGRATE: Migrate is installed with logging active, version 3.1.0
This page is using the deprecated ResourceLoader module "jquery.tipsy".
This page is using the deprecated ResourceLoader module "jquery.ui".
Please use OOUI instead.
JQMIGRATE: jQuery.fn.delegate() is deprecated

Click on welcome tab:
JQMIGRATE: jQuery.fn.bind() is deprecated
JQMIGRATE: jQuery.fn.unbind() is deprecated
JQMIGRATE: jQuery.isWindow() is deprecated
JQMIGRATE: jQuery.fn.offset() requires a valid DOM element

JQMIGRATE: jQuery.fn.andSelf() is deprecated and removed, use jQuery.fn.addBack()
Thanks for looking into this. MANdARAX  XAЯAbИAM 07:44, 23 July 2020 (UTC)
Okay woof. Took me a while but I figured it out. Opened a PR which should take care of it I think. Hard to test on IE! ~ Amory (utc) 12:52, 23 July 2020 (UTC)
Yep, it works now. Sorry it was so difficult. Thank you very much for going to the effort! MANdARAX  XAЯAbИAM 17:47, 23 July 2020 (UTC)
Mandarax, Wait, it works? I didn't push the change live to Wikipedia yet, so if it started working... ~ Amory (utc) 01:18, 24 July 2020 (UTC)
Well, I just tried again, and it doesn't work. So the one that did work was either some bizarre fluke, or, more likely, I may have absentmindedly tried it from an iPad. Sorry I don't remember. (In my defense, I got very little sleep.) MANdARAX  XAЯAbИAM 02:57, 24 July 2020 (UTC)
Mandarax, thanks for that update. Sorry for not pushing the fix for this yet; the fix for this could have affected other modules, and given all the issues above with tagging, I didn't want to mix up any reporting. It looks like this also solved one of the related tag issues above, so I'll push this live now to fix your issue. Let me know if you see any additional funkiness... ~ Amory (utc) 19:10, 25 July 2020 (UTC)
It works! (And, yes, this time I definitely used IE.) No need to apologize for the delay: 1) it's for a browser that's not in wide use, and 2) I could still welcome people using other browsers (or manually). Once again, thank you very much – not just for this, but for everything you do around here! MANdARAX  XAЯAbИAM 20:45, 25 July 2020 (UTC)
  • I'm having similar issue and I keep forgetting to come here and mention it.[1] It's only when I welcome from a diff, doing it directly from their talk page still works fine so it's not a huge deal. I'm using Chrome 83.0.4103.119. (actually when I went to check the version it said I needed an update so as of right now I'm using 84.0.4147.94) Beeblebrox (talk) 23:26, 31 July 2020 (UTC)
Well crap, since that update it is now working very, very slowly. Beeblebrox (talk) 23:46, 31 July 2020 (UTC)
this was apparently a side effect of the update, which also signed me out of absolutely everything, so forget that part of it. Beeblebrox (talk) 01:08, 1 August 2020 (UTC)
Thanks for the report, yup! Just posted a fix, should be taken care of now! ~ Amory (utc) 09:58, 1 August 2020 (UTC)
Just tested it, works fine now. Thanks! Beeblebrox (talk) 18:29, 1 August 2020 (UTC)

Technical changesEdit

For maintainers of other projects be aware that the method in which Twinkle modules are loaded changed, so anyone who maintains an up-to-date Twinkle gadget will have to update the gadget definition as well. Twinkle-related changes and deprecations include:

  • Decentralise module initialisations (#946, by SD0001)
  • morebits: Remove tipsy dependency, use jQuery UI for tooltips (#971)
  • Remove useragent 2.0 specification (#970)
  • Merge individual chunk prefs into one: batchChunks (#978)
  • Note dependencies on mediawiki.Title (morebits) and mediawiki.api (Twinkle) (#983)
  • Use Twinkle.hatnoteRegex to store hatnote templates (#1022)

For the more technical folks, there were a number of behind the scenes improvements that might be interesting:

  • Add Morebits.quickForm.getInputData for easy access to form data (#908, by SD0001)
  • form getters: don't return null (#908, by SD0001)
  • quickForm: add shiftClickSupport option for checkboxes (#1041, by SD0001)
  • Allow chaining of methods (#1022)
  • Add insertAfterTemplates to (#1022)
  • Add ability to not follow cross-namespace redirects (#915, by SD0001)
  • fix ability to query in JSON (#1007)
  • api: auto-retry on badtoken errors. (#1038, by SD0001)
  • api: use GET for all action=query requests (#1038, by SD0001)
  • api: use formatversion=2 by default while making API calls in JSON (#1038, by SD0001)
  • Don't allow null append or prepend text (#1032)

~ Amory (utc) 15:43, 19 July 2020 (UTC)


Why can't it be selected in the CSD menu? Could have used this a lot of times. --TheImaCow (talkcontribs) 18:40, 20 July 2020 (UTC)

Because it's just another way to put G6? Primefac (talk) 21:59, 20 July 2020 (UTC)

Add a block template pleaseEdit

There seems to be a level of agreement that failure to WP:ENGAGE is best handled by a partial block from article space, which is kinder than a sitewide block. I'd like to see a canned block with the following settings:

  • Duration: Indefinite
  • Log reason: Editing issues and failure to engage with the community
  • Talk page rubric to include the fact that this block can be lifted as soon as the user begins engaging on article and user talk pages.

Thoughts? Guy (help!) 22:24, 21 July 2020 (UTC)

@JzG: Probably the User warnings project is a better place for this, once it's made, we can add it to Twinkle. --qedk (t c) 20:02, 25 July 2020 (UTC)

Facing 2 issuesEdit

I know that I am using an outdated version. Still, there are 2 issues. Firstly, please check this edit. In that, the text 'ഒഴിവാക്കാൻ, ലയിപ്പിക്കാൻ, അഥവാ പുനഃനാമകരണം' (meaning delete, merge or rename) needs to show only one text. Now it's showing three. Secondly, 'വിക്കിപീഡിയ:ഒഴിവാക്കാൻ സാദ്ധ്യതയുള്ള ലേഖനങ്ങൾ' is the replacement for Wikipedia:Afd in mlwiki. The problem is, the summary appears correctly like the summary for this but the page doesn't contain the item, meaning, the deletion page is not getting posted in that. Adithyak1997 (talk) 18:48, 22 July 2020 (UTC)

Adithyak1997, Regarding your first point, that's because the older version of xfd doesn't add the action parameter to the CfD notification template. I added that in this PR (specifically, this commit). I can't see the second link you posted, it's been deleted; sorry. ~ Amory (utc) 16:01, 26 July 2020 (UTC)

Possible bugEdit

Hello. This action resulted in User talk:, where Twinkle replaced Hello, I'm Pyrite Pro... at the top of Pyrite Pro's warning, with Hello, I'm DB1729.... In fact, it did the same thing when WikiMacaroons issued a warning. --DB1729 (talk) 10:30, 23 July 2020 (UTC)

DB1729, in both these cases, the UW templates weren't substituted as they should have been by Pyrite Pro as shown in the uw template documentation, so this issue occurred there and not with Twinkle as far as I can tell. You can even see a bot go round and fix this a bit too late in the page history. I've left Pyrite Pro a reminder. Ed6767 talk! 11:08, 23 July 2020 (UTC)
OK. Thanks for the reply. --DB1729 (talk) 11:12, 23 July 2020 (UTC)

"Unknown user" and rollback errorsEdit

Since changing some Twinkle options a few days ago, including setting "rollback in place" ([2]) I've been seeing "Reverted 1 edit by an unknown user" instead of the usual user name or IP, and rollback is only doing the first edit. See [3] yesterday and today for example. But it doesn't happen every time. Is there a fix for this? Thanks. --IamNotU (talk) 15:47, 25 July 2020 (UTC)

That's definitely a bug IamNotU, thanks for the report! Do you remember where you clicked on the links from? Diff, history, contributions, that sort of thing? ~ Amory (utc) 15:38, 26 July 2020 (UTC)
I don't remember, sorry. I'll try to keep an eye on it and get back to you. --IamNotU (talk) 15:41, 26 July 2020 (UTC)
Amorymeltzer, it just happened again, I was on this page: Special:Contributions/2601:199:4180:F670:542F:E131:AC1F:E73B/64 and I made this revert using Twinkle's "rollback" link. I got the small popup box on the right for the "rollback in place". Maybe it's related to this being the page for an IP range (/64) and not a single IP? But it's also related to one of the changes I made in the preferences, because it always worked before. I'll try to go find some more edits to revert... --IamNotU (talk) 21:47, 26 July 2020 (UTC)
@IamNotU: Yup, that's definitely an issue, if not the issue! I know you said you didn't recall where you clicked previously, but, if they were contributions, would they also have been on the /64? ~ Amory (utc) 09:58, 27 July 2020 (UTC)
IamNotU, I just pushed a fix that should take care of it when being run from an IP range's contributions page. It will take a few minutes to go through (and you might need to clear your cache), but let me know if you still see anything, or if you think you ever saw it from somewhere other than IP range contributions page. ~ Amory (utc) 10:39, 27 July 2020 (UTC)
Seems to be working now, thanks! The other times were all IPV6s, so it's likely I was on a /64 page, which I do often but not always. Also I'm not sure anymore that it was related to changing my prefs, because it looks like it happened also the day before I did that. Maybe just a coincidence. PS, is it possible somehow to get the AGF/rollback/vandalism links to show on an article's history page and/or my watchlist too? I use a "live diffs" script so I don't have to click on the diff link, so it would be great if I could just do everything without leaving the page. I know I can do it with "real" rollback, but I haven't found a good solution to make proper edit summaries that way. Thanks again... --IamNotU (talk) 19:26, 27 July 2020 (UTC)
It wasn't, so no worries on your end. I changed the way the various links are created, unifying a lot of code that was largely duplicated, and then separately put in a system to handle cases where usernames were revision deleted (rare, but possible). In doing the latter, I didn't account for the fact that Twinkle uses a little hack to enable itself on IP range contribution pages and failed to provide the correct usernames for each link.
You can enable rollback links on history pages in your Twinkle prefs, at the very end of the revert and rollback section. Twinkle has never been activated on the watchlist, mainly to avoid further slowing down an already-slow page. ~ Amory (utc) 19:44, 27 July 2020 (UTC)
Ok, thanks for taking care of it. Don't know how I missed that checkbox for history pages before. It still would be really nice to have it on my watchlist though. If I could do "live diffs" and "rollback in place" direct from the watchlist, I think it would more than make up for any slowness in loading it. Maybe you'll have time to add it someday... --IamNotU (talk) 20:33, 27 July 2020 (UTC)

Posted at VPTEdit

For those interested, I plan on using tags to identify Twinkle edits and actions rather than the current add-to-editsummary method. I posted about it WP:VPT. ~ Amory (utc) 19:27, 29 July 2020 (UTC)

AN3 not workingEdit

Trying to report this user's reverts on А́ to AN3 does not work for me. Clicking "Load" turns up nothing. I wonder if it has to do with the fact А́ is currently a redirect. Nardog (talk) 05:18, 2 August 2020 (UTC)

Yes, indeed! That's been the case since the feature was added in 2013 but I can't say I'm entirely sure why it's a good idea. ~ Amory (utc) 10:08, 2 August 2020 (UTC)

Merging feature should be implemented on TwinkleEdit

I installed Twinkle originally to revert vandalism. However, I found that XfD nominations become very simple in Twinkle. Unfortunately, I cannot use Twinkle to request to merge articles. Therefore, I request to semi-autonomise the requested merge. Thank you. --Soumya-8974 talk contribs subpages 17:01, 2 August 2020 (UTC)

Soumya-8974, you can. It's in the tag section. I missed it for ages as well. --Trialpears (talk) 17:02, 2 August 2020 (UTC)
  Thank you --Soumya-8974 talk contribs subpages 17:03, 2 August 2020 (UTC)

Not notifying creator of a BLPprod articleEdit

When I blpprodded Dolly-Rose Campbell I expected Twinkle to notify its creator, but it didn't? A bug, a temporary glitch, or have I accidentally unset a setting? PamD 06:46, 5 August 2020 (UTC)

@PamD: Did you navigate away from the page between when the tag got placed and when the notification got sent? Jackmcbarn (talk) 21:09, 5 August 2020 (UTC)
@Jackmcbarn: I prodded the article, did a couple more edits, edited another article and then for some reason checked the creating editor's page, found there wasn't a message, and added it manually. It's likely, from the timing, that I was editing on phone when I prodded and then on laptop later. PamD 22:04, 5 August 2020 (UTC)
Return to the project page "Twinkle".