Wikipedia talk:Twinkle/Archive 33

Archive 30

Archive 31

Archive 32

Archive 33

Archive 34

Archive 35

→

Archive 40

Common warnings

Can we please have common warnings sections for single-issue notices and warnings as well. For instance, the self-reverted test edit is a situation that frequently comes up. But it is such a mission to find it that I rarely bother and use the less appropriate {{uw-test1}} instead. I also need the engvar template fairly frequently, but again it is not easy to find, the browser search facility does not work on pop-up boxes.

Ideally, users should be able to customise the common warnings according to the work they typically do. Is there a kludge to this I could put on my .js page? SpinningSpark 10:40, 22 May 2013 (UTC)

I didn't categorise the single issue warnings/notices, really because it is a lot more difficult to find a decent categorisation system. But I've made a start on one. If you have any ideas for a categorisation system, please suggest it.

In the meantime, you could use the "custom warnings" feature in WP:TWPREFS#twinkle-config-section-10 to save yourself some time - you could add your frequently-used templates as "custom warnings" (it doesn't matter if they are already in Twinkle) and set "custom warnings" as the default warning level. — This, that and the other (talk) 09:40, 23 May 2013 (UTC)

Thanks for the info, I've done that. SpinningSpark 19:41, 23 May 2013 (UTC)

Trying to add text in the "optional message" doesn't seem to work with custom warnings; is this known behaviour? :) ·Salvidrim!· ✉ 00:33, 24 May 2013 (UTC)

It worked for me here. Can you provide a diff showing where this has failed for you? — This, that and the other (talk) 02:00, 24 May 2013 (UTC)

The diff won't show much, but here. The message I added in the next diff was initially added in the "optional comment" section of the uw-harass1 post (from custom templates). :) ·Salvidrim!· ✉ 02:18, 24 May 2013 (UTC)

Could you try again, this time using the "Preview" feature in the warn dialog and seeing if that gives the correct output? — This, that and the other (talk) 02:26, 24 May 2013 (UTC)

I had. Lemme try it now on your talk page. :) ·Salvidrim!· ✉ 02:43, 24 May 2013 (UTC)

It worked. Frankly, I've no idea what happened. Sorry for taking up your valuable time! :) ·Salvidrim!· ✉ 02:45, 24 May 2013 (UTC)

Good to hear. If it happens again, please post here with any relevant details. — This, that and the other (talk) 05:47, 24 May 2013 (UTC)

Talkback opt-out

I read a "discussion" the other day where Person A was mad at Person B for using {{Talkback}} on Person A's talk page. Person A has an edit notice strongly urging editors to not use TB on his/her talk page. However, Person B used Twinkle to send the TB message so the editnotice was not seen.

I am wondering if it's possible to have something that prevents Twinkle from using TB if a user specifically requests it. So if you try to use TB, a box would pop up saying "This user requests you do not use Talkback on his/her talk page." –Fredddie™ 03:52, 24 May 2013 (UTC)

I really don't think that is possible unless you create a template that Twinkle would check for or something. Person A seems pretty jumpy over something so minor. Ramaksoud2000 ^{(Talk to me)} 03:55, 24 May 2013 (UTC)

I was thinking something akin to robots.txt or a hidden category. I totally agree that Person A was overreacting. –Fredddie™ 03:58, 24 May 2013 (UTC)

Well then, since we both agree, why does anything need to be done solely to appease a single person? Ramaksoud2000 ^{(Talk to me)} 04:09, 24 May 2013 (UTC)

I, for one, would use it since I hate TB. I am neither Person A or B in the above example. Person B's talk page is on my watchlist, which is how I saw the altercation. –Fredddie™ 01:44, 25 May 2013 (UTC)

Updates

Have pushed some updates, I hope they wont trash too much, but if so, here is the blame list:

Kevin Ji (2):
      Prevent non-confirmed users from using Twinkle; make the if test more readable; remove individual twinkleUserAuthorized tests
      Add a prompt when user clicks on the "Twinkle" bar and they are not confirmed

Marius Hoch (1):
      Overhaul and fix Morebits.wiki.page.patrol

This, that and the other (5):
      morebits: fix subtle gallery/infobox handling bug in commentOutImage
      morebits.css: use forward-compatible class name
      speedy: add url parameter to user talk notifications for G12
      xfd: add "fixing AFD" in the same vein as "fixing RPP"
      xfd: need a purge to bring it up to date

