Jump to content

Wikipedia talk:Twinkle/Archive 36

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 30←Archive 34Archive 35Archive 36Archive 37Archive 38→Archive 40

A11

So for a long time now (actually, ever since A11 was implemented and added to Twinkle), there seems to be a problem with A11. When I tag an article as A11, unlike the other CSD criteria, for some reason, Twinkle doesn't automatically add a message at the creator's talk page. Instead, I have to manually add the message. None of the other CSD options have this problem. Is this a bug, or did someone just forget to make it in such a way that when a page is tagged as A11 with Twinkle, the creator is automatically notified? Narutolovehinata5 tccsdnew 04:54, 10 December 2014 (UTC)

Go to your Twinkle options and see if you've checked off the box under notify editors for A11. KonveyorBelt 19:50, 10 December 2014 (UTC)
Although we added A11 to the default list of CSD criteria for which a user talk notification is provided, anyone who has customised their CSD notification preferences will find that the A11 notification is turned off. This is an unfortunate consequence of our preferences system - every time a new CSD criterion is added, you will have to manually enable the notification at WP:TWPREFS if you are using non-default CSD notification settings. If you use the "Reset" link to go back to the default, you won't need to worry about this. — This, that and the other (talk) 00:02, 11 December 2014 (UTC)

UAA Shared use

We need a Shared use option on the UAA Advance Reporting and Vetting dialog box. Mlpearc (open channel) 18:44, 17 November 2014 (UTC)

An "Other" radio box selection would help. Mlpearc (open channel) 22:32, 23 November 2014 (UTC)
This is one I've wanted for a long time. Often a username will simply represent an organization rather than an individual. I select the "promotional" option as the closest choice even though I don't consider the user's edits to be promotional. MANdARAX • XAЯAbИAM 23:17, 23 November 2014 (UTC)
@Mlpearc: These are checkboxes not radio buttons; you don't have to tick any of them. You can leave them all unchecked and write your reasoning in the text box. -- John of Reading (talk) 06:59, 24 November 2014 (UTC)
It would be fine if that were true. Unfortunately, it's not. At least one selection is required. MANdARAX • XAЯAbИAM 09:21, 24 November 2014 (UTC)
Hmm, looks like poor old UAA could do with a bit of an update. Would you all agree if I made it possible to submit to UAA with no checkboxes selected, so long as a comment is entered? And if I added a fifth checkbox "Username implies shared use", "Shared-use username", or some such? — This, that and the other (talk) 09:30, 24 November 2014 (UTC)
That would work for me, none of the "required" options are rarely true when shared use or implied is the main reason for the posting. Mlpearc (open channel) 19:02, 24 November 2014 (UTC)
Yes, that would be great. Thanks! MANdARAX • XAЯAbИAM 22:51, 24 November 2014 (UTC)
@Mandarax, Mlpearc, and John of Reading: This has been implemented now. Give it a try! — This, that and the other (talk) 00:05, 11 December 2014 (UTC)
Looks great ! Thanx. :) Mlpearc (open channel) 02:36, 11 December 2014 (UTC)
Yes, thanks T,t&to! Strange, your ping didn't work on me. The notification system is really quirky. MANdARAX • XAЯAbИAM 07:48, 11 December 2014 (UTC)

Translating

Is it possible to install this gadget in another Wikipedia, translating it and mantaining it updated and translated? I mean, we can just copy the code in the respective Mediawiki pages and then translate it but this translation wouldn't keep when upgraded.

Thank you in advance, --Gerardduenas (talk) 17:06, 11 December 2014 (UTC)

Yes please, some hints on how to translate TW would be great. I am willing to translate the tool in Greek but didn't manage to find out how (except for some messages that are in MediaWiki:Gadget-Twinkle.js. Please don't tell me that each template has to be translated individually :). Please also bear in mind that TW edits appear in RC and articles' history and readers that don't speak English will be having a rough time. Thanks - Badseed (talk) 00:23, 13 December 2014 (UTC)

Right now, Twinkle is not really geared up towards internationalisation/localisation. A number of wikis have done this manually, the most notable (and up-to-date) effort being undertaken by Jimmy xu for Chinese Wikipedia (see [1]). But it is a lot of work, and ideally requires a decent understanding of JavaScript to get the most out of Twinkle. Most wikis have a severely outdated version of Twinkle that somehow manages to limp along.
I would suggest that localisation of some modules that are highly English-Wikipedia-specific (ARV, XFD, etc) may prove impossible, or at the very least, extremely difficult. But some modules ought to be more straightforward. It has been my long-term goal for some time to make an internationalisable version of Twinkle, as I know there is demand for it. I'll have more of a think about this in the coming days and see what I can come up with.
You may like to look at the Twinkle on other wikis section of WP:TW, as well as Wikipedia:Twinkle/Localisation. However I would not advise you to follow those instructions, as they are outdated and generally a bad way to operate. I mention them just for your interest and edification.
Thanks, — This, that and the other (talk) 12:05, 13 December 2014 (UTC)

Windows 8.1

I recently bought a new laptop that runs on Windows 8.1. My previous laptop ran on Windows 7, Service Pack 1. When I used Twinkle with W7 I had no problems, but with W8.1 the small window for adding a personalized edit summary does not open and instead the reversion is completed. The result is a generic edit summary with no explanation of the reversion. If this is a problem with Twinkle or W8.1, then a correction is needed ASAP. If it is something I did wrong, please explain so that I won't do it in the future. SMP0328. (talk) 08:26, 13 December 2014 (UTC)

This is a problem in the "immersive" app version of Internet Explorer that ships with Windows 8.1. To work around this issue, we suggest you use the desktop version of Internet Explorer, which can be reached by clicking "Desktop" on your Start screen, and opening Internet Explorer from the taskbar as you did in Windows 7. Eventually we may implement a work-around to this issue, but the best advice for now is to avoid using the immersive Internet Explorer app. — This, that and the other (talk) 01:27, 14 December 2014 (UTC)

d-batch

Minor issue - When I use d-batch, the main files in the category are deleted OK, and the pop-up shows "completed" - but for the redirects to those articles, it never shows that the process completes - it says 0% for deleting the redirects and for the redirect page name it says "Deleting page..." and never changes - but the redirects are actually deleted OK. See User:Ronhjones/Dbatch for a copy of the pop up window for 50 files deleted for G13. Ronhjones  (Talk) 20:34, 14 December 2014 (UTC)

Thanks for fixing iPhone warning selection

I was very pleasantly surprised to discover that the warning selection on my iPhone now works perfectly. (My request to get it fixed was archived about two weeks ago.) Many thanks to This, that and the other! MANdARAX • XAЯAbИAM 20:15, 16 December 2014 (UTC)

When warning for edit-warring

The edit summary says "Warning: Violating the 3 revert rule at {page}" but the template is for generic editwarring and does not imply that the 3RR rule was broken. It should be changed to "Warning:Edit warring at {page}. KonveyorBelt 18:31, 18 December 2014 (UTC)

Suggested enhancement

Could Twinkle be enhanced to do what's proposed here: Wikipedia:Village pump (proposals)/Archive 117#History diff link in deletion discussions? Please comment there as to whether this is possible or desirable. Oiyarbepsy (talk) 06:10, 22 December 2014 (UTC)

I already commented there: yes, it should be possible. — This, that and the other (talk) 23:51, 22 December 2014 (UTC)

Add {{db-spamuser-sandbox}} to CSD interface

I patrol the recent changes tag "Possible self-promotion in userspace" regularly and often come across sandboxes that would fit under this criteria. Was wondering, is there a reason why there's {{db-spamuser}} but not this one? And if it could be added after U5 and G11, maybe? — kikichugirl speak up! 21:37, 25 December 2014 (UTC)

the place to discuss thesis at WT:CSD; twinkle just reflects the options set on the various actual policy pagers. DGG ( talk ) 00:24, 26 December 2014 (UTC)
That's only partly true; we certainly wouldn't add any CSD criteria without agreement at WT:CSD, but CSD templates are a different kettle of fish. I'll have to have a look at this particular template and will reply in more detail later. — This, that and the other (talk) 07:52, 26 December 2014 (UTC)

Odd Twinkle Notification Issue

There appears to be a complicated problem with Twinkle in notifying the creator of an article that it has been tagged for speedy deletion or nominated for deletion at AFD. A page that is a biography of a living person was created in user space for a non-existent user, as User:Hari Singh Nalwa (Scientist), which was just incorrect. I moved the page to draft space as Draft:Hari Singh Nalwa (Scientist). The author then moved/promoted the article into article space as Hari Singh Nalwa (Scientist). (By the way, the disambiguator is necessary, because Hari Singh Nalwa was a general with an existing article.) Another editor then tagged the article for speedy deletion. However, rather than notifying the originator of the tagging, Twinkle put the tag on User talk: Hari Singh Nalwa (Scientist). Another editor then removed the speedy tag. I then nominated the article for deletion via deletion discussion. Twinkle again put the tag on User talk: Hari Singh Nalwa (Scientist). I have copied the notice to the originator's talk page. I realize that this is a problem that is unlikely to occur under normal conditions (because creating a BLP as a user page is a strange error), but can someone look into it? It does appear to be reproducible, because the same article has been nominated twice via two processes. Robert McClenon (talk) 22:25, 27 December 2014 (UTC)

This seems to have been resolved at WP:VPT. -- John of Reading (talk) 22:30, 27 December 2014 (UTC)

Cleanup tag nominated for deletion

See here. (I am not the nominator, but am leaving a message here since the nominator did not.) –Chase (talk / contribs) 06:06, 2 January 2015 (UTC)

Template:Rfd2m nominated for merging into Template:Rfd2 at WP:TFD

For those who watch this page, I would like to inform you that I have listed {{Rfd2m}} for merging into {{Rfd2}}. The discussion can be found at Wikipedia:Templates for discussion/Log/2015 January 2#Template:Rfd2m. Also, side note, from what I see, Twinkle only utilizes {{Rfd2}} and not {{Rfd2m}}, so that gadget should be unaffected if this merge occurs per my nomination. Steel1943 (talk) 02:17, 3 January 2015 (UTC)

No Twinkle options on user and user talk pages which don't exist

I'm not getting Twinkle options on redlinked user and user talk pages, either registered or IP. It works fine on pages which exist already, but I generally do more warns/welcomes/arvs for users with redlinks. I first noticed the problem yesterday or maybe the day before. I use MonoBook in case that's relevant. MANdARAX • XAЯAbИAM 10:57, 24 December 2014 (UTC)

