Wikipedia talk:Twinkle

From Wikipedia, the free encyclopedia
Jump to: navigation, search
"WT:TW" redirects here. For other uses, see Wikipedia talk:Transwiki log, or the WikiProject Taiwan talk page.

This page is for general discussion and questions related to Twinkle. It is also one possible venue for reporting bugs and requesting new features; although see Bugs and feature requests below.

Consider also checking Twinkle's documentation, which may answer your question.

e·h·w·Stock post message.svg To-do:
  • Update TODO list
  • Ability to remove maintenance tags from articles using the "tag" module
  • Incorporate one of the many delsort scripts into Twinkle (see WP:DELSORT)
  • Incorporate FurMe into Twinkle

Bugs and feature requests[edit]

Bugs and feature requests can be reported at (you will need to have a GitHub account). This will probably result in the issue being noticed sooner, as an e-mail is sent to all Twinkle developers. Alternatively, start a new discussion on this page. Possibly slower service, but you will be able to gain consensus, etc., if you need to.

Go to user talk when reverting pending changes[edit]

When a page is reverted with the pending changes "Revert changes" button, Twinkle should give a nice link to go to the user's talk page with the page name pre-filled, like it does when "real" rollback is used. Jackmcbarn (talk) 04:35, 11 January 2014 (UTC)

I'll look into this. I only have reviewer rights on testwiki, so I hope our setup is not too different. — This, that and the other (talk) 02:17, 1 February 2014 (UTC)
@Jackmcbarn: Hm, I'm not quite sure what you are referring to here. When I clicked "Reject changes" I seemed to get sent back to the article itself. — This, that and the other (talk) 06:14, 15 February 2014 (UTC)
A link from the confirmation page, I mean. Jackmcbarn (talk) 23:03, 15 February 2014 (UTC)
Being hopelessly inexperienced with Pending Changes, I will need step-by-step instructions of every click you are making :) — This, that and the other (talk) 02:52, 16 February 2014 (UTC)
Talk page link on pending changes revert screen.png Jackmcbarn (talk) 18:31, 16 February 2014 (UTC)
So you want to see a talk page link even before you have made the revert? That seems like a strange order in which to do things. — This, that and the other (talk) 06:41, 18 February 2014 (UTC)
Yes. I know that's kind of strange, but after the revert is made, there's nowhere to put the talk page link. The other alternative is to make the user's talk page pop open in a new window after the revert, the way that it does when you use Twinkle's own rollback to revert someone. Jackmcbarn (talk) 13:27, 18 February 2014 (UTC)
@Jackmcbarn: Sorry Jack, I missed your reply. Yes, a popup wouldn't be a bad idea, although I'm hesitant to add another one. I'll see what is possible here and think about the best way to implement it. — This, that and the other (talk) 07:26, 3 March 2014 (UTC)
Threadcromancy, but I would suggest using popups to direct you quickly to their user talk page. You'll have to copy the page name manually, but it's nonetheless faster than clicking and clicking repeatedly. --k6ka (talk | contribs) 22:09, 28 April 2014 (UTC)

I don't want to see the vandal's talk page, but I would like this bot to automatically create a talk page for the vandal, if necessary, and post a notice on the vandal's talk page that they did something offensive. In my recent use of this bot, no notice was posted on the vandal's talk page; apparently because there was no existing talk page for the vandal. - Ac44ck (talk) 19:11, 3 May 2014 (UTC)