theopolisme (3):
      Add OTRS noticeboard option to talkback module (fixed #154)
      OTRSReply is not supposed to be substituted
      Explicitly define variable names after first is defined in {{OTRSreply}}

Regards, _→AzaToth 20:37, 28 May 2013 (UTC)

Twinkle down?

My menus just got a lot emptier. I'll try the usual cache stuff. --j⚛e decker^talk 01:20, 29 May 2013 (UTC)

Least I'm not the only one to suffer lol - →Davey2010→→Talk to me!→ 01:29, 29 May 2013 (UTC)

We are not alone. New worl (talk) 02:16, 29 May 2013 (UTC)

Thanks god, I am not alone. I was installing Teahouse scripts and next thing I noticed, my action menu has lost most of good stuff instead of adding two new ones I installed. My browser is also not able to load NPP. Plus Since 2-3 hours, suggestions option in searchbox is also absent.Vigyani_talk^{ਯੋਗਦਾਨ} 02:49, 29 May 2013 (UTC)

Same here. Was about to send a userpage to MfD, and I tried warning a user for vandalism - no go. hmssolent\^{You rang?} _{ship's log} 02:56, 29 May 2013 (UTC)

This is a Wikimedia issue that I have experienced before but it affects only certain projects at once. I've experienced this before on Commons. If you notice, all your gadgets are missing, not just Twinkle. And [1] lags page loading heavily. The only thing you can do is wait it out until it gets fixed or something. Ramaksoud2000 ^{(Talk to me)} 03:11, 29 May 2013 (UTC)

It was fixed just as I was typing that apparently. Ramaksoud2000 ^{(Talk to me)} 03:12, 29 May 2013 (UTC)

Twinkle is up now. Cheers, New worl (talk) 03:13, 29 May 2013 (UTC)

CSD G13

CSD G13 is a fairly new CSD criteria that is not included in Twinkle yet. It should be though. Ramaksoud2000 ^{(Talk to me)} 02:39, 27 April 2013 (UTC)

It sure is implemented in Twinkle; see Wikipedia talk:Articles for creation/sms world 4 you for an example. — This, that and the other (talk) 06:54, 27 April 2013 (UTC)

I had to look twice, too. I expected to find G13 underneath G12; instead it is at the top. -- John of Reading (talk) 07:05, 27 April 2013 (UTC)

I put it in the "namespace specific" section so we didn't have to see an irrelevant G13 option on every single Wikipedia page. — This, that and the other (talk) 10:28, 27 April 2013 (UTC)

There's a discussion on this at Wikipedia_talk:Criteria_for_speedy_deletion#Should_G13_only_be_valid_in_WT:_namespace.3F, where I've included a list of nine example rejected AfCs from three other namespaces, they're not common, but perhaps 1-3% of rejected AfCs end up in "the wrong" namespace (the number is much higher for submitted ones, most of those get moved.) --j⚛e decker^talk 16:36, 3 May 2013 (UTC)

Then do it manually :D Mdann52 (talk) 10:01, 15 May 2013 (UTC)

3% of 78,000 is about 2,000. I'll leave those for you. Get working. ;p --j⚛e decker^talk 01:22, 29 May 2013 (UTC)

Now that the RFC on WT:CSD has closed, I am happy for Twinkle to reflect the CSD policy by making G13 available on all pages. — This, that and the other (talk) 08:15, 29 May 2013 (UTC)

WP:AN3

I made a implementation for Edit Warring now at last, I hope it's functional and useful (and works). _→AzaToth 01:07, 29 May 2013 (UTC)

Except you killed the JavaScript minifier :) Twinkle's just too big for MediaWiki to handle, it seems. — This, that and the other (talk) 11:40, 29 May 2013 (UTC)

"they" say we should split up twinkle in multiple files, perhaps we should return having each module in it's own file. _→AzaToth 12:22, 29 May 2013 (UTC)

Ok, it's live now again. please test it :) _→AzaToth 15:52, 30 May 2013 (UTC)

Request to update maintenance templates

To avoid redirects (and hopefully make Twinkle easier to use), could you please change the list of maintenance templates that Twinkle inserts as follows:

• {{linkrot}} → {{Cleanup-bare URLs}}
  • I guess so - the real name is so much uglier, but... it's the real name. — This, that and the other (talk) 08:02, 29 May 2013 (UTC)
    • What's a "cleanup-bare URL"? _→AzaToth 12:23, 29 May 2013 (UTC)
      • Cleaning up bare URLs is what we want editors to do in order to avoid linkrot. GoingBatty (talk) 22:48, 29 May 2013 (UTC)
        • I think AzaToth's point is that "cleanup-bare URLs" makes it seem like "cleanup-bare" is an adjective used to describe the URLs. It really is a poor name for the template. — This, that and the other (talk) 10:36, 30 May 2013 (UTC)
    • To be honest, I like the shorter and more to the point {{Linkrot}} myself. The other just seems too wordy and doesn't relay the same message. The first one says that something needs to be done to prevent linkrot, the second one says that bare URLs need to be cleaned up (which when I clean the floor or dishes or whatever clean up means remove). Just my thoughts. Technical 13 (talk) 12:23, 30 May 2013 (UTC)
• {{ref improve}} → {{refimprove}}
  • Twinkle uses the spaced name as it is friendlier. In my view the template should actually be moved over the spaced redirect. — This, that and the other (talk) 08:02, 29 May 2013 (UTC)

Thanks! GoingBatty (talk) 03:58, 29 May 2013 (UTC)

• • I prefer the {{Ref improve}} myself. It is easier to read and makes the word "improve" stand out giving it more importance to me. Just my thoughts. Technical 13 (talk) 12:23, 30 May 2013 (UTC)

"Out of date" tag

I've been working on the AWB/Tasks#{{Out of date}} replacement and just went to tag a page for another purpose and noticed that Twinkle hasn't been updated to remove the tag from it's tag module. Per TfD, {{Out of date}} has been merged into .{{Update}} This TfD was from August of 2012, not sure why it took so long to be noticed. Technical 13 (talk) 13:50, 12 May 2013 (UTC)

You're right, there was consensus to merge in August 2012, but the actual merge was never carried out, and actually still has not been completed (if it were properly merged, {{out of date}} would just transclude {{update}} with the proper parameters). Having said that, now that the merge is obviously underway, Twinkle should probably stop adding {{out of date}}, in order to pave the way for {{out of date}} to finally be retired as a separate tag. Is this what you had in mind? — This, that and the other (talk) 02:53, 13 May 2013 (UTC)

I've currently 640 articles left in my list out of 2700 that were using {{Out of date|...}} changed to use {{Update|inaccurate=yes|...}}, so if Twinkle could stop adding that tag (or even add it in its new "{{Update|inaccurate=yes|...}}" capacity), that would be great. Thanks TTO. Technical 13 (talk) 11:40, 13 May 2013 (UTC)

It's back up to 1100 articles... When might this tag be removed or updated in Twinkle? Thanks. Technical 13 (talk) 13:22, 22 May 2013 (UTC)

I'll have a look at coding this tonight - thanks for the reminder. However, I can't guarantee when the change will be synced to the gadget on-wiki. — This, that and the other (talk) 02:12, 24 May 2013 (UTC)

Should be  Done now. I'm very sorry for the severe delay in carrying this out. — This, that and the other (talk) 05:22, 1 June 2013 (UTC)

request

In placing copyright (G12) notices on user talk pages, Twinkle's template does not include the name of the page the copyright is believed to be in violation of. This can sometimes create a bit of confusion, it would be nice if Twinkle could pass along the information in the user notice. --j⚛e decker^talk 20:32, 12 May 2013 (UTC)

It seems to work as it should. Could you give an example diff of a case where it hasn't worked? — This, that and the other (talk) 03:03, 13 May 2013 (UTC)

I think he meant the URL of the page that the text was copied from (in your test case, http://www.example.net), which {{Db-copyvio-notice}} (the template used by Twinkle) does not currently support. jcgoble3 (talk) 03:27, 13 May 2013 (UTC)

Ah, thanks, I see what was meant now. This shouldn't be a problem to add. — This, that and the other (talk) 10:14, 13 May 2013 (UTC)

Should be  added. — This, that and the other (talk) 05:22, 1 June 2013 (UTC)

Another copyvio request

I recently reverted a large copyvio a new editor added and when I went to warn the user I was surprised at not seeing a selection for such an infraction. Could that be added? My76Strat (talk) 19:08, 14 May 2013 (UTC)

In the "Warn user" dialog, if you select "Single issue warnings" in the first list box you should find {{uw-copyright}} in the second. -- John of Reading (talk) 19:15, 14 May 2013 (UTC)

I see. I'd never used that "Single issue warnings". Thanks. My76Strat (talk) 19:32, 14 May 2013 (UTC)

Twinkle adding pages to my watchlist

When tagging an article for speedy deletion, it doesn't add it to my watchlist (I think that's an intended feature, and one I like, since my watchlist is already ridiculously huge). The problem is that it isn't consistent. For example, if tag an article with multiple criteria, the page is watched. Also, I end up watching the page whenever I PROD an article. One solution would be simply to change my preferences so that articles I edit aren't automatically watched, but it would be nice if Twinkle was a little more consistent in that regard, or at least to have the option as to what to watch and what not to. Narutolovehinata5 ^tccsdnew 03:16, 31 May 2013 (UTC)

Wikipedia:Twinkle/Preferences has a checkbox to control whether PROD-ed articles should be watched - do you have that ticked? Are further down there are separate ticks for each CSD criterion; I would hope that the code for "multiple criteria" tagging does something sensible with those, but I've no idea how to check this. -- John of Reading (talk) 04:47, 31 May 2013 (UTC)

If you are using "multiple criteria", and at least one of the criteria you select has watchlisting enabled in your preferences, the page will be watched. For example, by default, tagging with both G3 and G6 will add the page to your watchlist, while tagging with both A1 and G2 will not. — This, that and the other (talk) 01:49, 1 June 2013 (UTC)

Template:uw-login

I noticed this isn't in the single warning section. I encounter this frequently at NPP when editors log out after receiving final warnings for removing BLP prod's, CSD tags, and the like, to remove the tags. Any objections to included it? I also searched the archives and didn't find any prior discussion about so I decided to bring it up. Ramaksoud2000 ^{(Talk to me)} 00:15, 29 May 2013 (UTC)

OK, let's have it. — This, that and the other (talk) 08:12, 29 May 2013 (UTC)

I think this is working now. — This, that and the other (talk) 09:56, 9 June 2013 (UTC)

Template:Talkback vs. Wikipedia:Notifications

Duplicated discussion: WT:Notifications#Template:Talkback vs. Wikipedia:Notifications Technical 13 (talk) 16:33, 3 June 2013 (UTC)

In my opinion, Wikipedia:Notifications has made Template:Talkback obsolete. Template:Talkback should be modified to pop up a message indicating this, and Wikipedia:Twinkle should be modified so as to no longer allow placing of talkback notices. Agree? Disagree? --Guy Macon (talk) 12:11, 3 June 2013 (UTC)

For now, I think talkback should stay. Simply because the notification for "mentions" only seems to count if a user's userpage is linked, not if their username is simply mentioned without wikilinks. If that is fixed, as in "mentions" will show up on notifications regardless if the userpage is linked or not, then talkback can easily be phased out. Narutolovehinata5 ^tccsdnew 15:32, 3 June 2013 (UTC)

Cue User:An going nuts. Keφr 16:21, 3 June 2013 (UTC)

• Since there is more discussion here, I'll move my comment from there to here... Technical 13 (talk) 16:33, 3 June 2013 (UTC)

  As much as I  Hate {{Talkback}}, I must disagree with you... Some users have turned off or disabled notifications in their settings or do not have javascript available which is required for notifications to work properly. {{tb}} still has a place for these users. Technical 13 (talk) 12:31, 3 June 2013 (UTC)

How? WP:Notifications isn't WP:Flow. Ramaksoud2000 ^{(Talk to me)} 01:50, 4 June 2013 (UTC)

Ramaksoud2000 for whom is your response/question directed towards? Technical 13 (talk) 01:38, 7 June 2013 (UTC)

My bad. I was speaking to Guy Macon. I have modified it. Ramaksoud2000 ^{(Talk to me)} 04:12, 7 June 2013 (UTC)

To expand on my original comment, I recently got the same information several times. Someone replied to me on an article talk page, and I saw on my watchlist that this page had changed. And WP:notifications told me that he had mentioned me by name on that talk page. Then he used Twinkle to give me a talkback saying that he responded to me. Then WP:notifications told me that he had posted to my talk page. That's a bit much, in my opinion. --Guy Macon (talk) 08:01, 7 June 2013 (UTC)

Personally, I request that people do not leave me a {{Talkback}} on my talkpage via my talk page edit notice. You could also disable the "mentions" part of notifications by going to Preferences → Notifications and unchecking the box next to "Mention". While I agree that is too many notifications for some, for others it is not always an issue as they are forgetful, like me. Technical 13 (talk) 12:46, 7 June 2013 (UTC)

If you look at the Talkback opt-out section above, you will see that Twinkle drops the talkback on the page without showing that notice to the dropper. :( --Guy Macon (talk) 14:38, 7 June 2013 (UTC)

I didn't say that eliminated the problem, just that it reduced it. The majority of TBs left on my page weren't done with Twinkle or another service, and adding that note helped a lot. I wouldn't be opposed if TTO or AzaToth wanted to add a feature to Twinkle that would look for a {{NoTB}} template in section=0 of a user talk page and offered a warning popup informing the dropper that this user does not like/want TBs and confirming they want to do it anyways. It could even include an optional argument of something like {{{reason}}} that could offer an additional note to the dropper like "This user prefers you use {{User link|username}} and allow 24 hours for response before leaving a talkback" or something of that nature. Technical 13 (talk) 14:49, 7 June 2013 (UTC)

It's a good idea. It was rejected in the past (or at least put on hold) for various reasons, but I think it should be done. I'll investigate a lightweight way of achieving this. — This, that and the other (talk) 00:57, 8 June 2013 (UTC)

Help!

I'm using a public computer, and the Twinkle feature suddenly disappeared.--Seonookim (What I've done so far) (I'm busy here) (Tell me your requests) 00:44, 11 June 2013 (UTC)

I see. No JavaScript....--Seonookim (What I've done so far) (I'm busy here) (Tell me your requests) 00:45, 11 June 2013 (UTC)

Proposed DTTR warning

OmniArticleEditor has an idea to add some content to the Twinkle documentation discussing potential pitfalls of using warning templates (along the lines of WP:DTTR). I'd even go further and suggest that Twinkle's user warning dialog include a disclaimer advising caution and that some users may react negatively to being templated. I've also attempted to address the issue by creating Template:Don't template me. Omni's suggestion would augment that substantially, and go a long way toward promoting WikiHarmony. Thoughts? Ibadibam (talk) 22:43, 12 June 2013 (UTC)

If you carefully evaluate the arguments in the Wikipedia:Don't template the regulars and Wikipedia:Do template the regulars, I think that you will find the arguments in that latter to me more compelling. This whole idea that some folks get upset over perfectly normal and allowable actions so we should tell the person who does the perfectly normal and allowable action to stop has lots of applications. Don't revert the vandals. Don't report the sockpuppets. They might get upset.

I think we need a WP:TTR warning to give to those who invoke WP:DTTR, reminding them that they are not better or more privileged than other users, that they received that same template which can be used on any user, and to focus on the merits of the warning. --Guy Macon (talk) 23:54, 12 June 2013 (UTC)

There is a link to DTTR in WP:TW/DOC#speedy, for anyone who bothers to read the documentation... perhaps there should be a mention of it in in the "warn" section as well. I think DTTR is more important for modules like CSD and XFD where the Twinkle user never has to visit the user's talk page - with warn, they have to visit it to leave the warning, and they ought to be able to see for themselves whether they are dealing with a regular or not. — This, that and the other (talk) 01:02, 13 June 2013 (UTC)

Please explain why Wikipedia:Don't template the regulars should be made a part of Twinkle's documentation while Wikipedia:Do template the regulars is not. On what basis was the one essay elevated over the other? Where was the discussion and consensus for doing that? --Guy Macon (talk) 01:14, 20 June 2013 (UTC)

I for one would find it wildly inappropriate for Twinkle to take a side, either side, in this matter. Twinkle is just a tool, not a vehicle for expressing opinions. Anyone doing any sort of tagging or other leaving of messages, template or not,, automated or not, of newbies or admins with eight years of edits, is responsible as an individual for their actions. That message of accountability is what Twinkle's documentation should reflect. Beeblebrox (talk) 03:29, 20 June 2013 (UTC)

I have to agree with Beeblebrox here as a "regular" that prefers to be templated. If I did something stupid that you would post a template on my talk page if you didn't know I was a regular, then you should post it anyways. Having a million edits doesn't make anyone any less likely to forget one of the hundreds of (sometimes stupid in my opinion) rules or even completely unaware of it. Just my two cents. Technical 13 (talk) 12:23, 20 June 2013 (UTC)

I changed WP:TW/DOC#speedy from

"Normally, there is no reason to un-check the "notify" box; however, consider that the notification may not always be appropriate (see WP:DTTR), so use it with care."

to

"Normally, there is no reason to un-check the "notify" box; however, consider that the notification may or may not be appropriate (see WP:DTTR and WP:TTR), so use it with care."

It will be interesting to see if anyone argues for linking to DTTR and not TTR. --Guy Macon (talk) 01:12, 21 June 2013 (UTC)

I wrote that section of the documentation, and I put the mention of Don'tTTR there because I think I got told off by Rich Farmbrough or some other editor at one stage for spamming them with TFD notices that they didn't want. I just put it there as something to be aware of, not necessarily something that needs to be followed. DoTTR is all well and good in principle, but if editors are going to get grumpy at you for templating them, then there's no point being martyred for adhering to DoTTR. — This, that and the other (talk) 01:13, 21 June 2013 (UTC)

That's an interesting thought, but why restrict it to regulars? Newbies also get grumpy at you for templating them, usually with far stronger efforts to martyr whoever templated them. As I said before, I think we need a warning to give to those who invoke DTTR, reminding them that they are not better or more privileged than other users, that they received that same template as any other user, and to stop attacking the messenger and to instead focus on the merits of the warning. --Guy Macon (talk) 01:44, 21 June 2013 (UTC)

Just so. Really, anyone trumpeting "DNTTR" needs a good trouting. It's an essay just as good or bad as the essay opposing it. --Demiurge1000 (talk) 04:20, 21 June 2013 (UTC)

Rough Translation

When using Twinkle to put the Rough Translation on a page, you require the user to type in the full language name instead of its shortened code (eg EN for English, FR for French, ZH for Chinese). The issue is that the template placed at the top of the page uses what you type, the English name for a language, instead of the language's name in itself. IE You type "German" when the Languages bar says "Deutsch," and the message says This article is a rough translation from German. It may have been generated by a computer or by a translator without dual proficiency. Please help to enhance the translation. The original article is under "German" in the "languages" sidebar. Is it possible 1. to only type in the shortened code for the language instead of the full name and/or 2. have the part of the message I bolded match the language tab? Paris1127 (talk) 00:45, 25 June 2013 (UTC)

That sounds possible, but you'll need to fix the template {{rough translation}} before we can fix Twinkle! — This, that and the other (talk) 01:30, 25 June 2013 (UTC)

Template:Dead end

I nominated that template for deletion.--Müdigkeit (talk) 20:56, 25 June 2013 (UTC)

[Rollback vandal] to open user's talk page with warn module instead of in edit mode.

A majority of the time it is appropriate to post a warning on the talkpage of an edit that is being rolled back as vandalism. It would be easier to do this if Twinkle loaded the warn module on those user talk pages than opening the page in edit mode. It may also as a side effect reduce the number of people rolling things back as vandalism incorrectly (and I wouldn't be opposed to the idea of it requiring a warning to be sent in order to roll it back as a vandal edit). If the rollbacker doesn't want to leave a warning, they could always still use regular rollback or AGF rollback. I've also posted this request to GitHub Twinkle issue #162 and duplicated the request here to see if there is any consensus on this idea. Thanks. Technical 13 (talk) 12:06, 24 June 2013 (UTC)

• Bumping thread. Technical 13 (talk) 01:08, 6 July 2013 (UTC)}}
  • @Technical 13: I replied at the github issue. — This, that and the other (talk) 01:53, 6 July 2013 (UTC)

Talkback opt-out feature

Twinkle now recognises {{no talkback}} when it is placed on user talk pages. If you don't want editors to send you talkbacks with Twinkle anymore, please place this template on your user talk page (including a custom message if desired). If you want to see how Twinkle uses this information, try talking back to yourself using Twinkle.

Please note that this only applies to talkbacks. Other notices, including speedy deletion messages, noticeboard notices (e.g. {{Coin-notice}}), and warning templates, will not be affected by this template. — This, that and the other (talk) 07:22, 2 July 2013 (UTC)

I wonder where else I should post this message? The editors who don't want Twinkle talkbacks probably don't watch this page. — This, that and the other (talk) 08:28, 3 July 2013 (UTC)

• I'm going to be bold and suggest adding a note directly to the {{Talkback}} template itself. "To opt out of talkback notifications from Twinkle, do XYZ. Note that users may still leave talkback messages manually" or something of that effect. Technical 13 (talk) 17:32, 3 July 2013 (UTC)

Monobook installation

I like working in Monobook but Twinkle (and other gadgets) create too many tabs across the top so on article pages I always have a horizontal scroll bar. Is it possible to load the options in a portlet as happens if I use Vector? Or not to load some of the admin only options that I very rarely use, if at all, like d-batch, deli-batch etc. NtheP (talk) 15:38, 3 July 2013 (UTC)

See Wikipedia talk:Twinkle/Archive 23#Changing_tab_order. I'll add this information to Twinkle's documentation at WP:TW/DOC; I thought it was already there. — This, that and the other (talk) 01:16, 6 July 2013 (UTC)

It's here now. — This, that and the other (talk) 01:25, 6 July 2013 (UTC)

Thanks! I'd previously gotten rid of almost all of the ones I didn't want, but I couldn't figure out "current", which I've now discovered is "tw-curdiff". MANdARAX • XAЯAbИAM 01:52, 6 July 2013 (UTC)

{{external links}} at the top of an article unnecessarily

I was asked to raise the issue here. There was a tag at placed the top of Twitter (it gets thousands of hits a day) for over a month for no good reason (see the version, where I don't spot any external links in the prose). Is there a way for users to prevent this? Or is it a Twinkle issue? Biosthmors (talk) 07:19, 5 July 2013 (UTC)

I'm not sure if your concern is regarding the addition of the tag to that article, or the position of the tag within the article.

When tagging articles with Twinkle, the user selects the tags they think should be placed on the article. Twinkle doesn't do much thinking of its own; it just does the user's bidding. If you thought the tag should not have been added at all, you were correct to bring it up with the editor.

As for the positioning of the tag, you are right in saying that the {{external links}} tag should be placed at the top of the "External links" section of the article. However, Twinkle does not currently support tagging an article anywhere other than the top or bottom of the page. I will look into repairing this problem. — This, that and the other (talk) 01:14, 6 July 2013 (UTC)

it's about the positioning. he asked me to put them above the external links, but I just replied that I used twinkle, and to post here. -- Aunva6^{talk - contribs} 02:11, 6 July 2013 (UTC)

NFCR

There should be an option to list files at WP:NFCR which then adds {{NFCR}} to the file also. Werieth (talk) 14:28, 8 May 2013 (UTC)

Yes, why not? This should be easy. The only challenge is deciding where to put this functionality. Perhaps a new, separate NFCR module? That doesn't seem very satisfactory. — This, that and the other (talk) 01:40, 9 May 2013 (UTC)

I would toss it under the XFD module, since it seems to be a similar process in terms of nominating procedures (disclaimer: I've never dealt with NFCR, so that comment may be way off target), and could arguably be considered a type of XFD process since it can result in files being deleted. jcgoble3 (talk) 02:11, 9 May 2013 (UTC)

XfD seems like a reasonable place to me. Perhaps it "might" even slightly help people understand that XfD means "X for Discussion" and not necessarily "X for Deletion"... My question is this, would Twinkle's application of this tag also unlink the file from all "non-article" pages and how would that be done? I've had some ideas on what I think is the best approach to such a thing that I've mentioned briefly on a WT:NCC (I think that is the page) discussion where non-free files used in this manner should be reformatted to use an "Example" picture and {{{link|non-free file}}}. I more specifically think that a special image should be used for these cases to explain what happened to the picture (which I would be willing to create). Technical 13 (talk) 12:10, 9 May 2013 (UTC)

• Any update on this? Werieth (talk) 12:37, 22 May 2013 (UTC)
  • No, sorry: I've been snowed under a bit recently. It looks pretty straightforward, so it's just a matter of when I get around to it. — This, that and the other (talk) 02:13, 24 May 2013 (UTC)

• Bump Werieth (talk) 01:13, 31 May 2013 (UTC)
  • The snow's melted a bit, so I have been able to make a start on this. Shouldn't be long. — This, that and the other (talk) 05:18, 1 June 2013 (UTC)
• Bump Werieth (talk) 15:28, 10 June 2013 (UTC)
  • The code is actually done; not sure what was stopping me from uploading it to our GitHub repository. I'll see if I can get NFCR working on wiki soon. — This, that and the other (talk) 12:24, 11 June 2013 (UTC)
• Bump Werieth (talk) 14:33, 19 June 2013 (UTC)
  • Really just waiting on AzaToth or Amalthea to sync the gadget. You can ping one or both of them if you like. — This, that and the other (talk) 00:51, 20 June 2013 (UTC)
    • One thing I noticed due to a template issue, it should be {{NFCR|<PAGENAME>}} and not {{NFCR}} Werieth (talk) 12:20, 24 June 2013 (UTC)
      • You're going to have to be more specific: on which pages is there a problem? — This, that and the other (talk) 01:29, 25 June 2013 (UTC)
        • @Werieth: Do you want to elaborate before this gets archived? — This, that and the other (talk) 11:05, 7 July 2013 (UTC)
          • I fixed the template instead. If a there wasnt a page name given it prefixed the page title with File: . Werieth (talk) 12:31, 7 July 2013 (UTC)

uw-harass

Is there any objection to adding the uw-harass series of warnings (1, 2, 3, 4, 4im) to Twinkle's template set, under "behavior towards other editors"? :) ·Salvidrim!· ✉ 23:52, 23 May 2013 (UTC)

I don't have any. Ramaksoud2000 ^{(Talk to me)} 00:16, 24 May 2013 (UTC)

How frequently used is this series? I removed a few rarely-used warning series (uw-redirectX, etc) from Twinkle a while back, to help make the ones people actually use easier to find. — This, that and the other (talk) 01:48, 24 May 2013 (UTC)

To be honest, I only just used it now. :p :) ·Salvidrim!· ✉ 02:05, 24 May 2013 (UTC)

See here for a recent example where an editor could have used uw-harass to warn another editor who had used profanity in an edit summary. The warning editor couldn't find an adequate template via Twinkle and used uw-disruptive instead, which was erroneous because the edit in question was never reverted. Ibadibam (talk) 22:33, 12 June 2013 (UTC)

Seems like it might be worth adding to Twinkle then. Under the "Behavior towards other editors" section, I suppose. I'll do it. — This, that and the other (talk) 01:03, 13 June 2013 (UTC)

Hm, seems like this was forgotten. I'll go do it for real this time! — This, that and the other (talk) 04:55, 24 June 2013 (UTC)

It's done. Thanks for your patience. — This, that and the other (talk) 11:06, 7 July 2013 (UTC)

Watch Page Preference

Hi, I cannot seem to find a check-box for automatically watching a page after placing an article tag on an article. I do not want Twinkle to automatically watch every page I tag; it is time consuming to remove all of those pages off my watch list. Please let me know if there is a solution. --JustBerry (talk) 20:30, 6 July 2013 (UTC)

In Wikipedia:Twinkle/Preferences there is a "Tag" section, where the first checkbox is labelled "Add page to watchlist when tagging". Do you have that ticked? -- John of Reading (talk) 21:17, 6 July 2013 (UTC)

Hm, I wonder why I did not find that earlier. Oh well, thanks a lot. --JustBerry (talk) 03:14, 7 July 2013 (UTC)

Articles for creation notification support

Operations on an article namespace article whose previous move was from Wikipedia_talk:Articles_for_creation/ which currently have the option of notifying the creator should also have the option of notifying whoever moved it from AfC. Stuartyeates (talk) 07:38, 8 July 2013 (UTC)

• Stuartyeates, could you please elaborate a little. I'm not sure what you are asking, and that information isn't always available, it might be difficult to add that to Twinkle without adding stuff to the AFC system... Technical 13 (talk) 13:30, 8 July 2013 (UTC)
  • The more I think about it, the more this isn't actually an AfC thing (it started from here). The logic would be to go back X edits (or all the edits in X days) and see whether this article has been moved to article space from elsewhere by someone other than the creator. If it has been, notify them using a similar notification as the creator. Stuartyeates (talk) 19:56, 8 July 2013 (UTC)

Bug - pipes are not allowed in URLs

I'm posting this here as I don't have a github account yet. I just made an AfD submission including this URL from Google Translate, but the pipe broke the link and made me lose the subsequent text. I assume this is because the content is being passed to the AfD template, but it would be nice if we could escape the pipe to {{!}} in javascript as a workaround. Would that be a good idea, do you think? — Mr. Stradivarius ^{♪ talk ♪} 12:46, 8 July 2013 (UTC)

Mr. Stradivarius, I don't disagree something should be done. My question is, would percent encoding it be a better option? Technical 13 (talk) 13:32, 8 July 2013 (UTC)

That would work fine for URLs, but it would break wikisyntax if someone tried to put e.g. a wikitable in their AfD nomination. That may not be an important enough use-case to worry about, though. It would be nice if we could port the relevant template over to Lua and access the Lua code directly from the javascript to avoid this, but I haven't heard anything to suggest that that's technically possible yet. (Correct me if I'm wrong.) — Mr. Stradivarius ^{♪ talk ♪} 14:26, 8 July 2013 (UTC)

I discovered this back in 2011 (before I became a Twinkle maintainer) when I was making lots of TFD nominations with Twinkle; I discovered that you had to manually type {{!}} whenever you wanted a pipe. I was thinking about auto-replacing all pipes in XFD reasons with {{!}} but I can't remember why I didn't do it. I'll play around a bit more and see what can be done here. — This, that and the other (talk) 01:21, 9 July 2013 (UTC)

Everything seems to be fine if we auto-replace all pipes with {{subst:!}}. I might work on this in XFD and other modules (like prod). — This, that and the other (talk) 03:59, 9 July 2013 (UTC)

I am very grateful!

		The Admin's Barnstar
		The batch-delete function is absolutely fantastic for the database report gnome stalker in me. Just saved me from a thousand individual (uncontroversial) deletions. :) ·Salvidrim!· ✉ 01:02, 9 July 2013 (UTC)

Thanks, on behalf of the Twinkle team! And I'm glad to see that batch deletion is working properly. It needs an overhaul, in my opinion, but if it still works then that is great. — This, that and the other (talk) 01:18, 9 July 2013 (UTC)

It gets the odd database error every now and then but I'd estimate the bug rate to under 5%, which is not insignificant but negligible in regular use. :) ·Salvidrim!· ✉ 01:21, 9 July 2013 (UTC)

Fixing VisualEditor errors

I've proposed creating a bot for VE-related errors, now that they are starting to show up in IP edits (because the VE Team, yesterday, enabled VE for everyone) (background: WP:VPR#Filter 550 should disallow). At the BOTREQ page, someone pointed out that a bot needs a high degree of assurance of no false positives. I think for some errors that threshold can be met, but for others - and maybe all errors - a tool like TW would be better. So, is it possible for TW to detect errors such as this?

<nowiki>[[whatever]]</nowiki>

[The "nowiki" tags are getting embedded by VE, into the wikitext (VE doesn't like raw wikitext; think of the nowiki tags as its defense mechanism).]

-- John Broughton (♫♫) 18:10, 16 July 2013 (UTC)

It's worth noting that I don't consider these things to be "errors": VE is just doing what it is told. Perhaps it is something that needs to be improved, but not an error.

I don't think it is proper for Twinkle to be buying into this sort of business at the moment. What's more, I expect it will blow over in a few months, as VE is improved and users become more accustomed to its visual interface. — This, that and the other (talk) 12:35, 17 July 2013 (UTC)

Template request

I'd love to be able to tag {{dablinks}} {{incoming links}} and {{format footnotes}} with Twinkle. Is that feasible? --BDD (talk) 21:33, 17 July 2013 (UTC)

Certainly I think format footnotes would be a good one to add. However, with only 58 transclusions (and some of those not even in article space), I don't think dablinks is really appropriate to put in the default Twinkle toolset. However you can always add it to your custom tags: WP:TWPREFS, Tag section. Thanks, — This, that and the other (talk) 10:47, 18 July 2013 (UTC)

Great, I wasn't aware of that option. It's worth noting that transclusions aren't the best measure of the importance of {{dablinks}} {{incoming links}}, however. It's a pretty serious issue, and as a consequence, it's usually dealt with fairly quickly. But perhaps it's still not common enough to add to the default module. I'll leave that decision to someone else. --BDD (talk) 18:15, 18 July 2013 (UTC)

Welcome button issue?

I am trying to welcome a new user at this diff. First time I used the welcome link, it placed the template on the talk page of the editor who made the previous diff: User talk:Davideluis. Each subsequent time I am getting a 404 page like so:

Error

404 – File not found

http://en.wikipedia.org/w/undefined&friendlywelcome=norm&vanarticle=Dhantoli

We could not find the above page on our servers.

To check for "undefined&friendlywelcome=norm&vanarticle=Dhantoli" on Wikipedia, see: //en.wikipedia.org/wiki/undefined&friendlywelcome=norm&vanarticle=Dhantoli

Just wanted to pass this along. --| Uncle Milty | talk | 13:53, 21 July 2013 (UTC)

This was the result of a careless typo on my part. I'll fix it ASAP; in the meantime, you will find it will still work if you can arrange it so the user to be welcomed is on the left side of the diff. Thanks very much for letting us know about this error. — This, that and the other (talk) 02:39, 22 July 2013 (UTC)

i.e. switch the id's around; if the link is oldid=563083341&diff=565286108, change it to oldid=565286108&diff=563083341 . btw this same behaviour happened to me a few months ago; it was fixed after a day so I never reported it. Just saying. --John Vandenberg ^(chat) 05:56, 22 July 2013 (UTC)

Thank you. --| Uncle Milty | talk | 11:08, 22 July 2013 (UTC)

I had this issue a week back...welcomed and thanked a vandal instead of the user who reverted him. Facepalm — Reatlas (talk) 11:09, 22 July 2013 (UTC)

TW tab shown double in Bengali wikipedia

hi, we have implemented TW in Bengali Wikipedia in 2012 December. At that time there was no issue. But recently 2-3 days we found TW(main)tab shown in double. We have just replaced "টুইংকল" (twinkle) with your "TW" in now some skin dependent config area.... Can anyone fixed the issue?

// now some skin dependent config.
if ( mw.config.get( "skin" ) === "vector" ) {
	Twinkle.defaultConfig.twinkle.portletArea = "right-navigation";
	Twinkle.defaultConfig.twinkle.portletId   = "p-twinkle";
	Twinkle.defaultConfig.twinkle.portletName = "টুইংকল";
	Twinkle.defaultConfig.twinkle.portletType = "menu";
	Twinkle.defaultConfig.twinkle.portletNext = "p-search";
....
}

- Jayanta Nath ^{(Talk|Contrb)} 10:34, 22 July 2013 (UTC)

Template:WelcomeMenu

When posting Template:WelcomeMenu on an user's talk page using Twinkle, it is listing the "Welcome" header2 twice. After testing the template by removing the Welcome header from it and posting it, when not using Twinkle it doesn't post at all. But, again, "Welcome" posts twice using Twinkle. I tested this on my own talk page, and sure enough, "Welcome" is listed twice in header2 format. It appears that a fix is in order. Northamerica1000^(talk) 12:50, 22 July 2013 (UTC)

It's because someone changed the template without telling us. I'll fix Twinkle soon. — This, that and the other (talk) 00:48, 23 July 2013 (UTC)

After a brief test, the welcome header for Template:WelcomeMenu is now only posting once when posting it using Twinkle. Northamerica1000^(talk) 02:51, 24 July 2013 (UTC)

RFD error

Resolved

 – http://en.wikipedia.org/w/index.php?title=Template:RfD_subpage_starter&diff=564059961&oldid=242545165 broke it _→AzaToth 20:32, 23 July 2013 (UTC)

Twice today I've tried to list something at RFD and Twinkle failed to list it there (tagging and notifying of creators worked as normal). I don't see anything irregular on today's listing. Any ideas on what's happening? --BDD (talk) 20:34, 22 July 2013 (UTC)

 Confirmed _→AzaToth 19:49, 23 July 2013 (UTC)

Redirects to/from Xxx-language terms

Following an unopposed proposal at WP:CFDS to rename e.g. Category:Redirects from English language terms to Category:Redirects from English-language terms, I have modified Template:R from alternative language, inserting hyphens before " language terms" at the end of category names.

The categories are currently listed at Wikipedia:Categories for discussion/Working/Large. I left a couple at WP:CFDS awaiting responses comments about WP:DASH.

Please would somebody with the requisite expertise check whether Twinkle needs updating to reflect & implement the changes. – Fayenatic London 18:43, 29 July 2013 (UTC)

No action needed here. Thanks for the report. — This, that and the other (talk) 04:35, 30 July 2013 (UTC)

Adding ajax Move capability to Twinkle

A while back I wrote a script that does ajax Moves, which can be found at User:Kangaroopower/ajaxMove.js. If it would be useful in Twinkle, I could port the code to work with morebits.js and Twinkle and then submit a pull request to the github repo. Would that work? Thanks, --Kangaroopowah 19:19, 29 July 2013 (UTC)

I have never seen much need for a Twinkle module for moving a page. The closest thing we have now is our page protection (PP) module for admins, which performs much the same function as the standard MediaWiki "protect" tab, but with a few added extras to make it more sugary (more compact and sensible user interface, and it can add and modify protection tags on the page). On the other hand, the MediaWiki Special:MovePage interface is quite intuitive and featureful, and I feel any Twinkle module for this purpose would fall short. Unless you had in mind to add extra sugar to the standard move process (e.g. redirect fixing, redirect review), I see little need for a move module.

(It is worth noting that the Morebits.wiki.page object contains some code that supposedly can move pages via the API - I wrote it some years ago but then forgot about it, since there was no use for it at the time. It has literally never been tested, so I don't know what nasty surprises might be lurking in it.) — This, that and the other (talk) 04:43, 30 July 2013 (UTC)

Italics

If I issue a caution or a warning (and possibly other actions?) and manually append some text, that text is rendered in italics. Italicising one or more sentences can present a barrier to readability for people with conditions such as dyslexia. Please can we remove the italicisation? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:52, 27 July 2013 (UTC)

Now that OpenDyslexic is available on Wikipedia (it handles italics very well), I don't think this is such a concern.

However, I'm open to getting rid of the italic formatting in warnings if there is a general agreement that it should be done. I've never really liked it. — This, that and the other (talk) 06:06, 28 July 2013 (UTC)

Given that many new warnings/ guidance templates are used for new editors, and IPs, many of whom are using institutional computers, how confident are we that they will have OpenDyslexic enabled? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:06, 30 July 2013 (UTC)

Here is my view: Dyslexic people who are serious about reading or editing Wikipedia will probably make an effort to find out about our OpenDyslexic support. As for itinerant users, the italicised custom message trailing behind a Twinkle-issued warning message on a Wikipedia IP user talk page is the least thing that a dyslexic IP user accessing the site from a shared machine will be needing to worry about, considering the notorious verbosity of our warning templates and the many other distractions the site's interface presents.

What "we" think is another matter; I've already said that if there is a broader agreement that the italic formatting is somehow bad, then I will be happy to take it away. — This, that and the other (talk) 10:16, 31 July 2013 (UTC)

CSD deletion with page-creator notification

As an admin, I can use the [CSD] action to delete pages rather than tagging them, by unchecking the [Tag page only, don't delete] option. However, doing so disables the [Notify page creator if possible] option. That is, TW only lets me notify the page creator if I don't actually delete the page. I often want to both delete and notify, so feature request: let don't disable notify-page-creator when in actual deletion mode. DMacks (talk) 19:05, 30 July 2013 (UTC)

It'd be nice. However, the regular speedy deletion warning templates (such as Template:db-bio-notice) are not designed to be used by admins who are deleting a page. This is why Twinkle is able to open the creator's talk page in edit mode upon deleting a page.

Alternatively, if a separate set of user notification templates were provided for this purpose, Twinkle could be made to use them. — This, that and the other (talk) 10:19, 31 July 2013 (UTC)

Drop-down menus in Monobook?

I've been trying to condense the twinkle tabs in Monobook into a single dropdown menu. Is such a thing possible? It seems like I should be able to paste the code at the bottom of Wikipedia:Twinkle/doc#Location_of_Twinkle_menu_items into my twinkleoptions.js page, but it's not working. (I get a message saying it doesn't parse.) Any advice on how to do this? ~Adjwilley (talk) 18:51, 31 July 2013 (UTC)

This is not currently possible. All the more reason to switch to Vector :) — This, that and the other (talk) 07:37, 1 August 2013 (UTC)

Aw, man, that's not what I wanted to hear. Thanks! ~Adjwilley (talk) 12:37, 1 August 2013 (UTC)

COI-Thanks template

There is a discussion here about adding a new template {{COI-thanks}} to the Twinkle arsenal. The template is intended as the other side of the coin for the COI warning templates we have, to show appreciation for editors that handle their COI well. Several editors said it would be a good idea, but I don't think any of us know how to add it. CorporateM (Talk) 05:14, 5 August 2013 (UTC)

The way to get templates added is to post here :) However, there are a couple of problems with this request:

1. We would have to add this in the "warn" module, since this is where we put all our user templates like this one. This template is not a "warning" as such, so it would be a bit of an odd one out.
2. We really only support templates that are part of the "uw-" family, i.e. that follow the design guidelines set out by WikiProject User Warnings. I don't know how this tempate could be made to fit those standards.

I would actually suggest that this template be re-formatted as a barnstar, and a request be made to add it to the WikiLove tool (via MediaWiki:WikiLove.js) for ease of placement on user talk pages. — This, that and the other (talk) 07:51, 5 August 2013 (UTC)

Another possibility might be to reformulate it a little to fit in with the "welcome" module or "TB" perhaps? I agree that as it is, it would not fit nicely with any of the modules. You could get it added into the default WikiLove, and it wouldn't necessarily need to be a barnstar. Check out User:Ocaasi/WikiLoveinstallscript.js for an idea of what I mean. Technical 13 (talk) 12:22, 5 August 2013 (UTC)

Support adding it under welcome. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:25, 5 August 2013 (UTC)

But that would be even more confusing: it's not a template to welcome a user. I still think this would be better suited to WikiLove. — This, that and the other (talk) 00:19, 6 August 2013 (UTC)

Just for background User:OrangeMike disapproved of a barnstar being given to a PR rep, because he felt barnstars should be reserved for those donating their time here, as oppose to participating as part of their job. I have also noticed that editors are much more likely to give me barnstars for my volunteer work than my PR work, even if my PR-work is of much higher quality. So WikiLove sounds like a better place for it. CorporateM (Talk) 23:32, 9 August 2013 (UTC)

ARV warnings

it doesn't let me select diffs for reporting to AIV. -- Aunva6^{talk - contribs} 13:28, 5 August 2013 (UTC)

And additionally, can Twinkle stop reports to AIV when a bot has already reported the user? Insulam Simia (talk) 16:13, 9 August 2013 (UTC)

Problem is that bot reports are added to a different page thus we would need to load that first before; Could be done. _→AzaToth 16:29, 9 August 2013 (UTC)

Idea from zhwp

Hi, I'm an admin of zhwp, so the following situation only appling to Chinese Wikipedia.

Twinkle is one of the best tools in Wikipedia. Almost every editor uses Twinkle to patrol. But when patroller who wants to only tag the article will automatically marks pages as patrolled.

So is there any chance to add an opotion on tag page of Twinkle, that when patrollers don't want to mark page patrolled(they think they might need others patrol it again but want to tag some problems already found), they can choose it for only adding templates.--AddisWang (talk) 17:22, 17 July 2013 (UTC)

User:Jimmy xu wrk is the one to speak to for this, I think. Unless he sent you here :) — This, that and the other (talk) 11:27, 5 August 2013 (UTC)

Yep, I thought if this should be implemented it'd better be done in the upstream :P Jimmy Xu (talk) 14:06, 9 August 2013 (UTC)

OK. Another one to look at. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

AfD autosigning

I've seen a lot of double-signed AfD nominations, and I've done it myself a couple of times; it's easy to forget that Twinkle automatically signs your post when you use it to file an AfD. It would be useful if there was a reminder somewhere in the dialogue box, perhaps under the "Reason" field, saying something like "Your signature will be appended to this comment automatically". DoctorKubla (talk) 17:17, 23 July 2013 (UTC)

OK. I personally have not seen this at other discussion venues, so perhaps it is more common at AFD. I could add a pop-up tip next to the "Reason" heading above the AFD reason box if you think that would help. — This, that and the other (talk) 02:41, 24 July 2013 (UTC)

That would be great, thanks. DoctorKubla (talk) 06:37, 24 July 2013 (UTC)

Perhaps TW could look for a user inserted ~~~~ and ignore it? --Fiddle Faddle 22:37, 11 August 2013 (UTC)

I thought of that, but then users might think that the four tildes they type are actually needed, which would be quite unfortunate. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

Tto, what if it looked for it and notified the editor that it isn't needed, as it is done automatically, like WikiLove extension does? Technical 13 (talk) 13:28, 16 August 2013 (UTC)

Notenglish tags

If {{notenglish}} is placed on an article, the related user warning template {{uw-notenglish}} should automatically be placed on the user talk page of the article creator. Currently this has to be done manually and is therefore often forgotten. The user message is however valuable because it informs the editor of the language issue and of a possible deletion of the article. So I think an automated user messaging for this template should be implemented in Twinkle. De728631 (talk) 16:21, 9 August 2013 (UTC)

it's not always the creator's fault for the not english. manual is more adaptable -- Aunva6^{talk - contribs} 16:29, 9 August 2013 (UTC)

Nonetheless we have the convention of notifying the creator for pretty much anything. They are considered the article's 'father'. Fiddle Faddle 21:51, 11 August 2013 (UTC)

In this case, a manual means of notification is quite important, especially to see if there is anything relevant that has already been posted on their talk page. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

At least I've updated the template text itself. Now there's not only an instruction how to list the tagged page at WP:PNT, but also a hint to notify the author. I hope this will help a bit. De728631 (talk) 11:33, 16 August 2013 (UTC)

CSD enhancement

There are times when one realises that an additional CSD rationale is required. For example one might realise post tagging that what one thought was a test page also contains an attack, thus needs different handling.

At present (or last time I tried) Twinkle refuses to let a different CSD template be added until one has removed the existing one.

Please would you give consideration to allowing Twinkle either to replace an existing template with an 'better' one, or to creating a multiple reasons template from the existing and proposed new one(s) and applying that to the article. Fiddle Faddle 16:21, 11 August 2013 (UTC)

I agree, i've seen some CSD's that are uncategorized, or have the wrong criteria, but are still csd-able. be nice to replace the previous csd with an updated one. -- Aunva6^{talk - contribs} 22:22, 11 August 2013 (UTC)

This might be good to have. It will need a bit of thought, though: the current mechanism is a failsafe to stop NPPers unknowingly edit-warring with each other, and any new scheme would need to account for these scenarios. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

db-g12 now supports 3 sources

I've updated {{db-g12}}/{{db-copyvio}} to support up to 3 sources. It still works exactly as before if no source or one source is specified, but I'm letting you know about it per the template's doc page. Jackmcbarn (talk) 00:15, 12 August 2013 (UTC)

• Jack, I'm confused as to why that template needs to support multiple sources. Only one source is needed for it to be a copyvio and deletable, so simply pick the the source that is most copied and run with that. Technical 13 (talk) 13:03, 12 August 2013 (UTC)

Sometimes some of the page is copied from one source, and some from another, such as Global Nomads Group was, and this makes it easier for admins to verify them all with the extra DupDet links. Jackmcbarn (talk) 14:06, 12 August 2013 (UTC)

CSD could go the way of the tag module (i.e. getting rid of the pop-up boxes that ask for further info and replacing them with inline textboxes that appear as needed). This would make this change a bit easier to implement. What do you think? — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

"Group inside multiple issues" checkbox in tag module

The checkbox in question is at the very top of the dialog.

Is the "group inside multiple issues" checkbox in the tag module needed? Does anyone ever turn it off? Why should it ever be turned off? Can I take it out of Twinkle, with a view to using the space to add other setting(s)? — This, that and the other (talk) 12:07, 16 August 2013 (UTC)

• I've been known to turn it off if there are less than three tags and I think the editors of the page need the "extra" help the full version of the tags give. What would be cool is if the group inside was taken away and changed to add tags outside of multiple issues so I can still group up multiples ones except for one or two that I think need more focus. Technical 13 (talk) 13:37, 16 August 2013 (UTC)
  • it doesn't use it for less than 3, or, at least, it shouldn't. you can always go back and manually tag if you need it outside. -- Aunva6^{talk - contribs} 16:34, 16 August 2013 (UTC)
  • I think you'll find in that case that bots will wrap your "focus" tags back into the {{multiple issues}} template. — This, that and the other (talk) 09:42, 17 August 2013 (UTC)

Does not open user talk page

I did a reversion from an editor's change, and Twinkle said it was going to open the talk page of the editor, but all it did was go back to the article. Then if I want to issue a comment or warning on the editors page, I have to copy and paste the article name, open the article history, and select the most recent editor's talk page, which is inefficient. I am using Firefox. Edison (talk) 16:27, 16 August 2013 (UTC)

Perhaps you need to set your browser to allow popups from Wikipedia. In the circumstances you described, a yellow bar should appear at the top of the page allowing you to permanently allow popup windows from en.wikipedia.org. — This, that and the other (talk) 01:45, 17 August 2013 (UTC)

Here's an off-wiki webpage to explain Firefox's popup blocker: http://support.mozilla.org/en-US/kb/pop-blocker-settings-exceptions-troubleshooting. Andrew³²⁷ 19:32, 17 August 2013 (UTC)

Notenglish tags

If {{notenglish}} is placed on an article, the related user warning template {{uw-notenglish}} should automatically be placed on the user talk page of the article creator. Currently this has to be done manually and is therefore often forgotten. The user message is however valuable because it informs the editor of the language issue and of a possible deletion of the article. So I think an automated user messaging for this template should be implemented in Twinkle. De728631 (talk) 16:21, 9 August 2013 (UTC)

it's not always the creator's fault for the not english. manual is more adaptable -- Aunva6^{talk - contribs} 16:29, 9 August 2013 (UTC)

Nonetheless we have the convention of notifying the creator for pretty much anything. They are considered the article's 'father'. Fiddle Faddle 21:51, 11 August 2013 (UTC)

In this case, a manual means of notification is quite important, especially to see if there is anything relevant that has already been posted on their talk page. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

At least I've updated the template text itself. Now there's not only an instruction how to list the tagged page at WP:PNT, but also a hint to notify the author. I hope this will help a bit. De728631 (talk) 11:33, 16 August 2013 (UTC)

CSD enhancement

There are times when one realises that an additional CSD rationale is required. For example one might realise post tagging that what one thought was a test page also contains an attack, thus needs different handling.

At present (or last time I tried) Twinkle refuses to let a different CSD template be added until one has removed the existing one.

Please would you give consideration to allowing Twinkle either to replace an existing template with an 'better' one, or to creating a multiple reasons template from the existing and proposed new one(s) and applying that to the article. Fiddle Faddle 16:21, 11 August 2013 (UTC)

I agree, i've seen some CSD's that are uncategorized, or have the wrong criteria, but are still csd-able. be nice to replace the previous csd with an updated one. -- Aunva6^{talk - contribs} 22:22, 11 August 2013 (UTC)

This might be good to have. It will need a bit of thought, though: the current mechanism is a failsafe to stop NPPers unknowingly edit-warring with each other, and any new scheme would need to account for these scenarios. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

"Group inside multiple issues" checkbox in tag module

The checkbox in question is at the very top of the dialog.

Is the "group inside multiple issues" checkbox in the tag module needed? Does anyone ever turn it off? Why should it ever be turned off? Can I take it out of Twinkle, with a view to using the space to add other setting(s)? — This, that and the other (talk) 12:07, 16 August 2013 (UTC)

• I've been known to turn it off if there are less than three tags and I think the editors of the page need the "extra" help the full version of the tags give. What would be cool is if the group inside was taken away and changed to add tags outside of multiple issues so I can still group up multiples ones except for one or two that I think need more focus. Technical 13 (talk) 13:37, 16 August 2013 (UTC)
  • it doesn't use it for less than 3, or, at least, it shouldn't. you can always go back and manually tag if you need it outside. -- Aunva6^{talk - contribs} 16:34, 16 August 2013 (UTC)
  • I think you'll find in that case that bots will wrap your "focus" tags back into the {{multiple issues}} template. — This, that and the other (talk) 09:42, 17 August 2013 (UTC)

Does not open user talk page

I did a reversion from an editor's change, and Twinkle said it was going to open the talk page of the editor, but all it did was go back to the article. Then if I want to issue a comment or warning on the editors page, I have to copy and paste the article name, open the article history, and select the most recent editor's talk page, which is inefficient. I am using Firefox. Edison (talk) 16:27, 16 August 2013 (UTC)

Perhaps you need to set your browser to allow popups from Wikipedia. In the circumstances you described, a yellow bar should appear at the top of the page allowing you to permanently allow popup windows from en.wikipedia.org. — This, that and the other (talk) 01:45, 17 August 2013 (UTC)

Here's an off-wiki webpage to explain Firefox's popup blocker: http://support.mozilla.org/en-US/kb/pop-blocker-settings-exceptions-troubleshooting. Andrew³²⁷ 19:32, 17 August 2013 (UTC)

How Twinkle adds to CFD page

When Twinkle is used to nominate a category for discussion (to add a nomination to a WP:CFD page etc) it appears to upload the whole of the CFD page, not just the "NEW NOMINATIONS" section. The reason I know this is that (for technical reasons) I can only make small uploads and hence can't use Twinkle for CFDing once there's a few nominations or a discussion on todays CFD page (if I try Twinkle fails leaving a bit of a mess to be tidied up). Is it possible to change this (to help me and any other editors with the same problem as well as to avoid unnecessary network traffic) ? 05:13, 23 August 2013 (UTC)

When Twinkle was being rewritten a few years ago, there was some bug in the MediaWiki API that meant Twinkle was forced to either overwrite the whole page, or add to either the very start or very end of the page. The editing of individual sections was not possible, because the API threw up spurious edit conflicts. I don't know whether this bug is still present, since when I ran into this bug, I just abandoned all section-editing logic in Twinkle and replaced it with whole-page editing logic. There have been no problems with this logic up until now! I suppose I could investigate whether this API bug has been fixed, but I doubt it would help in the case of XFD, since we are usually interested in the location of a particular comment on the page, not the presence of a particular section. — This, that and the other (talk) 08:08, 23 August 2013 (UTC)

Feature request

Can this template be added to twinkle?? --Zayeem ^(talk) 20:14, 23 August 2013 (UTC)

I think it's too specific to be added to Twinkle for everyone. Jackmcbarn (talk) 22:09, 23 August 2013 (UTC)

I agree with Jack that it is too specific to be added to the general list; however, TTO, could Twinkle have custom welcome tags in the preferences just like the Tag module has? I ask because the Tah Module doesn't load on talk pages, and being able to apply custom templates to talkpages would be good too. Thanks. Technical 13 (talk) 00:04, 24 August 2013 (UTC)

Custom welcome templates have been available forever (I think they were even available in Friendly before that was merged into Twinkle). See WP:TWPREFS.

However, I see no reason why this couldn't be added to the "WikiProject welcomes" list in the welcome module. — This, that and the other (talk) 00:56, 24 August 2013 (UTC)

Yes, I was actually proposing to include it in the "WikiProject welcomes" list in twinkle, it would inspire more users from Bangladesh to become regular editors.--Zayeem ^(talk) 09:04, 24 August 2013 (UTC)

Error in PROD module?

Just now I PROD'ed the article Pootis,but there is a edit conflict and the article was redirected to Team Fortress 2.To my surprise,Twinkle put a PROD tag on Team Fortress 2.It seems TW doesn't check edit conflict before putting a PROD tag.Lsmll 03:29, 25 August 2013 (UTC)

The same thing happened to me with the CSD module before, (Ctenolepisma instead of Ctenolepisma longicaudata). Jackmcbarn (talk) 03:37, 25 August 2013 (UTC)

I've opened an issue about this on github.Lsmll 03:49, 25 August 2013 (UTC)

You're going to have to be clearer: what is the esact issue? As I understand it, it is this:

1. You go to an article and use Twinkle to CSD/PROD it;
2. Meanwhile, someone else has changed the article into a redirect;
3. Twinkle tags the target of the redirect instead of the page currently being viewed.

Is that the issue? — This, that and the other (talk) 04:12, 25 August 2013 (UTC)

Yes, at least that's what happened in my case. Jackmcbarn (talk) 04:15, 25 August 2013 (UTC)

Yes,that is the issue I said.If you see my contribution,you will notice twinkle sent a PROD notice to the creator of Pootis,but actually put a PROD tag on Team Fortress 2.Lsmll 04:27, 25 August 2013 (UTC)

Twinkle on Commons?

Hello, I just want to know if Twinkle is on Commons. If not, is there any other software that can do what Twinkle does? --Blurred Lines 23:36, 20 August 2013 (UTC)

Twinkle itself is not on Commons, but there are a number of gadgets available on Commons that fulfil similar roles. See commons:Special:Preferences#mw-prefsection-gadgets, in particular, items such as "QInominator", "RenameLink" (enabled by default), "Add {{Information}}", "AjaxQuickDelete" (enabled by default), "Quick Delete", etc. What particular functionality were you looking for? — This, that and the other (talk) 07:19, 21 August 2013 (UTC)

What I was looking for is like having a software on Commons that can report photos that are copyrighted or non-free, like Twinkle does when you report a file. --Blurred Lines 19:41, 21 August 2013 (UTC)

On the file information page, use "Nominate for deletion" in the toolbox. You should now be able to specify why you wish to delete the file. The "Nominate for deletion" link should be there by default. If you wish to nominate a file for speedy deletion (corresponding to Twinkle's "CSD" and "DI"), go to Commons:Special:Preferences#mw-prefsection-gadgets and "Quick Delete". This should add a couple of more links to your toolbox. --Stefan2 (talk) 12:36, 26 August 2013 (UTC)

RL Bug

morebits.css says that RL mangles data URIs in gadget css (and that's why its loaded through morebits.js). I didn't find this in any of the RL bugs. Could someone who originally encountered the issue please report it? Thanks.--Siddhartha Ghai (talk) 21:02, 24 August 2013 (UTC)

That was me. I'll see if it is still an issue and file a bug if it is. — This, that and the other (talk) 04:10, 25 August 2013 (UTC)

A quick test on testwiki seems to suggest that this issue is no longer present. — This, that and the other (talk) 12:49, 26 August 2013 (UTC)

Listing proposed mergers

Unless I'm missing something, Twinkle doesn't appear to list proposed mergers at WP:PM. Would it be possible to get Twinkle to list PMs, as it does AfDs? Is there any reason that's undesirable? Ibadibam (talk) 18:51, 23 August 2013 (UTC)

Instead, Twinkle has a functionality allowing for discussion to take place on the talk page of one of the articles to be merged. WP:PM is a bit disorganised, and there is a box at the top suggesting that it might be going away in the future, so I am reluctant to write any code specific to that page. — This, that and the other (talk) 01:12, 24 August 2013 (UTC)

Understood. Thanks for the clarification. Ibadibam (talk) 18:49, 27 August 2013 (UTC)

Automatic welcome

If you add a CSD template and notify the uploader, there is an option to welcome users automatically if the talk page doesn't exist. Could this option also be added for DI and XFD nominations? --Stefan2 (talk) 12:38, 26 August 2013 (UTC)

This logic is handled by the CSD notification templates themselves. I should think that, based on the precedent of CSD templates (and possibly also PROD), there would not be much resistance to adding a similar auto-welcome functionality to the XFD and DI notification templates. — This, that and the other (talk) 11:53, 27 August 2013 (UTC)

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

Do we really need this message? I was doing a CSD and closed the reason dialog as I wanted to cancel and check some history first. --  Gadget850 ^talk 00:42, 27 August 2013 (UTC)

That's just the error message for not specifying a reason. What do you want it to do instead? Jackmcbarn (talk) 00:51, 27 August 2013 (UTC)

Be less snarky? Or actually funny? --  Gadget850 ^talk 01:42, 27 August 2013 (UTC)

It seems that you don't appreciate my sense of humour! — This, that and the other (talk) 11:51, 27 August 2013 (UTC)

Although that message shouldn't appear when you click Cancel. I'll get rid of it in that circumstance. — This, that and the other (talk) 11:54, 27 August 2013 (UTC)

Sockpuppetry reporting

Resolved

 – was an easy fix _→AzaToth 13:38, 28 August 2013 (UTC)

When one reports only one puppet of a sockmaster, TW adds a 'spare' blank for a reported puppet. This then requires manual deletion. Now that is no biggy, but isn't hugely tidy. It also stutters during the process, appearing to come to a juddeirng halt despite not doing so (Thsi is mosdef if you elect to notify the participants)

This appears to happen because there are two fields for puppets initially. If there were to be a third one can add a field. Perhaps the 'add a field' element could com into play earlier, and only one initial puppet field be presented? That looks as if it ought to solve the issue without fancy if>then>else logic Fiddle Faddle 11:59, 27 August 2013 (UTC)

I noticed this a while ago myself. As a workaround, when there's only one, instead of ARVing the master as "sockpuppeteer" and entering the sock's name, ARV the sock as "sockpuppet" and enter the master's name. Jackmcbarn (talk) 12:41, 27 August 2013 (UTC)

I have also noticed it, and I assume it was per design in TTO:s head :), i.e. that it was required to link to more than one sock. anyway, I'm gonna fix that! _→AzaToth 13:31, 28 August 2013 (UTC)

If you want someone to blame, it's Amalthea [link] :) — This, that and the other (talk) 10:00, 29 August 2013 (UTC)

RfC: Are the Category:Wikipedians and its subcategories appropriate for Wikipedia

There is an ongoing RfC going on at Category talk:Wikipedians#RfC: Is this category and current subcategories appropriate for Wikipedia that readers of this Wikipedian software page may be interested it. Technical 13 (talk) 12:19, 29 August 2013 (UTC)

TfD for protected templates

When we use Twinkle to TfD or TfM a protected template, it would be handy if an {{Editprotected}} section could be automatically added to the template's talk page.

For examples, see Template talk:Infobox member of the Knesset#TfD and Template talk:Infobox royalty#Merge propsal. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:53, 13 July 2013 (UTC)

This bit me again yesterday. Can we do something? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:00, 29 July 2013 (UTC)

Well, the answer to your question is yes, I guess. What kind of message do you propose be posted? Something like

== Edit request for XX Month 0000 ==

{{editprotected}} Please place

:<code>tfd template that Twinkle tried to place goes here</code>

at the top of this template. Thanks, ~~~~

— This, that and the other (talk) 05:04, 30 July 2013 (UTC)

Yes; that should do it. Thank you. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:56, 30 July 2013 (UTC)

You'll notice that this still hasn't happened. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

Will it? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:17, 19 August 2013 (UTC)

Eventually. — This, that and the other (talk) 02:36, 1 September 2013 (UTC)

Page tagging feature

I've realized that Twinkle doesn't have stub tag listed on the tagging feature. Should it be implemented or was it removed ///EuroCarGT 05:00, 29 August 2013 (UTC)

I'd love to see a simple implementation of a {{Stub}}, but I'm not sure we need the full stub sorting shebang, do we? Fiddle Faddle 19:01, 31 August 2013 (UTC)

AfD autosigning

I've seen a lot of double-signed AfD nominations, and I've done it myself a couple of times; it's easy to forget that Twinkle automatically signs your post when you use it to file an AfD. It would be useful if there was a reminder somewhere in the dialogue box, perhaps under the "Reason" field, saying something like "Your signature will be appended to this comment automatically". DoctorKubla (talk) 17:17, 23 July 2013 (UTC)

OK. I personally have not seen this at other discussion venues, so perhaps it is more common at AFD. I could add a pop-up tip next to the "Reason" heading above the AFD reason box if you think that would help. — This, that and the other (talk) 02:41, 24 July 2013 (UTC)

That would be great, thanks. DoctorKubla (talk) 06:37, 24 July 2013 (UTC)

Perhaps TW could look for a user inserted ~~~~ and ignore it? --Fiddle Faddle 22:37, 11 August 2013 (UTC)

I thought of that, but then users might think that the four tildes they type are actually needed, which would be quite unfortunate. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

Tto, what if it looked for it and notified the editor that it isn't needed, as it is done automatically, like WikiLove extension does? Technical 13 (talk) 13:28, 16 August 2013 (UTC)

That's a good idea. — This, that and the other (talk) 11:33, 7 September 2013 (UTC)

db-g12 now supports 3 sources

I've updated {{db-g12}}/{{db-copyvio}} to support up to 3 sources. It still works exactly as before if no source or one source is specified, but I'm letting you know about it per the template's doc page. Jackmcbarn (talk) 00:15, 12 August 2013 (UTC)

• Jack, I'm confused as to why that template needs to support multiple sources. Only one source is needed for it to be a copyvio and deletable, so simply pick the the source that is most copied and run with that. Technical 13 (talk) 13:03, 12 August 2013 (UTC)

Sometimes some of the page is copied from one source, and some from another, such as Global Nomads Group was, and this makes it easier for admins to verify them all with the extra DupDet links. Jackmcbarn (talk) 14:06, 12 August 2013 (UTC)

CSD could go the way of the tag module (i.e. getting rid of the pop-up boxes that ask for further info and replacing them with inline textboxes that appear as needed). This would make this change a bit easier to implement. What do you think? — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

Sorry for the inattention here. This is still on the cards; I'll file it in the GitHub issue tracker. — This, that and the other (talk) 11:33, 7 September 2013 (UTC)

CSD'ing User Talkpage - Instead of user, I'm being notified instead

After I nominated User talk:Jesse Armenta for CSD, I was then notified [2] (As if I were nominating own tp), I assume this warning should've ended up on her tp not mine? (I've removed page content & retried & still being notified?
Thanks - →Davey2010→→Talk to me!→ 23:38, 2 September 2013 (UTC)

It's because you created that user's talk page, so Twinkle is notifying you as the page creator. In this case you should just turn off the "notify creator" checkbox, since notification is pointless. See also [3], and consider checking out WP:DELTALK for reasons why user talk pages are very rarely deleted. — This, that and the other (talk) 06:51, 3 September 2013 (UTC)

Ohhhh right, See I never CSD'd a TP but this one was promo stuff, Thanks for your help/replying - Much appreciated! →Davey2010→→Talk to me!→ 10:14, 3 September 2013 (UTC)

TTO, does Twinkle notify you in such cases that you were the page creator so you can un-check the "notify creator" checkbox? I've created many pages for other users and there is no way I could remember all of the ones that I created. Perhaps, it should default to "notify user" instead in these cases? Just some questions/ideas. Technical 13 (talk) 12:19, 3 September 2013 (UTC)

Idea from zhwp

Hi, I'm an admin of zhwp, so the following situation only appling to Chinese Wikipedia.

Twinkle is one of the best tools in Wikipedia. Almost every editor uses Twinkle to patrol. But when patroller who wants to only tag the article will automatically marks pages as patrolled.

So is there any chance to add an opotion on tag page of Twinkle, that when patrollers don't want to mark page patrolled(they think they might need others patrol it again but want to tag some problems already found), they can choose it for only adding templates.--AddisWang (talk) 17:22, 17 July 2013 (UTC)

User:Jimmy xu wrk is the one to speak to for this, I think. Unless he sent you here :) — This, that and the other (talk) 11:27, 5 August 2013 (UTC)

Yep, I thought if this should be implemented it'd better be done in the upstream :P Jimmy Xu (talk) 14:06, 9 August 2013 (UTC)

OK. Another one to look at. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

Sorry for the inattention here. My plan is to remove the "group inside multiple issues" checkbox and replace it with a "mark this page as patrolled" checkbox (initially checked, but can be turned off if wanted). — This, that and the other (talk) 11:33, 7 September 2013 (UTC)

That looks fine. Also, should this be done on xfd as well? (Sorry for the delay, was blocked from editing...) Jimmy Xu (talk) 15:20, 10 September 2013 (UTC)

Restore version function and user names

Is it just me, or does the restoring a previous revision function not substitute a user template into the edit summary? E.g. I get
Reverted to revision 123456789 by Bryceshughes
instead of
Reverted to revision 123456789 by Brycehughes (talk)
-Brycehughes (talk) 17:54, 9 September 2013 (UTC)

I think the link was removed to allow more characters for the restoration summary. Even a simple contributions link, [[Special:Contributions/Brycehughes|Brycehughes]], takes up 38 extra characters than the plain-text username. Every charcter counts with these restoration summaries.

What should be happening here is that Twinkle should be smart enough to include the link if there is space, or not include it if the user has entered a particularly loquacious edit summary. The tag module is already smart like this, but fluff not so far. — This, that and the other (talk) 05:46, 10 September 2013 (UTC)

Ah, gotcha. Thanks. Odd, since the other revert functions seem to pull it off okay. But I'm not about to lose any sleep over it. Brycehughes (talk) 06:12, 10 September 2013 (UTC)

Twinkle and popped up windows

Some time ago you fixed an issue where, when you were editing in a previously popped up (by Twinkle), presumably named, window/tab, Twinkle failed to achieve grabbing old revisions and reverting from within that window/tab.

Rather like Arnie, it, or a similar looking brute, has come back. Fiddle Faddle (talk) 07:00, 6 May 2013 (UTC)

Just so we're on the same page, could you give a clear series of steps I could carry out to reproduce this problem? Also, have you changed any relevant things in WP:TWPREFS? — This, that and the other (talk) 11:13, 6 May 2013 (UTC)

First. NO changes in TWPREFS.

Clear steps, no. Hazy steps: revert something>user talk window opens>do editing of anything at all in that window, possibly even move away from WP>Completely forget this is a popped up window>In that window in WP some time later, find an edit to revert>Attempt to revert it and see that the API failed for (too fast, it's gone the window has been replaced with a new user talk page).

That wasn't as much help as it might be, was it, sorry. The problem is that, when it hits, I've forgotten the steps that led up to is. it IS repeatable, and it is very similar to the problem you fixed that I mentioned a few months back. It almost feels like a reversion of that part of the code repository. Fiddle Faddle (talk) 09:17, 7 May 2013 (UTC)

I'll have to look into this more closely when I have more time. Sorry I can't be of more help right now. — This, that and the other (talk) 10:25, 13 May 2013 (UTC)

No-one will die if it takes a while :) Fiddle Faddle (talk) 11:44, 13 May 2013 (UTC)

MInd you, it is still happening. Just stopping this from being autoarchived. Fiddle Faddle 23:42, 4 June 2013 (UTC)

This is about to fall off the top, so bumping. — This, that and the other (talk) 07:49, 24 June 2013 (UTC)

Adding {{DNAU}} ahead to keep this thread on page. Feel free to delete it when this one can be archived. —me_and 10:44, 24 June 2013 (UTC)

@Timtrent: OK, I finally tested this out. Here's what I did:

• I used Twinkle to roll back an edit at Template:X2; a window popped up in which I was able to warn AvicBot2
• In the popped-up window, I visited Template:X1 and rolled back an edit there
• A second window popped up in which I could again warn AvicBot2

What are you seeing that is different? — This, that and the other (talk) 01:49, 6 July 2013 (UTC)

I will check again and come back here to brief you. It may take a day or three. Fiddle Faddle 07:48, 6 July 2013 (UTC)

Here is the chain of events I have just used to reproduce this, all using Twinkle.

• Rolled back a vandalism edit
• warned vandal
• closed ALL tabs except the one in which I warned the vandal
• attempted to revert a Good Faith edit in the window above
• received the "Error grabbing data (too fast to copy) message, and the page did not revert.
• The user who had performed that edit's talk page then opened in that window

Using Safari 5.1.9 (6534.59.8), Snow Leopard 10.6.8.

Sorry it took so long to get back to you. Real life intervened. Fiddle Faddle 13:06, 18 July 2013 (UTC)

@Timtrent: The reason this has been sitting here for so long is that (a) I simply cannot reproduce the issue, and (b) it is fairly minor. Can I suggest you reset the relevant preference at the top of WP:TWPREFS (by clicking the "reset" link then saving your changes) and see if that makes any difference? — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

I'm guessing this is the "open in a new tab" preference? I have reset it. Feel free to have a play in my Twinkle preferences. I'll let you know what happens next. May take a while until I'm in that situation again. Fiddle Faddle 11:36, 16 August 2013 (UTC)

Interesting. Now it opens a new and huge window, with no address bar or other attributes. (Safari 5.1.9 (6534.59.8)). I suspect that is not what you hoped?

Hm, sounds like this whole feature has issues. You can tell that I never use it! Wondering if AzaToth might like to weigh in? — This, that and the other (talk) 11:49, 19 August 2013 (UTC)

No rush. I see it as important but not urgent. Fiddle Faddle 15:09, 19 August 2013 (UTC)

By the way, you did cure this once. I am sure something has reverted the code, or interfered with it. Fiddle Faddle 07:26, 21 August 2013 (UTC)

@Timtrent: I think I finally got to the bottom of this issue, and it is fixed by this commit. The change should be deployed on-wiki soon. — This, that and the other (talk) 12:40, 2 October 2013 (UTC)

Well done, sir. It looks to have been more complicated that you believed. I suggest you let this thread archive now, and I will alert you if I see new behaviour? I imagine the code change will propagate over the next 24 hours or so? Fiddle Faddle 12:42, 2 October 2013 (UTC)

The change has been made live, thanks to Amalthea. — This, that and the other (talk) 12:02, 3 October 2013 (UTC)

G13 update

I'm coming here to notify Twinkle that {{db-g13}} has been updated by Technical 13; Twinkle's setup needs to be updated for the extra parameters. -- ^t numbermaniac ^c 03:04, 9 September 2013 (UTC)

Well, at the moment, there is something wrong with the template (see the talk page), so I will wait until that is fixed. — This, that and the other (talk) 07:45, 9 September 2013 (UTC)

What about now? :P -- ^t numbermaniac ^c 07:52, 9 September 2013 (UTC)

No; see the talk page again. — This, that and the other (talk) 08:05, 9 September 2013 (UTC)

I don't see any problems with it and Sphilbrick (one of the big G13 deleting admins) loves the new feature. I've added some examples of what it looks like with different types of timestamps and I've added an eligible timestamp to show it as eligible. Numbermaniac feel free to follow the ticket on GitHub as well requesting this. Happy editing! Technical 13 (talk) 12:04, 9 September 2013 (UTC)

Just a quick note to confirm that I do love the color coding. I process the green ones quickly, the yellow ones differently, and so far, haven't seen a red one (which I don't expect).

This may not be the right place, but as I see you mentioning an update to Twinkle, I checked out AWB to see if it would be helpful to use. I ended up deciding not to use it, but I did notice that it did not have a G13 option in the list of deletion reasons.--SPhilbrick(Talk) 12:18, 9 September 2013 (UTC)

• Please implement the request at https://github.com/azatoth/twinkle/issues/175 to have Twinkle add the |ts=timestamp as is documented on the template's documentation:

"Place {{Db-g13|ts= timestamp}} at the top of the draft, where the timestamp is the ISO 8601 formatted date and time, equivalent to Y-m-dTH:i:sZ (YYYY-mm-ddTHH:ii:ssZ) or the magic word version of a timestamp which resembles YYYYMMDDHHmmss (YmdHis)"

As this is the last largely used tool that may be used for tagging drafts for CSD:G13. Thank you! Technical 13 (talk) 19:47, 25 September 2013 (UTC)

This was done by MC10. We just need a sync: I'll ask AzaToth. — This, that and the other (talk) 01:34, 27 September 2013 (UTC)

It's  Done. — This, that and the other (talk) 12:02, 3 October 2013 (UTC)

Incorrect addition to "Multiple issues"

Think India (edit | talk | history | protect | delete | links | watch | logs | views)
This edit tried to add an extra tag within a {{multiple issues}} template, but adding it at the end didn't work in this unusual case. -- John of Reading (talk) 20:54, 12 September 2013 (UTC)

Yes, Twinkle doesn't handle these cases properly. This issue has arisen once before, and it was decided at that time that these cases were so rare that there was no point trying to write complicated workaround code. — This, that and the other (talk) 07:11, 13 September 2013 (UTC)

Fair enough. -- John of Reading (talk) 07:22, 13 September 2013 (UTC)

CSD Log wrong additions

Sometimes, when tagging multiple CSDs at the same time, instead of detecting an edit conflict, it does this. -- ^t numbermaniac ^c 03:08, 16 September 2013 (UTC)

This is one of those times when I throw my hands up in despair and wish the MediaWiki API had been written more robustly... I modified Twinkle's CSD logging code some months ago to try to avoid this situation (and a similar situation where the CSD log would get truncated), but obviously it hasn't worked. The only thing I can think of to help prevent this issue is the use of edit timestamps: I'll look into this when I get a decent chunk of spare time. — This, that and the other (talk) 07:50, 16 September 2013 (UTC)

Ok, thanks. -- ^t numbermaniac ^c 05:36, 17 September 2013 (UTC)

• Comment: TTO, fyi, the AFCH knows how to detect edit conflicts in its CSD tagging section using our page edit function, specifically this else function. Maybe you could adapt that to work for Twinkle as well. If I can help in any way, let me know. Technical 13 (talk) 12:29, 17 September 2013 (UTC)
  • Thanks to the brilliant work of UncleDouggie back in 2011, Twinkle can automatically resolve edit conflicts for full-page edits. However, the expectation is that the MediaWiki API handles the edit conflict logic for appends and prepends, and it doesn't do a very good job (it just seems to pretend the edit conflict didn't exist and save the page anyway). So the problem here lies in the MediaWiki API. I might have a look and see if I can perhaps write a patch for the API that would fix this problem. — This, that and the other (talk) 00:18, 18 September 2013 (UTC)

Requested moves

Could Twinkle handle "move requests", please? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:04, 27 September 2013 (UTC)

See Wikipedia talk:Twinkle/Archive 30#Requested move. This may be added someday, but since this is such a simple task to undertake manually, and it is unclear which Twinkle module would take on this functionality, it is not a priority. — This, that and the other (talk) 06:09, 28 September 2013 (UTC)

copy-paste move template

why is Template:Uw-c&pmove not in twinkle? I mean they don't happen all the time, but they are not unheard of either. it should be in the single-issue notices, but I didn't see it.. -- Aunva6^{talk - contribs} 18:58, 29 September 2013 (UTC)

It's there, in the correct place in the alphabetical order :) — This, that and the other (talk) 01:05, 30 September 2013 (UTC)

Well, depending on who you ask, that is. It's certainly in the "C"s, though. — This, that and the other (talk) 01:06, 30 September 2013 (UTC)

yeah, I see it now. easy spot to overlook... -- Aunva6^{talk - contribs} 02:50, 30 September 2013 (UTC)

Twinkle not properly autoaccepting reverts of PC articles

Tracked in Phabricator
Task T56812

When Twinkle is used by a reviewer to revert pending changes to an article, instead of using the standard pending-changes feature, the page isn't autoaccepted after the revert (example). Jackmcbarn (talk) 18:58, 29 September 2013 (UTC)

Yet another bug in the MediaWiki API! I'll look into this, but can't promise anything :( — This, that and the other (talk) 11:23, 30 September 2013 (UTC)

FYI, I've filed this issue as bugzilla:54812. — This, that and the other (talk) 01:13, 1 October 2013 (UTC)

I have implemented a workaround for this issue (for rollback only, not "restore this version") in this commit. The change should be deployed on wiki soon. — This, that and the other (talk) 12:40, 2 October 2013 (UTC)

The workaround is now active on-wiki, thanks to Amalthea. — This, that and the other (talk) 12:02, 3 October 2013 (UTC)

Bug?

See [4]. Why would it think that it's 2000? buffbills7701 20:48, 2 October 2013 (UTC)

Because the clock of the device used to post the warning was set to the year 2000? That would be known issue #6. Amalthea 22:12, 2 October 2013 (UTC)

Not just tag addition, but maintenance

Future enhancement:

I patrol articles I have already tagged, or that other have. Sometimes I want to remove a tag to replace it with another. An example might be to replace {{unreferenced}} with {{refimprove}}. Currently my only option is a manual edit or a two stage process.

It's probably a huge task inside the works, but could TW be enhanced to know what is already on a page and to edit that, removing, replacing, adding new tags? Fiddle Faddle 11:52, 3 October 2013 (UTC)

It's a great idea, and it has been on our rather silly little to-do list at the top of this page, and also in the GitHub issue tracker, for quite some time. As you have correctly assumed, it is a big ask to code such a feature - I did begin work on it a couple of years ago, but got so tangled up in the code that I really just gave up. However, there's no reason why it couldn't be attempted again in the future.

(By the way, I am currently working hard to rid the CSD module of popup prompts - it takes a bit of work, but I find it very rewarding to dust out some of the cobwebs that were lurking in the code!) — This, that and the other (talk) 12:02, 3 October 2013 (UTC)

Ah yes. I only just saw that to do list!

I had the feeling you enjoyed the challenge of making something that works become excellent. I knew this would be non trivial, probably requiring an article parsing module to be created from scratch and then called without losing performance :) Fiddle Faddle 12:09, 3 October 2013 (UTC)

Un-Prod

I am not sure, but could use some help in the direction of clarity. I wish to remove the PRODed from an article that I've objected to. 'I must' delete the actual code tag on the article itself Holor, then (suggested form) do the notifications to the particulars? Deletion is my concern. Pantarbe (talk) 19:13, 8 October 2013 (UTC)

Notenglish tags

If {{notenglish}} is placed on an article, the related user warning template {{uw-notenglish}} should automatically be placed on the user talk page of the article creator. Currently this has to be done manually and is therefore often forgotten. The user message is however valuable because it informs the editor of the language issue and of a possible deletion of the article. So I think an automated user messaging for this template should be implemented in Twinkle. De728631 (talk) 16:21, 9 August 2013 (UTC)

it's not always the creator's fault for the not english. manual is more adaptable -- Aunva6^{talk - contribs} 16:29, 9 August 2013 (UTC)

Nonetheless we have the convention of notifying the creator for pretty much anything. They are considered the article's 'father'. Fiddle Faddle 21:51, 11 August 2013 (UTC)

In this case, a manual means of notification is quite important, especially to see if there is anything relevant that has already been posted on their talk page. — This, that and the other (talk) 11:27, 16 August 2013 (UTC)

At least I've updated the template text itself. Now there's not only an instruction how to list the tagged page at WP:PNT, but also a hint to notify the author. I hope this will help a bit. De728631 (talk) 11:33, 16 August 2013 (UTC)

I keep finding non-English articles tagged with this message by Twinkle where the original author has not been notified at all, and this tends to happen every other day or so. Imo this situation is unacceptable. If nobody tells them, how are new editors supposed to learn that this one is not the only Wikipedia and there is most likely another Wikipedia in their native language? I'm urging the Twinkle coders to at least include a popup message for the tagging editor to manually notify the author of any non-English texts with {{uw-notenglish}}. For convenience, this should include a templated string like {{subst:uw-notenglish|<article>}} ~~~~ (note that are some bilingual versions of this talk page template available that could be triggered by the language parameter of the article tag {{notenglish}}, see template documentation). De728631 (talk) 14:06, 24 September 2013 (UTC)

that isn't a bad idea. shouldn't be hard to implement. -- Aunva6^{talk - contribs} 15:18, 24 September 2013 (UTC)

It's not that hard to code, but I have various personal reservations about doing this. But given the demand, I suppose I should just get over it and write the code :) — This, that and the other (talk) 11:52, 25 September 2013 (UTC)

That would be very much appreciated. De728631 (talk) 13:52, 25 September 2013 (UTC)

Coming soon. — This, that and the other (talk) 12:40, 2 October 2013 (UTC)

And  Done. Please test it out: I'm pretty sure it works, but one never knows... — This, that and the other (talk) 12:02, 3 October 2013 (UTC)

Thank you for implementing this. It seems to work just fine. De728631 (talk) 17:27, 9 October 2013 (UTC)

Reverts not opening talk page

When roll backing edits from my iPad, user talk pages of the vandal never open. It seems to sit there at opening page, but never does, and sometimes just skips the step altogether. I'm using an iPad 4 with the latest Safari on iOS 7.0.2. -- ^t numbermaniac ^c 06:14, 6 October 2013 (UTC)

It's designed to open in a pop-up window, which I daresay is not supported by iOS. Try changing your Twinkle preferences so that "When opening a user talk page, open it:" is set to "a new tab", and see if that helps. — This, that and the other (talk) 06:37, 6 October 2013 (UTC)

But here's what's confusing me:

1. My setting is set to in a new tab.
2. When using Chrome on my Windows XP computer, it opens it in a new window, which is very annoying.
3. When using Chrome on my iPad, it opens in a new tab, because you can't have multiple windows on iOS, as you said.
4. When using Safari on my iPad, it doesn't do anything. The revert happens but the talk page doesn't open.

I'm confused. -- ^t numbermaniac ^c 10:34, 6 October 2013 (UTC)

We have had reports of some problems related to popup window display on Safari, but since none of the Twinkle developers use a Mac or iOS device (and Safari for Windows is no longer supported), we have never been able to track down this problem. I'll think about this some more.

I'll have to look into the Chrome issue as well; doesn't sound good. — This, that and the other (talk) 07:57, 7 October 2013 (UTC)

Older versions do exist. http://support.apple.com/kb/dl1531. -- ^t numbermaniac ^c 08:15, 7 October 2013 (UTC)

I have used Twinkle to revert on an iPod; popup windows opened normally in a new tab, but only when I reverted as vandalism (as per my preferences). Have not yet tested on iOS7; Will do when next on WiFi. --Mdann52talk to me! 08:17, 7 October 2013 (UTC)

I haven't tried the red revert yet. I only tested the blue rollback, and that's where it failed. -- ^t numbermaniac ^c 21:14, 8 October 2013 (UTC)

Red, green, blue, none of them work :( -- ^t numbermaniac ^c 01:01, 12 October 2013 (UTC)

Can't tag images for deletion

I've found a few images claimed as "Personal work" that blatantly are not (film posters, adverts, etc), and have tried to tag them with Twinkle's "DI" button, but keep getting the error Tagging file with deletion tag: Failed to save edit: The article you tried to edit doesn't exist. Am I doing something wrong, or is this a bug? Edit: the specific image at the moment is this: File:Death Poster.jpg. MatthewVanitas (talk) 17:43, 11 October 2013 (UTC)

That image is on Commons; there is no page with that name at the English Wikipedia. The deletion procedures at Commons are different - Commons:Commons:Deletion policy. -- John of Reading (talk) 18:07, 11 October 2013 (UTC)

@MatthewVanitas: For me, Twinkle does not even show the DI module on such images. Which modules are available to you on the Death Poster image? — This, that and the other (talk) 05:02, 12 October 2013 (UTC)

Same for me. Only two options appear from memory. -- ^t numbermaniac ^c 05:12, 12 October 2013 (UTC)

Heading wikimarkup for welcome messages etc.

I noticed {{Welcomevandal}}, one of the welcome messages used by Twinkle, uses a horizontal bar and a division for "Welcome" instead of a level 2 heading. I brief look in Category:Templates used by Twinkle shows something of a variety of ways that the headings are being added... Some use fancy wikimarkup for if-statements and stuff while others don't and just use normal level-2 headings. It would be good for somebody intimately familiar with Twinkle to make sure all the active Twinkle messages are using the best way of handling the heading. I don't really know Twinkle enough to do it without accidentally "fixing" things that might need need to be changed. Jason Quinn (talk) 01:13, 14 October 2013 (UTC)

You're right, it is a bit of a mess. Having templates automatically insert headings is not as easy as it might seem, hence the confusion here. I'll take a bit of a look at this. — This, that and the other (talk) 06:56, 14 October 2013 (UTC)

The reason why templates engage in such shenanigans is BTW that we never want to transclude a talk page message template with a heading. Doing so makes section edit links go to the template and unsuspecting editors will then accidentally edit that instead of the user talk page -- see e.g. the history of this very template before the fake header was introduced.
If a template insists on bringing it's own heading the best method I know is indeed the fancy markup you noted (like in {{Welcome-personal}}): you get a proper editable section if substituted, and a fake header otherwise.
But yes, it's a bit of a mess, the templates weren't all written with consistency in mind.
Amalthea 09:19, 14 October 2013 (UTC)

Thanks, Amalthea; the non-subst/edit-section issue was what I was alluding to with "not as easy as it might seem". I think the approach of {{welcome-personal}} should be extended across all the welcome templates (including {{welcome}}: I wonder why that template doesn't have this already?). And I think those without a built-in header should have one added to the template, unless there is something unusual going on.

Amalthea, this would be easier for you (as an admin) than me; are you up for it? — This, that and the other (talk) 09:42, 14 October 2013 (UTC)

I notice I even was around when {{welcome}} changed the bolded header to an actual header. The problem with that partiular template is less severe I imagine since only admins will need to be careful (and they are warned by the red shade of the textarea) and it's auto-substed by bot these days.
Changing real headers to smart headers in templates that already have them should be uncontroversial and I can certainly do that, but I'm sure someone somewhere will oppose adding a new header or changing the style of an existing one. With your module overhaul last year it has gotten much easier to maintain all those differing formats, probably easier than trying to impose a common interface on all supported templates. Not sure it's worth trying to add a header to every single one.
Amalthea 11:42, 14 October 2013 (UTC)

AN3 report

Resolved

Why does Twinkle not allow an AN3 report unless it finds three edits to the same article within the last 24 hours? I had started an edit warring report last night using twinkle and there were only two reverts within the last 24 hours, and selected both. I explained in the comment section why it was edit warring and hit submit. Twinkle came back and said that I had to select at least three reverts before it would allow me to submit the report. Edit warring is more than just the three revert rule. GB fan 12:30, 29 September 2013 (UTC)

Yes, I can see this as an issue in cases where there has been a 1RR sanction set in place. Technical 13 (talk) 01:09, 30 September 2013 (UTC)

@AzaToth: ? — This, that and the other (talk) 02:09, 30 September 2013 (UTC)

That restriction could be alleviated a bit perhaps; The intention was to prevent people making reports where the letter of the rules hadn't been breached. _→AzaToth 21:17, 9 October 2013 (UTC)

@GB fan: Now, when you select fewer than three edits, you are simply asked to confirm whether this is what you meant to do, instead of being prevented from going ahead with the report. — This, that and the other (talk) 04:15, 27 October 2013 (UTC)

Auto Removal of Unreviewed template

Resolved

When using Twinkle to tag for improvement or nominate for any form of deletion an article with the {{unreviewed}} template nestling in what is presumably the Creation Wizard fluff and clutter, might TW be enhanced to remove that template and surrounding comment clutter from the article?

Currently it means using TW to do the main job and then going in and doing a manual edit to declutter it. Fiddle Faddle 11:08, 22 October 2013 (UTC)

Twinkle already did that with the target of that redirect, it now also removed {{unreviewed}}. (Had to be changed in four scripts, should be unified at some point). Amalthea 11:23, 24 October 2013 (UTC)

Thank you :) Fiddle Faddle 08:35, 25 October 2013 (UTC)

New CSD

Resolved

A new CSD criterion, A11, has been added, after talkpage discussion. Can this be added to Twinkle? –Roscelese (talk ⋅ contribs) 18:16, 23 October 2013 (UTC)

• CSD:A11 was reverted as it is covered by CSD:G1 - CSD:G3 Technical 13 (talk) 18:24, 23 October 2013 (UTC)
  • We've been discussing this for several weeks, consensus has emerged for a new criterion, and you never bothered to participatee. I don't think you get to unilaterally reject this. –Roscelese (talk ⋅ contribs) 18:56, 23 October 2013 (UTC)
• Still see no RfC, and I still see no consensus, and I've contributed to the discussion. Please do the same before creating a new criteria that duplicates the existing G1, G2, G3, A7, or A9. Thanks! Technical 13 (talk) 23:19, 23 October 2013 (UTC)
  • It's now been pointed out to you by multiple users that you are incorrect. Let's follow proper procedure and add this to Twinkle. If you succeed in changing everyone's minds, then it can always be removed. –Roscelese (talk ⋅ contribs) 00:46, 24 October 2013 (UTC)
    • I maintain that it is harmful to Wikipedia and proper course of action is to have an RfC to finalize this. Technical 13 (talk) 00:56, 24 October 2013 (UTC)
• I've made this change; it just needs to be merged now. https://github.com/azatoth/twinkle/pull/184 Jackmcbarn (talk) 01:11, 24 October 2013 (UTC)
• I agree that there should have been an RFC about this, but if the addition of A11 is stable (i.e. not constantly getting reverted in WP:CSD) then it should be added to Twinkle. — This, that and the other (talk) 07:23, 24 October 2013 (UTC)

CSD F10 description

Resolved

The CSD dialog box when used on a file page has the description for criteria F10 as "Useless media file". This should be "Useless non-media file" per WP:CSD#F10, can this be amended? January (talk) 18:32, 23 October 2013 (UTC)

Wording was changed at WP:CSD in early 2012, I've made the change in the repository to get it back in sync. Will be deployed on here shortly. Amalthea 11:13, 24 October 2013 (UTC)

New CSD

Resolved

A new CSD criterion, A11, has been added, after talkpage discussion. Can this be added to Twinkle? –Roscelese (talk ⋅ contribs) 18:16, 23 October 2013 (UTC)

• CSD:A11 was reverted as it is covered by CSD:G1 - CSD:G3 Technical 13 (talk) 18:24, 23 October 2013 (UTC)
  • We've been discussing this for several weeks, consensus has emerged for a new criterion, and you never bothered to participatee. I don't think you get to unilaterally reject this. –Roscelese (talk ⋅ contribs) 18:56, 23 October 2013 (UTC)
• Still see no RfC, and I still see no consensus, and I've contributed to the discussion. Please do the same before creating a new criteria that duplicates the existing G1, G2, G3, A7, or A9. Thanks! Technical 13 (talk) 23:19, 23 October 2013 (UTC)
  • It's now been pointed out to you by multiple users that you are incorrect. Let's follow proper procedure and add this to Twinkle. If you succeed in changing everyone's minds, then it can always be removed. –Roscelese (talk ⋅ contribs) 00:46, 24 October 2013 (UTC)
    • I maintain that it is harmful to Wikipedia and proper course of action is to have an RfC to finalize this. Technical 13 (talk) 00:56, 24 October 2013 (UTC)
• I've made this change; it just needs to be merged now. https://github.com/azatoth/twinkle/pull/184 Jackmcbarn (talk) 01:11, 24 October 2013 (UTC)
• I agree that there should have been an RFC about this, but if the addition of A11 is stable (i.e. not constantly getting reverted in WP:CSD) then it should be added to Twinkle. — This, that and the other (talk) 07:23, 24 October 2013 (UTC)

CSD F10 description

Resolved

The CSD dialog box when used on a file page has the description for criteria F10 as "Useless media file". This should be "Useless non-media file" per WP:CSD#F10, can this be amended? January (talk) 18:32, 23 October 2013 (UTC)

Wording was changed at WP:CSD in early 2012, I've made the change in the repository to get it back in sync. Will be deployed on here shortly. Amalthea 11:13, 24 October 2013 (UTC)

Auto Removal of Unreviewed template

Resolved

When using Twinkle to tag for improvement or nominate for any form of deletion an article with the {{unreviewed}} template nestling in what is presumably the Creation Wizard fluff and clutter, might TW be enhanced to remove that template and surrounding comment clutter from the article?

Currently it means using TW to do the main job and then going in and doing a manual edit to declutter it. Fiddle Faddle 11:08, 22 October 2013 (UTC)

Twinkle already did that with the target of that redirect, it now also removed {{unreviewed}}. (Had to be changed in four scripts, should be unified at some point). Amalthea 11:23, 24 October 2013 (UTC)

Thank you :) Fiddle Faddle 08:35, 25 October 2013 (UTC)