It turns out that the key piece of information was not the skin, but the browser. It works correctly in Firefox, but it's still broken in Chrome. MANdARAX • XAЯAbИAM 19:10, 24 December 2014 (UTC)
Ah, yes. I was wondering what you were referring to, as all is well in Firefox! I'll fire up Chrome and take a look. — This, that and the other (talk) 07:52, 26 December 2014 (UTC)
This is working now. If you fixed it, then thank you; if it was some MediaWiki bug that got fixed, then thanks to whichever unknown person may have taken care of that. MANdARAX • XAЯAbИAM 22:11, 5 January 2015 (UTC)
I actually could never reproduce this issue, so I have to assume the problem was on your end. In any case, I'm glad you have the tabs back! — This, that and the other (talk) 00:40, 6 January 2015 (UTC)

Anonymous IP

Hello, I have a feature request. Could you please make this took available to anonymous IPs? We are allready having a hard time with all the bias against IPs. Thanks :) 143.176.62.228 (talk) 21:26, 5 January 2015 (UTC)

No; create an account, make 10 edits and wait 4 days if you want to use Twinkle. — This, that and the other (talk) 00:27, 6 January 2015 (UTC)
This would be difficult to make available for anonymous IPs, because without an account, there is no preferences panel. Logged-in, autoconfirmed users can easily turn Twinkle on and off, whereas we would have to make it either mandatory for IPs (not what most would want) or, as it is now, not there at all. So, can't help you...see This, that and the other's comment. Eman235/talk 00:34, 6 January 2015 (UTC)
Editing without an account means anybody can run basic lookups on your IP address. Editing with an account actually increases your anonimity, so sign up today, and get Twinkle by Friday! ☺ · Salvidrim! · ✉ 00:43, 6 January 2015 (UTC)
Actually, anonymity≠privacy. IP editors are a-nonymous in the literal sense (having no name); it just happens that in this case having no name also means reduced privacy. HJ Mitchell | Penny for your thoughts? 00:51, 6 January 2015 (UTC)

When warning for edit-warring

The edit summary says "Warning: Violating the 3 revert rule at {page}" but the template is for generic editwarring and does not imply that the 3RR rule was broken. It should be changed to "Warning:Edit warring at {page}. KonveyorBelt 18:31, 18 December 2014 (UTC)

@Konveyor Belt:: Which template are you referring to? — This, that and the other (talk) 04:50, 8 January 2015 (UTC)

Header levels for CSD and PROD logs

I'm pinging @Σ: as the operator of lowercase sigmabot III, since that bot is directly related to my question. I have set up the code for lowercase sigmabot III to archive my CSD and PROD logs, and I noticed that the code has to be placed before the first == Level 2 header ==, but Twinkle uses === Level 3 headers === in the logs. I have manually archived my submissions to date, but I'd like to be able to "set it and forget it." Will the difference in header levels cause problems with the automated archiving? If so, would it be possible to either adjust the header levels in Twinkle to Level 2 or to allow for sigmabot to archive Level 3 headers if no Level 2 headers exist? — Jkudlick tcs 10:04, 9 January 2015 (UTC)

Request for new template

There should be a template called "uw-warningclear", in which it is stated that the user is allowed to clear warnings but the one he cleaned was not allowed to be removed. --ToonLucas22 (talk) 00:43, 9 January 2015 (UTC)

Be bold and create one! Use another single-issue notice or warning template as a model. — This, that and the other (talk) 10:55, 9 January 2015 (UTC)

Proposed change to Multiple issues template

I have proposed changing {{multiple issues}} to remove support for the deprecated old-style parameters. Discussion is welcome at Template talk:Multiple issues#Request to remove old-style parameters. Thanks! GoingBatty (talk) 23:58, 9 January 2015 (UTC)

Thanks for letting us know. I don't think this requires any immediate changes to Twinkle, although some old conversion code that automatically turns old-style {{multiple issues}} to the new style will be able to be removed down the line. — This, that and the other (talk) 07:58, 10 January 2015 (UTC)

Issue?

When reviewing pending changes and reverting I sometimes get "Automatically accepting your changes: 'flag_status' parameter missing from query.",
It continues with the revert so it's not really a problem but wasn't sure if it's something more serious with Twinkle or whatever,
Thanks, –Davey2010Talk 18:57, 12 January 2015 (UTC)

This is a recently introduced MediaWiki bug: phab:T86258. I've asked for the offending change to be reverted, so we'll see what happens. — This, that and the other (talk) 00:47, 13 January 2015 (UTC)
Should be fixed now. If you're a reviewer, please test it again. — This, that and the other (talk) 03:56, 17 January 2015 (UTC)
Oops sorry wasn't aware you replied, Thanks for your help, Will do, Thanks, –Davey2010Talk 04:07, 17 January 2015 (UTC)

WP:UAA

Resolved

Twinkle's adding new entries at the top of the User-reported section. Other reports are being added at the bottom (as Twinkle does elsewhere). It's combining to make the section a mess where the oldest reported items are somewhere in the middle. Twinkle needs to change to add at the bottom. Bazj (talk) 16:07, 12 January 2015 (UTC)

Note that the instruction to add at the bottom was added two days ago, based on this discussion. MANdARAX • XAЯAbИAM 19:03, 12 January 2015 (UTC)
Yes, someone should have notified us a bit earlier! I'll make the change, and hopefully someone can synchronise it soon. — This, that and the other (talk) 00:40, 13 January 2015 (UTC)
Sorry, only just saw the commit, change is live now. Amalthea 16:40, 18 January 2015 (UTC)
Thanks. Bazj (talk) 21:02, 18 January 2015 (UTC)

Request

I think Template:uw-attempt2 and Template:uw-attempt4 should be available trough the Warn thing. I also renamed Template:uw-attempt to Template:uw-attempt3. --ToonLucas22 (talk) 22:36, 22 January 2015 (UTC)

Problem submitting AfD

When I submit articles for deletion, I get the following:

Next discussion page: Wikipedia:Articles for deletion/Edith Vonnegut (2nd nomination) Adding deletion tag to article: Failed to save edit: error "error" occurred while contacting the API. Creating article deletion discussion page: completed (Wikipedia:Articles for deletion/Edith Vonnegut (2nd nomination)) Adding discussion to today's list: error "error" occurred while contacting the API. Opening page "Edith_Vonnegut": error "error" occurred while contacting the API.

Not sure what's going on. Kindzmarauli (talk) 20:07, 26 January 2015 (UTC)

WP:UAA reporting

Is there a way the reporting script can check Wikipedia:Usernames for administrator attention/Bot to see if the username has been reported there ? Cut down on repeat reports. Mlpearc (open channel) 00:01, 30 January 2015 (UTC)

Another request

I decided to make a request, after tagging a stub as a Egypt writer stub.

My request is that you should be able to tag stubs, and be able to choose a stub tag from a list (e.g; {{party-stub}}, {{videogame-stub}}, {{chile-stub}}, etc.), which can be ordered from category or alphabetical order, just like when clicking the Tag button on the TW tab. --ToonLucas22 (talk) 00:23, 1 February 2015 (UTC)