...for lack of a better heading.

  • The preferences panel at Wikipedia:Twinkle/Preferences nowhere states that twinkle preferences are actually stored on a wiki page, and are hence public (unlike the mediawiki preferences). A js-savvy user could easily understand what they mean (and even a not-so-savvy user could copy-paste someone else's preferences and then go to the twinkle preferences panel). Also, the page doesn't mention that the prefs will be released under the default wikipedia license. (Not sure if there's a copyright/privacy violation in there anywhere, but you might want to look into this.)
  • Someone might want to take a look at this commit I did downstream back in 2012. It includes a function to softcode namespace names in regex creation for the unlink tool in morebits.js. Devs may want to properly implement that upstream. The benefit would be that the regex would work on any wikipedia without problem.
  • There's a script at hi:User:Siddhartha Ghai/twinkle.js which loads for me a personal version of twinkle from various user subpages. The only difference from the gadget version is that the header and footer have been kept separate. Devs might want to consider separating them again since using this script, changes in one module can be tested easily with the other live modules (i.e copy one module to your userspace, make some changes, use hi:User:Siddhartha Ghai/twinkle.js to load the default gadget, only replacing the changed module with the userspace subpage instead of the mediawiki page) and you can test the changes live!
  • Over the past 1.5 months I've done a lot of updates to the gadget at hi.wp (stuff dating from May 2012 to October 2013). I'm just giving a heads up since I may have to take a long wikibreak and if the gadget breaks there, someone might complain here. Anything that was implemented after mid-October hasn't been implemented there (including the mediawiki js deprecations removal)
  • Oh, and it seems that Jimbo uses Twinkle too, in case any of the devs ever want to do an April Fool's prank for users in the founder group ;) --Siddhartha Ghai (talk) 16:14, 27 April 2014 (UTC)
Wow, even Jimbo Wales uses Twinkle? Man, this is just reason enough to get all autoconfirmed users in good standing to get Twinkle, even if they're not planning on using it often. It's just an awesome tool. --k6ka (talk | contribs) 21:51, 28 April 2014 (UTC)
I'm considering adding a line to the top of the preferences panel saying "Note that your preferences will be released publicly as JavaScript code in a subpage of your user page." Thoughts? Eman235/talk 06:01, 1 September 2014 (UTC)
If you really want to do it, perhaps something less technical would be better: "Note that your preferences are stored in (a subpage of your user page). Only you (and Wikipedia administrators) can modify your preferences, but the settings you choose are visible to everyone." — This, that and the other (talk) 12:10, 1 September 2014 (UTC)
And now the {{-}} is boggling me. If this note is going to be put in I don't think I can do it. Face-confused.svg Eman235/talk 00:38, 3 September 2014 (UTC)
*slaps self* never mind, figured it out. I made a slight change to the wording mention that it is JavaScript, not blatant text -- dunno what you think of that -- but yes, item one in this list is amended, kind of. Eman235/talk 00:48, 3 September 2014 (UTC)

Question regarding marking pages patrolled[edit]

I know twinkle marks pages as patrolled when nominating them for speedy deletion or PROD. However, does it also automatically mark them as patrolled when nominating them for AfD? I ask because another editor left a message on my talk page saying I had not marked Bitcoin network analyzed by network science as patrolled when I nominated it using Twinkle. If it doesn't do this currently, is it a feature we could add? Thanks -War wizard90 (talk) 04:22, 6 June 2015 (UTC)

I am the editor that bought this up with War wizard90. I'm also noticing articles tagged for PROD deletion not being patrolled. Is this a bug? --I dream of horses (T) @ 07:12, 16 June 2015 (UTC)

Don't add pp-icon unneeded[edit]

When setting page protection with Twinkle, it automatically adds {{pp-template}} to the page. In certain situations, this is not needed and so it clutters the page (for me esp in developing and sandboxing). IIRC, it also adds a page to the WP:JOBQUEUE (which is ironic when the protection is asked because of high-usage).

Some weeks age, Redrose64 already asked for this Wikipedia_talk:Twinkle/Archive_36#Protection_templates. -DePiep (talk) 21:28, 8 June 2015 (UTC)

Sorry Redrose64, I thought I'd replied to your post, but it must not have actually made it to the server (maybe it was all in my head). In any case, I'll look into this. Remember that you can always choose the "None" option from the "Choose protection template" dropdown in the PP dialog box, which will prevent the tag from being added in cases where it is not needed. — This, that and the other (talk) 01:09, 9 June 2015 (UTC)
@This, that and the other: I don't use Twinkle. I'm concerned about the unnecessary edits made by others when they use TW, which when the prot expires some weeks or months later leads to further edits by myself which also should not have been needed. As DePiep notes, an edit to a template puts all transcluding pages in the job queue - even if the only changes are inside <noinclude>...</noinclude> tags. --Redrose64 (talk) 11:05, 9 June 2015 (UTC)
I'm also concerned that Tw adds the prot template without putting it inside <noinclude>...</noinclude>, such as with this edit by Swarm (talk · contribs), which has the effect of putting most, if not all, of the transcluding pages into Category:Wikipedia pages with incorrect protection templates. Many templates (such as this one) have a <noinclude>...</noinclude> already, usually at the bottom, and that is where the protection icon template should be placed - but again, only if it is actually needed. --Redrose64 (talk) 18:40, 16 June 2015 (UTC)

Batch operation tools have been overhauled[edit]

Some exciting news for administrators: Twinkle's batch operation tools (batch delete, batch undelete, batch protect, deprod, and unlink) have been overhauled. They should now be significantly more reliable and provide more useful status output. Helpful options, such as "Select All" and "Deselect All" buttons and the ability to shift-click to toggle many checkboxes at once, have been provided. In addition, batch deletion has a number of new options, including the ability to delete the talk pages of the pages being deleted.

Some long-standing bugs have also been fixed, such as the long-obsolete CSD criterion "R1" being referenced in some deletion summaries.

Admins who use the image deletion ("Deli-batch") tool should know that it has been deprecated. The reason why Twinkle has a separate tool for image deletion goes back to the pre-API days (before 2011) and has not been relevant for some years. Admins are advised to use batch deletion ("D-batch") instead. If there are any features from Deli-batch that are missing from the new, updated D-batch module, please let us know here. In a few months, Deli-batch will be removed altogether.

Thanks, This, that and the other (talk) 03:25, 10 June 2015 (UTC)

@This, that and the other: No, it's not "deprecated", it's not working at all. You've now gone and removed a functionality I've been using for years without even as much as a warning. Worse, there is precisely zero documentation on how to install d-batch. Despite being quite technical myself, I can't figure it out.[1] Now I'm stuck here with a category full of files I can't delete: Category:Wikipedia files reviewed on Wikimedia Commons by Magog the Ogre. What gives? Magog the Ogre (t c) 23:41, 13 June 2015 (UTC)
Also, sorry if I snapped a bit. Magog the Ogre (t c) 23:56, 13 June 2015 (UTC)
For the time being I d-batched the files in the category above, but I use the "simple" Twinkle package, not specific modules of it, so I don't know how to replace your deli-batch installation with a d-batch one... that being said, both currently work in Twinkle's full installation. ☺ · Salvidrim! ·  00:20, 14 June 2015 (UTC)
@Magog the Ogre: First of all, I apologise for these problems. There does appear to be an issue with Deli-batch; I'll try to find it and fix it as soon as I can.
The "D-batch" tab has always been available to administrators on every category page. Do you not see it at all? I see it here when I switch to Monobook.
Finally, once you get D-batch working, please let me know if there are any features in Deli-batch that you miss in D-batch. — This, that and the other (talk) 07:27, 14 June 2015 (UTC)
I found the problem with Deli-batch. If you would like to fix it yourself, it is as simple as editing MediaWiki:Gadget-twinkledelimages.js to replace the two occurrences of the code Twinkle.getPref('batchDeleteMinCutOff') with the numeral 5. — This, that and the other (talk) 07:49, 14 June 2015 (UTC)
@This, that and the other: seems to be working. D-batch never worked on categories; only deli-batch did. Now they both work on categories, it seems. Magog the Ogre (t c) 16:01, 14 June 2015 (UTC)

Unlink and galleries[edit]

When an image is used in a <gallery>, the file isn't unlinked if the namespace isn't used. Can this be fixed? The <gallery> tag works both with and without namespace. --Stefan2 (talk) 23:49, 13 June 2015 (UTC)

New block template for sockmasters[edit]

Please correct me if I'm wrong, but it appears right now we have only {{uw-spoablock}} (redirects to {{SockBlock}}) as a block template for sockpuppets. It uses nonstandard parameters to tweak the copy and appearance when blocking the sockmaster and resultantly does not play nice with the new Block module.

I think we should have a separate template for sockmasters, {{uw-smblock}}, that will accept the standard |time=, |anon=yes, |notalk=yes, |indef=yes, and even the styling, in conformity with the stewardship of WikiProject User warnings. {{uw-spoablock}} could remain as-is for use on sockpuppets. Since it's always of indefinite duration, we won't need any extra parameters. We can still leave support of the nonstandard parameters simply for backwards compatibility.

Any objections? Or is there a better way to handle this scenario? MusikAnimal talk 05:13, 14 June 2015 (UTC)

Be bold and do it yourself! I will be drafting that template at User:ToonLucas22/uw-smblock to see how it goes. --TL22 (talk) 12:39, 14 June 2015 (UTC)
MusikAnimal - the SPI team (and mostly Callanecc) recently overhauled/cleaned up our set of templates for sockmasters/sockpuppets, so you might wanna talk it out before making any big changes. I think we mostly worked on the userpage "tags" and not on the usertalk "warnings", though? ☺ · Salvidrim! ·  15:01, 14 June 2015 (UTC)
Yeah we did to the tags, but I've had User:Callanecc/uw-sockblock written (it looks like the standard block template) for a while and just never got around to starting the process to change the current {{uw-sockblock}}. It defaults to sockpuppets but a hardcoded calling of |masterblock=yes and the other parameters being optional would do the job. Callanecc (talkcontribslogs) 15:11, 14 June 2015 (UTC)
The only thing is for the Block module (and WikiProject User Warnings conformity) we'll need a separate template for sockmasters, otherwise we'd have to program a special use case for the one sockpuppet template. I do think Callanecc we could use yours for normal sockpuppets since it adopts the standard styling. So in short ideally we'd have {{uw-sockblock}} as an indefinite template (does not accept |time=) and {{uw-smblock}} (does accept |time=), both in full conformity to our user warnings standards. MusikAnimal talk 18:56, 14 June 2015 (UTC)
{{User:Callanecc/uw-sockblock|masterblock=yes}} will work with the time parameter, and also ensures consistency with the format and wording. So could you have {{uw-smblock}} just call that? Callanecc (talkcontribslogs) 04:28, 15 June 2015 (UTC)
The other thing is that the one in my userspace accepts the time parameter for both socks (defaults to indef) and masters (defaults to temporary). It's probably not likely at all that a sock would only be temp blocked but having the functionality there isn't a bad thing. Callanecc (talkcontribslogs) 04:31, 15 June 2015 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────Pinging some active SPI admins: @Callanecc, Salvidrim!, Bbb23, and Mike V: I just want to make sure we're all on the same page. In its current intended form, Twinkle should be able to handle any standard template, and have little if any functionality for non-standard parameters. As a short-term solution, I'm proposing we include only two SPI-related presets:

  • Sockpuppetry uses {{uw-spoablock}} as it is now, accepts only |notalk=. Defaults to hard block of indefinite duration, account creation disabled
  • Sockpuppetry (master) uses {{User:Callanecc/uw-sockblock}} (which we'll move to {{uw-sockblock}}), accepts |time= and |notalk= parameters. Defaults to hard block of 31 hours, account creation disabled

It seems as though with sockpuppetry you may want more control, e.g. enter in the SPI case, whether it was confirmed by a checkuser, etc. Are we looking to incorporate these types of options into Twinkle? I can do this, but it will take a little while. There'd still be the two presets as aforementioned, but both would use Callanecc's template, which has control for seemingly all SPI scenarios. It would include checkboxes for "confirmed", "spi" and "evidence", and will set |anon=yes automatically when blocking an IP. How does that sound? Is the short-term solution okay, and are you interested in the extended functionality? MusikAnimal talk 00:23, 16 June 2015 (UTC)

I'm working with the understanding that most (of not all) SPI Clerks and CUs work with the SPI Helper userscript, through which user warnings are delivered whenever appropriate. I'd be curious to know how many people regularly block for sockpuppetry via Twinkle as opposed to SPI-Helper. ☺ · Salvidrim! ·  00:43, 16 June 2015 (UTC)
I'm sort of with you on this. There's no need to reinvent the wheel. I do however want to handle the base cases. Right now Twinkle can only issue {{uw-spoablock}} of indefinite duration, so there's no appropriate preset for the sockmaster. That I consider below par, so the short-term solution described above should be implemented if nothing else, I think – or we can simply remove SPI-related templates altogether from Twinkle. MusikAnimal talk 00:56, 16 June 2015 (UTC)
I'm not sure I understand the presets. But I can tell you what I want, which is the ability to block based on sock puppetry indefinitely or for a limited duration. Being able to add the SPI should also be there as when I do an SPI block from the SPI case, it automatically fills that in in the standard block form. As for the confirmed, I'm neutral. Not all checkusers operate the same way. Normally, if a sock is confirmed, on the standard form I use the template, something like "checkuser-block-account", while still leaving in the pointer to the case. Then, because I believe in tagging (with some exceptions), the user page says the block was confirmed.--Bbb23 (talk) 00:45, 16 June 2015 (UTC)
The autofill at Special:Block comes from the wpReason, which the link that those SPI links supply. I could have Twinkle look for that and auto-fill the block reason, but if you're already doing this from the SPI case it sounds like you should give SPI helper a try :) MusikAnimal talk 01:04, 16 June 2015 (UTC)
  • I'm not too concerned with whether the one I wrote is used for both socks and masters (and that can be done later anyway). One thing I'd suggest is that the default block time for sockpuppeteers be longer, I normally jump from warning to 2-3 days as a minimum. Just noting as well that if the one I wrote is moved a couple of changes (to parameter names) will likely be needed to the helper script. Regarding Salv's question, I don't think I've ever used Twinkle to block socks or puppeteers, if I don't use the helper script I generally use easyblock as it adds the user page tag as well as blocking and adding the block notice. Callanecc (talkcontribslogs) 01:55, 16 June 2015 (UTC)

custom tag list[edit]

The previous version had a feature of customizing the tag list by removing or renaming various options, & adding custom ones. The current versionseems to only permit adding them--or am I missing something? DGG ( talk ) 00:12, 17 June 2015 (UTC)

I don't ever think Twinkle allowed you to remove or rename tags. How long ago was this? — This, that and the other (talk) 14:33, 17 June 2015 (UTC)
It certainly did before it was a gadget, because you could edit the script. I do not recall whether earlier gadget version did. It certainly ought to. DGG ( talk ) 03:53, 21 June 2015 (UTC)
Whew, that's going back a few years. Well yes, if you can edit the script you can do anything. I suppose something could be added into Twinkle for the benefit of advanced users, but don't hold your breath... — This, that and the other (talk) 12:20, 21 June 2015 (UTC)


Can we use {{uw-repost}} for WP:G4, instead of the intimidating wall of text that is {{Db-repost-notice}}, made complete by the danger sign? Alakzi (talk) 22:41, 15 June 2015 (UTC)

I've changed the warning icon to the info one in the meantime, as I can't see a reason to assume bad faith. Callanecc (talkcontribslogs) 01:59, 16 June 2015 (UTC)
@Alakzi: But isn't {{uw-repost}} just another wall of text? Doesn't seem like much of a win to me. — This, that and the other (talk) 14:35, 17 June 2015 (UTC)
It is shorter and friendlier, and it is what the documentation of {{Db-g4}} recommends to be used. Alakzi (talk) 16:55, 18 June 2015 (UTC)

The new block module[edit]

@MusikAnimal: A few more issues (continued from Wikipedia:Administrators' noticeboard/Archive272#New Twinkle block module!). Sorry!

  • When I untick the warning template and just issue a block, the blue popup window doesn't time out. It's only a minor issue, but it would be more consistent if it displayed the user contribs page (to show the block) after the usual timeout.  —SMALLJIM  12:05, 16 June 2015 (UTC)
    Got it. A fix will be deployed with the next release MusikAnimal talk 15:19, 16 June 2015 (UTC)
  • It would be nice if the usual "reloading talk page in a few seconds" timeout could be shortened or made customisable.  —SMALLJIM  12:05, 16 June 2015 (UTC)
    I've also thought the timeout was too long. I didn't set this, it's apparently the way core Morebits.js behaves. I can look into some customization but that job may be better fit for the author of Morebits MusikAnimal talk 15:19, 16 June 2015 (UTC)
  • Regarding customising the order of the block reasons as already discussed, I understand that adding this ability to the Twinkle preferences panel would be hard. I wonder if Twinkle.block.blockGroups in MediaWiki:Gadget-twinkleblock.js could be overridden in userspace (in vector.js?) I don't know anything about large-scale javascript, so feel free to tell me if this is a stupid idea.  —SMALLJIM  12:05, 16 June 2015 (UTC)
    Yes! I tried this out on testwiki and it just worked. You could even come up with your own Twinkle.block.blockPresetsInfo, just go by the comments at the top. You change the order and grouping of Twinkle.block.blockGroups as you please, it just needs the format:
Twinkle.block.blockGroups = [
    label: 'Group label'
    list: [
      { label: 'description of preset #1', value: 'preset_1' }
      { label: 'description of preset #2', value: 'preset_2' }
    ...another group...
Etc, where preset_1 correlates to the key of a Twinkle.block.blockPresetsInfo. Hopefully that makes sense, and let me know if you need help MusikAnimal talk 15:19, 16 June 2015 (UTC)
For info: I've been trying this out for the last couple of days. I added a revised Twinkle.block.blockGroups array to my vector.js, and it's been ...interesting. Basically, after several purges to get it to stick at all, it now works sometimes, but I can't suss out what causes it to work or not. Sometimes it works after purging the page I'm on again, but not always: it may relate to which user page (talk, user, contribs) that I'm invoking TW's Block from. I tried moving the array to the top of my vector.js page, but then it stopped everything else in there from running at all.
I suppose I could fork the whole TW code into my userspace, but that's not a good idea. I found this on hi.wp (linked from #Stuff above), which seems to be a halfway house, but I couldn't understand it well enough to try it out.  —SMALLJIM  16:33, 18 June 2015 (UTC)
@Smalljim: You're having trouble with it because it's a structural problem with trying to override a variable in a (portion of a) script that isn't designed to handle it. Specifically, it depends on the order your various JavaScript files are downloaded and parsed by your browser. Since TW is a gadget, it loads separately from your vector.js, and may come before *or* after it. If vector.js loads before TW does, then the override you're trying won't work, because TW resets the variable when it loads. If TW loads first, then when vector.js loads, it overrides the variable correctly, and it will work as you were expecting it to.
A solution to this structural problem would be to check whether Twinkle.block.blockGroups is defined or not before the assignment statement, e.g. if (typeof Twinkle.block.blockgroups === "undefined") and assign a value to the variable only if it's not already defined. This would require a change to the module. —Darkwind (talk) 23:40, 18 June 2015 (UTC)
Thanks for that clear explanation, Darkwind. Couldn't I do that check in my vector.js, and if it's true (i.e. undef) wait a few hundred ms for TW to load and then load the variable? Or, instead of loading TW as a gadget, would loading it first in my vector.js work? (I don't think so) Or what about using Greasemonkey instead? I assume that does its stuff after everything has come down the wire (I've got it installed, but never tried writing anything for it).  —SMALLJIM  10:30, 19 June 2015 (UTC)
@Smalljim: Actually, what might work is to bind the overriding assignment to the window load event, which is supposedly the last event to fire as the page loads (e.g. after all scripts have been downloaded and parsed). You could do so like this. —Darkwind (talk) 20:00, 19 June 2015 (UTC)
@Darkwind: Thanks! - in the meantime, I moved the revised Twinkle.block.blockGroups definition into a Greasemonkey script (it's simple!) where it worked at least as well as before: I've now wrapped the window load event round it there, so will see if it works 100% now. Thanks for these ideas - I've done the same thing for the Morebits timeout ( = 1000;) (see bullet 2 above) and that seems to work too.  —SMALLJIM  21:00, 19 June 2015 (UTC)
  • When I tried to issue a notice (after already having blocked), not only did the popup not time out but the block template was not added to the page. I had to add it manually. I was not having any other issues at the time. User_talk:Andhisteam was the page concerned. Thanks, Black Kite (talk) 12:14, 16 June 2015 (UTC)
    @Andhisteam: Not able to reproduce. You say that the popup didn't time out, which leads me to believe you reblocked when you thought you were issuing a template, since it's the issuing of the template that makes the popup automatically close (I'm fixing this, though). Are you sure you're checking the right options? Note also you typically will block and template at the same time using Twinkle. MusikAnimal talk 15:19, 16 June 2015 (UTC)
    No, I definitely unticked the block option (I'd already blocked the editor, forgetting about the new block options). I'll let you know if it happens again. Black Kite (talk) 01:16, 19 June 2015 (UTC)
    It's just happened to me again. Blocked an editor, then went to add the template using the new module, same result. Had to add the template manually. Also, when I try to actually block an editor using the module, I simply keep getting an error message "please provide an expiry" even if I already have done. Is it just me? Black Kite (talk) 10:13, 19 June 2015 (UTC)
  • Template:Blocked talk-revoked-notice isn't being subst'ed (e.g. at User talk:Rahul Panchal classic tenders).  —SMALLJIM  12:28, 16 June 2015 (UTC)
    Got it. The reason why it is not is because the template name is not prefixed with uw-, which is how the script determines it should substitute in accordance with WikiProject User Warnings. This is a bad way of doing it, and I will change it so that there's a definition of whether a template should be substituted, but what I'm getting at is this template should have the uw- prefix. MusikAnimal talk 15:19, 16 June 2015 (UTC)
    Maybe it should be moved to {{uw-Blocked talk-revoked-notice}} (or some better name, this seems unecessarily unwieldy). 15:28, 16 June 2015 (UTC) — Preceding unsigned comment added by Salvidrim! (talkcontribs)
    What about moving it to {{uw-talkrevoked}} (which is a redirect currently)? It looks better. --TL22 (talk) 20:33, 16 June 2015 (UTC)
    That's pretty much exactly the kind of "better name" I was thinking of. Perhaps, instead of actually renaming, Twinkle could just call on {{uw-talkrevoked}}? Is it fine if Twinkle calls template redirects? ☺ · Salvidrim! ·  20:48, 16 June 2015 (UTC)
    It can! I still think implementation-wise I should have some programmable indication of whether a template should be substituted, but anything prefixed with uw- is supposed to be WP:UW standard, meaning it's substituted. So for the purposes of this bug report, we can consider it fixed and will go out with the next deploy. Thanks MusikAnimal talk 20:57, 16 June 2015 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────Just so you know I'm tracking issues and adding documentation at User:MusikAnimal/twinkleblock. I will also update the Twinkle documentation soon. MusikAnimal talk 23:42, 16 June 2015 (UTC)

How to get Twinkle[edit]

How do you get Twinkle on your account? I wonder how people possess such applications on Wikipedia. Qwertyxp2000 (talk - contributions) 02:04, 21 June 2015 (UTC)

Twinkle is available to any registered user, I think. Go to your preferences, then the "Gadgets" tab, and you will find Twinkle about halfway down the "Browsing" section. -- John of Reading (talk) 06:50, 21 June 2015 (UTC)
(any autoconfirmed user*) — Jeraphine Gryphon (talk) 09:31, 21 June 2015 (UTC)
I think this needs more emphasis. I just spent 10 minutes trying to figure out why I wasn't seeing the option. 217IP (talk) 01:58, 22 June 2015 (UTC)
@Qwertyxp2000: There are instructions at Wikipedia:Twinkle. If they are not clear enough, please let us know so we can improve them for other users. Thanks for your interest in Twinkle! — This, that and the other (talk) 12:22, 21 June 2015 (UTC)
Yes! Thank you! I enjoy Twinkle. I even created a template that shows that a user uses Twinkle to use RFPP. Qwertyxp2000 (talk | contribs) 07:21, 22 June 2015 (UTC)


I have rewritten this template for compliance with the other CSD notice templates and to separate it from {{uw-attack}}. --TL22 (talk) 15:13, 21 June 2015 (UTC)

Looks good. I had a bit of a go at improving the wording further . Feel free to revert if you don't like it, but I really think at least the "Thank you" has to go. It doesn't make a whole lot of sense in the context of the message (are we thanking users for creating an attack page?) and especially not halfway through the message. — This, that and the other (talk) 13:01, 22 June 2015 (UTC)


uw-dls has been unfortunately deleted per an outcome in a deletion discussion. Please remove it from the single issue warnings section. --TL22 (talk) 20:43, 21 June 2015 (UTC)

Twinkle broken? Only issuing level 1 warnings[edit]


Attempting to issue a >level 1 warning still presents the list for the level 1 messages, and that indeed is what gets left on the page. [2] & [3] were both supposed to be level 3s. Andy Dingley (talk) 22:57, 23 June 2015 (UTC)

Having the same problem. Also doesn't report users to WP:RVAN. Datbubblegumdoe (talk) 23:37, 23 June 2015 (UTC)
Also can't access anything other than the level 1 warnings (meaning no single issue warnings, for instance). ~ RobTalk 00:58, 24 June 2015 (UTC)
I'm testing at User talk:Sandbox, nothing but level 1 warnings! The Sky Is Falling!!!! EoRdE6(Come Talk to Me!) 03:22, 24 June 2015 (UTC)
It had started working again for me earlier, so it appears that this issue is coming and going for whatever reason. ~ RobTalk 03:23, 24 June 2015 (UTC)
@BU Rob13: According to MusikAnimal at VPT, "Judging by the error I'm seeing in the JavaScript console I think it may have to do with a class having recently been removed. This is also affecting the Warn module of Twinkle, where you are unable to issue anything other than a level one warning. I've reported it and I was told it is being fixed." What ever change is made will probably filter through to everyone and the servers eventually. EoRdE6(Come Talk to Me!) 03:28, 24 June 2015 (UTC)
Yes this should have been fixed. Twinkle started working again for me sometime yesterday. Try clearing your cache MusikAnimal talk 03:31, 24 June 2015 (UTC)
@MusikAnimal: After trying to warn an IP a few minutes ago for posting nasty comments to my talk page, I found that when I tried to post a level 4 warning, only a level 1 was posted, so I'd call the issue "not fully resolved". Dustin (talk) 15:35, 24 June 2015 (UTC)
I should probably read your entire comment next time. I'll try to clear my cache. Dustin (talk) 15:36, 24 June 2015 (UTC)
Neither bypassing the cache on the specific page nor clearing the entire browser cache resolves the problem. This is still an issue. --Chris (talk) 15:41, 24 June 2015 (UTC)
I agree; the problem is still present even after I clear my cache. See my level 4 test. I normally don't notice the numbers in the template names once I select the warning level/type from the top, but I see that General note, Caution, Warning, Final warning, Single issue notices, and Single issue warnings all just show "General note"'s selection. Dustin (talk) 15:46, 24 June 2015 (UTC)
Per the section below this one, it does seem to be fixed now if I purge my cache. --Chris (talk) 15:53, 24 June 2015 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────Yes, it is working for me, and the issue that apparently caused it was the absence of mw.RegExp, which is defined when I try it in my browser's JavaScript console. Hang tight, we'll figure it out eventually. Sorry for the disruption MusikAnimal talk 15:56, 24 June 2015 (UTC)

Ah, looks like Amalthea took care of it. See, I told you it'd get fixed! Face-grin.svg MusikAnimal talk 15:58, 24 June 2015 (UTC)
It seems to be working now. Dustin (talk) 16:03, 24 June 2015 (UTC)

Block templates[edit]

I dont know if this is related, but Twinkle didnt have the block templates for me when I tried to use them. I often manually type out the notices anyway, but I clicked Twinkle to find which ones were available (i.e. looking for an edit filter related one) and found that they weren't available at all. I double checked to make sure I hadn't suddenly gotten logged out, but sure enough I was logged in to my admin account and Twinkle seemed to think that I wasn't. And just clarifying that this was after I purged the cache, though I didn't take the "extreme" measure of deleting all browsing data since I assume the other people posting here didn't do that either. Soap 14:42, 25 June 2015 (UTC)

Block templates can now be found in MusikAnimal's new "Block" module, which should be accessible next to the "Warn" tab or menu item. — This, that and the other (talk) 15:04, 25 June 2015 (UTC)
OK thank you. It's actually three tabs over for me, because of other things I have installed, so I didn't notice it. This actually looks really good, since it has some of the ideas I've been wishing for all along, i.e. "custom block reason" as the default instead of just templates (templates are good, but I dont use them very much). And I like that you can test it (I assume that's what this is?) by having it type out the templates and whatever else you want in but not actually block the user. Actually, I guess that's probably intended for when you've already done the block and just need to add the message. Soap 15:48, 25 June 2015 (UTC)

Reports to UAA not working[edit]


Twinkle is hanging on the "retrieving the page" stage when reporting to UAA. EvergreenFir (talk) Please {{re}} 00:15, 24 June 2015 (UTC)

This worked fine for me on my Mac using Chrome: Diff of Wikipedia:Usernames for administrator attention. -- Diannaa (talk) 00:41, 24 June 2015 (UTC)
Just worked for me too. Not sure what was happening before. EvergreenFir (talk) Please {{re}} 00:43, 24 June 2015 (UTC)
It's started hanging for me just now. The bug where it only leaves level-1 warnings is "back", too—in quotes because I never had the problem yesterday when the others did, but I do now. I cleared my cache and it's still happening. dalahäst (let's talk!) 07:56, 24 June 2015 (UTC)
I'm having this problem, too. Liz Read! Talk! 11:13, 24 June 2015 (UTC)
  • I get the same error, where it's stuck on "retrieving the page", when I try to create AIV reports. (I've been getting the level-1 only warnings bug as well, yesterday and today.) I use Firefox for MacOS. --bonadea contributions talk 11:36, 24 June 2015 (UTC)

The js.console error for the warning level problem is TypeError: $.escapeRE is not a function. It looks as if it's related to the problem reported at WP:VPT#File upload wizard broken. @MusikAnimal, This, that and the other, and Amalthea: There appears to be a (temporary) resolution described there that the author can implement.  —SMALLJIM  12:28, 24 June 2015 (UTC)

Anyone know what's going on here? @Ori Livneh and Max Semenik: Was the jQuery.mwExtension just suddenly removed without any warning, or did I just miss the notification? — This, that and the other (talk) 13:46, 24 June 2015 (UTC)

I'm going to guess this jquery.mwExtension was added back? I was able to successfully report to UAA, and I tried $.escapeRE in the JavaScript console and it is defined. If I can get it to break on testwiki than I should be able to fix it, all is working fine there too. MusikAnimal talk 15:19, 24 June 2015 (UTC)
Apparently: "In ≥ 1.26 use #mediawiki.RegExp instead."[4] Amalthea 15:37, 24 June 2015 (UTC)
It was marked as deprecated 4 days ago apparently, I haven't checked why it's missing all of a sudden, but I have replaced the function call nonetheless ... should be working again in a few minutes. Amalthea 15:50, 24 June 2015 (UTC)
Thanks Amalthea - the warning levels are OK again after that fix.  —SMALLJIM  16:00, 24 June 2015 (UTC)
Working again for me now as well, and I don't get the undefined function error in Chrome's console. dalahäst (let's talk!) 18:24, 24 June 2015 (UTC)
You need to declare the dependency on jquery.mwExtension though. modules are never guaranteed to be present. —TheDJ (talkcontribs) 08:47, 25 June 2015 (UTC)
But I don't think we depend on mwExtension after Amalthea's recent fixes..? — This, that and the other (talk) 15:03, 25 June 2015 (UTC)
I'm rather certain we don't, and I've actually remembered to add mediawiki.RegExp to the dependencies … Amalthea 16:31, 25 June 2015 (UTC)

Delete batch tool: incorrectly deleted page as a redirect[edit]

See [5]. I think you've fallen prey to the same logic error that I did at phabricator:T87725. Magog the Ogre (t c) 02:28, 25 June 2015 (UTC)

Ah yes, seems we are using "list=backlinks&blfilterredir=redirects". I'll see if I can get it changed over to the more accurate alternative. I should point out that this is not a new bug, so well done for spotting it! — This, that and the other (talk) 15:01, 25 June 2015 (UTC)??

The new block module isn't working[edit]

Try it and you'll see. Is it off sick? Bishonen | talk 17:41, 26 June 2015 (UTC).

@Bishonen: Works for me. Can you give more information? Does the block module window open at all? MusikAnimal talk 17:44, 26 June 2015 (UTC)
I was just about to push an update but I will hold off until I can confirm the current version is working for you. If it is not I'll try to see if it can fixed with the next deploy as well MusikAnimal talk 17:50, 26 June 2015 (UTC)
Yes, the window opens, MusikAnimal, but it's blank except for a line at the top reading "Block or issue block template to [username]", and a "Submit query" button at the bottom. I can't ask it to do anything, you know? Just an empty window. It worked yesterday. Bishonen | talk 17:51, 26 June 2015 (UTC).
@Bishonen: Sounds like you've either got a very slow internet connection or running into an undiscovered bug, perhaps a conflict with another script you're using. What browser/operating system are you using? If you don't mind I'm going to walk you through opening up your browser's JavaScript console so we can check for errors. MusikAnimal talk 17:54, 26 June 2015 (UTC)
But it worked yesterday, and I haven't added any new scripts. Browser... browser... uh... Firefox 38.0.5. Mac OSX 10.6.8. Too old? Bishonen | talk 17:58, 26 June 2015 (UTC).
And my connection is very reasonably fast broadband. Bishonen | talk 18:01, 26 June 2015 (UTC).
Not too old at all, very modern browser at that! Please press Command+ Option+I to open up Firefox's developer console. At the top of the developer console are several tabs, please click on "Console". Now, try to open up the Twinkle block module and let me know if you see anything printed in the console. MusikAnimal talk 18:03, 26 June 2015 (UTC)
I've got the console, but there's an unbelievable amount of stuff in the "console" tab, and it's not searchable. And the little headers are all the same, "console.trace():". And the content of them looks very much the same too. :-( I can't see Twinkle. Bishonen | talk 18:12, 26 June 2015 (UTC).
Within the console, you can filter which types of messages are shown. I believe "logging" is on by default. The only one you want is the "JS" (orange dot). Errors are always printed in red. Do you see anything in red? MusikAnimal talk 18:15, 26 June 2015 (UTC)

Yeah, these are pink with a red x:

Blocked loading mixed active content ""[Learn More] load.php:2:0

Blocked loading mixed active content "^demon/csd.js&action=raw&ctype=text/javascript&dontcountme=s"[Learn More] load.php:2:0

Blocked loading mixed active content ""[Learn More]

Bishonen | talk 18:21, 26 June 2015 (UTC).

Do I have to remove the corresponding scripts in my monobook.js for the block module to work? I've had them for a long time, I'm no longer sure exactly what they do, but I think I need Zocky's searchbox. Bishonen | talk 18:26, 26 June 2015 (UTC).
No, you shouldn't have to. Also the "mixed content" errors you've listed shouldn't affect Twinkle. Who in particular are you trying to block? Also what skin are you using? MusikAnimal talk 18:32, 26 June 2015 (UTC)
Monobook. I tried to block 2001:590:3c03:17a:ad43:43b2:f6a:8efa. (I've done it by hand now.) Bishonen | talk 18:36, 26 June 2015 (UTC).
Hey, I just experimentally tried to block you, and it seemed fine! (I didn't actually confirm; should I try that too? :-) ) Is it those accursed IPv6'es that are the problem? I already hate them because the ranges are so mystifying. Bishonen | talk 18:40, 26 June 2015 (UTC).
No, I tried to block that IP and it worked fine. But please, do not block me!!! :) I guess try another IPv6 address, and also a IPv4 and let me know if you have problems. If you want to test blocking accounts you can use User:Keegagan MusikAnimal talk 18:42, 26 June 2015 (UTC)
OK, I was able to block 2001:5B0:28FF:EF0:0:0:0:3C. I can't block 2001:590:3c03:17a:ad43:43b2:f6a:8efa, 2001:590:3c03:185:2956:ef0e:2aa4:83c, or 2001:590:3c03:194:23fe:735d:1328:925e. (BTW I started to try to figger a possible rangeblock for the character who's using those three, but had to give up. I'm getting a "502 Bad Gateway" error for NativeForeigner's IPv6tool :-() I have no trouble blocking any IPv4's. Bishonen | talk 18:59, 26 June 2015 (UTC).

──────────────────────────────────────────────────────────────────────────────────────────────────── I'm stumped. I'm using the same browser/OS, I've tried the same IPs, and had another admin try it out as well, and it worked fine. I'm going to proceed with the update I had, as I don't think it will make your situation worse. My recommendation for you is to first try refreshing the page when Twinkle doesn't load, perhaps a few times before you can conclude it's that IP in particular and not something else. MusikAnimal talk 19:13, 26 June 2015 (UTC)

Just to be sure, let's also check your network log. When the Twinkle block module first opens, it hits the API before loading the module in full. The "blank window" as you describe would make sense if no response or bad response came back from the API. So... let's open back up the developer console with Command+ Option+I. Now select the "Network" tab. Now refresh the page. You should output in the developer console. Then open up the Twinkle block module. Now, the leftmost skinny column should have a checkmark as the title, right next to the "Method" column. Click on that check mark twice to sort the network activity. Please then go through the list and tell me if you see any entry with a code other than 200 (green) or 304 (orange triangle). Any errors should be in red, but I'm not certain. MusikAnimal talk 19:18, 26 June 2015 (UTC)
Not to hijack this thread, but I had a similar problem yesterday when I was trying to check the Twinkle Block Module for a block of a named account, but just got the same screen that Bishonen did (at least from what I can remember). I went back to easyblock to do the task. However, the twinkle module seemed to work today though I used it only for placing the notice and not performing the block (but all fields were there). I'm on FF 38.0.5 and 10.10.3, monobook with scripts on common if that should matter. It could have just been operator error on my part though. cheers. —SpacemanSpiff 19:25, 26 June 2015 (UTC)

Right. No, they're all 200 green or 304 orange. Sorry to be a pain. Hello, Spaceman. Bishonen | talk 19:37, 26 June 2015 (UTC).

Oh boy. I assume you did try refreshing the page a few times to verify it is that specific IP? It seems odd how it would vary user to user. Maybe if the username had abnormal characters, but with IPv6 you only have a-f, 0-9 and : MusikAnimal talk 19:48, 26 June 2015 (UTC)
Sure, I tried several times with those three pesky IPv6'es. It never happened that an IP wouldn't work at first and then worked after a few refreshs. The ones that worked, worked right away always; the ones that didn't work, never did. Seems odd is right. Especially when one IPv6, 2001:5B0:28FF:EF0:0:0:0:3C, worked fine. You can see how that one is off on its own, while the other three are related. But it seems absurd that it would affect the 2001:590:3c03:xxxx range specifically — doesn't it? Especially when it's apparently just me. Bishonen | talk 20:04, 26 June 2015 (UTC).
(edit conflict)::Was a simple enough username -- Lucky5833. I tried reblocking the user now and it seemed to work fine (didn't click to actually do it but I was able to select all options, got the already blocked notice, and able to preview), might have been a one-off. Hello Bishonen and thanks for checking it MA. —SpacemanSpiff 20:06, 26 June 2015 (UTC)

2 Redirect Tags Suggestion[edit]

Hello. I review redirects in the new pages feed, and there are two tags that I use commonly but Twinkle doesn't have in its tag menu, {{R from modification}} and {{R from short name}}. Could I have these added to the menu? Thanks! Compassionate727 (talk) 18:45, 26 June 2015 (UTC)

Oh, and I should also point out that it usually doesn't mark unpatrolled pages as patrolled while tagging them. This is also true for CSD (and probably PROD, AfD, etc., but I don't know about them). Compassionate727 (talk) 18:51, 26 June 2015 (UTC)

Create protect not working[edit]

When I go to the deleted page, pull up the page protect dialog box, and click Submit Query nothing happens. --NeilN talk to me 20:25, 26 June 2015 (UTC)

This is a known issue. Create protect has been broken for a little while now. I'll try to get a fix out really soon. — This, that and the other (talk) 02:36, 27 June 2015 (UTC)

Where should I put image[edit]

A screenshot of Twinkle's rollback and welcoming features

Where should I put this image within this Twinkle? Qwertyxp2000 (talk | contribs) 08:43, 28 June 2015 (UTC)

I'm afraid you're going to have to explain yourself a bit more clearly. What is it that you want to do? — This, that and the other (talk) 13:23, 28 June 2015 (UTC)
Put this image within WP:TWINKLE page. Qwertyxp2000 (talk | contribs) 05:31, 29 June 2015 (UTC)
I don't think it is a very good screenshot. It doesn't clearly show Twinkle's features. Moreover, I think the screenshot that is currently on WP:TW is more informative than yours, don't you think? — This, that and the other (talk) 11:38, 29 June 2015 (UTC)
Yep, I agree with you. By the way, does a gallery sound like a good idea? Qwertyxp2000 (talk | contribs) 20:35, 29 June 2015 (UTC)

Adding a "harassment directed to X" to Uw-harass[edit]

Hi, I am proposing to add an "as you did at x to user" in the templates uw-harass 1 through 4/4im. This will clearly tell the user who harassed others who was the victim. But that requies 3 params so it needs some coding of that part of Twinkle.

Please stop your disruptive behaviour. Your behaviour is verging on harassment. Wikipedia prides itself on providing a safe environment for its collaborators, and harassing other users, as you did on Foobar to UBX, potentially compromises that safe environment. If you continue behaving like this, you may be blocked from editing.

Stop icon You may be blocked from editing without further warning the next time you purposefully and blatantly harass a fellow Wikipedian, as you did at Foobar to UBX.

According to ToonLucas22,

That can't be done because the warnings then would need 3 parameters, on Wikipedia user warnings have only 2 parameters. Adding an extra parameter could potentially break the way Twinkle posts these warnings.

So could anyone on the Twinkle devteam help me solve this problem? --Fazbear7891 (talk) 23:17, 28 June 2015 (UTC) LGBT flag square.svg

Hi Fazbear, please keep in mind that the target of harassment may often prefer not to have their details propagated with the warnings as this may draw more unwanted attention. This is especially true if it is a personal attack or the language used was particularly offensive, such as racist, mysogynistic or homophobic in nature. An abusive user's edits can be easily tracked if an administrator wanted to check it over. -- (talk) 23:30, 28 June 2015 (UTC)
@Fazbear7891: please don't include images (such as File:LGBT flag square.svg) in your signature, however noble the intent: they go against WP:SIGN#Images, which is policy. --Redrose64 (talk) 08:33, 29 June 2015 (UTC)
@Redrose64: The images is after the timestamp, meaning it isn't part of the signature, but added manually after the message. No policy about that. (tJosve05a (c) 19:10, 29 June 2015 (UTC)
I agree with Fæ. — This, that and the other (talk) 11:37, 29 June 2015 (UTC)
The result is no. I will close the discussion here. --Fazbear7891 (talk) 20:34, 29 June 2015 (UTC)

Invisible Twinkle[edit]

A couple weeks back, on my nonWP wiki, I had a problem of Double-Twinkle. Thanks to the advice of "This, that", I could resolve that problem. At that point in time, Twinkle was working perfectly. Unfortunately, a week later, while trying to fix another problem after the upgrade of my MW installation, the tech staff on my server (RoseHosting) seem to have changed something - don't know what and they also don't know what - and now Twinkle has completely disappeared. To their credit, RoseHosting tech support did try to help in resolving this issue, but they failed.

The Gadgets extension is correctly installed. Some of my gadgets work correctly (for example, HotCat and RevisionJumper). Another gadget, Edittop, works, but only when the code is also placed in the user's personal common.js. But Twinkle is nowhere to be seen. When I go to the Twinkle/preferences page, the message I receive is: "You must have Twinkle installed (either as a gadget or manually as a user script) to use this page." Well, Twinkle is installed, but for some reason that I just cannot figure out, it is not working properly. I have also tried to resolve the issue by adding Gadget-Twinkle.js and the Gadget-morebits.js to the user's personal common.js, but even that unsatisfactory workaround did not succeed. Any ideas on what has gone wrong now and how to fix it? --Abhidevananda (talk) 14:55, 29 June 2015 (UTC)

@Abhidevananda: To rule out the obvious: did the tech staff revert the server to a backup predating your Twinkle setup? That can sometimes happen. If that's the case, you might just need to start over from the beginning and set it up again. The other possible issue I see is that with the upgrade to MW, it may be necessary to (re)declare or adjust ResourceLoader dependencies in the gadget (which unfortunately is not something I know how to do). jcgoble3 (talk) 02:03, 1 July 2015 (UTC)
Jcgoble3, thanks for your thoughts. Regarding "the obvious", no... they did not revert to a backup older than a single day. They wanted to go back one week (which also was long after my Twinkle setup), but I was not willing to give up so much work. So the installation of Twinkle appears to be exactly as it was before. It should be working fine, but MediaWiki treats it as if it is not yet installed. As to the second possible issue, I too have no idea how to adjust ResourceLoader dependencies, but I would happily give it a try if it could fix this. --Abhidevananda (talk) 04:11, 1 July 2015 (UTC)
Are you able to provide a link to the wiki? — This, that and the other (talk) 06:57, 1 July 2015 (UTC)
Absolutely. It's To avoid spam, we distribute login credentials on request. But I've just sent you by email the same admin credentials that RoseHosting uses. Thank you for your insights and assistance. --Abhidevananda (talk) 08:20, 1 July 2015 (UTC)
Thanks. I logged in using those credentials and Twinkle appeared without a problem for me, although it did often take a few seconds for it to appear (this may be due to a slow server). Try clearing your browser cache, logging out and in again, and seeing if it works using the credentials you sent me. If you use another account for your day-to-day work, try also logging in with that account. If it does not work there, you may have some invalid JavaScript code in another gadget or the user's "common.js" file. — This, that and the other (talk) 12:06, 1 July 2015 (UTC)
Wow! The problem seems to be somewhat browser dependent. Generally, I use Firefox. With Firefox, Twinkle just does not appear at all on my wiki, but it does appear on Wikipedia. With Firefox, Twinkle does not appear on my Wiki, regardless of what user ID I log in with. However, with Internet Explorer, Twinkle come up fine, again regardless of what user ID I log in with. So now the question is: What would have changed inside Firefox to block Twinkle, but only on my own wiki and not on Wikipedia? By the way, my cache was cleared. The problem is also not due to my add-ons; because I restarted Firefox in Safe mode (all add-ons disabled), and the problem persisted.) As I don't have any special settings inside Firefox for my wiki as opposed to for Wikipedia, this is rather mysterious. --Abhidevananda (talk) 13:01, 1 July 2015 (UTC)

I hate the new block module[edit]

Not to be a Negative Nancy, but I'm not a fan of the new setup at all. I've been trying to work with it, but it makes blocking slower and more complicated, not easier (at least for me), and the block message often doesn't say exactly what I intended it to say. Would it be possible to leave the traditional blocking options in the talk page warning box as it was before, while the new module would still be available for those who find it easier? --Bongwarrior (talk) 18:40, 29 June 2015 (UTC)

@Bongwarrior: Sorry you're having trouble! For starters, if you just want to add a block template, it should require no more clicks than it did before. TW > Block > uncheck Block > choose a template and submit. Before it was TW > Warn > choose Block > choose a template and submit. Let me know if that alone is an issue, as hopefully it is not!
What I am more interested to here is why you find it complicated. The idea is you don't have to go to Special:Block anymore, and if you are blocking and templating with Twinkle it should be considerably faster than the traditional route. Are you using Twinkle to perform the block itself? Can you give an example of when the template didn't say what you wanted it to? Thank you for bearing with me as I try to ensure this new module as a clear improvement for all admins. MusikAnimal talk 19:27, 29 June 2015 (UTC)
Thank you, and I need to reverse myself a little bit: I was under the impression that the new blocking options were only available under the user's contributions page, which I thought was cumbersome and counter-intuitive, particularly if I only needed to leave a block template. I now see that it's also available on the user's talk page, but my setup has it pushed waaaay off the screen to the right. I'll have to try to mess with my settings to put the block button somewhere more accessible, but once I do that it should be a lot easier for me.
As far as not saying what I want it to say, the main gripe I have is with the available IP block templates. From what I can tell, those templates always say "Anonymous users from this IP address have been blocked from editing...". That's fine sometimes, but if it's obvious that a single user is behind the IP, I'd rather it say "You have been blocked from editing...". For an example, see User talk: For some reason, NeilN's block said "you" but mine didn't, although we both used Twinkle and we both selected uw-vblock. Custom setup by Neil, or user error on my part?
Once I get everything figured out, I'd prefer to use Special:Block for blocking and Twinkle only for the block message, because the block message can usually wait a minute or two. I usually double check to make sure any vandal edits have been reverted (and reverted correctly) before leaving the block notice. --Bongwarrior (talk) 20:27, 29 June 2015 (UTC)
Ah, you are using Monobook? In this case I believe the Twinkle links are outlayed horizontally. The Block item should be towards the front with the other admin actions such as CSD.
The "anonymous users from this IP address..." was a recent addition to the Block module. Based on the documentation, I believe the text generated by {{uw-block}} is meant to be worded this way, where you should add anon=yes when blocking anonymous users (or rather, omit it when you are not). This is presumably in conformity to the stewardship of WikiProject User Warnings... but we can discuss at WT:UW to iron out if that is anything important. The old Twinkle Warn module simply did not offer this functionality, so I believe people just got used to that. It's difficult to please everyone here... but if we can establish either consensus or backing from WP:UW than that is what we will go with. I don't want to add yet another checkbox for omitting anon=yes unless enough people demand it. If it is clearly a single person behind the IP we could consider a hard block. The Block module looks at the selected/current block options and will omit the anon parameter if you are performing a hard block, as in that case anyone editing behind the IP (not just anonymous users) are unable to edit. For shared IPs there are various templated (e.g {{anonblock}}) presets you can use.
Have you given block+warn a try? It may win you over :) Just so you know, there is a "blank talk page on indefinite block" option in the Twinkle preferences, that will leave only the block notice and remove all other content. Hope this helps! MusikAnimal talk 21:16, 29 June 2015 (UTC)
Yes, Monobook, I can't stand the others. Thanks for your help, I've hidden the tabs I never used (which needed to be done anyway) and it should work out a lot better for me now. I'd still prefer that the old wording be available for IPs, but I'll adapt if I don't get it. One more trivial thing, no big deal at all, but after the standard tabs, mine currently go Warn, Welcome, then Block. Is there an easy way that you know of to swap Welcome and Block so that it goes Warn > Block > Welcome? --Bongwarrior (talk) 21:42, 29 June 2015 (UTC)
That is sensible and I can make that happen :) MusikAnimal talk 22:14, 29 June 2015 (UTC)

I love the new block module[edit]

I was instantly addicted to it. Just thought I'd mention that, to balance the TOC wrt to the previous section, and especially because I complained above about having mysterious trouble blocking some IPv6 users. Thank you very much for your quick response and extensive checking there, MusikAnimal. I just tested blocking those IPv6es again, and this time it worked fine. Since you've just done an update, if I've got that right, could that have been what fixed it, or is it just that the little man in my computer is now in a better mood? Bishonen | talk 10:30, 1 July 2015 (UTC).

@Bishonen: Glad to hear it!! Face-grin.svg I made an array of various changes with the last update, I can't say what would have fixed your issue, but hey, so long as it's working! As always let me know if you run into anymore issues and I'll do my best to address them. Cheers MusikAnimal talk 15:36, 1 July 2015 (UTC)

Twinkle enabled in preferences, how to get it going?[edit]

I've used Huggle and STiki previously, so I thought I'd try Twinkle out. Having enabled the checkbox in my preferences, I fail to see how to proceed. Shouldn't I be seeing an icon to start the program and begin patrolling? Thanks. Jusdafax 13:30, 1 July 2015 (UTC)

It's not that kind of a program. It just gives you a whole bunch of useful tools when you're already on certain pages, but it doesn't bring vandalism or other problems to you. I strongly recommend keeping it enabled though, it's insanely useful and convenient. — Jeraphine Gryphon (talk) 13:36, 1 July 2015 (UTC)
Ok, thanks. Jusdafax 13:50, 1 July 2015 (UTC)