See some previous discussions. This would be helpful, though, and possibly possible (I'm not a developer), with dropdown lists and such. Eman235/talk 21:15, 1 February 2015 (UTC)

Tag: Ref improve → Refimprove (2)

The {{Ref improve}} tag in Twinkle's article maintenance tagging feature is a redirect to {{Refimprove}}. Every time I insert it using Twinkle, a bot follows that edit to clean up the redirect. Why not just avoid this extra work and have Twinkle insert {{Refimprove}} in the first place?!?! -- P 1 9 9  ✉ 20:00, 2 February 2015 (UTC)

IMO, this problem is more with Yobot and AWB. I have posted in more detail at Wikipedia:Bot_owners'_noticeboard#Yobot. jcgoble3 (talk) 11:05, 3 February 2015 (UTC)
I've started a move request at Template talk:Refimprove#Requested_move_3_February_2015. If it fails I will change Twinkle to use "refimprove", but I hope people see the light. — This, that and the other (talk) 23:38, 3 February 2015 (UTC)

Template:R from Exif

This is your standard notification that this rcat has been renamed to {{R from file metadata link}}. I am in the process of updates to the documentation following the template move. Since there are several other metadata standards, since even JPEGs may use standards other than Exif, and since there is no way of telling which standard an image's metadata uses, the new name is more appropriate for these redirects. Joys! – Paine EllsworthCLIMAX! 18:13, 7 February 2015 (UTC)

Javascript pages and admins

Recently an admin MfD'd a javascript page using Twinkle. Because admins are allowed to edit other users javascript pages it should put: 

// {{mfd}}

Right now it breaks the script with: 

{{mfd}}

This change will stop the breaking of the script during the MfD process. Either that or Twinkle should consider not touching javascript pages as the code runs on the users browser. Chillum 18:13, 7 February 2015 (UTC)

  • Twinkle should not prefix the template with //. As soon as I get back to a computer in a few days I'll be modifying the template to be .js/.css friendly and changes to the way Twinkle applies the template will break that. Tagging these for MfD happens so rarely I don't think it's worth putting a bandaid on for a few days until the template is fixed. — {{U|Technical 13}} (e • t • c) 21:35, 7 February 2015 (UTC)
    • I don't think modifying the template will help. The problem is that {{mfd}} is illegal JavaScript syntax. — This, that and the other (talk) 06:18, 8 February 2015 (UTC)
      • Not once transcluded if it contains valid JavaScript. Transclusion on .js pages does occur (which is why categories are placed when users put {{Db-u1}} on them for example). If {{Mfd}} is modified to detect the the page content model is .js or .css (which will likely require me to make a small module in Lua based on my questions I asked on #wikimedia-tech on IRC) then it could add an appropriate .js console.error( '«pagename.js» has been nominated for deletion at «//enwp.org/MfD/pagename.js»' ) or even make use of a mw.notify so that people using the script will be certain to know there is a MfD on a script they are using. I'm not exactly sure what to do with .css pages yet, but I suppose there could be some kind of body:before message or a more appropriate place (I'm sure a discussion could figure out where to put it) so that those users would be notified of the discussion as well. — {{U|Technical 13}} (e • t • c) 17:07, 10 February 2015 (UTC)
Rather than try to make all templates an admin would put on a javascript page into valid javascript why not just comment it out? If the template is on its own line and start with "//" and ends with a new line then it is valid javascript. Any non-code change to javascript should be commented. Since a template is not meant to "run" as code it should be commented out.
I think you are over complicating things. Remember that the browser that puts the notice on the page is not the same browser that runs the javascript code. Just comment out non-code content on code pages, it is that simple.
Instead of editing every template that would end up on a special page a simple sanity check will suffice. Is this a CSS or JS page? If so use the appropriate comment symbol. Chillum 17:41, 10 February 2015 (UTC)
  • The entire purpose of the template is to notify editors that frequent the page that there is a deletion discussion, this works fine for regular pages that are viewed frequently or by a set of editors that have edited on the page. It doesn't work on JavaScripts that never get visited and the only person that may be watching it in most cases is the person who wrote the script. If you're going to comment the template out on these pages instead of make it notify the people that may be using the script as the template is intended, then it cannot do its job and what is the point of placing it on the page at all? — {{U|Technical 13}} (e • t • c) 20:06, 10 February 2015 (UTC)
Commenting it out in javascript will not stop the template from rendering on the wiki. Presumably the owner of the page will have it on their watchlist. Chillum 20:23, 10 February 2015 (UTC)
  • If only the owner of the page (which may be no-one if it isn't in User: space, it could be in Wikipedia for example) then why not just post a notification on their talk page and skip posting something on the .js itself? I'm not satisfied that would be sufficient as the owner of the page may not use or watch the script (I have created some for others I don't use or watch). The purpose of the template is to let everyone that uses the page, or in this case script, be aware that there is a discussion. This is why the notice is transcluded on templates (very rarely is it proper to <noinclude>...</noinclude> a TfD notice) to let everyone who would be effected know there is a discussion. I feel the same logic should apply here, it is not proper to comment out the notice, it should be transcluded to everyone that will be effected. We are talking about a handful of templates at most here and my idea for the solution is to create a wrapper template for all plausible templates that would run into this issue. I know there is {{Mfd}} and a couple of the {{Db-meta}} sub-templates (which can be one-shot fixed in Db-meta itself), what other templates do you think may be used on .js pages? — {{U|Technical 13}} (e • t • c) 20:37, 10 February 2015 (UTC)
  • I didn't actually respond to your comment; yes, it will. If I modify the template to contain console.error( '«pagename.js» has been nominated for deletion at «//enwp.org/MfD/pagename.js»' ); or mw.notify( '«pagename.js» has been nominated for deletion at [[pagename.js|a discussion]]' ); then putting // in front of it certainly will prevent it from rendering. — {{U|Technical 13}} (e • t • c) 20:40, 10 February 2015 (UTC)
I suppose whoever is in charge of feature implementation around here will have to decide between adding a couple of slashes or creating a new procedure. One thing I do know is that the script should not be altering javascript pages in a way that breaks them. Chillum 20:41, 10 February 2015 (UTC)

Prods

I've lately seen several situations in which the prodding editor notified the page's creator, even though it was created as a redirect. For example, Czar created Review of Education as a redirect, someone else converted it into a stub, and when a third editor prodded it using Twinkle, Czar was notified, but the converting editor wasn't. WP:PROD says Prodding an article via Twinkle will automatically inform the article's creator. Would it be possible to have Twinkle notify the first editor who made it a non-redirect? Nyttend (talk) 18:07, 2 February 2015 (UTC)

Twinkle currently doesn't have AI-enabled. We're still waiting for the moon juice and unobtainium supplies to arrive before we can work on it. The thing you're asking us to do requires human judgement. --QEDK ♠ T ♥ C 08:31, 22 February 2015 (UTC)

Suggested extra warning

We haven't got anything ideal for those users who keep uploading copyright images. Thus I've "borrowed" the one from commons and fixed it for here, it would be nice to add it to the warning list. See Template:End of copyvios Ronhjones  (Talk) 21:26, 21 February 2015 (UTC)

Support - Although I feel an onslaught of too bitey nay sayers :P Mlpearc (open channel) 21:37, 21 February 2015 (UTC)
It's quite easy to add but then unless it has a lot of usage, there's really no point. You can load it in the custom welcome module if you really need it, anyway. --QEDK ♠ T ♥ C 06:54, 22 February 2015 (UTC)
Ah, not played with the custom templates - thanks - I'll do that. Ronhjones  (Talk) 23:31, 22 February 2015 (UTC)

Vandalism on top

Can you please move "Vandalism" to the top of the level 4 warnings? That would make it consistent with levels 1 through 3, as well as 4im.

"Vandalism" is the most common warning, and I'll often just select a level and immediately click on Submit, knowing that Vandalism is first. I've inadvertently issued Generic level 4 warnings because that's listed first. No big deal, but still.... MANdARAX • XAЯAbИAM 20:53, 22 January 2015 (UTC)

Any comments before this gets archived? It's certainly not an important feature request, but one which would provide a small bit of convenience and consistency. MANdARAX • XAЯAbИAM 20:32, 10 February 2015 (UTC)
This may have changed since your comment, but now when selecting Level 4 you are offered the vandalism warning by default, not the generic one. Even though generic is top of the list, as far as I can see it can only be selected by positive action: Noyster (talk), 21:12, 13 February 2015 (UTC)
It hasn't changed; it still presents the Generic warning first for me. But now I see what's going on. If you're at a warning at any level (e.g. uw-vandalism1), then switch levels, it presents you with the same warning at the new level (e.g. uw-vandalism4) if that warning exists, or if it doesn't, then the first listed warning at that level. Users without custom warnings are presented with uw-vandalism1 first, so switching to level 4 gives you uw-vandalism4. However, users with custom warnings get their first custom warning first, which generally won't have a corresponding warning elsewhere, so switching to level 4 gives you the first warning listed there. Moving the vandalism warning to the top spot in level 4 would still provide consistency for everybody, as well as convenience for users with custom warnings. MANdARAX • XAЯAbИAM 23:32, 13 February 2015 (UTC)
I checked the code and Mandarax is right. But, why is level 4 the only level to have a generic template. I wonder. Fixing this is easy but I guess TTO must have done it for a reason. --QEDK ♠ T ♥ C 08:27, 22 February 2015 (UTC)
I simply thought it would be more logical to put the generic one first. The symptoms Mandarax is noticing only appear in a narrow set of circumstances (when you set custom warnings or one of the single-issue groups as your default warning level at WP:TWPREFS, and then select level 4 from the warning level dropdown without having selected another level beforehand). It would be possible to alleviate this by moving uw-generic4 one spot lower, but that would make the layout of the level 4 warning dropdown less logical for all users... — This, that and the other (talk) 12:33, 22 February 2015 (UTC)
It would be just as logical to have it last. After you've looked at the other choices, if none of them is appropriate, you'd come to the generic one. As I mentioned above, having vandalism first would make level 4 consistent with the other levels. I don't really see why uw-generic4 should be listed under "Common warnings" at all. From what I've seen, far from being common, it's very rarely used. Personally, I've never intentionally used it. MANdARAX • XAЯAbИAM 10:24, 23 February 2015 (UTC)

Alternative welcome talkback templates?

Does the community have any input on an idea for adding templates like {{talkbacktiny}} and {{whisperback}} to Twinkle? —George8211 / T 19:50, 10 February 2015 (UTC)

Section level

Hi! When I use Twinkle do propose pages for deletion, those pages are logged by Twinkle to a deletion log in my userspace (User:Vanjagenije/Deletion log). Deletion log uses separate sections for every month. But, those are level 3 sections (===December 2014===). Is it possible to change this to level 2 sections (==December 2014==). I want the bot to archive my log, but bots cannot archive level 3 (sub)sections, only level 2 sections. Thanks! Vanjagenije (talk) 16:26, 26 February 2015 (UTC)

Well, the bots ought to be smarter :) Changing this is not trivial, because of the need to ensure compatibility with existing deletion logs using level 3 headers. — This, that and the other (talk) 10:53, 28 February 2015 (UTC)

Proposal for improvement

Currently Twinkle has a function to report an user that is edit warring. This works very well. However, more often than not an edit war occurs between multiple users. So I was wondering I if would be possible to change/add to the function so you that you could, if desired, report more than one user within the same edit war report. Tvx1 20:04, 28 February 2015 (UTC)

{{W-screen}} - what's happened to the bouncy ball

I like the bouncy ball in {{W-screen}}, but I've noticed it's been missing when I've added it to some user talk pages recently - eg User talk:Daxueshan. Is Twinkle quietly adding the "Static=true" parameter? If so, please can we have the original version as an option on the Twinkle menu. Was there any discussion as to whether editors choosing that template prefer it with or without the bouncy ball? PamD 16:19, 21 February 2015 (UTC)

I just checked and it seems, yes, we do add the static=true parameter. This is something we can fix. --QEDK ♠ T ♥ C 06:49, 22 February 2015 (UTC)
I'm sure there was discussion. Let me be clear, that bouncing ball is a horrible intrusion on the sanity of our new users - they are forced to watch it continually go up and down, up and down, etc. every time they view their user talk page! Unless they figure out how to remove it, of course, but they probably will have been put off editing by that point. I certainly won't be having anything to do with removing that static parameter - I'll leave the decision up to others. — This, that and the other (talk) 07:00, 22 February 2015 (UTC)
There wasn't. I searched for the keyword, "bouncy ball" and the only related thread was [2]. I never use it so I'm fine either way. --QEDK ♠ T ♥ C 08:17, 22 February 2015 (UTC)
  • I've commented on the issue on GitHub. I don't think that |static=true should be removed from the way that Twinkle applies the template and if people want that option, they should simply add it as a custom welcome template or use one of the other available scripts that posts the template with the globe bouncing. — {{U|Technical 13}} (e • t • c) 21:59, 24 February 2015 (UTC)
  • I've got no idea what or where this "GitHub" is, to comment there. I don't see why the template should be applied by Twinkle in other than its default state. Please offer it as an option on Twinkle in its default state, with bouncy ball, as it used to be until a few weeks ago. I wouldn't know how to create a "custom welcome template" etc ... and doing so would mean that users I welcomed missed out on any updates or improvements to the W-screen template. Thanks. PamD 20:10, 2 March 2015 (UTC)
  • Looking at the discussion QEDK quoted above, I see that it was at my request that {{W-screen}} was included in Twinkle's menu, and This-that-and-the-other commented then that they didn't like the bouncy ball. But I do. In fact I nicked it from that welcome template to add to my user page. Someone has decided to add the "static" parameter, and I would like it to be removed, or made (non-technically) optional. PamD 20:15, 2 March 2015 (UTC)
  • Although I understand that you like the bouncy ball, Pam, I think there are more of us who prefer not to have it in the template, judging by comments here and at the template talk page. In any case, you are by all means free to add {{W-screen}} to your custom welcome templates using WP:TWPREFS so you may have it in Twinkle for your own use. I hope this helps you. — This, that and the other (talk) 06:59, 3 March 2015 (UTC)
It's the new editors who receive this image who would benefit from having an easily found option to stop the bouncing. The senders never see it: Noyster (talk), 09:29, 3 March 2015 (UTC)
  • I'll say this one more time to be clear. It is easier to have it in Twinkle with the static parameter by default and to have it as a custom welcome template without the parameter (allowing the bouncy ball) and it would be very difficult for people to add it as a custom template with a parameter set (to disable the bouncy ball). Despite the fact that I like the bouncy ball version better (and why I use the bouncy ball version in my wikilove script), it is technically better for Twinkle to offer the no bouncy ball by default. If you need help setting it up as a custom welcome template, I'd be happy to help. — {{U|Technical 13}} (e • t • c) 12:54, 3 March 2015 (UTC)

@Technical 13: Thank you for this clarity. I hadn't seen any statement that it was "easier" to have the static version in Twinkle, only that various people don't like the bouncy ball. I may need some help in adding it as a custom template but am still experimenting. PamD 13:27, 3 March 2015 (UTC)

OK, I give up: how do I add the bouncing version to my Twinkle Preferences, please? PamD 13:40, 3 March 2015 (UTC) 
//... some stuff here
  "friendly": {
    //... some stuff here possibly
    "customWelcomeList": [
      {
        "value": "W-screen",
        "label": "{{W-screen}}: bouncy ball welcome"
      }
      //... some stuff here possibly
    ]
//... some more stuff here maybe
// End of twinkleoptions.js
— {{U|Technical 13}} (e • t • c) 14:40, 3 March 2015 (UTC)
@Technical 13: Thanks - Success! I think I got confused by the "Add" button within that "Edit items" dialogue, tried various variations but couldn't get it to work. Apologies for the clutter on your talkpage edit history, but I'm not aware of a "User:Sandbox" to use for testing stuff like welcome templates etc - is there anything? Thanks for your help. PamD 16:23, 3 March 2015 (UTC)
PamD you could use User:ThisIsaTest. That's an account used in new admin school for blocking, but should be fine for testing twinkle as well. Martijn Hoekstra (talk) 16:25, 3 March 2015 (UTC)
(edit conflict) Martijn Hoekstra Thanks for the suggestion ... and it works, just tried it. Useful for future experimenting. PamD 16:36, 3 March 2015 (UTC)
Technical 13 Thanks again. In fact User talk:Example advises using User talk:Sandbox for user warnings as a testbed. Glad to find it. (And I'd temporarily forgotten that I do have a declared alt account myself I could use for such experimenting...!) PamD 16:42, 3 March 2015 (UTC)

No multiple nomination?

Currently, there is no non-manual way to list multiple articles/redirects/categories/etc. I and some other users (see Wikipedia:Redirects_for_discussion/Log/2015_February_13#Debauchery) would appreciate if an option to list multiple pages for deletion to discuss within the same discussion was added to Twinkle. Doing it manually is very tedious, as we have concluded. "Pinging" agreeing users: @Ivanvector:; @Steel1943:. --Mr. Guye (talk) 01:02, 6 March 2015 (UTC)

  • Confirming: yes, I'd like to see this, and thanks for the ping. If it were possible to tell Twinkle to add a redirect to an existing nomination by way of a drop-down or something, I would be happy. Ivanvector (talk) 01:07, 6 March 2015 (UTC)
  • @Mr. Guye: I agree, Twinkle needs to be updated in one way or another to accommodate multiple nominations. However, until that happens, I found a way to sort of "manipulate" Twinkle into performing multiple nominations, provided they are all done immediately and during the same day. Please see my comment on Wikipedia talk:Redirects for discussion for what I've been doing as a temporary workaround in lieu of Twinkle being able to so it with one click. Steel1943 (talk) 02:33, 6 March 2015 (UTC)
  • I agree this is needed. I remember back in 2011 when I was doing a significant cleanup of unused templates that I managed to figure out the necessary templates to insert in Twinkle's "reason" field to make multiple nominations, and it wasn't pretty. Having said that, I don't have time to be writing new Twinkle features, so it won't be me that does it. — This, that and the other (talk) 10:10, 6 March 2015 (UTC)

Can't post to a talk page

At User talk:RightBKC I'm trying to leave a copyvio warning, but get the message "User talk page modification: Could not resolve redirects for: User_talk:RightBKC". Dougweller (talk) 13:27, 7 March 2015 (UTC)

@Dougweller: Apparently a database error occurred during a page move. --RacerX11 Talk to meStalk me 13:42, 7 March 2015 (UTC)
Thanks. Dougweller (talk) 14:56, 7 March 2015 (UTC)

Redlinked edit summary

I'm not sure how it caused this to render weird in the edit summary, but correctly on the page itself. — kikichugirl speak up! 09:02, 19 February 2015 (UTC)

Whoa! I think Twinkle is not expecting the user to type in the User talk: prefix. It doesn't appear to break the template, but it clearly doesn't do much good for the edit summary. This is something we can fix. — This, that and the other (talk) 11:23, 19 February 2015 (UTC)
ClockC — This, that and the other (talk) 11:26, 10 March 2015 (UTC)

Move {{uw-salt}} to "Single issue warnings"

{{uw-salt}} is currently in the "Single issue notices" section of the Warn thing on Twinkle, but I think it should be moved to the "Single issue warnings" section, because it looks more like a warning than a notice. --ToonLucas22 (talk) 19:37, 28 February 2015 (UTC)

Yes, that's definitely a warning. I'll move it; hopefully that doesn't confuse people who are used to finding it in single-issue notices. — This, that and the other (talk) 09:13, 9 March 2015 (UTC)
 Done — This, that and the other (talk) 11:26, 10 March 2015 (UTC)

T3, again

Twinkle provides the following CSD T3 criterion: "Templates that are not employed in any useful fashion". However, this was removed from the relevant policy in January last year. Can it also be removed from Twinkle? Alakzi (talk) 02:24, 10 March 2015 (UTC)

This was added in 1632e5571e2255d48b9a6bbfe911f833cc9e2e8f in 2012, apparently following this "request". However, the policy has changed since then, so I suppose we can get rid of it. — This, that and the other (talk) 05:40, 10 March 2015 (UTC)
 Done — This, that and the other (talk) 11:26, 10 March 2015 (UTC)

Tagging images as missing permission?

Already discussed under #File Derrivitives above. Many options under the DI tab are currently non-working. --Stefan2 (talk) 13:10, 12 March 2015 (UTC)

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

Tagging images as "No evidence of permission" stopped working maybe 2 days ago. I hit the button and nothing happened. I have tried clearing my cache and it doesn't work. I turned on Firefox's browser console and the error it is getting is on load.php line 232 column 918, "ReferenceError: derivative is not defined". Any ideas? --B (talk) 13:02, 12 March 2015 (UTC)

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

File Derrivitives

Could the di section on file pages be expand to include...

and add the appropriate talk messages...

Thanks in Advance. Ronhjones  (Talk) 22:17, 7 March 2015 (UTC)

 Done, please let us know if it doesn't work. — This, that and the other (talk) 11:26, 10 March 2015 (UTC)
Certain "DI" features (for example, {{subst:nfurd}}) stopped working when the above was implemented. Could you take a look at this? --Stefan2 (talk) 17:26, 11 March 2015 (UTC)
Oops, seems that I missed something... — This, that and the other (talk) 09:58, 12 March 2015 (UTC)
@B: You can fix this if you like, by altering MediaWiki:Gadget-twinkleimage.js so that the line var type, non_free, source, reason, replacement; reads var type, non_free, source, reason, replacement, derivative; — This, that and the other (talk) 00:53, 13 March 2015 (UTC)
 Done. I had actually solved it in my own vector.js [3], but hopefully this takes care of it for everyone. --B (talk) 01:32, 13 March 2015 (UTC)

User notification not creating new section

When tagging a page for CSD G6 (Copy-and-paste page move), Twinkle fails to create a new section for the warning it places on the author's user talk page and instead appends the message into the last paragraph. (This is a bug report, but I don't have a Github account.) --Paul_012 (talk) 13:36, 14 March 2015 (UTC)

This was actually a problem with the {{db-copypaste-notice}} template, caused by an edit I made to it 2 years ago. I've tried to fix it in this edit. — This, that and the other (talk) 02:48, 15 March 2015 (UTC)
Thanks for the clarification. Shouldn't Twinkle add a new line before subst'ing the template, though? --Paul_012 (talk) 06:58, 15 March 2015 (UTC)
It does indeed add a new line; however, as you know, adding a single newline within a paragraph has no effect. Ideally Twinkle would add two new lines before the warning, but this causes an ugly blank space to appear at the top of the page when a new user talk page is being created for the first time. — This, that and the other (talk) 08:52, 15 March 2015 (UTC)

RFD nomination placed in wrong day

See this edit. The RFD template and edit happened on March 19 (UTC), but the entry was placed on the March 20 page. Steel1943 (talk) 00:01, 20 March 2015 (UTC)

Also, bizarrely, this one. Alakzi (talk) 00:03, 20 March 2015 (UTC)
Twinkle relies on the user's clock and timezone settings. If someone's clock is off by a few minutes, their nomination will end up in the wrong day. — This, that and the other (talk) 00:24, 20 March 2015 (UTC)

Template:On

The {{On}} was deleted a couple years ago, but for some reason when you click on the little arrow next to any of the options under the "tag" tab, it still links to that template? I would assume these are supposed to link to the actual template you use if you choose that tag. Would it be possible to get this fixed, or at the very least remove the link to the now defunct template? Thanks -War wizard90 (talk) 05:39, 20 March 2015 (UTC)

It works fine for me, so it must be a browser-specific issue. Which browser are you using? Would I be right if I guessed Internet Explorer 9? — This, that and the other (talk) 10:24, 20 March 2015 (UTC)
Yes, IE9, is there anyway to fix it short of using another browser? -War wizard90 (talk) 22:41, 20 March 2015 (UTC)
A fix is forthcoming. — This, that and the other (talk) 00:30, 21 March 2015 (UTC)
Cool, Thanks! -War wizard90 (talk) 00:56, 21 March 2015 (UTC)

Requesting unprotection

Is there a reason why the "rpp" tab doesn't allow us to request that a page or template be unprotected or have its protection level lowered? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:11, 21 March 2015 (UTC)

Works for me. Under the "Type and reason" dropdown box, the very first option at the top of the list for me is "Unprotection". And to have it lowered, just request the level you want it lowered to. Twinkle will automatically calculate whether to post it in the "increase" or "reduction" section of WP:RFPP. Example: [4] jcgoble3 (talk) 05:57, 22 March 2015 (UTC)

Invalid token?

I am trying to submit an SPI using Twinkle. But each time, I receive a pop-up error message "Failed to save edit: Invalid token". It's not something that has ever happened before. I haven't changed any settings since this last worked. Is there a general fault/bug, or is there something wrong with my setup? RolandR (talk) 11:04, 20 March 2015 (UTC)

Hm, interesting. If this happens, you have to refresh the page and start again. But I thought we had some logic in Twinkle that would stop this type of error from occurring. I'm not sure what's going on. — This, that and the other (talk) 10:26, 22 March 2015 (UTC)
I tried refreshing the page, and reloading Firefox, but it made no difference. I have now submitted the SPI manually, so can't at present check if the problem has resolved itself. Perhaps I should look for another sock in order to see if it works now! RolandR (talk) 12:06, 22 March 2015 (UTC)

{{Multiple issues}}

I think Twinkle should group inside {{Multiple issues}} when two issues supported by that template are selected, not three because it doesn't make sense. --ToonLucas22 (talk) 21:07, 24 February 2015 (UTC)

@ToonLucas22: I think it could be because two amboxes are fine, but three is unsightly. That's just my guess though. —George8211 / T 20:18, 2 March 2015 (UTC)
I'd agree with ToonLucas22 that even with only two issues a multi-issue box looks much better. PamD 16:29, 3 March 2015 (UTC)
AWB Puts two notices in a multiple notice box anyway. This should be unified in some way. EoRdE6(Come Talk to Me!) 00:22, 23 March 2015 (UTC)

{{uw-agf4}}

I recently created {{uw-agf4}} to comply with the major overhauls to {{uw-agf2}} and {{uw-agf3}}. Could you please add it to the "Final warning (4)" on the Warn tab? --ToonLucas22 (talk) 18:42, 22 March 2015 (UTC)

Noting for the record that the edits to the level 2 and level 3 templates have been reverted by another user, and the new level 4 template has been nominated for deletion. jcgoble3 (talk) 05:07, 23 March 2015 (UTC)
I agree with those actions. I think the commentary at the TFD says what I was going to say. Thanks, — This, that and the other (talk) 08:46, 23 March 2015 (UTC)

Twinkle sends notification to wrong person if you CSD a user talkpage

here I nominated User talk:Atul Birmal Salgar for deletion as a U5 (not a web host), and because User:Wgolf was the first person to post on that user talk, they were incorrectly sent the nomination for CSD message by Twinkle. It's happened to me quite a few times when nominating user talk for CSD, is there a way to fix this? Joseph2302 (talk) 20:46, 23 March 2015 (UTC)

@Joseph2302: As the declining admin stated in their edit summary, talk pages are not normally deleted. Just blank the inappropriate material or request redaction as necessary. — MusikAnimal talk 20:55, 23 March 2015 (UTC)
Oh okay thanks. I thought it was considered bad to remove content from talk pages of others. Is it fine to remove it as long as it clearly violates one of the CSD criteria (unambiguous advertising/not a web host etc...)?
Anything meeting deletion criteria can be courtesy blanked, though you may not necessarily want to use the {{courtesy blanked}} template. The more serious stuff can be redacted. — MusikAnimal talk 21:14, 23 March 2015 (UTC)

Custom warnings

I created some custom warnings and when I use them (see here), Twinkle adds words like "Notice", "Warning", "Caution", and "General note" in the edit summary and to me it appears completely random. How can I control what it says? — Jeraphine Gryphon (talk) 18:41, 27 March 2015 (UTC)

See the Twinkle code for some more info. Basically it looks at the last character (or in the case of "4im", last 3 characters) of the template's name and selects an appropriate term. If you don't want these terms to be used, but instead you want to see the more generic "Notice" in edit summaries, rename the templates so they don't end in "1", "2", "3", "4" or "4im". I hope that helps! — This, that and the other (talk) 23:47, 27 March 2015 (UTC)
Thanks! — Jeraphine Gryphon (talk) 08:57, 28 March 2015 (UTC)

User:MusikAnimal created a new template called {{uw-copyright-org}}, which I think would be a good addition to the other copyright templates under the single-level warning menu. This is particularly useful for cases of WP:COI editors who are unaware that copying and pasting text directly from their websites is unacceptable. I deal with this type of situation frequently, so it would be handy to have that in the Twinkle toolbox. --Drm310 (talk) 15:18, 20 March 2015 (UTC)

Did we have any discussion or anything of that sort on this? --QEDK ♠ T ♥ C 15:50, 2 April 2015 (UTC)

Suggestion for UAA reporting change

Very minor, but suggest adding "or explicit" to the "Offensive username" option under the UAA panel. Certain names relating to bodily functions aren't exactly offensive, but their explicit nature is a problem. E.g., admins have been blocking users with "poop" in their name. EvergreenFir (talk) Please {{re}} 22:54, 31 March 2015 (UTC)

The word "poop" is not of itself offensive (nor is it explicit); but it is offensive to the efforts of collaboratively building a serious encyclopedia to have usernames containing words like "poop" appearing in revision histories, signatures, and the like. Does that explain it for you? — This, that and the other (talk) 08:56, 2 April 2015 (UTC)
Wouldn't that fall under "disruptive"? EvergreenFir (talk) Please {{re}} 23:30, 2 April 2015 (UTC)

Add {{histmerge}}

Uncontroversial feature request: Twinkle doesn't support the {{histmerge}} tag. It should be added because it would simplify the work of Wikiarchaeologists who frequently request histmerges. One compulsory (source page name) and two optional parameters (reason and details) need to be there. SD0001 (talk) 17:21, 28 March 2015 (UTC)

@SD0001: You should be able to add that template to Custom article maintenance tags to display in your Twinkle preferences. Mlpearc (open channel) 17:46, 28 March 2015 (UTC)
@Mlpearc: No, it doesn't work since the source page name (unnamed) parameter is necessary, else the tag is meaningless. As far as I see, it's not possible to make the option for entering it display. SD0001 (talk) 18:12, 28 March 2015 (UTC)
IIRC histmerge is available via the CSD module, as technically, history merges fall under the scope of G6. Does this meet your needs? — This, that and the other (talk) 08:44, 29 March 2015 (UTC)
Wow, I see that the CSD module produces the message {{Db-histmerge}}, which is actually a redirect to {{Histmerge}}. I find it rather strange that this is included in the CSD module as history merging only requires a temporary deletion, so logically speaking this is not a deletion at all. Problem solved, but the CSD module still doesn't allow us to input the reason and details fields. Another problem is that it enters the page into our CSD log. SD0001 (talk) 17:21, 30 March 2015 (UTC)
You should be able to select the templates logged using TWPREFS. --QEDK ♠ T ♥ C 15:28, 2 April 2015 (UTC)
I think histmerge is in CSD because it applies to all pages in whichever namespace, whereas the article tagging module only applies to articles. As far as I can see, it gives you the option to state which page should be merged into the current page; do you think a rationale field should be added as well?
As it is indeed a speedy deletion request, I think it makes sense for it to be logged in the CSD log. If you don't want that behaviour you can always disable it in WP:TWPREFS, as QEDK suggests. — This, that and the other (talk) 23:54, 2 April 2015 (UTC)

Help needs for localisation, ta.wiki

I would like to localize Twinkle in ta.wiki. I have sysop rights there and a have basic skill on scripts, but more in vb.net and other program languages. I am good at English-Tamil translation too. I have looked at Localisation, but I am not fully understand on Find a javascript-savvy user. Could you help me regarding to localisation? Tell me what I want to do. You can contiune you assistance here, my user's talk page or my user's talk page at ta.wiki. Thanks. --AntonTalk 08:49, 22 March 2015 (UTC)

Do I want to wait for some more days to get response? --AntonTalk 04:31, 3 April 2015 (UTC)
Try jimmyxu, he localized twinkle for zhwiki (perfectly). Also, check this issue. --QEDK ♠ T ♥ C 17:10, 3 April 2015 (UTC)
Thank you QEDK. I will try. --AntonTalk 17:15, 3 April 2015 (UTC)
The point of finding a JavaScript-savvy user is that for now the localization of this tool is not limited to translating strings. So basically there are morebits.*, which only requires changing some strings and namespace numbers and it would live happily on your wiki. And there is modules/, in which some (e.g., prod & deprod) are useless outside enwiki and should be dropped, some (e.g., diff, unlink, batch*) only need changes similar to morebits, some (speedy, protect, tag, etc) would mostly work but you need to change the reasons and put in the right templates, and some (notably xfd) may need to be rewritten depending on the specific procedures on your wiki (enwiki uses subpages for nomination, zhwiki uses one page per day). AFAIK most people would copy Twinkle as a whole to their wiki (see GitHub for instructions), and tweak things around bit by bit. Maybe you could also try asking User:Siddhartha Ghai, the maintainer of Twinkle on hiwiki. Jimmy Xu (talk) 06:46, 4 April 2015 (UTC)

Thank you Jimmy Xu. --AntonTalk 08:02, 4 April 2015 (UTC)

Terminating edit summary Suggestion

I was just writing an edit summary after a rollback with Twinkle. It got too lengthy but there was no stop or prevention on the maximum number of characters in an edit summary. If we write an edit summary without a gadget, it accepts only a predefined number of characters, but Twinkle doesn't do that and when we go on typing the whole lot in Twinkle, in the revision history it only comes as that definite number of characters with three dots in the end. And, my whole sentence is over. Shouldn't there be a maximum number of characters allowed on the edit summaries?--Kashish Arora (talk) 06:08, 1 April 2015 (UTC)

+infinity Not knowing where my edit summary will be cut off is by far my biggest frustration with Twinkle. Please, for the love of all that is holy, fix this. jcgoble3 (talk) 06:31, 3 April 2015 (UTC)
Normally, you wouldn't be allowed to make the edit. Twinkle cuts it off instead. Let's see. And could you post the difflink? I mean, just seeing if it was something extraordinary. --QEDK ♠ T ♥ C 17:13, 3 April 2015 (UTC)
@Jcgoble3: Sure, this is really, really frustrating. This really needs to be fixed. @QEDK: Yes, here is the link. I had to explain a little bigger in this to prevent edit warring on that topic. When the real statement started, it had already crossed the limit of maximum characters. Let us see if anything can be done.--Kashish Arora (talk) 04:38, 4 April 2015 (UTC)
You'll notice that Twinkle "smartly" avoided linking the username, and completely removed the link to the user talk page, in order to show as much of your typed message as possible. Having said that, it would nice if you could be alerted when you are over the limit. I'll work on it.
In the meantime, know that you'll have less space available if you use AGF rollback. When you use the "generic" Twinkle rollback link (the middle one of the three), you will get a few more characters. Also note this text from Help:Edit summary: "If an edit requires more explanation than will fit in the summary box, post a comment to the article's talk page to give more information, and include "see talk" or "see discussion page" in the edit summary." — This, that and the other (talk) 05:56, 4 April 2015 (UTC)
Alright, I will make sure the edit summary doesn't cross the limit next time. And, I will wait for the new edit summary pop-up box with limited characters.--Kashish Arora (talk) 09:30, 4 April 2015 (UTC)

Proposal to improve the function for reporting edit warring.

Currently Twinkle has a function to report an user that is edit warring. This works very well. However, more often than not an edit war occurs between multiple users. So I was wondering I if would be possible to change/add to the function so you that you could, if desired, report more than one user within the same edit war report. Tvx1 05:13, 9 April 2015 (UTC)

Need an urgent block feature

The Twinkle spree by Hookey75 (talk · contribs) should not repeat. We can't rangeblock the underlying sockmaster. Could someone design some software block inside TW, ASAP please. Materialscientist (talk) 07:02, 10 April 2015 (UTC)

I don't see how it would help. If the powerful MediaWiki blocking toolset can't stop them, I don't see how Twinkle blocking is going to help. And in any case, instead of blocking the account from using Twinkle, you would just block the account itself, no? — This, that and the other (talk) 09:27, 10 April 2015 (UTC)
Agree with Materialscientist. Something needs to be done to avoid another episode like that. Is there any way to even have a feature like an admin bat signal? Or maybe have it so that if an account is reported to AIV or SPI, twinkle is disabled (since twinkle is not a right or part of the standard set of tools, I don't think disabling them in this manner is a problem.) Just spit balling ideas. EvergreenFir (talk) Please {{re}} 17:13, 10 April 2015 (UTC)
I agree with Materialscientist ans EvergreenFir I went to #wikipedia-en-help connect looking for an Admin to block Hookey75 (talk · contribs) just because of the speed and amount of edits being made, I thought the user was using a bot but, if there is an adjustment that can be made in Twinkle to "stop a run" like yesterday I say lets add it in to prevent this again. Mlpearc (open channel) 17:44, 10 April 2015 (UTC)
There were 1,015 edits within 15 minutes. Started at 2:23 EDT and ended at 2:38 EDT. This should not happen. I too thought this was a bot. EvergreenFir (talk) Please {{re}} 18:38, 10 April 2015 (UTC)
The "unlink" feature should be restricted. It's very powerful and easily abused, and most users would rarely if ever have a need for it. I've personally never used it, and have css to hide it so I don't accidentally click on it. I think it should be an admin-only function. If people think that's too severe, it should at least be restricted to rollbackers, who've been determined by an admin to have a certain level of trustworthiness and competence. MANdARAX • XAЯAbИAM 21:04, 10 April 2015 (UTC)
Anybody could fork Twinkle, remove the restriction and run it. This is mostly not an issue with Twinkle, but with the MediaWiki software. There are other less severe remedies, such as restricting the frequency of unconfirmed users' edits. Alakzi (talk) 21:14, 10 April 2015 (UTC)

{{incoherent}} wrongly summarised

Hallo, in the Twkinle menu {{Incoherent}} is summarised as "article is incoherent or very hard to understand", but the message displayed by the template is actually "This article or section lacks a single coherent topic.", which is a rather different message, using a different and perhaps less common sense of the word "incoherent".

Could the text of the Twinkle dropdown menu please be changed so it matches the message the template actually displays? They are two very different messages. I've been editing some appalingly-written articles recently and found a couple had been tagged with {{incoherent}}: they were certainly "incoherent" in the usual sense of the word, but "lacking a single coherent topic" was one of the few faults they didn't have. Seeing the Twinkle menu makes me realise why sensible editors were mis-tagging them. PamD 15:07, 10 April 2015 (UTC)

AGREED. I've noticed this too. — Jeraphine Gryphon (talk) 15:53, 10 April 2015 (UTC)
There's a relevant discussion starting at Template_talk:Incoherent#Unmerge_request_due_to_inconsistent_template_name.2C_banner.2C_and_usage. PamD 23:23, 12 April 2015 (UTC)

New warning templates

I have made a set of new warning templates inspired by a talk page discussion found here.

  • Information icon Hello, I'm Electricburst1996. Your recent edit appears to have reinstated information or content another user has expressed a problem with, so I have removed it for now. You are encouraged to open a discussion to seek consensus on this matter. If you think I made a mistake, or if you have any questions, you can leave me a message on my talk page. Thank you.
  • Information icon Please do not reinstate information or content a user has expressed a problem with into articles. Reinstating your preferred version without discussing runs afoul of the "community" aspect of this project, and as a result your edits have been reverted. Per WP:BRD, you should have opened up a discussion to seek consensus on this matter. If you would like to experiment, use the sandbox. Thank you.
  • Warning icon Please stop your disruptive editing. If you continue to restore information or content a user has expressed issues with, you may be blocked from editing.
  • Stop icon You may be blocked from editing without further warning the next time you disrupt Wikipedia by restoring information or content content a user has expressed issues with.

Just wanted to let you guys know. ElectricBurst(Electron firings)(Zaps) 23:08, 26 March 2015 (UTC)

I'm not sure that I really like those templates, as they look to me as if they are condoning article ownership. They don't provide guidance on how or where to start discussions, and blameful language like "you should have opened up a discussion" is also unhelpful. I imagine none of these things were intentional, but I'd be interested to see what the folks at WT:UTM (and this page) think. — This, that and the other (talk) 08:47, 27 March 2015 (UTC)
Blameful language re-worded. ElectricBurst(Electron firings)(Zaps) 21:00, 27 March 2015 (UTC)
Hm...does this really need a level 4 warning? Can we really block somebody for this?
Other than that, I'd say that the first one needs a link to the page's talk page (on "open a discussion"). This needs a parameter, obviously. Eman235/talk 17:05, 27 March 2015 (UTC)
It has been done. ElectricBurst(Electron firings)(Zaps) 21:00, 27 March 2015 (UTC)
I'd say the first one needs more informative links and the last two are unnecessary since we have edit warring warnings which are more appropriate in that case. And the sandbox comment in the second warning seems a little patronizing/not appropriate for that action. — Jeraphine Gryphon (talk) 17:27, 27 March 2015 (UTC)
Sandbox comment eliminated. ElectricBurst(Electron firings)(Zaps) 21:00, 27 March 2015 (UTC)
We don't need a combination of {{uw-disruptive1}} and {{uw-ew}}/{{uw-3rr}}. One making disruptive edits against consensus can simply be warned with {{uw-disruptive1}} and someone edit warring can be warned with {{uw-ew}} (or {{uw-3rr}} if they violated the three-revert rule). If an edit seems to constitute disruptive editing and edit warring at the same time can simply be warned with {{uw-ew}} as it is more disruptive. --TL22 (talk) 21:00, 8 April 2015 (UTC)
I agree with TL22. The proposed set of templates are a redundant form of existing templates. The difference here is that you are attempting to outline a specific type of disruptive editing and/or edit warring, but the problem is that there could be hundreds if not thousands of different types. We shouldn't need a different template for each scenario. If you really want to get more specific with a user, use the generic template to post the notice, and then simply edit it afterwards tweaking it to fit the situation. --GoneIn60 (talk) 09:15, 14 April 2015 (UTC)

Double entry PROD

Please look at this diff which may well vanish if the article is deleted. It appears that Twinkle duplicated the text in the PROD box. However, this has not happened when it notified the creating editor here. I image it to be a template issue more than anything else. Fiddle Faddle 16:07, 23 April 2015 (UTC)

Very strange. It appears to be a problem with the template; I don't have time to look at it right now but I don't think it's anything to do with Twinkle this time. Thanks for raising it, though. — This, that and the other (talk) 10:28, 24 April 2015 (UTC)

Unlinking the sandbox, again

Yesterday someone tried out the "Unlink" function in the sandbox again; according to the history of {{uw-test1}} that's the third time this has happened. Time to strengthen the warning or add special-case code? I suggest changing the heading partway down the dialog from Backlinks to Pages that you are about to edit -- John of Reading (talk) 07:02, 26 March 2015 (UTC)

Bah, not again. You'd think people would be sensible enough not to do this! In any case I think special-casing the Sandbox wouldn't be a bad idea. — This, that and the other (talk) 10:22, 26 March 2015 (UTC)
"You'd think people would be sensible enough "
No? Why would you even think that? This is what users exist for. Andy Dingley (talk) 10:28, 26 March 20015 (UTC)
@John of Reading: The "Unlink" option no longer appears on WP:SB. — This, that and the other (talk) 03:16, 5 April 2015 (UTC)

@John of Reading and This, that and the other: (Pinging so that you see this comment that's coming after a month) Nah, that was a good faith editor. He left a request at WP:ANI that his edits be mass rollbacked. (He didn't have the rights himself). And consented to being sent to Village stocks. 103.6.156.167 (talk) 13:20, 24 April 2015 (UTC)

Yes, it was a good faith editor. But it would still be worth making it harder for another editor to make the same mistake. -- John of Reading (talk) 14:25, 24 April 2015 (UTC)

Thank you for your contributions, we want to delete them

When tagging for CSD, it welcomes a user if they haven't been already. But look here -- it uses the standard welcome, not {{Welcome|newuser=y}}. Might want to change that... Eman235/talk 19:50, 25 April 2015 (UTC)

@Eman235: Actually, it uses {{First article}}, which is intended specifically for this purpose (note the text "Unfortunately, one or more of the pages you created may not conform to some of Wikipedia's guidelines, and may not be retained." in the first paragraph). Basically, it says that "We appreciate that you want to contribute, but unfortunately what you did may need to be deleted, so here's some helpful links to help you not make that mistake again." jcgoble3 (talk) 03:16, 26 April 2015 (UTC)
I agree that the prose of {{first article}} could do with some improvement. Be bold! — This, that and the other (talk) 03:29, 26 April 2015 (UTC)
@Jcgoble3 and This, that and the other: Re-opened a discussion, here. Eman235/talk 17:06, 26 April 2015 (UTC)

Template:Di-no permission-notice-final

Would it be possible to have {{Di-no permission-notice-final}} added as a choice for warning the user on the image deletion panel when leaving {{subst:npd}}? Please see Wikipedia:OTRS_noticeboard#Proposal_to_move_to_dated_pending_and_received_categories. This is a new template that we are proposing to use if the uploader has claimed to have sent permission, but none has been received. (In an ideal world, maybe there would be some sort of check that only shows this if you are in the OTRS user group or maybe at least warns you if you aren't that you may have hit the wrong button.) Thanks. --B (talk) 12:06, 29 April 2015 (UTC)

  • Probably possible depending on the final consensus in that discussion. Alternatively, if the Twinkle folk don't want to add it, it could certainly be added to the speciality OTRS script I wrote for Ron. — {{U|Technical 13}} (e • t • c) 00:58, 4 May 2015 (UTC)

Stub Template

So I know this has been discussed/requested several times before, but nothing ever seems to come of the discussions. I would really like to see, at the very least, an option to add the {{stub}} to articles via Twinkle. The page curation tool has this feature which is nice, but sometimes I want to add a stub tag to an article when I'm doing something other than new page patrol. I understand that adding all the various stub sorting categories may be too difficult at this time, but there seems to be general support in previous discussions for adding the standard stub template, and then allowing specialists to sort the stubs. Is there any way we could do this? -War wizard90 (talk) 02:13, 7 May 2015 (UTC)

  • I'm guessing there is an option without a large discussion and community consensus for the Twinkle people to code this. You could write a new module and submit a pull request to get it added to Twinkle. I know that option requires that you know JavaScript and how Twinkle are coded to some extent (or the ability to read the open source code on GitHub), or to find someone that can do it for you, but I'm guessing that is your best option to get this added at this time. — {{U|Technical 13}} (e • t • c) 02:46, 7 May 2015 (UTC)

Protection templates

When Twinkle is used to protect a page, it adds a protection template such as {{pp-template}}. Please can Twinkle be amended to not do this to template pages when either {{documentation}} or {{collapsible option}} is present. These templates automatically display the appropriate padlock icon if the page is protected (notice that after this edit and this edit, the pink padlock is still present at upper right); and when the protection expires, we don't then need to go back to remove the padlock, because it's already gone. --Redrose64 (talk) 16:21, 7 May 2015 (UTC)

Multiple Issues inclusion

Hi, I think this is a bug. I clicked on all of the tags it added and the orphan tag. In the list of things it did, it said that the Orphan tag was detected, but it didn't include it in the resulting edit https://wiki.riteme.site/w/index.php?title=La_Brindille_D%27Or&diff=662007855&oldid=662007562 and I was wondering why or if it could be fixed as that template should be in the multiple issues. Thank you. 3gg5amp1e (talk) 14:54, 12 May 2015 (UTC)

In case I was misleading, I was (am) not planning on doing this myself at this point. I was just asking a question as a programmer that I would want to know the answer to before I started working on such a project. Hope that clears up any potential confusion I may have caused since this request has been sitting here more than a day already. Thanks and happy editing! 3gg5amp1e (talk) 11:56, 14 May 2015 (UTC)
We're all busy and can't always answer in a hurry. This is a long-standing feature request with no immediate plan to implement this. — This, that and the other (talk) 03:54, 15 May 2015 (UTC)

Posting to userpage instead of talk

Any idea how I messed up with this diff? --Dweller (talk) 08:28, 15 May 2015 (UTC)

Hi Dweller, it's probably because Twinkle followed a redirected talk page. In general, user talk pages should not redirect to pages outside the User talk namespace, as it has precisely this effect (to confuse automated tools like Twinkle). — This, that and the other (talk) 10:14, 15 May 2015 (UTC)
That makes sense, ta. --Dweller (talk) 11:22, 15 May 2015 (UTC)
See these redirects. Following any one of them will take you to that user page. --Redrose64 (talk) 13:10, 15 May 2015 (UTC)

user rights management notifications?

The actual process of assigning user rights works fine, I'm just wondering if it would be possible for admins to get a menu of the relevant templates for user talk pages through Twinkle? Calling the templates by copy and pasting is kind of a pain if you are using a tablet or smartphone, this would make it simple and I imagine would not be too complicated to add on. Thanks for your consideration. Beeblebrox (talk) 21:47, 3 May 2015 (UTC)

By the way, all of the templates are listed at Category:User rights granting notification templates. Beeblebrox (talk) 21:59, 3 May 2015 (UTC)
  • Would you want it to open the talk page with an interface to pick a template or just post a static template for each change or have the interface for making changes offer a dropdown of templates to pick from? — {{U|Technical 13}} (e • t • c)
I was imagining it as just another option when on a user talk page. Beeblebrox (talk) 04:32, 4 May 2015 (UTC)
Why do you need this when Echo does it for you? — This, that and the other (talk) 03:50, 15 May 2015 (UTC)
Because it doesn't? I think you must be misunderstanding the request. When an admin is modifying someone's user rights, they open the user rights management interface, make their changes, and add a description of that they did to the user rights log. then, it is usually appropritate to add one of the standard user rights modification templates to their user talk. I'm just asking for Twinkle to have a drop down menu of those templates, just like it does for warning, welcoming, blocking, etc. Beeblebrox (talk) 16:12, 16 May 2015 (UTC)
According to Wikipedia:Notifications#Triggering events, seventh bullet, you are notified when your user rights change. This has actually happened to me twice (although not on English Wikipedia), for these rights changes. The messages were (i) "Your user rights were changed by Chris McKenna (WMUK). You are now a member of this group: sysop." and (ii) "Your user rights were changed by Richard Symonds (WMUK). You are no longer a member of this group: sysop." --Redrose64 (talk) 16:51, 16 May 2015 (UTC)

Yeah, that's all well and good but it is not the same thing by a long shot. As a regular reviewer of requests at WP:PERM for the last several years I can assure that it is in fact standard procedure to use one of the standard notification templates on the user's talk page pretty much every single time you add a new user right. An echo notification just tells you a change has been made. The templates explain what the change means for the user and provides guidance to them on how to proceed. Beeblebrox (talk) 16:57, 16 May 2015 (UTC)

mark rollback vandalism as vandalism in edit summary

Due to a discussion about two years ago, the vandalism edit summary was removed from twinkle. Wikipedia_talk:Twinkle/Archive_32#Please_remove_the_.22vandalism.22_summary.

I believe it should be restored. Prior to my knowledge of the prior discussion, I submitted this as a bug in github, and was redirected here. https://github.com/azatoth/twinkle/issues/264

While I understand the reasoning in the discussion, if there needs to be some safeguard against incorrectly choosing vandalism, then we should go that route (or take away the right to use the button from those that abuse it, or restrict it to only rollbackers), but I believe having the diffs marked as vandalism serves an important purpose. Namely, vandalism is an affirmative defense for "breaking" a number of policies such as per WP:BANEX and WP:3RR etc. If someone used the function with the intent of rolling back vandalism, then we should mark it as such, otherwise it leaves ambiguity of if they were just being lazy with not providing a rollback summary.

Even if the summary didn't explicitly say "Vandalism", if it said something that could be used in discussions to show that that was the link used it could be enough.

Gaijin42 (talk) 19:30, 18 May 2015 (UTC)

Suggestion: silliness

Could you add the {{silly}} template to the dropdown of single-issue warnings? --Dweller (talk) 15:10, 19 May 2015 (UTC)

And maybe trouts as well... Eman235/talk 22:14, 19 May 2015 (UTC)
So far, we have only included uw- series templates in Twinkle. And besides, this template looks a bit too silly for the relatively serious Warn module; isn't its purpose well served by existing templates like the uw-test* series?
If you wish to use it via Twinkle in spite of all this, you can add it to your custom Twinkle warnings using the options at WP:TWPREFS. — This, that and the other (talk) 23:55, 20 May 2015 (UTC)

{{uw-dls}}

I made {{uw-dls}} in accordance with WP:DEADLINKSPAM. Could you guys please add it to the "Single issue warnings" section please? --TL22 (talk) 03:01, 25 April 2015 (UTC)

I don't understand how a single-issue warning can have the text "you may be blocked from editing". That is, I believe, a distinct characteristic of a level4 or level4im warning. 103.6.156.167 (talk) 12:33, 25 April 2015 (UTC)
Some single-issue warnings such as {{uw-multipleIPs}} use that text. I don't see anything wrong with that. --TL22 (talk) 13:41, 25 April 2015 (UTC)
How common is this issue really? I've never heard of it. — This, that and the other (talk) 03:30, 26 April 2015 (UTC)
Well, spammers have been frequently replacing dead links with spam links between 23/12/14 (12/23/14 for americans) and 27/12/14. Short period, I know, but it can resume anytime. --TL22 (talk) 12:43, 26 April 2015 (UTC)
"Frequently" within a 4-day period at the end of last year? I'm not going to add a warning to Twinkle just for that... — This, that and the other (talk) 01:33, 30 April 2015 (UTC)
There has been this user called Techtipsmart who was doing this dead-link spam technique, so it may be worth it. --TL22 (talk) 02:40, 3 May 2015 (UTC)
@ToonLucas22 and Konveyor Belt: Done, thanks. — This, that and the other (talk) 00:58, 23 May 2015 (UTC)
@This, that and the other: Oh by the way it has been nominated for deletion by someone else. Just a notice. --TL22 (talk) 00:59, 23 May 2015 (UTC)

Tag: Ref improve → Refimprove (3)

Follow up to Wikipedia talk:Twinkle/Archive 36#Tag: Ref improve → Refimprove (2). The template was not renamed, and a bot still renames the template after inserting it using Twinkle. Now it is high time to fix it: have Twinkle insert {{Refimprove}} in the first place. -- P 1 9 9  ✉ 19:31, 4 May 2015 (UTC)

Hmm, seems like a case of perfect being the enemy of the good, unfortunately. I'll adjust Twinkle accordingly. — This, that and the other (talk) 04:36, 5 May 2015 (UTC)

Bug: When you press cancel on the "Restore this revision" in Safari

When you press cancel on the "Restore this revision" in Safari on Mac OS X, It will proceed to revert WITHOUT an edit summary or my consent instead of just cancelling the revert as expected. I am not sure if this bug exists on other web browsers, but if you can reproduce it on a Mac... Can you check if the bug also exists on other web browsers? In that way, try reproducing it on your PC... DSCrowned(talk) 13:22, 16 May 2015 (UTC)

I can reproduce this in the unsupported Safari for Windows 5.1.7, so that may aid debugging without a Mac. (This is the edit produced by my test, where I clicked "Cancel" on the edit summary dialog.) The problem does not occur in Firefox on Windows, where clicking "Cancel" correctly aborts the revert. jcgoble3 (talk) 05:21, 23 May 2015 (UTC)

Twinkle abuse?

Where does one report Twinkle abuse (which is a subsection of the previous page)?

I am concerned that Twinkle was used to undo 36 of my edits [6], against revert policy and against DRN policy (which does not grant moderators quitting moderators superpowers on Wikipedia).

Dame Etna (talk) 15:14, 23 May 2015 (UTC)

Any abusive behaviour (with Twinkle, other tools, or without them) can be reported at WP:AN/I. ☺ · Salvidrim! · ✉ 16:42, 23 May 2015 (UTC)

CSD-G6 discrepancy

Hallo, the Twinkle mouseover text for CSD G6 "Unnecessary disambiguation page" refers to pages which "disambiguate two or fewer pages and whose title ends in "(disambiguation)" ". The message Twinkle puts on the creating editor's talk page says the same. But the message displayed on the article itself refers to "disambiguates only one extant Wikipedia page and whose title ends in "(disambiguation)"", and this is the current wording at WP:G6. Could Twinkle please be brought into line with the current criterion here? The change was made in this edit with summary "Institute change discussed on talk page with no substantial objection", though I haven't found the discussion mentioned. Thanks. PamD 14:07, 26 May 2015 (UTC)

Request Page Protection via Twinkle: Question

Recently the Request for page protection process has changed. The new guideline for Requesting page protection is to Add the requested page at the bottom of the page (As opposed to the top like it use to be). I was wondering if Twinkle has been updated to add the protect template to the button of the page now? Please reply with {{u|CookieMonster755}} — Thank you! CookieMonster755 (talk) 19:21, 22 May 2015 (UTC)

Changing from top-posting to bottom-posting is a bit more difficult than the other changes. It would require significant coordination between all parties, as having some top-posted entries and some bottom-posted entries would make a mess. Personally I think sticking with top-posting is the simplest option. — This, that and the other (talk) 01:12, 23 May 2015 (UTC)
This, that and the other - Well, that's not my decision. That was up to the administrators active at RPP. However, like you said, we can't have request at the top and bottom of the page. Hopefully somebody will modify Twinkle to work with the new RPP system. I wish they just kept it like it was before, an unnecessary change. CookieMonster755 (talk) 23:35, 23 May 2015 (UTC)
@CookieMonster755: I also disagree with the new RFPP system. It just makes new requests go unnoticed. I may start discussion when there is enough debate about this. --TL22 (talk) 19:50, 25 May 2015 (UTC)
I don't like it neither ToonLucas22. CookieMonster755 (talk) 00:49, 26 May 2015 (UTC)
I very much agree with the instructions at WP:RPP to post new requests to the bottom of the page, making it consistent with AIV, UAA and in general with noticeboards and talk pages. I hope Twinkle will soon be amended to comply with this: Noyster (talk), 08:13, 26 May 2015 (UTC)
I agree with this new system and don't understand how new requests go unnoticed. If you ask me the old system always had old requests go unnoticed cause it always sat there on the bottom. With administrators working their way from top to bottom new requests eventually work their way up as my bot regularly archives handled requests.—cyberpowerChat:Online 17:20, 26 May 2015 (UTC)

Can't seem to add Twinkle to my new account

Hi, I'm SummerPhD, now editing under Tefkasp.

I think by now I'm autoconfirmed, but I can seem to figure out how to verify this. Twinkle is not showing up as an option for me at preferences/gadgets, so I'm thinking that might be the issue. Any tips? - SummerPhD, v2.0 02:18, 30 May 2015 (UTC)

It should be under browsing between revision jumper and suppress fundraiser banners. If its not there, you might try clearing caches, locally and with the purge command. (Dunno if that even works in preferences, but may as well try) [7]. Monty845 02:27, 30 May 2015 (UTC)

Speedy deletion issue

When I nominate a page for speedy deletion using Twinkle, and the user who created it doesn't have a talk page already, the function that's supposed to notify them of the speedy deletion on their talk page isn't working. Does anyone else have this problem? Everymorning talk 10:49, 30 May 2015 (UTC)

  • Actually, this now seems to be happening regardless of whether the creating user has a talk page already. When I nominate a page for speedy deletion I get some sort of database query error. Everymorning talk 11:00, 30 May 2015 (UTC)
Works fine for me, at least did yesterday. I'm more curious about how I could automatically watchlist those talk pages... — Jeraphine Gryphon (talk) 11:01, 30 May 2015 (UTC)
I get database errors some of the time. I suspect it's not just a Twinkle issue. Eeekster (talk) 11:03, 30 May 2015 (UTC)
I got some of those too, today. — Jeraphine Gryphon (talk) 11:07, 30 May 2015 (UTC)
The specific error I get is called "d02ec687". Everymorning talk 16:25, 30 May 2015 (UTC)
Thanks for that piece of useful information, Everymorning! It seems that this is the same issue as phab:T100577. Essentially, this happens because the Wikipedia database servers are under heavy load (?), and are throwing errors when attempting to increment your edit count. — This, that and the other (talk) 03:32, 31 May 2015 (UTC)

TB Edit Summary Problem

When using the Twinkle TB menu's "Please see" if you put in a page name, but no linked section, the edit summary still shows a hashtag after the page-name even though there is no section. See this diff for an example. 19:15, 2 June 2015 (UTC)

Hello anonymous person, a fix for this will be rolled out shortly. Thanks for reporting. — This, that and the other (talk) 09:32, 6 June 2015 (UTC)

Semi-protection and Pending changes doesn't work together

When I try to add semi-protection and PC1 with both boxes checked, only the semi-protection works. PC1 seems to get ignored. I'm having to apply PC1 as a separate action. Is this a bug or am I missing something?
 — Berean Hunter (talk) 03:34, 26 May 2015 (UTC)

  • I find the same issue. I just tried, on User:Salvidrim!/sandbox, using the "PP" module to go from no protection at all to SPP + PC1 (1month) + MPP (indef). It only applied to SPP + MPP and ignored the PC part.
Well I just tried applying PC and it says "The target page is not in reviewable namespace.", which makes sense in userspace... ☺ · Salvidrim! · ✉ 03:40, 26 May 2015 (UTC)
I tried applying PC1 + SPP (1 month) to Salvidrim test and it only took the SPP. I then tried to remove SPP & add PC1, and it only added PC1 without removing SPP. It seems that since PC and general protection appear to be different systems, Twinkle won't allow users to interact with both in a single use of the PP function. ☺ · Salvidrim! · ✉ 03:49, 26 May 2015 (UTC)
Something has broken then since May 16. They worked together here on May 16 and here on Feb. 3, also here. These are randomly chosen from my PC1 log. I never had to add PC1 as a discrete action when choosing to add both before. It breaks starting on May 18 according to my protection log...those politicians should have had it applied but it didn't take and I didn't notice until today.
 — Berean Hunter (talk) 04:24, 26 May 2015 (UTC)
Hm, looking at the code, this ought to have never worked. So I wonder why it ever did. In any case, I've uploaded a fix here, which will make its way here in the near future. — This, that and the other (talk) 07:07, 26 May 2015 (UTC)
@Salvidrim! and Berean Hunter: This should be fixed now. Give it a try! — This, that and the other (talk) 09:33, 6 June 2015 (UTC)
Yes, it's working. Thank you very much.
 — Berean Hunter (talk) 12:40, 6 June 2015 (UTC)

uw-test3

{{uw-test3}} was nominated for deletion or merging yesterday; the nomination is at Wikipedia:Templates for discussion/Log/2015 June 6#Template:Uw-test3. -- John of Reading (talk) 05:41, 7 June 2015 (UTC)

Blocking

When I use Twinkle to place a block notice on a user talk page, the first drop-down has an entry for Blocking to enable me to select a template in the second drop-down. That Blocking entry is gone.--Bbb23 (talk) 16:45, 8 June 2015 (UTC)

  • And so (?) I can't place a block notice on a not-yet existing talk page. Drmies (talk) 17:01, 8 June 2015 (UTC)
  • In theory this could make things easier, except that apparently we weren't told. Other issues--for a VOA, the automatic duration of the block should be indefinite, and that notification could/should come automatically. Also, there seem to be no more presets, like an automatic hardblock for a VOA, which we used to have. Drmies (talk) 17:04, 8 June 2015 (UTC)
  • Bbb23, you're talking about the Warnings dialog box? I noticed that too. It's now on the Twinkle block tab. I'm assuming this is new as things seemed to have changed from yesterday. --NeilN talk to me 17:07, 8 June 2015 (UTC)
Probably something to do with these edits by MusikAnimal (talk · contribs). --Redrose64 (talk) 17:26, 8 June 2015 (UTC)

Sorry for the delay... for a while I was convinced the Block module wasn't loading at all. Turns out it was just me. Please refer to Wikipedia:Administrators' noticeboard/Archive272#New Twinkle block module! for the official announcement and where to report concerns. Thank you! — MusikAnimal talk 17:37, 8 June 2015 (UTC)

So this is all your fault. Who looks at AN, ANyway?--Bbb23 (talk) 17:38, 8 June 2015 (UTC)
Breaking scripts and making admins unhappy is a skill :) I posted at WP:AN per recommendation. I'll make a few "please see"'s on other noticeboards. Best — MusikAnimal talk 17:43, 8 June 2015 (UTC)

Double-Twinkle

On my nonWP wiki, after upgrading to MediaWiki 1.25.1, Twinkle now seems to be uploading twice. See Double-Twink.jpg. Twinkle seems to work okay, but the menu item is unsightly. Any suggestions as to how I can fix the cosmetic problem? --Abhidevananda (talk) 07:27, 10 June 2015 (UTC)

Hi, you probably need to update your wiki's copy of morebits.css from here, as well the twAddPortlet and twAddPortletLink functions in Twinkle.js. If you require any assistance, please don't hesitate to ask. — This, that and the other (talk) 08:47, 10 June 2015 (UTC)
Thanks for the advice. I did what you said, and it worked perfectly. Double-Twink has become Single-Twink once more. Thanks a lot! --Abhidevananda (talk) 09:45, 10 June 2015 (UTC)

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)

Batch operation tools have been overhauled

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.[8] 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)

New block template for sockmasters

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 (talk • contribs • logs) 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 (talk • contribs • logs) 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 (talk • contribs • logs) 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 (talk • contribs • logs) 01:55, 16 June 2015 (UTC)

Question regarding marking pages patrolled

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

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)

Db-g4

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 (talk • contribs • logs) 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

@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 (Morebits.wiki.actionCompleted.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! (talk • contribs)
    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)

custom tag list

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)

uw-dls

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)

How to get Twinkle

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)

{{Db-attack-notice}}

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)

Delete batch tool: incorrectly deleted page as a redirect

See [9]. 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)??

Twinkle broken? Only issuing level 1 warnings

Resolved

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. [10] & [11] 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! — MusikAnimal talk 15:58, 24 June 2015 (UTC)
It seems to be working now. Dustin (talk) 16:03, 24 June 2015 (UTC)

Block templates

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

Resolved

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."[12] 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 (talk • contribs) 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)

2 Redirect Tags Suggestion

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)

Retrieved from "https://wiki.riteme.site/w/index.php?title=Wikipedia_talk:Twinkle/Archive_36&oldid=1142553586"