Wikipedia talk:Twinkle/Archive 35

Archive 30

←

Archive 33

Archive 34

Archive 35

Archive 36

Archive 37

→

Archive 40

Implement automatic archiving on talk pages

I use Twinkle all the time, and thank you to the developers for maintaining and releasing Twinkle!

I often seen article talk pages that are getting quite long, and I think a very helpful extra feature would be for Twinkle to be able to automatically coordinate page archiving using Mizbot or Lowercase Sigmabot the third. Specifically, I request:

• Incorporate "Add automatic archiving" as an option
• Automatic archiving asks users for the duration of archiving, and the number of remaining posts (default 4)
• Twinkle creates Talk:x/Archive 1
• Twinkle adds the following to the talk page:

• {{User:MiszaBot/config |archiveheader = {{talkarchivenav}} |maxarchivesize = 70K |counter = 6 |minthreadsleft = 4 |algo = old(20d) |archive = Talk:x/Archive %(counter)d }}
• {{auto archiving notice|bot=MiszaBot II|age=20}}
• {{archives |auto= short |index= /Archive index }}

Or something similar. Twinkle is extremely useful at performing effort-intense or complex tasks, and implementing page archiving is one of them... it would be very useful, and I am sure be used all through Wikipedia to start archiving talk pages when they get quote old. Although frankly, I think this kind of basic functionality ought to be part of the Wikipedia platform. Kind regards, --LT910001 (talk) 01:47, 16 March 2014 (UTC)

We're not permitted to force talkpage archiving, as users are in charge of their user pages. See WP:ARCHIVE DP 13:27, 23 March 2014 (UTC)

I don't think it was meant for user talk page-archiving, but for normal talk pages. I know I have set up a few talk pages manually, and it is kind a hard, and could be made easier using a tool like twinkle. (t) Josve05a (c) 13:51, 23 March 2014 (UTC)

Yes, that is my meaning. My meaning is setting up talk page archiving -- the archiving may be done by another bot. It's complex and if Twinkle could be engineered to do it I'd be very pleased =D. --LT910001 (talk) 02:36, 24 March 2014 (UTC)

Tag description

The tag item for {{essay-like}} is so vague that it's not helpful: article is written like an essay and needs cleanup.

Could we change it to something more precise, like "article is written like a personal reflection or opinion essay"? That's what the tag itself says. WhatamIdoing (talk) 21:17, 27 March 2014 (UTC)

I absolutely agree with this. A lot of the cleanup tags have descriptions that could be improved. ☺ · Salvidrim! · ✉ 14:47, 28 March 2014 (UTC)

Indeed, it's a great suggestion. If you would like to propose new descriptions for any other tags, go ahead. As long as they are not too verbose, I would be happy to accept improved descriptions. — This, that and the other (talk) 10:37, 29 March 2014 (UTC)

Template:welcome-anon-delete

I have created an anonymous counterpart to template:welcome-delete. Could this be included in Twinkle as well? If not, tell me why and I will try to improve it. Passengerpigeon (talk) 08:36, 31 March 2014 (UTC)

It looks good. It's on its way into Twinkle. Thanks. — This, that and the other (talk) 09:58, 4 April 2014 (UTC)

Question - 'Pages missing lead section' tag

Hi! Id like to learn more about the pages which are in the 'Pages missing lead section' category. Could you tell me if they are automatically tagged per some algorithm? I am led to suspect this because of the large number of pages which appear in this category. I would also like to know - If I add a lead section per Wikipedia standards, do I remove the tag myself? And if I dont, will the tag eventually be removed automatically? Thank you! https://en.wiki.x.io/wiki/User:January2009

Hi January2009. People will often use Twinkle to apply the {{lead missing}} template if they come across an article with no lead section. When "(TW)" appears in the edit summary for that edit, you know that the edit was manually invoked (i.e. someone decided that the page in question should be tagged as missing a lead section). From what I can tell, almost all the articles in Category:Pages missing lead section were put there by a human, which just goes to show how dedicated our vast contingent of editors can be.

If you think a tag no longer applies to a page (in the case of {{lead missing}}, perhaps the article already has a lead section, or you just wrote one), it is helpful if you remove the tag yourself. Otherwise, the now unneeded tag may languish there for some time. I hope this helps! — This, that and the other (talk) 09:58, 4 April 2014 (UTC)

CSD U5

A new CSD criterion, "U5: Blatant WP:NOTWEBHOST violations" has just been created. Can it be added to Twinkle? Jackmcbarn (talk) 23:33, 3 April 2014 (UTC)

@Jackmcbarn: It's on its way. I wonder if you could come up with a more friendly summary for MediaWiki:Deletereason-dropdown, though? I don't think your current suggestion, with its raw, unpiped use of the shortcut WP:NOTWEBHOST and no real explanation of the reason for deletion, is particularly friendly for our newest users who are confronted by this type of deletion. — This, that and the other (talk) 09:58, 4 April 2014 (UTC)

@This, that, and the other: It's been changed to "Blatant misuse of Wikipedia as a web host". Jackmcbarn (talk) 19:57, 4 April 2014 (UTC)

Page split function

Is there any way that a parameter could be added so that we could propose the splitting of pages? Correct me if I'm wrong, but I wasn't able to find anything out there that states that this is supported, so that is why I am curious. Kevin Rutherford (talk) 19:11, 2 April 2014 (UTC)

It isn't supported, and I don't really know why not. What exactly needs to be done to propose a split? Is it similar to merge? — This, that and the other (talk) 09:58, 4 April 2014 (UTC)

This, that and the other, yes, as from what I understand, the parameters are the same, except that you are proposing splitting up the page instead of merging multiple pages together. Kevin Rutherford (talk) 04:54, 5 April 2014 (UTC)

CSD for Files and the CSD Log

Hi. I would like to know if it's possible to change the link for files that were proposed and logged in the CSD log. Currently, after locally (en.wp) saved versions of a file are deleted, the CSD log entry wikilinks to the en.wp pointer page for the file held on Commons -- this makes examining a CSD log harder since those files do not have red links. If it's not possible to change the wikilink, it should be possible to add a link to the file's deletion log using Special:log. (This is probably easier.) Thanks! - tucoxn\^talk 22:29, 25 February 2014 (UTC)

Where would you like the link to point? There isn't a whole lot of choice. (I actually wish image redlinks went to the File: namespace page instead of the Upload Wizard, as that is a pretty useless destination.)

I agree a link to the deletion log could be a useful addition to the CSD log in the case of files. — This, that and the other (talk) 05:26, 26 February 2014 (UTC)

How about pointing to the deleted page history. For the example of File:HOT ROD!.jpg, which was deleted on en.wp but justifiably remains on Commons, a link to the file's history could be added; the history also shows that the file has been deleted. I think this might turn out red if a wikilink is used. In any case, adding the deletion log to all CSD entries would be useful. - tucoxn\^talk 20:55, 27 February 2014 (UTC)

This, that and the other: do you think there is interest and/or use for having this change implemented? - tucoxn\^talk 02:54, 4 March 2014 (UTC)

Well, you're interested and I guess I am too :) It's an idea that makes sense, I'm just a bit snowed under right now to do anything substantial to Twinkle. — This, that and the other (talk) 10:31, 4 March 2014 (UTC)

User:This, that and the other: Any update on this. Is there anything I can do to help get it implemented? - tucoxn\^talk 02:02, 14 March 2014 (UTC)

No update; I may not have time to work on this for quite some time. Unless you're a JavaScript coder, there is not a whole lot you can do to help. — This, that and the other (talk) 06:05, 14 March 2014 (UTC)

This, that and the other: Just keeping tabs on this idea....? Thanks! - tucoxn\^talk 05:36, 27 March 2014 (UTC)

I've just added the issue to our tracker so it doesn't get lost. — This, that and the other (talk) 08:38, 27 March 2014 (UTC)

I'm not sure if I checked the tracker right but it seems like this idea is still being considered for development, with no action taken. Is that correct? Thanks! - tucoxn\^talk 05:51, 13 April 2014 (UTC)

Getting Twinkle on another wiki

Continued from /Archive_34#Help_with_putting_Twinkle_on_another_wiki

I think I've done everything you've asked, now in Twinkle.js it says "undefined is not a function" under the Twinkle.warn() line. Help? -- ^t numbermaniac ^c 04:42, 16 April 2014 (UTC)

AfD:Notifying initial contributor

When I use twinkle to nominate an article for the AfD, that article was formerly a redirect, and it notified the user that created the redirect rather than the one who converted it into an article. Please correct this. --TheChampionMan1234 10:23, 14 March 2014 (UTC)

TheChampionMan1234, I think that would be hard to implement, as that would require looking for the difference that expanded the page a certain amount, and that might be an issue on a page with many reverts and creations. Kevin Rutherford (talk) 19:04, 2 April 2014 (UTC)

The way to change this is to notify all significant contributors,even if it be unnecessary in many case>. It is important that all major contributors see the deletion request, so they will have the chance to improve the article. I suggest this include anyone making an edit adding over a certain size, or moving a page. DGG ( talk ) 03:51, 20 April 2014 (UTC)

Tag preview

Would it be possible to provide an option for previewing tags? What I do now when I'm uncertain about the wording of a tag is copy the name of the template and view it in another window before submitting in Twinkle. Previews are very useful and convenient for warnings and welcomes, and it would be great to have the option for tags too (although I suspect that it may be more difficult to implement for tags because of the multiple checkboxes). MANdARAX • XAЯAbИAM 20:04, 13 April 2014 (UTC)

Yes, this is very badly needed. We should encourage the customization of tags in appropriate cases, as this makes it more easily practical. (I often do it anyway, but manually, although it is much slower) DGG ( talk ) 03:44, 20 April 2014 (UTC)

Yes, it would be nice. The tag dialog could have a few extra things added to it. — This, that and the other (talk) 12:25, 20 April 2014 (UTC)

Minor failure

There's a minor failure in placement of {{rough translation}}: Twinkle appears not to be inserting the foreign-language name of the foreign language. If it's German, the template reads: "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." But that is not so – the original article is under "Deutsch" in the Languages sidebar. The easiest fix may be just to remove that last sentence – anyone capable of improving the translation will know the name of the language anyway. Justlettersandnumbers (talk) 21:42, 19 April 2014 (UTC)

I tweaked the template to stop doing this. It should now just say 'The original article is available in the "languages" sidebar.' when the foreign language name is not supplied, as is the case when Twinkle places this template. — This, that and the other (talk) 12:25, 20 April 2014 (UTC)

Can a section heading be added to the copyvio notice?

Looking at WP:ANI#Can anyone convince me I shouldn't block this editor? there are comments that the notice was 'buried' on the talk page. Is there any way in which a new section heading can be added to draw editors' attention to the fact that this is a copyright violation notice? Thanks. 07:11, 23 April 2014 (UTC) — Preceding unsigned comment added by Dougweller (talk • contribs)

Please fix the IPv6 bug ASAP

It was reported quite a while ago and is becoming quite a nuisance now. Dogmaticeclectic (talk) 23:51, 22 April 2014 (UTC)

It's really a bug in MediaWiki. No-one seems interested in fixing it, though. I suppose we might have to implement a workaround in Twinkle. — This, that and the other (talk) 09:40, 23 April 2014 (UTC)

Bug report: wikilink in CSD report broken

I just tagged Massacre of Turks by the Greeks (1919-22) for CSD with three reasons, and it seems Twinkle didn't correctly report one of them to the page's author: WP:CSD#A10 for Greco-Turkish War (1919–22) was reported as:

It covers a topic on which we already have an article - [[:{{{article}}}]].

I thought I'd let you know. QVVERTYVS (hm?) 10:17, 27 April 2014 (UTC)

Thanks for the report. There is a pathway in the Twinkle code that ought to be handling this, but it is clearly not behaving correctly. I'll look into it. — This, that and the other (talk) 11:21, 27 April 2014 (UTC)

Stuff

...for lack of a better heading.

• The preferences panel at Wikipedia:Twinkle/Preferences nowhere states that twinkle preferences are actually stored on a wiki page, and are hence public (unlike the mediawiki preferences). A js-savvy user could easily understand what they mean (and even a not-so-savvy user could copy-paste someone else's preferences and then go to the twinkle preferences panel). Also, the page doesn't mention that the prefs will be released under the default wikipedia license. (Not sure if there's a copyright/privacy violation in there anywhere, but you might want to look into this.)
• Someone might want to take a look at this commit I did downstream back in 2012. It includes a function to softcode namespace names in regex creation for the unlink tool in morebits.js. Devs may want to properly implement that upstream. The benefit would be that the regex would work on any wikipedia without problem.
• There's a script at hi:User:Siddhartha Ghai/twinkle.js which loads for me a personal version of twinkle from various user subpages. The only difference from the gadget version is that the header and footer have been kept separate. Devs might want to consider separating them again since using this script, changes in one module can be tested easily with the other live modules (i.e copy one module to your userspace, make some changes, use hi:User:Siddhartha Ghai/twinkle.js to load the default gadget, only replacing the changed module with the userspace subpage instead of the mediawiki page) and you can test the changes live!
• Over the past 1.5 months I've done a lot of updates to the gadget at hi.wp (stuff dating from May 2012 to October 2013). I'm just giving a heads up since I may have to take a long wikibreak and if the gadget breaks there, someone might complain here. Anything that was implemented after mid-October hasn't been implemented there (including the mediawiki js deprecations removal)
• Oh, and it seems that Jimbo uses Twinkle too, in case any of the devs ever want to do an April Fool's prank for users in the founder group ;) --Siddhartha Ghai (talk) 16:14, 27 April 2014 (UTC)

Wow, even Jimbo Wales uses Twinkle? Man, this is just reason enough to get all autoconfirmed users in good standing to get Twinkle, even if they're not planning on using it often. It's just an awesome tool. --k6ka (talk | contribs) 21:51, 28 April 2014 (UTC)

Add invite to The Wikipedia Adventure interactive tutorial

Hi. Bluerasberry (talk · contribs) suggested adding an option to invite new editors to play The Wikipedia Adventure using Twinkle. It would be a nice fit, complimentary to Teahouse invites, I think. And we have an invite already semi-automatically going out to WP:Snuggle-approved editors. This would just provide a manual option.

Background on The Wikipedia Adventure: Final Report

Link to the invite template: TWA invite

Curious what you think! Cheers, Ocaasi ^{t | c} 14:58, 22 April 2014 (UTC)

• Support I use Twinkle to welcome new users. The Wikipedia Adventure is an interactive tutorial for new users, and I think that people who complete that tutorial find it useful. This is something which has been tested for some time. I think that it is beyond an experimental stage and could be presented more widely for more use and feedback to guide future development. Most importantly, I expect no harm to come to new users or Wikipedia if this tool is shared more widely. For these reasons I would like for Twinkle to include an option to welcome new users with the template inviting them to this interactive tutorial. Blue Rasberry (talk) 15:06, 22 April 2014 (UTC)
• See above under #Wikipedia Adventure as an option. I've added the necessary code in the development repository but it has not yet been synchronised with our copy of the gadget. Unfortunately the template will be in a rather obscure corner of the Welcome module: that is because it is not a welcome template (again see the above discussion). — This, that and the other (talk) 09:39, 23 April 2014 (UTC)
  •  Done, thanks. — This, that and the other (talk) 12:06, 1 May 2014 (UTC)

Wikipedia Adventure an an option

Could we add the Wikipedia Adventure invite to the list of options? Right now, the invite is only distributed by bot and it doesn't find all the good-faith n00b editors that need to learn the buttonology. Chris Troutman (talk) 04:30, 11 April 2014 (UTC)

• I support this idea, but it is not "only" distributed by a bot. It is also offered as a link in a couple of the welcome messages for new users like {{Welcome-screen}} (which I add to "most" new users' talk pages when I create their account through WP:ACC with User:Technical 13/Scripts/ACC WikiLove.js). — {{U|Technical 13}} ^{(t • e • c)} 14:02, 11 April 2014 (UTC)

First, the template needs to be fixed to not talk about HostBot, or to only mention HostBot when a particular parameter is supplied. I suppose the author of HostBot would need to be notificed, I don't have time to deal with that now. — This, that and the other (talk) 12:50, 12 April 2014 (UTC)

• It's already a parameter, kind of... <small>This message was delivered automatically by your robot friend, {{ {{{|safesubst:}}}#if: {{{signature|}}}| {{{signature}}}|HostBot}}</small> — {{U|Technical 13}} ^{(t • e • c)} 22:20, 12 April 2014 (UTC)

• @Technical 13: Mr. Stradivarius has graciously made the change to the template so that it doesn't automatically indicate the bot does delivery. I was previously unaware of Template:W-screen but I'd still like to have this enabled through Twinkle. Chris Troutman (talk) 06:44, 16 April 2014 (UTC)

I'll put it under WikiProject-specific welcomes, since it isn't a general-purpose welcome template.

In fact, this template doesn't belong in the Welcome module at all, since it doesn't say "Welcome", provide a basic set of links, etc. But since there isn't anywhere better for it to go right now, it can go in Welcome. (Part of me wants to put it in Talkback for some reason, but that would be kind of silly.) — This, that and the other (talk) 12:25, 20 April 2014 (UTC)

 Done — This, that and the other (talk) 01:30, 2 May 2014 (UTC)

User warning for inaccessible sigs

I have created a level one warning template, {{Uw-sigdesign1}}, which reads:

Hello, I'm [Username]. I wanted to let you know that your signature ("sig") design might cause problems for some readers. This is because of low colour contrast, an unreadable font, or suchlike. If you think I made a mistake, or if you have any questions, you can leave me a message on my talk page, or take a look at our guidelines and policy on customising sigs. Thank you.

where "of low colour contrast, an unreadable font, or suchlike" can be replaced by |1= and "Thank you" by |2=.

I invite comment about its content and deployment, including the possibility of using it in Twinkle, on its talk page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:12, 18 April 2014 (UTC)

• Andy, not a bad premise, although I think the wording is lacking a bit... Perhaps:

Hello [Username], I wanted to let you know that the design of your signature might cause problems for some readers. This is because of low [[Wikipedia:Manual of Style/Accessibility|{{SAFESUBST:#switch:{{{en|uk}}}|us=color|uk|gb|au|#default=colour}} contrast]], an unreadable font, or suchlike. If you think I made a mistake or if you have any questions, you can leave me a message on [[Special:MyTalk/{{SAFESUBST:REVISIONUSER}}|my talk page]], or take a look at our guidelines and policies on customizing signatures. Thank you.

With the |1= replacement for reason. I'm not sure the |2= is needed. — {{U|Technical 13}} ^{(t • e • c)} 23:08, 18 April 2014 (UTC)

I copied the structure and wording from another uw template (I forget which) which had |2=; I think the intention is to allow the editor using the template to append further comment. The extra link to WP:Signatures is good; I;ll implement that now. Do we need to allow for national spelling variations in "colour"? I'm not sure why you have removed "I'm" from the opening line. Finally, I suggest further discussion take place on the template's talk page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:30, 19 April 2014 (UTC)

• Andy Mabbett, if some wants to add extra comment on the end, a parameter isn't needed in the template, just add it after the template before the signature, so that parameter isn't really needed. When it comes to \binternationali(z|s)ation\b for words like \bcolo(u)?r\b, I do agree that a parameter is probably not needed but on reconsideration "color" should probably be the default. My thought process on it is this, I believe that there is a higher proportion of Americans not educated enough to know that the flavor in the spelling is just that. Many of those Americans will think "colour" is misspelled and be more likely to cause trouble for themselves and others. British are more likely to see the it as caving to prevent an issue that could be caused by a dumb American. I know that reason is convoluted when I write it out, but it is very much a reality in the clarity it exists in my head. :\ — — {{U|Technical 13}} ^{(t • e • c)} 12:40, 19 April 2014 (UTC)

How common a problem is this, really? The list of Twinkle warnings is long enough as it is. — This, that and the other (talk) 12:25, 20 April 2014 (UTC)

• It's actually really common and even a lot of senior editors and admins are using poorly coded signatures and such a notice would likely be heavily used. The template could use some more work for common signature mistakes like contrast ratio, deprecated html code, non-standard fonts that can't be read by most / not English, or signature forgery / nicknames with no actual username or missing a link to the user's space. — {{U|Technical 13}} ^{(t • e • c)} 20:30, 20 April 2014 (UTC)

Without wanting to seem pedantic and obstructionist, I'm still not taken by this template. In brief, it's saying, "Your signature breaks the rules. Please fix it.", without actually stating how the signature breaks the rules, and more importantly, not explaining what needs to be done to fix it. Whenever I inform a user that something is wrong with their signature, I always suggest a possible fix (providing a snippet of code if relevant) that the user can put in place straight away. Newbies in particular can find signatures quite mystifying, and a templated message like this is probably not going to help clarify their understanding. — This, that and the other (talk) 12:12, 22 April 2014 (UTC)

A parameter for including a specific reason why a sig is inappropriate is included deliberately. The template also links to guidance on good and bad sigs. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:44, 2 May 2014 (UTC)

Feature request: |type=sidebar

One particular editor nominates a lot of infoboxes for deletion using Twinkle but refuses to manually add |type=sidebar in his nominations, resulting in added effort for other editors. Is it possible to add the sidebar parameter as an option? --AussieLegend (✉) 07:48, 3 May 2014 (UTC)

Template:Uw-sanctions is deprecated; Template:Alert

Hello. Due to changes by ArbCom to the discretionary sanctions system, Template:Uw-sanctions is deprecated. Could you please remove it from the Twinkle system? Template:Alert, a neutral informational notice (not a user warning!), has also been made available for arbitration areas of conflict. Could this template be added to the system? AGK [•] 08:57, 4 May 2014 (UTC)

Edit summary for RFPP report

Is it possible, practical, or a good idea to link to the history of an article in the edit summary when reporting a page to RFPP via Twinkle, rather than linking to the page itself? I watch RFPP, and if I see someone request page protection on my watchlist I will often go to that one first before looking at the rest of RFPP. It would be much more useful for me to click on the history of the page in question via the edit summary, rather than having to go to the article, then the history, or to RFPP and then the history. The history has to be checked anyway before protecting or declining protection. Just a thought. --kelapstick^(bainuu) 02:22, 15 May 2014 (UTC)

• Kelapstick, while I agree that is a useful idea, the only way to get to the history page is with a full url, which the MediaWiki software doesn't currently allow to be links. So, while the url could be in the edit summary, there is no way to make a link out of it short of a custom userscript. If you're going to go to that extent (I'd be happy to create the subscript for you), then there is no need to add the url to the edit summary itself as it can be done with just the page name. — {{U|Technical 13}} ^{(t • e • c)} 02:28, 15 May 2014 (UTC)
• See also bugzilla:11456. — This, that and the other (talk) 08:26, 15 May 2014 (UTC)
  • So effectively it would have to change to what is put into the edit summary to a url, and then a personal script for anyone who wants to convert it? That doesn't seem very practical for the handful of people it would actually be useful for, Thanks for the feedback though. --kelapstick^(bainuu) 11:48, 15 May 2014 (UTC)
    • Interestingly, Special:History is only available on the mobile site (Pie).--kelapstick^(bainuu) 13:08, 15 May 2014 (UTC)

• What I was saying is that since the current edit summary line source looks like:

  <li class="selected"><span class="mw-history-histlinks">(cur&nbsp;| <a href="/w/index.php?title=Wikipedia:Requests_for_page_protection&amp;diff=608686768&amp;oldid=608685610" title="Wikipedia:Requests for page protection">prev</a>)</span><input value="608686768" style="visibility:hidden" name="oldid" id="mw-oldid-null" type="radio"><input style="visibility: visible;" value="608686768" checked="checked" name="diff" id="mw-diff-608686768" type="radio"> <a href="/w/index.php?title=Wikipedia:Requests_for_page_protection&amp;oldid=608686768" title="Wikipedia:Requests for page protection" class="mw-changeslist-date">09:28, May 15, 2014</a>‎ <span class="history-user"><a href="/wiki/User:Qed237" title="User:Qed237" class="mw-userlink">Qed237</a>  <span class="mw-usertoollinks">(<a href="/wiki/User_talk:Qed237" title="User talk:Qed237">talk</a>&nbsp;| <a href="/wiki/Special:Contributions/Qed237" title="Special:Contributions/Qed237">contribs</a>)</span></span>‎ <span class="mw-changeslist-separator">. .</span> <span class="history-size">(22,106 bytes)</span> <span dir="ltr" class="mw-plusminus-pos" title="22,106 bytes after change">(+369)</span>‎ <span class="mw-changeslist-separator">. .</span>  <span class="comment">(Requesting semi-protection of <a href="/wiki/David_Moyes" title="David Moyes">David Moyes</a>. (<a href="/wiki/Wikipedia:TW" class="mw-redirect" title="Wikipedia:TW">TW</a>))</span> (<span class="mw-history-undo"><a href="/w/index.php?title=Wikipedia:Requests_for_page_protection&amp;action=edit&amp;undoafter=608685610&amp;undo=608686768" title="&quot;Undo&quot; reverts this edit and opens the edit form in preview mode. It allows adding a reason in the summary.">undo</a></span>&nbsp;| <a class="mw-thanks-thank-link" href="//en.wiki.x.io/wiki/Special:Thanks/608686768" title="Send a thank you notification to this user" data-revision-id="608686768">thank</a>)</li>
  

  there is no need to change how the edit summary looks, the only needed piece of info is there, the page name. Using just a script, it's fairly easy to get the page name, and inject a link to (info| edit | hist | talk | protection log | etc) if wanted. — {{U|Technical 13}} ^{(t • e • c)} 14:02, 15 May 2014 (UTC)

Well if you would be able to write that for me Technical 13, it would be greatly appreciated. There are probably a couple others that would use it too, I imagine. Cheers, --kelapstick^(bainuu) 14:12, 15 May 2014 (UTC)

• Kelapstick, I listed a lot of possible links and destinations to add as a toolbar, which ones are of value? — {{U|Technical 13}} ^{(t • e • c)} 01:31, 16 May 2014 (UTC)

• Technical 13 probably just (read|history|protection log)--kelapstick^(bainuu) 11:31, 16 May 2014 (UTC)

Down?

The rollback, the functions are all not showing up for me. Other people have reported the same problem. Is there any official announcement? Tutelary (talk) 20:47, 16 May 2014 (UTC)

Great to know it's not just me having problems :) →Davey2010→→Talk to me!→ 20:56, 16 May 2014 (UTC)

Nothing to do with Twinkle, see the discussion at the Wikipedia:Village pump (technical). It's being worked on. Dougweller (talk) 21:03, 16 May 2014 (UTC)

Template:Non-free reduced, used in Twinkle, is being depreciated

Hello Twinkle developers. The template Template:Non-free reduced, which is currently in use in Twinkle, is being merged into Template:Orphaned non-free revisions, per this discussion. Please update Twinkle to use the new template. Sven Manguard Wha? 16:03, 29 April 2014 (UTC)

So, put simply, you would like us to remove "non-free reduced" from Twinkle?

(Re your title I would rather use the word "deprecated".) — This, that and the other (talk) 12:01, 1 May 2014 (UTC)

Hello, TTO. Yes, exactly; but also any code in the Twinkle that services Category:Rescaled fairuse files must now service Category:Non-free files with orphaned versions.

Best regards, Codename Lisa (talk) 23:05, 1 May 2014 (UTC)

@This, that and the other: Basically, from the File Maintenance tagging window, we need {{Non-free reduced}} to be removed from the options. It might also be wise to add "(includes reduced non-free media)" to {{Orphaned non-free revisions}}. I think that's the only place this comes up. Cheers, TLSuda (talk) 00:01, 2 May 2014 (UTC)

@Sven Manguard, Codename Lisa, and TLSuda: This was  Done earlier in the week. — This, that and the other (talk) 04:38, 18 May 2014 (UTC)

Possible bug found when reverting long form IP

Twinkle rollback button only reverted the latest edit of a series of long form IP edits and failed to rollback properly to the clean version, resulting in this awkward series of edits by me. Thought it was my mistake at first, but is it a glitch? --RacerX¹¹ Talk to me^{Stalk me} 11:55, 26 May 2014 (UTC)

Yes, this is a known bug. See Wikipedia talk:Twinkle/Archive 35#Please fix the IPv6 bug ASAP and probably some earlier archives as well. -- John of Reading (talk) 18:08, 26 May 2014 (UTC)

Ahh, thanks. Well it's noted in my brain to not try that again since there appears to be no immediate plan to fix it. --RacerX¹¹ Talk to me^{Stalk me} 18:41, 26 May 2014 (UTC)

I finally decided to do something about this. I've fixed the issue in our repository and the fix should be live here in a few days. — This, that and the other (talk) 01:59, 31 May 2014 (UTC)

Can a section heading be added to the copyvio notice?

Sorry to nag, but my experience is that this would be useful. Looking at [1] there are comments that the notice was 'buried' on the talk page. Is there any way in which a new section heading can be added to draw editors' attention to the fact that this is a copyright violation notice? Thanks. Dougweller (talk) 09:37, 15 May 2014 (UTC)

Sorry for ignoring this request. The problem here is that there was an existing "April 2014" header on the user's talk page, to which Twinkle duly added the additional warning. This is the standard behaviour, and while it may not be ideal, a better idea has not yet been proposed as far as I know. (I would argue that BracketBot should stop using "month/year" headings and switch to something more descriptive; the "month/year" headings are de facto reserved for user warnings and should not be used for trivialities such as markup notifications.) — This, that and the other (talk) 11:10, 15 May 2014 (UTC)

If month year headings are used by BracketBot, then they are not de facto reserved for user warnings. I'd also argue that, absence any evidence of it, there is no community consensus for such reservation. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:26, 15 May 2014 (UTC)

Before BracketBot came in, they were definitely de facto reserved for user warnings. BracketBot is a fairly recent innovation. Note also that the disambiguation page link notifier bot, whatever it's called, uses its own specific section heading. — This, that and the other (talk) 06:37, 16 May 2014 (UTC)

Switching BracketBot isn't going to help if you have a bunch of warnings, then a bunch of comments, and add another warning (copyvio or other) within the same month, it just gets pasted at the bottom of the page under the latest section. If there are any warnings that were placed in that month, it will not create a new heading. The problem is (not just with copyvio templates) is if there are comments after the section titled current month/year, it just attaches it to the bottom without a new heading. I wouldn't say they are de facto reserved for warnings, there is nothing stopping me (technically or policywise) from starting a discussion on someone's talk page with a month/year heading. I went through the process at User talk:Kelapstick/Workshop, and I would suggest that a section should always be added when adding a warning via twinkle, unless the newest section is currently titled month/year. --kelapstick^(bainuu) 12:59, 15 May 2014 (UTC)

Thanks for the replies. The only place that I have found these month/year headings at all useful are on IP talk pages. Is there a good reason for them? Could we just get rid of them? Dougweller (talk) 14:21, 15 May 2014 (UTC)

Or add a check box where Twinkle asks if you want to create a new section (to allow for prominence) or not (to allow for grouping of like messages). I would suggest the default to be checked. What you suggest for heading titles Doug? Just "Warning" or "Notice" (depending on the classification).--kelapstick^(bainuu) 14:35, 15 May 2014 (UTC)

Yes, that would be fine, special section headings for each warning are probably too much. Dougweller (talk) 16:28, 15 May 2014 (UTC)

Here are my thoughts:

• Twinkle's current algorithm is rather dumb: it just looks to see if a current month header exists, and doesn't check to see if it is the last header on the page. This ought to be fixed - Twinkle should add an additional "May 2014" section to the bottom of the page if the existing "May 2014" section is not the last section. I think that would go some way to resolving most people's concerns.
• I'm not exactly sure why month/year headers began to be used. I generally think they're a good idea, since most warnings are temporal in nature (after a few months they become less relevant). They also have the added benefit of grouping together a progression of warnings (1 to 4), presumably making it easier for admins working through the WP:AIV queue. I think the section headers "Warning" and "Notice" are too vague and not particularly useful - they're good enough for the edit summary, but not for the header that introduces the warning.
• When I said that the month/year heading style is de facto reserved for warnings, I meant that, generally speaking, the only things you ever see with month/year headings are user warnings and silly old BracketBot. OF course there is nothing stopping you going and using that format; the fact is, nobody seems to do that.

— This, that and the other (talk) 06:46, 16 May 2014 (UTC)

Yes, in general I agree with you This, that and the other, I think the month/year, aside from what you mentioned, are beneficial because they are neutral (non-aggressive) and since they they don't actually say "warning" or "stop it" or something similar, the the same heading can be used for level 1 warnings, single issue notices, single issue warnings, 4im warnings, etc. Now, for me, and I am sure others, seeing a month/year heading generally means that the user did something wrong (not necessarily intentionally). --kelapstick^(bainuu) 11:39, 17 May 2014 (UTC)

On second thoughts, it might not be a bad idea to add an extra section header above some of the longer notices, in order to more clearly set them apart from other notices. I am particularly thinking of changing Twinkle so it adds a header for these templates:

• {{uw-copyright-new}} (for example, == Wikipedia and copyright ==)
• {{uw-coi}} (for example, == Managing a conflict of interest ==)
• {{uw-coi-username}} (for example, == Your username ==)
• {{uw-lang}} (for example, == National varieties of English ==)

I wouldn't mind doing this for {{uw-ew}} and {{uw-ewsoft}} as well, although I can't think of an appropriate heading. If you think any other templates should have a header (a full list is available here) or if you want to suggest different header text for one of these templates, please feel free to say so. — This, that and the other (talk) 08:02, 18 May 2014 (UTC)

That sounds great. I certainly think those sound like good suggestions and would help focus editors' attention. Dougweller (talk) 10:53, 18 May 2014 (UTC)

 Done Thanks for your input. — This, that and the other (talk) 11:34, 2 June 2014 (UTC)

Change to template available in Twinkle

{{R from scientific name}} now allows an optional unnamed first parameter specifying the kind of organism involved; for example {{R from scientific name|plant}}. As of now, only "plant" (and spelling variations) is recognized, all other values are ignored. It is expected that other group names (e.g. bird, mammal) will be added in future. Peter coxhead (talk) 19:51, 2 June 2014 (UTC)

Can we change "anonymous users" to "IP addresses"

Most editors here edit anonymously, I'm among a minority who do not. See User talk:Jimbo Wales#MediaWiki:Anoneditwarning and MediaWiki talk:Anoneditwarning#Should we tell IP editors that an account can offer more anonymity?. Thanks. Dougweller (talk) 11:53, 25 May 2014 (UTC)

Sorry for not replying, but it's quite unclear what you are referring to here. In the Welcome module we already use the term "IP user" (I think "IP address" was avoided due to space constraints, if I remember rightly). Where else does Twinkle use the term "anonymous user"? — This, that and the other (talk) 02:24, 3 June 2014 (UTC)

Non-English welcomes

{{Welcomeen-ar}} has recently been created. Can it be added to the list of Non-English welcomes? -- John of Reading (talk) 14:33, 5 June 2014 (UTC)

Tag: Ref improve → Refimprove

The {{Ref improve}} tag in Twinkle's article maintenance tagging feature is a redirect to {{Refimprove}}. Inserting this redirect creates more work for editors and bots that clean up redirects. This should be a quick and easy fix? -- P 1 9 9  ✉ 14:44, 4 June 2014 (UTC)

Isn't it better to use the more friendly name? I wonder why the template isn't at the title "Template:Ref improve". — This, that and the other (talk) 10:57, 5 June 2014 (UTC)

• Looking at the template history, Refimprove appears to be the original name, and the name stuck. I'm sure it is possible to show it as "Ref improve" in the menu, but insert the "Refimprove" template. -- P 1 9 9  ✉ 13:08, 5 June 2014 (UTC)

Of course it's possible; I just don't see why we should make a special exception for this one template... — This, that and the other (talk) 00:08, 6 June 2014 (UTC)

• I'm only suggesting to fix a redirect. This isn't the right place to discuss changing the template's name... -- P 1 9 9  ✉ 14:00, 6 June 2014 (UTC)

Duplicate AIV reports get dumped

Hiya, and thank you guys for working on Twinkle, which is a super-useful utility. A few times now I've submitted users to AIV with super-detailed reports, only to learn after clicking save, that the report exists, and my changes are discarded. That's kind of a bummer because I often collect more details than the editor who originally submitted the report and having them discarded amounts to wasted work. It would be helpful if either Twinkle kept the information displayed on screen so we can choose to append or incorporate the information manually, or if Twinkle could add the second report as a sub-comment kind of like this:

• 127.0.0.1 (talk · contribs · deleted contribs · filter log · info · WHOIS · RDNS · trace · RBLs · http · block user · block log) Persistent removal/blanking of sourced content, removal of references/ciations (from reliable sources) and biased editing (pushing an agenda). Has been warned multiple times, but has not ceased. UpsetUser123 (talk) 01:05, 30 May 2014 (UTC)

(Duplicate report appended by Twinkle) Persistent disruption from IP user. Examples: [1][2][3][4] May also be editing from 127.0.0.2 and 127.0.0.3 Thanks, Cyphoidbomb

Thanks for listening, and again, thanks for the hard work. (P.S. sorry for the tempting, but fake, links. ) Cyphoidbomb (talk) 17:06, 30 May 2014 (UTC)

Yes, this is an unpleasant problem; thanks for reporting it. What I have done in our code repository is to make Twinkle display your AIV or UAA comments on screen if it finds that the user has already been reported, so you can copy and paste what you wrote onto the AIV or UAA pages if you wish. I think this is possibly better than automatically adding to the existing report, as it allows you to go back and read the report that was already made; in any case, adding to an existing report is not always easy to achieve. The change should go live in the next few days. — This, that and the other (talk) 03:14, 31 May 2014 (UTC)

@Cyphoidbomb: Now  Done as I explained. I know it's not quite the way you suggested, but hopefully it helps all the same. Thanks for the report! — This, that and the other (talk) 11:35, 2 June 2014 (UTC)

@This, that and the other: Wow, hey, thanks a bunch! Looking forward to giving it a whirl. Much obliged, and thanks for the hard work! Cyphoidbomb (talk) 15:51, 2 June 2014 (UTC)

Could this be done for regular reverts as well? It's irritating when I type in a detailed edit summary only to have an edit conflict ruin it all. --k6ka (talk | contribs) 16:53, 2 June 2014 (UTC)

@This, that and the other: I submitted a duplicate AIV report today, and got to see the new persistent window. Worked great. The one thing I'd maybe consider adding is a link to [[WP:AIV]] in the text at the top of the window that says, "in case you want to copy this information over to AIV" (or whatever the actual text is.) Anyhow, this saved me lots of time today, so thanks again. Cyphoidbomb (talk) 16:47, 7 June 2014 (UTC)

Redirecting to RFPP

First, I would like to have an option so that I can have it open RFPP in a new tab instead of changing the page I am on. I often see stuff I want to get changed on the page, request the protection level lowered, and then read the page further to see if there is anything that needs attention before the request is granted. I've also been known to request protection before reverting vandalism. So, being able to request protection, and then still be on the page is important to me.

Second, I'd like it to either take me to my RFPP post or at very least the section my post is in (since mine should be the top post anyways). Having it dump me on the top of the page is simply extra work and annoying. There is no priority rush on this, and I'm happy to discuss it if you have any questions. Thanks guy, you really do a great job here. :) — {{U|Technical 13}} ^{(e • t • c)} 19:57, 7 June 2014 (UTC)

Twinkle stopped loading

Resolved

Anyone else having issues? --NeilN ^{talk to me} 21:36, 7 June 2014 (UTC)

^{(duplicate conversations merged)} I just noticed... Twinkle is no longer working for me. It simply will not load. Any information on this? --k6ka (talk | contribs) 21:37, 7 June 2014 (UTC)

I am affected as well. Cyphoidbomb (talk) 21:45, 7 June 2014 (UTC)

Okay, it might've had something to do with Amalthea's recent edits to what appears to be some of Twinkle's modules. Or WMF might've made some software updates that broke Twinkle, though I think that's unlikely.

June 7, 2014

• (diff | hist) . . MediaWiki:Gadget-friendlywelcome.js‎; 17:24 . . (+17)‎ . . ‎Amalthea (talk | contribs)‎ (v2.0-717-gb28bc42: tag: Switch to scrollbox; add link to each template's documentation; morebits, welcome, shared: Overhaul scrollbox functionality; morebits: Remove padding: 0 from footer buttons; morebits: Add DocumentFragment and CSS class support) [rollback]
• (diff | hist) . . MediaWiki:Gadget-friendlytag.js‎; 17:24 . . (+559)‎ . . ‎Amalthea (talk | contribs)‎ (v2.0-717-gb28bc42: tag: Switch to scrollbox; add link to each template's documentation; morebits, welcome, shared: Overhaul scrollbox functionality; morebits: Remove padding: 0 from footer buttons; morebits: Add DocumentFragment and CSS class support) [rollback]
• (diff | hist) . . MediaWiki:Gadget-friendlyshared.js‎; 17:24 . . (-34)‎ . . ‎Amalthea (talk | contribs)‎ (v2.0-717-gb28bc42: tag: Switch to scrollbox; add link to each template's documentation; morebits, welcome, shared: Overhaul scrollbox functionality; morebits: Remove padding: 0 from footer buttons; morebits: Add DocumentFragment and CSS class support) [rollback]
• (diff | hist) . . MediaWiki:Gadget-morebits.css‎; 17:24 . . (-37)‎ . . ‎Amalthea (talk | contribs)‎ (v2.0-717-gb28bc42: tag: Switch to scrollbox; add link to each template's documentation; morebits, welcome, shared: Overhaul scrollbox functionality; morebits: Remove padding: 0 from footer buttons; morebits: Add DocumentFragment and CSS class support) [rollback]
• (diff | hist) . . MediaWiki:Gadget-morebits.js‎; 17:24 . . (+1,026)‎ . . ‎Amalthea (talk | contribs)‎ (v2.0-717-gb28bc42: tag: Switch to scrollbox; add link to each template's documentation; morebits, welcome, shared: Overhaul scrollbox functionality; morebits: Remove padding: 0 from footer buttons; morebits: Add DocumentFragment and CSS class support) [rollback]

--k6ka (talk | contribs) 21:47, 7 June 2014 (UTC)

This issue is affecting me too; it's really annoying because I was trying to revert vandalism earlier but Twinkle wouldn't load. Dustin (talk) 21:55, 7 June 2014 (UTC)

Sorry, should have tested it before putting it live ... give me a minute to look into it, please :) Amalthea 21:56, 7 June 2014 (UTC)

(edit conflict) @Dustin V. S.: If you're active in the anti-vandalism section of the wiki, then you should seriously get rollback rights. They help, it's only adding user warnings that becomes a pain without Twinkle.

@Amalthea: With your permission, can we put you in the Village Stocks? :P --k6ka (talk | contribs) 21:58, 7 June 2014 (UTC)

k6ka, nah this is small potatoes compared to the template editor who edited the infobox person template a couple months ago and somehow made all images display at their uploaded size. Justin Bieber's face taking up 90% of my screen... --NeilN ^{talk to me} 22:14, 7 June 2014 (UTC)

@NeilN: Or the administrator who deleted the main page XD They sure went fishing for a while. --k6ka (talk | contribs) 22:16, 7 June 2014 (UTC)

• @NeilN:, why were you looking at the Justin Bieber page in the first place? o.O j.k :p — {{U|Technical 13}} ^{(e • t • c)} 14:53, 8 June 2014 (UTC)

I actually just put out a request for rollback rights yesterday. Dustin (talk) 22:03, 7 June 2014 (UTC)

• Amalthea, the error I'm getting in my console is "SyntaxError: malformed Unicode character escape sequence" and when I dig in for the details, it is the line of code:

		$checkbox.parent().append(["\uA0", link]);

Hope this is helpful... — {{U|Technical 13}} ^{(e • t • c)} 22:01, 7 June 2014 (UTC)

Yes, fixed in repo and put live, should be working again in a bit for everybody. Sorry again. :/ Amalthea 22:04, 7 June 2014 (UTC)

Are you sure? I looked, and... Dustin (talk) 22:06, 7 June 2014 (UTC)

(edit conflict × 2) Is there some sort of delay when editing the MediaWiki interface? It still wasn't working when I checked. Dustin (talk) 22:08, 7 June 2014 (UTC)

Mine's back up! Thanks all. Cyphoidbomb (talk) 22:06, 7 June 2014 (UTC)

(edit conflict) Think it's fixed, the TW drop-down menu appeared for me. --k6ka (talk | contribs) 22:08, 7 June 2014 (UTC)

It's working now, for me. Thank you! Dustin (talk) 22:09, 7 June 2014 (UTC)

(edit conflict)x3 - Still affecting the Gadget on non-Wikimedia wikis. Mlpearc (open channel) 22:10, 7 June 2014 (UTC)

• If it is not working for you right away, you may need to WP:BYPASS to make it take faster. — {{U|Technical 13}} ^{(e • t • c)} 22:16, 7 June 2014 (UTC)

Sorry, everyone... this is my fault. I was fairly sure I tested that piece of code, but obviously I didn't test it completely enough, or maybe I modified it after testing it, which is always a bad thing to do. My apologies. Please don't blame Amalthea; he's totally innocent! — This, that and the other (talk) 02:33, 8 June 2014 (UTC)

It wasn't down for that long, honestly. I've seen CBNG down for weeks at a time. That is much, much worse. --k6ka (talk | contribs) 11:56, 8 June 2014 (UTC)

• No worries TT&tO and Amalthea. You did fine. Things can only be fixed as fast as they are reported. — {{U|Technical 13}} ^{(e • t • c)} 14:53, 8 June 2014 (UTC)

WP:NOTAFORUM warning message

I just used the WP:NOTAFORUM warning message for the first time just now. The popup asks for the article title. I don't mean to pick nits but this is a bit misleading. The sentence that is provided by the template is clearly talking about talk pages: "...talk pages such as Foo are for discussion..." I think it would be better if the popup either A) asks for the talk page and not the article title, or B) adds the word "Talk:" on to the beginning of the article title when it is supplied. (I'm not watching this page, so please {{ping}} me in replies) Thanks, Dismas|^(talk) 13:46, 10 June 2014 (UTC)

Are new or anonymous users allowed to use Twinkle?

I read something about "autoconfirmed users" on the project page. However, is it true that I (as a new user) am allowed to use Twinkle when reverting edits? Would I get in trouble? The Ranoclue (talk) 23:57, 9 June 2014 (UTC)

Yes, you are allowed to use Twinkle. As long as you don't revert edits that don't need to be reverted, I'm talking constantly, usually once or twice or even three times will be forgiven, you may be blocked I'm not sure if admins are able to take away Twinkle from someone. Tutelary (talk) 00:10, 10 June 2014 (UTC)

^{(this comment has been removed by the author)} --k6ka (talk | contribs) 02:18, 11 June 2014 (UTC)

Multiple triangles in TW menu

Resolved

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

---

Just recently I've started seeing multiple triangles and overlapped "TW" text in the Twinkle menu. This happens to me in both Safari 7.0.4 and Firefox 30.0 on OS X. Here is a screenshot of the bug:

Does anyone know what causes this and how to fix it? If you need any additional information please let me know. —RP88 ^(talk) 19:41, 12 June 2014 (UTC)

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

Duplicate text and extra arrows appearing in drop down menus

It's not an issue with just Twinkle.
The duplicate texts are also appearing if you've activated "page and user options - drop-down menus" in Gadgets→Appearance section.
Abhinav—Ŧ—� 20:47, 12 June 2014 (UTC).

• See above, and wP:VPT the panda ₯’ 21:27, 12 June 2014 (UTC)

Is anyone else?

Resolved

Seeing the the twinkle drop-down menu arrow duplicated? FoCuSandLeArN (talk) 19:18, 12 June 2014 (UTC)

So am I. I wonder what the heck's going on now. --k6ka (talk | contribs) 19:19, 12 June 2014 (UTC)

Filtered out Special:RecentChanges to show only MediaWiki changes. I suspect these might be the culprits...

June 11, 2014

• (diff | hist) . . MediaWiki:Gadget-ProveIt.js‎; 23:08 . . (-95)‎ . . ‎Krinkle (talk | contribs)‎ (Clean up) [rollback]
• (diff | hist) . . MediaWiki:FileUploadWizard.js‎; 23:00 . . (-12)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:ImageAnnotatorConfig.js‎; 22:59 . . (-130)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:Gadget-massblock.js‎; 22:58 . . (-16)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:RecentRelated.js‎; 22:58 . . (-109)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:RecentRelated.js‎; 22:56 . . (-31)‎ . . ‎Krinkle (talk | contribs)‎ (addOnloadHook -> $)
• (diff | hist) . . MediaWiki:RecentRelated.js‎; 22:56 . . (-45)‎ . . ‎Krinkle (talk | contribs)‎ (Remove obsolete check)
• (diff | hist) . . MediaWiki:Wikibugs.js‎; 22:55 . . (-26)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:Common.js/shuffle.js‎; 22:54 . . (-96)‎ . . ‎Krinkle (talk | contribs)‎ (Update) [rollback]
• (diff | hist) . . MediaWiki:WikiProject User scripts/Scripts/Multi-NS search.js‎; 22:53 . . (-56)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:Gadget-LongEditSummaries.js‎; 22:53 . . (-5)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:Gadget-sidebar-ca-modern.js‎; 22:51 . . (-4)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:Gadget-CleanDeleteReasons.js‎; 22:51 . . (0)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:Sandbox.js‎; 22:50 . . (-373)‎ . . ‎Krinkle (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:Geonotice.js‎; 19:11 . . (+418)‎ . . ‎Calliopejen1 (talk | contribs)‎ [rollback]
• (diff | hist) . . MediaWiki:Spam-blacklist‎; 02:03 . . (+23)‎ . . ‎Black Kite (talk | contribs)‎ (+1) [rollback]

Pinging users: Krinkle, Black Kite, Calliopejen1. --k6ka (talk | contribs) 19:22, 12 June 2014 (UTC)

Here's a screenshot of the glitch...

--k6ka (talk | contribs) 19:32, 12 June 2014 (UTC)

Yeah, the same problem is happening to me, too. Epicgenius (talk) 19:32, 12 June 2014 (UTC)

• I'm guessing about everyone is seeing it, I would guess it was one of the edits by Krinkle because those are the only ones falling into the time frame. The only other possibility is MW devs pushed the next release and there is a bug of some sort. — {{U|Technical 13}} ^{(e • t • c)} 19:35, 12 June 2014 (UTC)
• MediaWiki-related? I also see double "edit" links on file information pages on Commons.

Commons - Wikipedia --Stefan2 (talk) 19:38, 12 June 2014 (UTC)

• Same here, Just assumed Chrome failed or whatever... –Davey2010 • (talk) 19:40, 12 June 2014 (UTC)

Glad I'm not alone. Would offer to help find the error, but I'm more likely to cause problems than solve them... EvergreenFir (talk) 21:24, 12 June 2014 (UTC)

• Similar discussion in WP:VPT - this should be centralized the panda ₯’ 21:26, 12 June 2014 (UTC)

I submitted a patch for this issue: https://github.com/azatoth/twinkle/pull/225. Twinkle has been doing too many workaround for its own good, the patch removes three of them fixing the problem. Matma Rex talk 05:23, 13 June 2014 (UTC)

Unlink/MediaWiki bug

In this edit, Twinkle's "unlink" feature placed <!-- Commented out: on one line and everything else on the second line. MediaWiki doesn't recognise this as an XML comment, so the image remains in the article and the ending --> is displayed as normal text. Seems to be a bug in either MediaWiki or Twinkle. --Stefan2 (talk) 11:27, 12 June 2014 (UTC)

@Stefan2: MediaWiki bug, not Twinkle. MediaWiki should recognize that, but the gallery markup apparently is an exception to that. It seems that each line inside gallery tags is parsed completely independently of all other lines inside the gallery tags, which breaks multi-line comments. I'd report this at WP:VPT. jcgoble3 (talk) 07:25, 13 June 2014 (UTC)

@Stefan2: Twinkle seems to have been confused by the extra blank line at the beginning of the gallery. This can be worked around within Twinkle.

I'm interested that you use Unlink; I really didn't think anyone ever used it. In view of the fact that the tool has at least one user, I've decided to implement a few minor improvements, in particular, a "Select All"/"Unselect All" button. I may even get around to implementing shift-click (click a checkbox, hold down Shift, and click another to select/deselect all in between). As always, feedback and suggestions are welcome. — This, that and the other (talk) 12:07, 13 June 2014 (UTC)

@This, that and the other: Me, me! I happen to have some code lying around to support shift-clicking checkboxes, the wikibits code had a couple of limitations ... Y 07f75bba1, 051bc0cc. :)
Feel free to move around, implement, clean up as you like, it's been ages since I've added anything to Twinkle. ;)
Amalthea 13:12, 13 June 2014 (UTC)

I think that "Unlink" is a very convenient feature for removing images used in violation of WP:NFCC. Thank you for the selection buttons! Now it is faster to select the right pages if a file only should be unlinked from a small number of the pages on which it is used. --Stefan2 (talk) 19:38, 13 June 2014 (UTC)

• See also #unlinking issue below. — {{U|Technical 13}} ^{(e • t • c)} 19:48, 13 June 2014 (UTC)

unlinking issue

Moved from User talk:Technical 13 § Emergency!

I need help; I used Twinkle (the unlinking feature) on WP:SANDBOX, and it unlinked a whole bunch of pages. Look at my contributions. Help!!! --JustBerry (talk) 18:49, 13 June 2014 (UTC)

All reverted. Huon (talk) 18:51, 13 June 2014 (UTC)

• Hrrm... First, thanks Huon... Second, This, that and the other, I remember seeing that you were encouraged to working on Twinkle's unlinking feature in the near future. Based on this good-faith accident, I'm wondering if perhaps Twinkle's unlinking feature shouldn't work on such sandboxes, or at very least shouldn't be unlinking things based on template transclusions from those pages. Comments or ideas on this? A better explaination of what exactly caused it so we can come up with an appropriate plan of action? Want to move this discussion to WT:Twinkle (if so go ahead and just leave a {{Moved|WT:Twinkle#unlinking issue}} here or something)? — {{U|Technical 13}} ^{(e • t • c)} 19:04, 13 June 2014 (UTC)

To me it looks as if the feature was run not on the sandbox, but on WP:Requests for page protection. That said, it seems a very powerful tool - I don't want to know what would happen if it were used on some really heavily linked page. If the purpose is to unlink deleted pages, should the feature check whether the target page exists? Huon (talk) 19:12, 13 June 2014 (UTC)

I've taken it upon myself to move it here myself. This is certainly a very powerful Twinkle option/tool and this needs to be discussed more in depth with everyone interested in Twinkle's development. — {{U|Technical 13}} ^{(e • t • c)} 19:29, 13 June 2014 (UTC)

• I think that the unlink feature is a very convenient tool for removing unambiguous violations of the non-free content criteria, for example like this (unambiguous violation of WP:NFCC#8 and WP:NFCC#10c). Based on edit summaries, it seems that User:Werieth uses "unlink" for the same purpose. However, you always need to be careful not to unlink too much, in particular if the page still exists. --Stefan2 (talk) 19:55, 13 June 2014 (UTC)

I added a small explanation to the top of the Unlink dialog box, which was intended to avoid such incidents as this. However, it seems that this incident occurred after the explanation was added, which suggests to me that my wording wasn't clear enough! What do others think? — This, that and the other (talk) 01:20, 14 June 2014 (UTC)

I think that people should be careful with how they use Twinkle. For example, Wikipedia:Miscellany for deletion/Wikipedia:Sandbox (4th nomination) has been deleted lots of times, and it seems that Wikipedia:Miscellany for deletion/Wikipedia:Sandbox (3rd nomination) also was created as a result of someone not being careful enough when using Twinkle. I don't know how to best warn users. Maybe Twinkle should warn if used on the sandbox? --Stefan2 (talk) 02:05, 14 June 2014 (UTC)

• I'm not convinced that any amount of clarity or and warning is going to prevent young or otherwise excitable editors from "having to try" all of the features of Twinkle. I'm guessing that the only way to prevent this type of thing is for Twinkle to technically prevent it on pages where it shouldn't be used. I've never cared to try it that I can remember, so I can't say exactly how such a technical restriction might be decided upon. — {{U|Technical 13}} ^{(e • t • c)} 02:09, 14 June 2014 (UTC)
• Having seen other reports of messes created by this tool, I am afraid to even click on Unlink in the menu, especially since the documentation does not explain how the function works, so I have no clue what would happen if I tried it. It's probably the only non-admin aspect of Twinkle that I haven't used. jcgoble3 (talk) 07:38, 14 June 2014 (UTC)

WP:NOTHERE

AS WP:NOTHERE is now on the dropdown for blocking (indefinitely), I have created a new template {{uw-nothere}}, could this be added to twinkle please as a user talk indefinite block rationale? Thanks. Black Kite kite (talk) 00:40, 15 June 2014 (UTC)

Looks good, although I boldly moved the template to {{uw-nothereblock}}, to match other block templates that end in "block". {{uw-nothere}} looks as if it should be a single-issue warning template. Your new block template is on its way into Twinkle. — This, that and the other (talk) 02:26, 15 June 2014 (UTC)

Thanks very much. Black Kite kite (talk) 02:32, 15 June 2014 (UTC)

Feature request - Accesskey for "last"

Hey guys, I often find myself at the bottom of the page reading an edit (semi|template)? request, and there is a reference cited using the ref tag or whatnot. This is annoying and I either have to click on "edit" to see the reference, or I have to scroll all the way back up to the top of a long talk page (ctrl+home doesn't always work for me) in order to click on the dropdown for twinkle and click the "last" link. What I'm requesting is an accesskey (I'm thinking "<" would be a good key because it is close to alt and shift and indicats "back" and "l" is taken by the system for "watchlist") to be able to load the diff from wherever I am on the page in one shot. Than ks for your consideration on this idea. — {{U|Technical 13}} ^{(e • t • c)} 15:31, 15 June 2014 (UTC)

Deletion of Rahul Kumar Page

Resolved

Respected Sir, Rahul Kumar has enough references from leading newspapers I am surprised to see that it has been nominated for deletion. If you check the history of this page, we proved to Ascii002 the notability and he accepted the same too. The page is credible and is a short biography and must not be deleted, rather it should be suggested what is missing. Notability is not the issue as article have references from leading newspapers, and most of the credible links are over 3 years old, proving the notability. — Preceding unsigned comment added by Wikicontri1968 (talk • contribs) 05:04, 16 June 2014 (UTC)

Wikicontri1968: The article has not been deleted, but it has been nominated for deletion at Wikipedia:Articles for deletion/Rahul Kumar (businessman). If you wish the article to be kept, you should participate in the deletion discussion. Also, this page is the wrong place to debate the deletion. --Stefan2 (talk) 11:29, 16 June 2014 (UTC)

Not loading

Resolved

Hi T13, Need your expertise here. I was following the discussion over at Wikipedia talk:Twinkle#Twinkle stopped loading and unfortunately Twinkle still failed to load for me despite WP:BYPASS. Please advise. Cheers. LRD NO (talk) 13:50, 15 June 2014 (UTC)

• That was a week ago, are you still having issues? If so, I'll need some information like what skin you are using, what browser you are reading Wikipedia on, what gadgets you have enabled, and any beta features you are using. If you need help finding that information, let me know and I'll instruct on how to find the information. :) — {{U|Technical 13}} ^{(e • t • c)} 14:04, 15 June 2014 (UTC)

Yes, that was quite some time back. I thought it would come back eventually but it didn't. I'm using the default skin with a custom css, Chrome, and only TW enabled. Cheers. LRD NO (talk) 15:42, 15 June 2014 (UTC)

• That's quite odd. I'm assuming you tried WP:BYPASS a few times. Have you tried a different browser or machine (if available)? This would help narrow it down to whether or not it is an issue with your account settings or machine. I'm sure we can fix it either way, but this would help guide us to the solution. — {{U|Technical 13}} ^{(e • t • c)} 15:59, 15 June 2014 (UTC)

Just tried in on IE and it's the same. Do not have a second machine to try it on atm. Cheers. LRD NO (talk) 16:06, 15 June 2014 (UTC)

• That suggests to me that it has something to do with your account. I moved this conversation to the Twinkle talk page here as there may be someone who knows what the problem is or where to look now because they've encountered the problem before instead of waiting for me to figure it out. — {{U|Technical 13}} ^{(e • t • c)} 16:21, 15 June 2014 (UTC)

Running Chrome (latest) and haven't spotted the issue. Shift+Reload always clears issues for me. --Ankit Maity ^{«T § C»}_{«Review Me»} 18:12, 15 June 2014 (UTC)

@LRD NO: Which browser versions are you using? Try pressing F12, switching to the "Console" tab, typing "Twinkle" and pressing Enter. — This, that and the other (talk) 01:42, 16 June 2014 (UTC)

• TTO, he said he normally use Chrome but it happens in IE as well. Since they use separate caches and cookies, I'm thinking it is some other preference he is using (maybe a beta feature?) that is causing his issue. — {{U|Technical 13}} ^{(e • t • c)} 02:11, 16 June 2014 (UTC)

@TTO I'm using Chrome. I just tried F12 as you said and nothing happens. And what is this 'console' tab you speak of? Sorry if I'm not the most technically inclined.

@T13 Thanks for your help so far. Cheers. LRD NO (talk)

In Chrome, try pressing the key combination Ctrl+Shift+J, which should display the same window, with "Console" tabs etc across the top. If "Console" isn't already selected, click on it. Then type "Twinkle" and press Enter. This will tell me at least if Twinkle is available or not.

If that shows an error, try copying and pasting the following code into the console: mw.loader.load("ext.gadget.Twinkle");, press Enter, and then try typing "Twinkle" and pressing Enter.

It would still be helpful to know which versions of Chrome and IE you are using; this will tell you if you don't know. — This, that and the other (talk) 06:58, 16 June 2014 (UTC)

These are the results returned.

Twinkle Object {userAuthorized: true, initCallbacks: Array[0], addInitCallback: function, defaultConfig: Object, getPref: function…} mw.loader.load("ext.gadget.Twinkle") undefined Twinkle Object {userAuthorized: true, initCallbacks: Array[0], addInitCallback: function, defaultConfig: Object, getPref: function…}

Browsers used are Chrome35 and IE9. LRD NO (talk) 08:35, 16 June 2014 (UTC)

From that it is clear that Twinkle is loading correctly for you; I assume that you are still not seeing it in the interface. Try having a look at the Main Page in the Monobook skin and see if you get the appropriate "csd", "xfd", etc tabs along the top. — This, that and the other (talk) 11:25, 16 June 2014 (UTC)

The TW tab at the top of every page, I have it all along. But the [rollback], [vandalism], [undo] options etc on my watchlist are no longer there. LRD NO (talk) 11:38, 16 June 2014 (UTC)

@LRD NO: If you /had/ some Twinkle functionality all along, why did you say it "failed to load"? It obviously didn't, you were merely missing some specific links.
There aren't supposed to be any Twinkle links on your watchlist, only on diff pages and when viewing other people's contributions, so everything seems to be working as intended.
Amalthea 12:00, 16 June 2014 (UTC)

As mentioned, there were the various [rollback], [vandalism], [undo] options in the various colours on my watchlist (definitely) or edit history pages (iirc). Those disappeared ("failed to load") around the time everyone had problems with TW. I have a genuine technical issue here and have never intended to mislead anyone. Cheers. LRD NO (talk) 12:06, 16 June 2014 (UTC)

A sample of what my watchlist looks currently. There were various options to undo, rollback etc at the end of the edit summary, where you could perform, say an undo and add in the edit summary in a pop-up window. My apologies if I had wasted any of the good people's time here. LRD NO (talk) 12:19, 16 June 2014 (UTC)

As Amalthea said, the [rollback], [vandalism], [undo] only appear on contributions pages and diffs. They never appear on the watchlist or on history pages. There has simply never been any code in Twinkle that can do that (although that doesn't mean such functionality might be added in the future, in some form or another). — This, that and the other (talk) 12:33, 16 June 2014 (UTC)

They did for me in all honesty and I found it a helpful function. But since everyone says to the contrary, I'll leave it at that. @T13, TTO - Thanks for the patience and help anyway. LRD NO (talk) 12:39, 16 June 2014 (UTC)

Don't notify self on XfD

The "Notify page creator if possible" should be inactive (or not work) if the creator happens to be the tagger. This can happen with redirects caused by page moves, and with categories which had been renamed . עוד מישהו Od Mishehu 19:58, 18 June 2014 (UTC)

• I'd be okay with not checked by default, but I like to see when it actually gets deleted (by the link turning red) when I nominate my own stuff for deletion (for cases when there has been sufficient other editor interaction and CSD is inappropriate). — {{U|Technical 13}} ^{(e • t • c)} 20:26, 18 June 2014 (UTC)

Multiple SPI cases for same sockmaster

Currently, when Twinkle is used to report suspected sockpuppets to SPI, any additional suspected socks reported for the same open case will generate a new case, e.g. this case. I know that, with the right changes to the code, additional reports could just be added to the open case. My question is, is this reasonably feasible? We only see this problem a few times a year, so the cost may outweigh the benefit. Thanks ​—DoRD (talk)​ 13:27, 19 June 2014 (UTC)

Hiding or shortening tabs

Basically, I don't have enough room on my screen for all of the tabs I want (Twinkle and an AfD script). Is there away to a.) hide tabs, b.) shorten existing tabs (e.g. 'delete to 'd') or c.) force all tabs to be displayed? -- John Reaves 15:42, 21 June 2014 (UTC)

Well, you could move into the modern era and switch to the Vector skin :) There is a way to hide individual tabs for those people who insist on using bad old Monobook, though; see Wikipedia:Twinkle/doc#Hiding individual Twinkle tabs. Changing the tab names is a bit more involved; there is a user script User:Ioeth/friendlytabs.js which can do this, although it seems to lack instructions or documentation. To see all tabs at once, you could try pressing Ctrl+hyphen to zoom out, although this is clearly not a long-term solution. — This, that and the other (talk) 10:58, 22 June 2014 (UTC)

@John Reaves: I'm using some CSS to cram the tabs closer together:

/* more room for tabs */
div#p-cactions { width: auto; }
#p-cactions li { margin-right:-1px; }
#p-cactions li#ca-talk { margin-right:1.6em; }

Amalthea 09:24, 23 June 2014 (UTC) Tweaked 14:34, 23 June 2014 (UTC)

@Amalthea: That "catactions" probably isn't doing quite what you intended... — This, that and the other (talk) 11:16, 23 June 2014 (UTC)

Heh, my secret cat actions navbar … removed it, thanks, apparently having no effect is exactly what was intended … ;) Amalthea 14:34, 23 June 2014 (UTC)

@Amalthea and This, that and the other: Wow, I didn't know that the vector skin existed, it makes Twinkle and other scripts much more manageable. Now let's see if I can get used to it. I'll try the CSS if I switch back. Thanks for the help. -- John Reaves 14:18, 23 June 2014 (UTC)

Bug?

Resolved

Twinkle stopped working for me at 02:26 Pacific on 23 June 2014. The pull down menu deploys but nothing happens when I hit any button (except that it adds a # at the end of the URL). Initially I thought this was because I installed the Hedonil X tools but I removed it and Twinkle still doesn't work. I'm using Chrome 35.0.1916.153 m and I already checked the console to be sure everything's in order. I've been waiting to see if anyone else noticed the issue on GitHub but I see other users not having a problem so maybe it's just me. Chris Troutman (talk) 12:29, 23 June 2014 (UTC)

Try bypassing your cache, or if that has no effect, clearing your cache entirely. See WP:BYPASS for instructions on these two procedures. — This, that and the other (talk) 03:08, 24 June 2014 (UTC)

Yup, that did it. Thanks. Chris Troutman (talk) 03:54, 24 June 2014 (UTC)

Add stub templates?

Would it be a good idea to add stub-sorting features to Twinkle? For example, in addition to adding maintenance tag, can it be added so that Twinkle can also add stub-templates to articles? Narutolovehinata5 ^tccsdnew 05:21, 24 June 2014 (UTC)

See https://github.com/azatoth/twinkle/issues/222 for some related discussion. — This, that and the other (talk) 08:12, 24 June 2014 (UTC)

Change to Template:Rfd

Please see WT:RFD#Change to how the Rfd template works. Short version is, barring objections, instead of using positional parameter 1 of {{rfd}}, use the name parameter instead, and stuff the rest of the page into the first positionalcontent parameter. Jackmcbarn (talk) 23:02, 20 June 2014 (UTC)

The change is finalized here, and I've submitted a pull request at [2]. (This isn't urgent, because the new code is backward-compatible with the old method.) Jackmcbarn (talk) 22:15, 23 June 2014 (UTC)

Jackmcbarn, something was borked.

Old way's first line: {{Rfd/core| (see [3])

New way: {{ {{{|safesubst:}}}#invoke:RfD|<includeonly>1</includeonly> (see [4])

Bgwhite (talk) 06:05, 25 June 2014 (UTC)

@Bgwhite: I'm a little mystified at this comment. Did you mean to link to a different page in your second link? — This, that and the other (talk) 10:29, 25 June 2014 (UTC)

That change is intentional and correct. I'm not sure what you're saying the problem is. Jackmcbarn (talk) 15:32, 25 June 2014 (UTC)

Jackmcbarn, I'm always in state of confusion and it looks like I've added to yours. Yes, I meant a different second links. Here's the link. Problem being... Why is {{{|safesubst:}}} in there? Should it just be safesubst:, with out the curly brackets? Why the includeonly?. I'm not sure what is going on? — Preceding unsigned comment added by Bgwhite (talk • contribs) 17:45, 25 June 2014‎ (UTC)

It's supposed to have both of those. The Lua module is doing black magic to make transclusions of the "redirect" work properly, even though it isn't technically a redirect anymore. Jackmcbarn (talk) 18:22, 25 June 2014 (UTC)

@Redrose64: Jackmcbarn, You didn't answer my questions. Again, why is {{{|safesubst:}}} in there? Should it just be safesubst? There is nothing, anywhere, that adds template variables inside an article. There is nothing, anywhere that has template programming in articles. Why is the article being treated as a template and not an article? Bgwhite (talk) 20:25, 25 June 2014 (UTC)

It should not just be safesubst, because without the wrapper, it would get substed on the page it was placed on. That's not actually a template variable; it will never be anything but safesubst. Re getting treated like a template, the same code is used for template redirects and article redirects, and it needs to be the way it is for template redirects to work. Jackmcbarn (talk) 20:28, 25 June 2014 (UTC)

@Bgwhite: Which questions was I asked that I did not answer? --Redrose64 (talk) 20:30, 25 June 2014 (UTC)

Redrose64, I pinged you because maybe you can understand what I'm trying to say. It looks like Jackmcbarn and I are not understanding each other. You are more used to my stupidese.

Currently, there are no articles with template variables or things wrapped in {{{ }}}. None at all. No where is {{{|safesubst:}}} used in an article. It appears as if the code for {{rfd}} is being copied into the article and not transcluded (hope I'm saying that right).

The code for {{rfd}} is {{ {{{|safesubst:}}}#invoke:RfD|main}}

The article has {{ {{{|safesubst:}}}#invoke:RfD|<noinclude>1</noinclude>

Why does the article have almost the exact same code as the template? Why isn't {{subst:rfd}} being used in the article instead? If the same code is being used for template and article redirects, why doesn't "the code" show up in the article like it is doing for RFD? Bgwhite (talk) 20:55, 25 June 2014 (UTC)

It's not almost the exact same, even though it looks that way. The first positional parameter of a #invoke is the function, which is different, so totally different code runs. Also, I can't figure out what you're saying is wrong. What isn't working the way you want it to? Jackmcbarn (talk) 20:58, 25 June 2014 (UTC)

Someone tweaked the Batch deletion and made a bug?

The batch deletion now displays incorrect page names as it deletes - it is using the last on in the list for all of them (the correct page does get deleted) - see File:TWbatch.jpg It worked fine last week!  Ronhjones  ^(Talk) 19:17, 26 June 2014 (UTC)

Yes, I have been tweaking batch delete and undelete. You will notice it no longer has to fetch the delete token every time, which is supposed to make the process faster. However, it seems that, in doing this, I caused a subtle bug that has always been present in Twinkle to come to the fore. The bug has never had a visible impact (except on the stress levels of Twinkle coders), but now that it is showing up to users, I suppose it is time to fix it properly. I'll work on it. — This, that and the other (talk) 01:24, 27 June 2014 (UTC)

Huh, I managed to come up with a quick, hacky fix for now. The resolution of the underlying issues will take a lot longer. — This, that and the other (talk) 04:53, 27 June 2014 (UTC)

Worked OK tonight. Ronhjones  ^(Talk) 00:03, 1 July 2014 (UTC)

AfD Twinkle glitch?

Today I started an AfD at Wikipedia:Articles for deletion/List of notable Bahranis using Twinkle; a while later I saw that Cyberbot I had completed this AfD because it had not correctly transcluded to the log. [5] Twinkle has always successfully completed the AfD process in the past for me; I may have done something wrong this time but I'm not sufficiently adept to figure that out. I note another glitchy AfD today, also evidently created by Twinkle. [6]. --Arxiloxos (talk) 18:14, 6 July 2014 (UTC)

The first issue occurred because someone else apparently edit-conflicted with you, but did not resolve the edit conflict properly (or perhaps the software had a glitch and didn't offer that user a chance to resolve the edit conflict). See the following edit.

The reason the second one was glitchy was because the user mistyped a wikilink, opening it with [[ but closing it with ]. This broke the template syntax. — This, that and the other (talk) 01:13, 7 July 2014 (UTC)

Thanks very much for figuring it out. --Arxiloxos (talk) 04:39, 7 July 2014 (UTC)

Deletion tag log

When I use Twinkle to tag an article for speedy deletion, the article is not included in the Deletion tag log. Why? When I use the page curation tool to tag an article for deletion, it is included in the Deletion tag log. I know that Twinkle has an option to make deletion log in the userspace. But, I want all my deletion logs to be in one place, because I sometimes use page curation, and sometimes Twinkle. I don't want to have to look for deletion logs in two separate places. Vanjagenije (talk) 21:27, 10 July 2014 (UTC)

The deletion tag log is part of Special:Log, which is a standard feature of the MediaWiki installation. Page curation is also part of the MediaWiki software, so it is able to write to the MediaWiki log files. However, Twinkle is essentially a user-written gadget: it can write to regular pages, but cannot write to the MediaWiki log files, so it uses a regular page to record its actions. --Redrose64 (talk) 23:33, 10 July 2014 (UTC)

Automate notification

Wikipedia:Possibly unfree files for many years has required that the nomination process include the step of adding a tag to the image caption on any articles the image is on. This is to attract more attention to the deletion debate to see what should be done. Unless there's an objection, nominated files are deleted after 7 days. Could twinkle please take care of performing this step?--{{U|Elvey}} ^(t•c) 22:54, 10 July 2014 (UTC)

This is patently wrong. There was an RFC, and the outcome was to remove this requirement. I understand that you don't agree, but if you continue this disruptive behavior, you will be blocked. Final warning. TLSuda (talk) 02:05, 11 July 2014 (UTC)

R from alternative language

Please include a popup entry box requesting the language code when I insert the {{R from alternative language}} tag on a redirect, just like when I add an {{Expand language}} tag on an article. Thanks. TheChampionMan1234 04:01, 16 July 2014 (UTC)

Option to turn off automatic capitalization of edit summaries

I think the headline says it all. Is there (or could there be) an option to disable automatic capitalization of edit summaries? Sometimes I don't want my edit summary capitalized, for example "rvv" and the like. I see in the archives that this was mentioned once a long time ago, but it seems nobody replied to the request. Cheers. Ivanvector (talk) 18:17, 16 July 2014 (UTC)

Would you be happy with a preference at WP:TWPREFS? — This, that and the other (talk) 08:19, 17 July 2014 (UTC)

Redirected talk pages and warnings

Recently ran into an editor who by repeatedly revert warring a redirect onto their talk page managed to cause multiple twinkle warnings to end up the wrong person's talk page. Would it be possible to have twinkle either ignore the user talk page redirect when leaving a warning, or at least ask the user issuing the warning what to do? Monty₈₄₅ 00:29, 20 July 2014 (UTC)

Twinkle follows talk page redirects by default, as in most cases they relate to renamed users or alternate accounts. In almost all cases this "silent" behaviour is appropriate. Obviously it wasn't appropriate here, but that was due to the disruptive actions of a single editor. AFAICS you were aware of the redirect before invoking Twinkle, so it would have made sense to remove the redirect before attempting to issue warnings to that user. However, it is possible that this may not always be the case (e.g. when issuing a Speedy Deletion warning). If this pattern of disruption becomes more common we may have to reconsider our approach here. — This, that and the other (talk) 07:13, 20 July 2014 (UTC)

For the template "Template:Confusing"

For the template "Template:confusing" I suggest another template with the words "The phrasing in this article may be unclear. Please reword the unclear phrasing into phrasing that everyone can understand."

Qwertyxp2000 (talk) 04:57, 21 July 2014 (UTC)

The template provides a parameter for a more detailed explanation: {{Confusing|reason=The phrasing in this article may be unclear. Please reword the unclear phrasing into phrasing that everyone can understand}}. Mlpearc (open channel) 05:04, 21 July 2014 (UTC)

Template deletion nominations

I noticed a somewhat inconvenient feature is that when templates of a single category are nominated for deletion using Twinkle, each template is individually nominated. When hundreds of templates are being nominated for the same reason, this becomes overwhelming and confusing. The templates for discussion page instead asks that such templates be grouped together to facilitate discussion. It might be worth looking into adding the ability to add templates to an existing discussion, rather than nominate them individually. Please excuse my ignorance if this feature is already included; I am merely passing along my observation of a user using Twinkle, perhaps incorrectly, to individually nominate dozens of templates for a common reason. --Zfish118 (talk) 00:29, 23 July 2014 (UTC)

Twinkle does not include the feature you speak of; the way Twinkle is designed makes this somewhat cumbersome. See also Wikipedia_talk:Twinkle/Archive_34#Nominating_multiple_categories_for_renaming.3F, where a user asks for a similar suggestion (but for nominating multiple categories for renaming). Basically, the suggestion is the start the deletion nomination with Twinkle, and complete it manually. — This, that and the other (talk) 09:27, 24 July 2014 (UTC)

Tagging a protected page gives out a notification to creator even if the page wasn't tagged

See header. This shouldn't happen. Special:Diff/618695588 while I was testing something else. --Glaisher (talk) 17:20, 27 July 2014 (UTC)

You're not wrong; this shouldn't happen. Creator notification ought to be dependent on success of the PROD tagging itself. I'll look into it. — This, that and the other (talk) 07:32, 28 July 2014 (UTC)

Template deletion nominations - GLAM ZOO Miskolc

Help me please, this project page my hungarian GLAM ZOO project page in english. GLAM ZOO Módis Ágnes Vadszederke (talk) 15:47, 28 July 2014 (UTC)

Hi Módis Ágnes Vadszederke, if you would like a translation of this page to English, I'm afraid we can't help you, as there is no-one involved in the Twinkle project who speaks Hungarian. I would suggest that you speak to someone at Wikimédia Magyarország. — This, that and the other (talk) 10:55, 29 July 2014 (UTC)

how use

i trick use twincle my setting . but no use. how i revert any change to give summery its vanalidse--Amt000 (talk) 04:04, 1 August 2014 (UTC)

I'm sorry but unfortunately I don't fully understand your question because your English is not really comprehensible. But since you mentioned reverting and Twinkle you might want to read this manual. De728631 (talk) 17:12, 1 August 2014 (UTC)

Template deleted

On the Tag popup for articles each line has a > link. The link goes to the deleted Template:On. —teb728 t c 01:29, 7 August 2014 (UTC)

Hm, interesting. It works correctly for me. So you're saying that all ">" links take you to this mysterious {{on}}? Which browser are you using? — This, that and the other (talk) 08:46, 7 August 2014 (UTC)

IE 10 —teb728 t c 09:10, 7 August 2014 (UTC)

Where is it supposed to go? Is it possible someone has changed the source? —teb728 t c 09:19, 7 August 2014 (UTC)

It's supposed to take you to the template description page of each relevant template (e.g. the ">" next to {{copy edit}}} is meant to go to Template:Copy edit). There's a slight change to the code that needs to be made to get it to work in Internet Explorer 9 and 10. (Note that it works correctly as is in Internet Explorer 11; if you can, you should consider upgrading your browser.) — This, that and the other (talk) 09:59, 7 August 2014 (UTC)

Open a DR?

Can I open a deletion review / request for undeletion with Twinkle? Is there a configuration setting needed? I vaguely recall that it had this functionality. If not, consider this a request. (An admin deleted a file that was verifiably released under a free license, asserting it was a copyvio just because they happened to find it somewhere else on the 'net w/o a license specified.) --{{U|Elvey}} ^(t•c) 16:01, 7 August 2014 (UTC)

CSD: Planning changes to Template:Db-u1 and g7

I really feel like those templates be changed.

Like every other speedy deletion template I see, u1 and g7 is when the author or user requests deletion to his/her page. But there is one abnormality, they do not have to be such a legal or if I can say it phrase. I want the presentation of the templates to be softer. That is, they do not use 'speedy deletion' in a hard and fast style. I have a live preview here. That is how I want them to look like, both templates should be nice to everyone, not organised in a way that only administrators can really get the personality of those strict templates. Thanks! DSCrowned (talk) 10:59, 28 July 2014 (UTC)

Full discussion here. — Preceding unsigned comment added by DSCrowned (talk • contribs) 12:30, 28 July 2014 (UTC)

• Please note that Twinkle is normally only updated for things like this once consensus is reached for the new usage outside of Twinkle; the discussion you started is the best way to reach that, but nothing will be done to Twinkle until and unless consensus is reached there for the changes. ☺ · Salvidrim! · ✉ 16:38, 29 July 2014 (UTC)

Note that this change, even if it were implemented, would not require any changes to be made to Twinkle. Jackmcbarn (talk) 00:31, 2 August 2014 (UTC)

Note, however, that this template is prominently tagged, If you plan to make major changes to this template, move it, or nominate it for deletion, please notify Twinkle's users/maintainers at Wikipedia talk:Twinkle [i.e. this page -ed.] as a courtesy, as this template is used by the standard installation of Twinkle. Thank you!.--{{U|Elvey}} ^(t•c) 16:16, 7 August 2014 (UTC)

Afd log

Forgive me if this has already been suggested but since you have the option of creating a CSD log and a PROD log, shouldn't there be an option to create your afd log as well? Though it may not fair too well in a request for adminship request, I do want to keep one for logging reasons. Tutelary (talk) 16:05, 7 August 2014 (UTC)

The difference is that non-admins cannot review their past successful CSD or PROD logs because the only edit is to the page that gets deleted. AfD means you edit both the nomination page AND the AfD log, which remains visible and traceable through a user's "live" contributions even for non-admins. ☺ · Salvidrim! · ✉ 18:13, 7 August 2014 (UTC)

You may also find your personalized AfD Statistics interesting. Does more than a Twinkle log could hope for. Monty₈₄₅ 18:45, 7 August 2014 (UTC)

Thank you! I'll be using that instead. I didn't know this was already here. Thanks again! Tutelary (talk) 18:43, 9 August 2014 (UTC)

Draft space

Twinkle is currently not letting speedy deletion tags be put on article in Draft Space. (However, is however letting XfD tags be placed.) I think this is a bug from the last rewrite.. DGG ( talk ) 21:42, 12 August 2014 (UTC)

Works for me. I can apply all the "G" criteria to draft space... What exact problem are you facing? In what way is Twinkle not "letting" you do it? — This, that and the other (talk) 10:08, 14 August 2014 (UTC)

UAA Reporting not working

Tried to report 5 accounts to WP:UAA using Twinkle and they did not show up on the page. Not sure where to report. EvergreenFir (talk) Please {{re}} 18:29, 26 August 2014 (UTC)

OK, good to know it's not just me. I also had multiple failures trying to report an account today as well. --Drm310 (talk) 18:46, 26 August 2014 (UTC)

See if this edit has fixed it. I suspect that Twinkle is looking for this exact comment. -- John of Reading (talk) 19:53, 26 August 2014 (UTC)

That appears to have done the trick. Thanks John! --Drm310 (talk) 20:21, 26 August 2014 (UTC)

Awesome! Thank you! EvergreenFir (talk) Please {{re}} 20:29, 26 August 2014 (UTC)

Another block template

Quite often we block IP addresses because they're being used to evade a block or ban; however we don't block them indefinitely for obvious reasons. On the Twinkle block dropdown there is {{uw-spoablock}} but that's an indefinite sock block. We already have a template for temporary blocking of IP addresses being used to evade and that's {{Uw-ipevadeblock}} - any chance of adding it below the first one? Cheers, Black Kite (talk) 12:43, 22 August 2014 (UTC)

Would it work if you added it as a custom template? Is there a way to pass parameters to custom templates? ☺ · Salvidrim! · ✉ 20:48, 26 August 2014 (UTC)

Added this template in the repository. It'll appear on wiki soon. — This, that and the other (talk) 08:30, 27 August 2014 (UTC)

Make thanks for contributions optional

Most of the Welcome templates start with "thanks for your contributions". There are situations, though, where that just sounds wrong (like obvious tests/vandalism), yet you would otherwise want to use one of those templates because of the educational links it provides. How about replacing that language with something like "thanks for your interest in Wikipedia"? Alternatively, have a checkbox to make the line optional? —[AlanM1(talk)]— 12:50, 29 August 2014 (UTC)

That would require a change to the text of the welcome template(s) involved, not to Twinkle. ☺ · Salvidrim! · ✉ 14:00, 29 August 2014 (UTC)

I was looking for some input, really, on what others think about it. The last option (adding a checkbox to make it optional) would require change to both Twinkle and the templates. —[AlanM1(talk)]— 12:14, 30 August 2014 (UTC)

FYI: Template:Cleanup-bare URLs nominated for deletion

The talk page of Template:Cleanup-bare URLs says that the Twinkle maintainers and users would appreciate knowing if anyone proposes changing or deleting that template. Jodosma (talk) recently proposed deleting it, so you might want to stop by the discussion. — Control.valve (talk) 20:40, 28 August 2014 (UTC)

Crisis averted. SNOW kept. —[AlanM1(talk)]— 12:23, 30 August 2014 (UTC)

Hierarchical tags

Some tags are mutually exclusive; one being a stronger version of another,. For example, if I use twinkle to add {{Ref improve}}, it would be nice if it removed at the same time any existing {{Unreferenced}} tag, or vice versa - or at least warned me and asked whether to do so. Ids such functionality panned, or can it be added, please? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:10, 12 August 2014 (UTC)

Such functionality ids not panned. (Sorry, I couldn't resist that...) In all seriously, though, this would be nice to have. How many groups of mutually exclusive tags are present on the list? Clearly the ones you mentioned; probably some BLP pairs, over/underlinked, etc? — This, that and the other (talk) 10:06, 14 August 2014 (UTC)

Some suggestions:

• {{uncategorized}} and {{improve categories}} are incompatible
• {{stub}} shouldn't be added, or present, if any {{foo-stub}} is present
• {{refimprove}} should be changed to {{BLP sources}} if Category:Living people is present
• {{unreferenced}} should be changed to {{BLP unsourced}} if Category:Living people is present

PamD 17:20, 14 August 2014 (UTC)

Actually, I almost tagged an article with both over- and under-linked today – correctly. You can have repetitive linking of some terms while still having a lack of linking of others, particularly in different sections. —[AlanM1(talk)]— 12:30, 30 August 2014 (UTC)

Dup checking on tags

I went to tag an article that already had a multiple issues template which included the {{refimprove}} template as one of its params. In the dialog, I selected {{ref improve}} (note space) as one of several choices. The result was that it added {{ref improve}} instead of replacing the existing {{refimprove}}. I don't know if it checks for dups at all, but if it does, it doesn't handle the case where the existing one is a different name for the same template (i.e. either the old or new one is a redirect). It would be nice if it handled this.

BTW, looks like Twinkle is the one using the redirect name – the template is at {{Refimprove}}. —[AlanM1(talk)]— 12:40, 30 August 2014 (UTC)

I've been meaning to file a requested move for that template for some time. — This, that and the other (talk) 02:46, 31 August 2014 (UTC)

G10 logging revisited

Today I nominated a page for speedy deletion G10 with Twinkle. While the talk page notification for the creator removes all mention of the article name, I noticed that the edit summary and content of my CSD log contained the page name. At first I thought this was an oversight, but on searching the archives here it turns out that this issue was brought up on this page two years ago, by none other than yours truly. I still think that we should be redacting the page name from CSD logs for G10s, as they can sometimes be very nasty, and the logs show up in Google searches. Is there any chance that this could be implemented? — Mr. Stradivarius ^{♪ talk ♪} 07:50, 27 August 2014 (UTC)

At the very least, CSD/PROD logs should be NOINDEX'ed. ☺ · Salvidrim! · ✉ 21:13, 28 August 2014 (UTC)

For those of us that aren't admins, though, it can be useful to have this information, since we have no other easy way to get it. How about a checkbox (whose default is "sticky") on the criteria selection dialog, which controls whether it is masked? I'd like to see masking done by changing every other character to "*", too, so you can still figure out what it was, yet still achieve any necessary hiding of offensive material. —[AlanM1(talk)]— 12:21, 30 August 2014 (UTC)

If the page name were to be hidden from the CSD log, it would be behind a piped link (e.g. [[XYZ is a tool|''attack page'']]). It does not make sense to remove the article name from the log altogether, as this defeats the purpose of the CSD log.

Personally I favour the option of making CSD logs noindexed. I'll take a look at this. — This, that and the other (talk) 02:50, 31 August 2014 (UTC)

Make preview and optional comments universal

A number of Twinkle features do not have a Preview function (like ARV), but need to. It's annoying to look like I was lazy in not using preview when making a mistake in a posting to an admin page.

Also, there are situations where I'd like to use the Welcome templates instead of the warnings, but I can't because there is no support for an ad-hoc comment (like there is in the warnings). The ability to add such a comment should be available everywhere possible. —[AlanM1(talk)]— 12:46, 29 August 2014 (UTC)

This has been on my mental to-do list for some time. Currently, Warn and Welcome have a preview feature. Some (like CSD and PROD) don't really need it. Others, like XFD and ARV, should have it. — This, that and the other (talk) 02:47, 31 August 2014 (UTC)

If support is added for optional comments to CSD (one of the places I've needed it occasionally), a preview function would also be necessary. —[AlanM1(talk)]— 20:33, 31 August 2014 (UTC)

Inline TFD tagging

When adding an inline TFD tag to a template, Twinkle should not insert a newline between the tag and the template code. When it does, like here, you get this, where the "quick brown fox" placeholder should be on the same line as the bullet but isn't (in other words, the line break inserted by Twinkle breaks the bullet). As that is the only page affected, I've intentionally left it unfixed for demonstration purposes. jcgoble3 (talk) 05:21, 12 August 2014 (UTC)

Thanks, Jonathan. A fix for this is forthcoming. — This, that and the other (talk) 12:11, 1 September 2014 (UTC)

Tagging as stub?

I'd be surprised if no-one's thought of this before, but why isn't there a module for tagging as stubs? Eman235/talk 06:04, 5 September 2014 (UTC)

Widen input textboxes

The textboxes that are used for explanation when adding templates like {{uw-username}}, linked article name, etc. are unnecessarily short. It would be nice if they were at least as long as there is room for in the dialog (385px instead of the existing 178px on my system). —[AlanM1(talk)]— 11:12, 6 September 2014 (UTC)

Make Warn and Wel available from user contributions page

On the Special:Contributions/username page, the Twinkle menu only has ARV and TB. It would be nice if it had the Warn and Wel options as well. I routinely have to take the extra step of navigating to the talk page to send a welcome or warning. —[AlanM1(talk)]— 13:22, 4 September 2014 (UTC)

How do you know they haven't already received a welcome or warning without looking at their talk page? That's the reason why those features aren't available from Special:Contributions. — This, that and the other (talk) 01:24, 6 September 2014 (UTC)

Because I'm working with a list that looks like: username (talk | contribs) where the redlinks indicate the page has not yet been created and I have moused over a talk page link that shows me the page is empty. —[AlanM1(talk)]— 11:16, 6 September 2014 (UTC)

Where do I make a complaint of an editor using twinkle inappropriately to violate BLP?

Should I open up a case for arbitration? Afronig (talk) 03:33, 8 September 2014 (UTC)

Speedy-deletion tags for possibly transclued pages

I think that we need for:

1. An option, in the CSD window, for wrapping the tag with <nowiki> tags;
2. This option to be checked by default for pages in the template namespace, and for subpages of Wikipedia:Articles for deletion and Wikipedia:Miscellany for deletion.

עוד מישהו Od Mishehu 09:05, 7 September 2014 (UTC)

You do mean <noinclude>? I suppose this could be useful. Certainly, such a checkbox should only appear for pages where it is relevant (i.e. templates). Are AFD and MFD subpages really CSD'd that often? — This, that and the other (talk) 12:44, 7 September 2014 (UTC)

Portal sub-pages are another case where this would be useful. -- John of Reading (talk) 06:44, 8 September 2014 (UTC)

Linkrot

Twinkle adds {{Linkrot}}, but Yobot then updates this to "Cleanup-bare URLs" (approx - editing on mobile so can't easily check exact template name). Could Twinkle please be updated to use the current template name? Thanks. PamD 06:17, 8 September 2014 (UTC) PamD 06:17, 8 September 2014 (UTC)

Technically, {{Linkrot}} is just a redirect to {{Cleanup-bare URLs}} but if it triggers any unnecessary bot action I guess we shouldn't use it any more. De728631 (talk) 06:30, 8 September 2014 (UTC)

I recall seeing pretty much the exact same discussion here/at TfD/at RfD several times just this year already. ☺ · Salvidrim! · ✉ 06:35, 8 September 2014 (UTC)

If I had the time I would try and shepherd through a requested move for this template. "Cleanup-bare URLs" is a truly terrible name for this template, for reasons I've explained in the past. Ask yourself: what is a "cleanup-bare" URL? — This, that and the other (talk) 09:30, 8 September 2014 (UTC)

How about "Cleanup — bare URLs"? BIIG difference. XD Eman235/talk 22:44, 8 September 2014 (UTC)

All the other cleanup templates seem to start with "Cleanup-", so "Cleanup-bare-URLs" might be an idea - not ideal, but consistent and less confusing than the current version. PamD 14:56, 9 September 2014 (UTC)

Yeah, but then you have bare-urls, which doesn't really make sense either. Eman235/talk 00:50, 10 September 2014 (UTC)

Why does the name of this template even need to begin with the word "cleanup"? Most of our article maintenance tags relate to cleanup of some kind, yet they don't state it in the name... — This, that and the other (talk) 10:36, 11 September 2014 (UTC)

Speedy deletion templates changing

Hello Twinkle users,
As I mentioned at Wikipedia talk:Criteria for speedy deletion#Proposal: Separate templates for A3 subcriteria, I am going to create seperate CSD and CSD-Warn templates for different subcriteria of A3, similar to what is already the case for A7. The issue with Twinkle is that it currently tags pages for deletion with {{db-nocontent}} and notifies the author with {{db-nocontent-notice}}. Once my userspace drafts get moved into templatespace, {{db-nocontent}} (which currently redirects to {{db-a3}}) will be overwritten with a new template, and the current template {{db-nocontent-notice}} will be moved on top of its redirect at {{db-a3-notice}}. Please reconfigure Twinkle to add {{db-a3}} to pages and notify the author with {{db-a3-notice}} so that Twinkle does not apply the wrong templates once the new ones have been rolled out. I will inform you once the new templates are finished so that you can (please?) add them.
Sorry for the disruption, Passengerpigeon (talk) 13:20, 11 September 2014 (UTC)

Just letting you know that I've seen this and will do preliminary work on it tomorrow. As you say, please contact us when the new templates are put into place. — This, that and the other (talk) 12:43, 12 September 2014 (UTC)

{{Manual}}

Hi.

I've noticed Twinkle doesn't currently support inserting {{Manual}} into the article. Can this be added? I think its place is under "Style of writing" category.

Best regards,
Codename Lisa (talk) 15:43, 10 September 2014 (UTC)

Submitted a pull request. https://github.com/azatoth/twinkle/pull/242 --Glaisher (talk) 16:02, 13 September 2014 (UTC)

New feature requested - AIV reports

In the cases where a user wants to make an AIV report but has not reverted the edit to be reported (someone else has) is it possible to enter a diff into the report dialog box instead of entering the page name and hunting for revision ID's? --NeilN ^{talk to me} 15:23, 13 September 2014 (UTC)

+1! It would be so much easier to just copy/paste one link than the current select/copy/paste three times (article name, old id, new id). —[AlanM1(talk)]— 07:04, 17 September 2014 (UTC)

New feature requested

Can we get previews on all of the templates? For example all of the drop-downs under ARV lack preview functionality. And though I've said it before, thank you for all your hard work on Twinkle. It's awesome! Cyphoidbomb (talk) 02:31, 20 September 2014 (UTC)

+1. FYI: #Make preview and optional comments universal —[AlanM1(talk)]— 18:52, 20 September 2014 (UTC)

Invite back message

Just a quick note before I forget, I thought it might be nice to have a standard "invite back" message that can quickly be left on the talk pages of users who used to edit but seem to have left the project. Might be a nice way to promote editor retention. Jason Quinn (talk) 21:34, 20 September 2014 (UTC)

Seconding PROD

Can we get a {{Prod-2}} option when there's a prod on an article? Eman235/talk 05:03, 29 September 2014 (UTC)

Just use the PROD module normally, and upon trying to save, it will detect the existing prod and pop up an alert asking if you want to add Prod-2. jcgoble3 (talk) 05:58, 29 September 2014 (UTC)

O-oh. OK, I thought that might work, but I didn't want to try just in case...thanks Eman235/talk 06:20, 29 September 2014 (UTC)

Reflinks rewrite

Just as a note that I've added my Reflinks rewrite to {{Cleanup-bare URLs}}. This does not affect the inner workings of the template. Zhaofeng Li [talk... contribs...] 09:36, 30 September 2014 (UTC)

drop down or tickboxes for afd

when you nominate a page for deletion, there should be tickboxes or a drop down.

for articles, you should be given the option to select one of Category:Wikipedia notability guidelines and other related pages.

so if you nominated White Christmas (song), you would tick the music box which would produce

White Christmas (song) (edit | talk | history | protect | delete | links | watch | logs | views) – (View log · Christmas (song) Stats)

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Does not meet our notability guidelines for music.--Otterathome (talk) 18:33, 4 October 2014 (UTC)

About the recent "Adıyaman Province" edit

I don't see the third reference can someone share it, please? ( My reference is legitimate i put here too: http://ir.ide.go.jp/dspace/bitstream/2344/110/3/ARRIDE_DE_Vol41(3)_2003.03.04_hazama_erratum.pdf )

I believe the IP is confused. This is not the place to discuss Adıyaman Province. Please try Talk:Adıyaman Province. Cyphoidbomb (talk) 17:01, 5 October 2014 (UTC)

FYI

I've made a proposal to change the format of RfPP (WT:RFPP#Proposal to change the format of RfPP). This is a courtesy notification because obviously it will affect Twinkle functionality if my proposal is successful. I'd be grateful if Twinkle developers could advise whether it would be practical to modify Twinkle to cope with the proposed new format. Thanks, HJ Mitchell | Penny for your thoughts? 14:43, 6 October 2014 (UTC)

@HJ Mitchell: Yes, this should be achievable. Let me know of the outcome of the discussion. — This, that and the other (talk) 09:09, 9 October 2014 (UTC)

Assume good faith

Twice fairly recently I have see an message generated by Twinkle that starts "Reverted good faith edits by ..." made when reverting edits made by editors who have a long history of good faith editing.

While such a comment may be useful when reverting the edits of an IP address or a new user, both to reassure the inexperienced editor who's edit is being reverted and to inform other editors that this new editor has not vandalised the page, I think it is a breach of WP:AGF to place such a message on the revert of an edit by an experienced editor, because it implies that the editor making the revert thinks that the edit being reverted was made by an editor who also makes bad faith edits.

If the experienced editor does not make bad faith edits, why include the comment with a link to the guideline when one ought assume all edits are made by other edits are made in good faith?

It is up the the editor making the edit to look at the edit history of the editor they are revering and make a judgement call before issuing such breach of AGF, it is not something that should be a default for semi-automated scripts such as Twinkle. -- PBS (talk) 11:06, 26 September 2014 (UTC)

It is not a default; the user gets the choice of using the "good faith" summary or using a generic summary. I don't think that calling a particular edit "good faith" implies that that user also makes bad faith edits; it simply means that the reverter thinks it was a good faith edit, and doesn't want any bad feeling to come out of the revert. — This, that and the other (talk) 11:55, 27 September 2014 (UTC)

If it does not imply that user also makes bad faith edits then why include the statement (because one ought to assume good faith, without asserting it)? After all you did not consider it necessary to add to your edit summary of "reply" "reply to a good faith edit by PBS" because it is taken as granted that most editors most of the time are making good faith edits.

The place to where an editor ought to make sure that there is no "bad feeling to come out of the revert" is either to join, or initiate a conversation on the talk page, not by implying that an experienced editor sometimes makes bad faith edits in the edit summary of an article. It is a matter of commenting on the content of the article not the motives (good or otherwise) of the editor (as advised in WP:TPYES for comments on the talk page). -- PBS (talk) 15:28, 27 September 2014 (UTC)

You raise an interesting point, but I'm not going to remove one of Twinkle's longest-standing features (the AGF revert option almost 8 years old) without more input from other users. — This, that and the other (talk) 23:13, 28 September 2014 (UTC)

I use the AGF rollback occasionally, and I don't see any problems with it. Why remove it now? It works for new and inexperienced editors, giving them a link to one of our key principles automatically. --I am k6ka ^{Talk to me!} _{See what I have done} 02:10, 29 September 2014 (UTC)

It is a bad idea to teach new users to assume that other editors make bad faith edits. Do you use the wording when reverting edits by established users if so why? -- PBS (talk) 15:44, 29 September 2014 (UTC)

I don't take that a particular edit is good faith to mean the person also makes bad faith edits, rather that other people people make edits that aren't in good faith. RJFJR (talk) 14:56, 30 September 2014 (UTC)

"rather that other people make edits that aren't in good faith" I am confused by your comment do you do not assume good faith in other established editors? -- PBS (talk) 15:47, 30 September 2014 (UTC)

When someone inserts the word "butthole" into an article I do not assume it was in good faith. RJFJR (talk) 18:06, 30 September 2014 (UTC)

Have you many examples of established editors adding "butthole" into an article where later you have reverted one of their good faith edits with with "Reverted good faith edits by ...."? Have you ever used "Reverted good faith edits by ...." when reverting an edit by an established editor where you have not examined every edit they have ever made to check for a bad faith edit? If not (or if you have not found one), you ought to assume good faith, and if you do assume good faith what is the justification for using "Reverted good faith edits by ...."? when reverting an edit by an established editor? -- PBS (talk) 14:17, 10 October 2014 (UTC)

Welcome after self-revert

It has been suggested at Wikipedia_talk:Vandalism that the template {{uw-selfrevert}} could usefully be added to the list of welcome messages available on Twinkle. It could cover the frequent cases where a test or vandalistic edit has been self-reverted before patrollers get there. Any opinions?: Noyster (talk), 07:48, 8 October 2014 (UTC)

@Noyster: It's already there under Warnings - Single issue notices. --NeilN ^{talk to me} 14:28, 10 October 2014 (UTC)

AFD Log?

There is one for CSD and PROD, why not AfD? KonveyorBelt 18:56, 10 October 2014 (UTC)

+1 I like that Twinkle keeps logs. I imagine the reason AfD log isn't an option is because AfD is a consensus process and good people can disagree. CSD is just the nominator and the admin. PROD (on an unwatched article) is the same small audience. AfD also leaves an explanatory discussion where CSD and PROD do not. I'd still like to see it, though. It would be a good metric to evaluate deletionism on Wikipedia. Chris Troutman (talk) 19:07, 10 October 2014 (UTC)

See Wikipedia talk:Twinkle/Archive 35#Afd log ☺ · Salvidrim! · ✉ 20:27, 10 October 2014 (UTC)

Feature request

Hi, I almost never click the big red "rollback (VANDAL)" button because it doesn't append any sort of explanation to the edit summary like "Rvv" or "revert vandalism" or similar. Can we change that? It would be helpful for other users to see why the change occurred. Doesn't seem to make sense to not clarify. Thanks, and Twinkle rules! Cyphoidbomb (talk) 22:37, 30 September 2014 (UTC)

I support this change. The edit summary was simplified in 2013 after the discussion at Wikipedia talk:Twinkle/Archive 32#Please remove the "vandalism" summary. -- John of Reading (talk) 06:21, 1 October 2014 (UTC)

Interesting to read, or more accurately to skim. I can understand how this could be abused, but maybe the ones misusing it should have their Twinkle privs revoked. But, what if instead of "RVV" or "revert vandalism" we just used it as the literal opposite to "rollback (AGF)" or "rollback (ABF)" (assuming bad faith). Or just allow us to add our own edit summaries the way we do anywhere else. This edit I rolled back with the red link because it looked like vandalism to me, with unexplained blanking, removal of sourced content, etc. But nobody knows my rationale, because the redlink is silent. I don't really understand the purpose of the big red button unless it's doing something like notifying ClueBot that the person who just got reverted is being a rascal. Cyphoidbomb (talk) 20:59, 4 October 2014 (UTC)

Is this something that needs more community input, a la an RfC? Not sure what/if I can do anything to have this receive the contemplation it deserves. Cyphoidbomb (talk) 20:18, 15 October 2014 (UTC)

Rename media log

Given that Twinkle does a great job keeping CSD and PROD logs, would it also be able to be programmed to both 1) Tag pages in the "File:" namespaces with {{Rename media}}, and 2) Be able to create a log page of pages the user tags with {{Rename media}}, and possibly the destination title used in the template? Steel1943 (talk) 21:00, 15 October 2014 (UTC)

Concern about Unlink feature

I'm a little concerned that the unlink feature on Twinkle could be used for malicious purposes. For example, an autoconfirmed vandal could decide to delete all links to a very popular article, thus orphaning it.--Writing Enthusiast ^{(talk | contribs)} 19:59, 15 October 2014 (UTC)

Ssh!! See WP:BEANS. Sure it could happen, but it has been decided in the past that the benefits of keeping unlink available to autoconfirmed users outweigh the potential disadvantages. — This, that and the other (talk) 07:19, 16 October 2014 (UTC)

Article feedback warning templates

{{uw-af-contact}}, {{uw-af-personalinfo}}, and {{uw-af-question}}, have been deleted and no longer exist. They still appear in Twinkle's warn module, so could they be removed from the module as they are no longer needed? Thanks. --I am k6ka ^{Talk to me!} _{See what I have done} 19:46, 16 October 2014 (UTC)

Oops, I thought we got rid of those ages ago! Indeed, I see they've been deleted for quite some time. They're going to go away from Twinkle soon. Thanks for the message. — This, that and the other (talk) 10:29, 17 October 2014 (UTC)

Template POV needs to be brought in line with Core policy on NPOV

The discrepancy between the Template and the NPOV core policy has caused some confusion on one of the Current Event Articles. I have left a message on the Template Talk page, which asks that Twinkle editors should be alerted if an update is required. I am a newbie, so I don't know how to update the template myself, and would very much appreciate it if someone experienced can maintain the Template. A single word needs addressing, but it is causing disproportionate problems. Thanks Tennispompom (talk) 11:32, 17 October 2014 (UTC)

Request addition of Non-English user warning templates

When warning contributors who have edited in other languages it seems futile giving a warning only in English. Adding the contrib templates in Category:Non-English user warning templates as a Single-issue warning, with an option to choose the specific language template (e.g. hy for {{Contrib-hy1}}, ta for {{Contrib-ta1}}) is desirable. Bazj (talk) 11:49, 17 October 2014 (UTC)

Restore this version - possible glitch

This question from Ymblanter appears at WT:Notifications: "I have just semiprotected an article (Catherine Deveny), apparently not at the best version, and then another user reverted to one of the previous versions. I did not have any edits to the article except for the protection but I still got an echo notification that my edit (which was the protection) was reverted."

Here is the relevant history - it looks like C759 used Twinkle's "Restore this version" link to undo 3 revisions, but it ended up sending a "Revert Notification" to Ymblanter who merely had the final log-entry in the row of revisions being reverted (and that log-entry was just a place-holder for the Protection action).

I did some sandbox testing, and only the latest editor gets notified, when Twinkle is used to rollback many revisions.

So, if that's accurate, possibly Twinkle or Echo needs to be changed, to account for one or more of these aspects. (I'm thinking that "Restore this version" needs to not ever trigger Echo, as it could be causing many false-positive notifications of this type). Let me know if I should file a bug against Echo instead, or can help otherwise. Thanks :) Quiddity (WMF) (talk) 03:11, 18 October 2014 (UTC)

Rename request

Couldn't there be added the renaming request @Twinkle? Both for technical and other move requests. --Edgars2007 (talk/contribs) 13:05, 21 October 2014 (UTC)

Can anyone help me to show a box showing "hello world" using morebits.js?

Hi,

I want to write a text spliting (save splited text to page namespace for proofreading) script for Chinese Wikisource. I've found the script morebits.js powerful but unable to do anything with it due to I only have basic javascript programming ability.

I previewed this in my commons.js and my web console indicate that "morebits is not defined":

mw.loader.load('//en.wiki.x.io/w/index.php?title=MediaWiki:Gadget-morebits.js&action=raw&ctype=text/javascript');

alert(Morebits);

//or

Morebits.status.error( 'hello', 'world' );

Can anyone help me to show a box showing "hello world" using Morebits.status?

Cheers. --The Master (talk) 11:25, 13 October 2014 (UTC)

A function exists called mw.loader.using which can be used to load JavaScript dependencies, but unfortunately it won't work in your case, since it requires the script to be installed on the server or as a gadget. However, you could try something similar to

$.getScript( '//en.wiki.x.io/w/index.php?title=MediaWiki:Gadget-morebits.js&action=raw&ctype=text/javascript' , function() {
  alert(Morebits);

  //or

  Morebits.status.error( 'hello', 'world' );
});

I haven't tried this myself, but it seems like it ought to work. If it works, you should see an alert box saying "[object Object]" (this is how the Morebits object looks when converted to a string), and an error line labelled "hello: world" in your browser's JavaScript console.

I hope this helps you. If you have any trouble or further questions, please don't hesitate to ask. — This, that and the other (talk) 11:10, 14 October 2014 (UTC)

Thank you very much. I've finished the script.--The Master (talk) 02:02, 22 October 2014 (UTC)

Add {{Research paper}} to tagging feature under Style of Writing section

I made this as sort of a counterpart to {{essay-like}}, and would like it if it could be added. KonveyorBelt 17:31, 5 November 2014 (UTC) I have also opened a request at Github [7]. KonveyorBelt 17:42, 5 November 2014 (UTC)

Why not just add appropriate wording to the essay template? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:05, 6 November 2014 (UTC)

Courtesy notification

See Template talk:Primary sources#WP:ABOUTSELF/WP:BLPSELFPUB caveat. OK to go ahead with that as an edit request to the template? --Francis Schonken (talk) 08:56, 6 November 2014 (UTC)

Thanks for the note. No change required from our end! — This, that and the other (talk) 10:09, 7 November 2014 (UTC)

Help me

Hi,
I am stuck up with my Twinkle. Its just showing up the options, but I am not getting the task windows. Can you please see my documentations and check them and mend them if needed. Its not as a gadget for me (unchecked in preferences). Twinkle preferences shows- Before modifying your preferences here, make sure you have removed any old TwinkleConfig and FriendlyConfig settings from your user JavaScript file...Please help me..--The Herald 06:37, 8 November 2014 (UTC)

@The Herald: Is your browser configured to block all pop-up windows? You'll have to allow en.wiki.x.io as an exception if you want to use Twinkle. -- John of Reading (talk) 06:41, 8 November 2014 (UTC)

@John of Reading:..Thanks...I have set it as an exception. But still it is not showing up warn and wel popups neither the twinkle preferences panel..The Herald 07:34, 8 November 2014 (UTC)

@The Herald: I'm stuck then! But it would probably help if you posted your browser name and version number here, so the real experts can work on the problem. -- John of Reading (talk) 07:47, 8 November 2014 (UTC)

Its Chrome. (38.0.2125.111 m)--The Herald 07:52, 8 November 2014 (UTC)

@The Herald: You've enabled global Twinkle globally so it's enabled here as well. Global Twinkle is not meant for use at English Wikipedia. You need to specifically disable global Twinkle at enwiki. To fix this:

1. First, to disable global Twinkle at enwiki, go to m:User:The Herald/global.js and add if ( mw.config.get( 'wgDBname' ) !== 'enwiki' ) { to the top of the page and close it by adding } to the bottom of the page.
2. Go to Special:Preferences#mw-prefsection-gadgets and tick the checkbox next to Twinkle to enable English Wikipedia's Twinkle.

Regards, --Glaisher (talk) 07:54, 8 November 2014 (UTC)

@Glaisher: and @John of Reading:..Thanks...Done it..!!The Herald 08:13, 8 November 2014 (UTC)

Problem selecting warnings on an iPhone

When selecting a warning on an iPhone, some of the choices are truncated. Warning levels one through four, as well as only warning, work fine: all of the warning choices, including the explanatory notes, no matter how long, are displayed in their entirety. But for single issue notices, single issue warnings, and custom warnings, only the first part is shown, with the majority of it unscrollably truncated. After a warning is selected and you move on to another field, the whole thing is shown, and can be read by scrolling. The truncation is especially inconvenient for custom warnings, which display the full path, so when you're trying to select one, all you see is the path and not the specific warning (unless the path to your custom warnings is very short; in my case, they're in a user's space, and the path is about twenty characters). You have to either remember what order they're in, or select one at random, see which one you ended up with after you select it, and if you guessed incorrectly, try again. Even though it's a less severe problem for the single issue notices/warnings, it's still not a desirable situation – the explanatory notes are there for a reason, and it's helpful for a user to be able to see them when selecting a warning. MANdARAX • XAЯAbИAM 07:44, 5 November 2014 (UTC)

Twinkle is certainly not designed to be used on mobile devices; indeed, MediaWiki isn't really designed to be used on such devices in "desktop view". It would be nice to fix this, but I don't have an iPhone to be able to test and determine the cause of this issue – Amalthea, do you have one? — This, that and the other (talk) 07:23, 6 November 2014 (UTC)

I'm wondering if it may not be necessary to have the device to be able to fix the problem. It seems that the first five sets of warnings must be handled differently than the last three, and if those last three can be changed to do things the same way as the others, everything would be fine. (Of course, things are usually more complicated than one thinks, so there may be something else going on.) MANdARAX • XAЯAbИAM 07:56, 6 November 2014 (UTC)

The level x warning dropdowns use option groups (bold headings under which sets of options are groups), while the single issue and custom dropdowns don't use option groups. It's bizarre that you are seeing problems on the ones without option groups, as I would think that option groups are more problematic for mobile devices. But apparently not!

I suppose we could add a compatibility hack for iOS. What is the string you see when you visit http://whatsmyuseragent.com/? — This, that and the other (talk) 09:10, 8 November 2014 (UTC)

I tried three iOS devices. The problem exists for iPhones 4 and 5, but everything works fine on an iPad. The requested strings are ...

iPhone 4: Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_2 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D257 Safari/9537.53

iPhone 5: Mozilla/5.0 (iPhone; CPU iPhone OS 8_1 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12B411 Safari/600.1.4

Thanks for looking into this. MANdARAX • XAЯAbИAM 01:45, 9 November 2014 (UTC)

Don't have one either, sorry. Amalthea 10:56, 11 November 2014 (UTC)

Twinkle issues

Hello! I am currently having difficulty using Twinkle on my Mac running OS X Yosemite. When I click on the "TW" dropdown, I am able to see the proper buttons; however, when I click on any of them, a number sign is appended to the URL in my browser's address bar. In addition, the expected window (CSD, for example) doesn't pop up. Does anyone know what may be causing this and/or know how I may remedy it? Thank you! MJ94 (talk) 03:34, 9 November 2014 (UTC)

Could you please follow the steps 4, 5 and 6 of WP:JSERROR and report your findings? In particular, I'm interested to know what browser you're using, and whether you see any JavaScript errors. — This, that and the other (talk) 09:39, 9 November 2014 (UTC)

@This, that and the other: I am using Google Chrome (38.0.2125.111). After bypassing Chrome's cache and attempting to use individual Twinkle tools while in the Javascript console, I receive the following errors when clicking CSD, XfD, and RPP, respectively: "Uncaught TypeError: Cannot read property 'initDialog' of undefined", "Uncaught TypeError: Cannot read property 'callback' of undefined", and "Uncaught TypeError: Cannot set property 'protectionLevel' of undefined". These are all collapsable errors, so let me know if you want me to give you more information on any of them. While using Firefox (33.0.3) I received the errors "TypeError: Twinkle.speedy is undefined", "TypeError: Twinkle.xfd is undefined", and "TypeError: Twinkle.protect is undefined" while trying to use CSD, XFD, and RPP, respectively. I hope that helps! MJ94 (talk) 16:05, 9 November 2014 (UTC)

Mysterious. I notice you have a number of user scripts installed in both your User:MJ94/vector.js and User:MJ94/common.js files. While I can't see anything obvious there that would cause a conflict with Twinkle in there, you should try blanking those pages, clearing Chrome's cache (WP:BYPASS#CLEAR) and testing Twinkle on some other pages.

You could also switch the the "Console" tab of the F12 tools and type the word "Twinkle" and press Enter. See what comes up. If it's "undefined" or some similar message, then it seems that your Twinkle object is somehow being overwritten. — This, that and the other (talk) 11:16, 12 November 2014 (UTC)

@MJ94:..Me too had the same problem, now solved by the above procedure.--The Herald 11:39, 12 November 2014 (UTC)

Ah yes, that is what the problem is. Thanks for putting MJ94 on the right track! I really need to engage with PiRSquared and give him some guidance on how to fix Global Twinkle. It's currently a bit of a mess, from a coding perspective. — This, that and the other (talk) 01:05, 13 November 2014 (UTC)

Minor Error

Sometimes when using deli-batch, one of the files in the list will give a Deleting image: Failed to delete the page: An unknown error occurred in storage backend "local-swift-eqiad" and does not delete, if I run deli-batch again it gets deleted. Ronhjones  ^(Talk) 22:57, 10 November 2014 (UTC)

This is a MediaWiki issue; see bugzilla:69760 and bugzilla:73094. There's not much we can do about it from our end; it seems that when this error occurs, the server needs a few moments to get itself in order before the deletion can succeed. Automatically retrying the deletion might be counterproductive, for this reason.

By the way, I've noticed you're a relatively heavy user of Twinkle's batch deletion tools. If you have any requests or feedback, please don't hesitate to ask here. — This, that and the other (talk) 01:10, 13 November 2014 (UTC)

TW from mobile

Hello,i can't use Twinkle from my Smartphone,right now I am editing from my smartphone but i putting the laptop version instead the mobile version,and twinkle seems not work on Android ice cream sandwich. How i can use Twinkle from the smartphone? thanks! Carliitaeliza TALK 18:29, 17 November 2014 (UTC)

Edit summary mistake

When warning with the blocking selection {{uw-ipevadeblock}} Block-evasion block - IP address it says "...Your IP address have been blocked from editing because it has been used to evade a previous block...." but it should be "...Your IP address has been..."

Best, Anna Frodesiak (talk) 06:56, 23 November 2014 (UTC)

Noted, thanks. A change is on its way. — This, that and the other (talk) 09:25, 24 November 2014 (UTC)

Request for change when reporting Socks

A admin that frequently investigates sockpuppets asked me not to use the notify reported users feature because it may cause problems. If that's actually the desire of all admins, we should consider removing the checkbox from that panel. Is that possible? Walter Görlitz (talk) 04:42, 28 November 2014 (UTC)

@Bbb23: Could you comment here?

A word about the history of this feature: the notification to the sockpuppeteer has been present in Twinkle ever since the SPI functionality was first added to Twinkle, way back in 2007. The notification to each sockpuppet account was added later. It was made optional in 2010 by Timotheus Canens. So it's a very long-standing feature, and I am hesitant to remove it without a clear agreement that it should never be used.

I also note the wording in the tooltip: "Especially in less egregious cases involving users who has not been reported before, notification may make the cases fairer and also appear to be fairer in the eyes of the accused. Use your judgment." — This, that and the other (talk) 02:10, 5 December 2014 (UTC)

All I can tell you is the history of the instructions at SPI. At one time the notification was optional, although the instructions made it clear that you might not want to give the notification. Then it changed to the notification not being mentioned in the instructions, and it has stayed that way. Personally, I think a reasonable inference from removing the notification (unlike other administrative boards where notice is required) is that the powers that be don't want an account to be notified.

As an SPI clerk, I believe I work for the checkusers. I defer to them, not just in their CU findings, but in other matters as well. Thus, I think it might be useful to get their input to this discussion. A few of the CUs that hang out at SPI lately are Ponyo, DeltaQuad, and Callanecc. There are, of course, others.--Bbb23 (talk) 02:24, 5 December 2014 (UTC)

The vast majority of the time it's better not to notify the reported parties as, especially, with longer term sockpuppeteers as they are then aware that the sock has been found so they create others (usually using methods which are difficult to detect). Really the only time we do seek input is when it's a close call or there are experienced users involved, if that's the case a clerk usually does it anyway. Callanecc (talk • contribs • logs) 10:13, 6 December 2014 (UTC)

Courtesy blanking option for CSDs

Please add an option to blank the page for CSD:U1, CSD:G7, and CSD:G12 deletions. U1 and G7 are author requested deletions, and there is no reason an author shouldn't be able to blank a page they feel they completely messed up for some reason while tagging for deletion and my experience from working on AfC drafts is that copyright violation quick-fail criteria says:

Check that the submission has not been copied from another source. Search for a portion of the text of the article on Google or another search engine. Also check the sources provided, and, if relevant, check a person's or organization's web site, even if not given as a reference or link. If the submission contains material that has been copied from elsewhere and the source is not released under a suitable free license or in the public domain, immediately decline the submission as a copyright violation and ensure you select the checkbox to blank the submission using {{afc cleared}}. If the entire page is an unambiguous copyright violation, you should also tag the page for speedy deletion with {{db-g12}}. This can be done using Twinkle, if you have this gadget installed. Consider also warning the user on their user talkpage using {{subst:uw-copyright-new}}

This suggests to me that all G12's should at be blanked as well. Thank you. — {{U|Technical 13}} ^{(e • t • c)} 04:38, 5 December 2014 (UTC)

Perhaps the same should extend to other CSD criteria? Attack pages come to mind. ☺ · Salvidrim! · ✉ 05:20, 5 December 2014 (UTC)

• I was thinking it should extend to G11 pages as well, but I couldn't find any kind of policy to back that as being appropriate. — {{U|Technical 13}} ^{(e • t • c)} 11:50, 5 December 2014 (UTC)

G10s are already automatically blanked by Twinkle. As for G7 and U1, I see no real benefit in having the page blanked; in my experience these deletions are usually handled quickly. G12 is an interesting one... there seem to be mixed messages about whether to blank these or not. I wonder if it might be worth bringing this up at WT:CSD. — This, that and the other (talk) 06:25, 6 December 2014 (UTC)

• TTO, the benefit to adding a checkbox to allow an editor to blank a creation of their own when tagging it for CSD is to prevent them from having to do extra work. Example: I just had to manually blank User:Technical 13/SandBox/prevnext.js before using Twinkle to tag it for deletion. I simply wanted it blanked because there was no reason to leave the unrefined code sitting around for someone to try and use before it actually gets deleted and I wanted to use Twinkle to tag it because I want the tagging logged in my CSD log. I'd think it easy to add a checkbox next to (or replacing) "Notify creator if possible" in these situations that says "Blank page". What is the conflict about G12? I am missing something it seems. Thanks! — {{U|Technical 13}} ^{(e • t • c)} 15:56, 6 December 2014 (UTC)

Unlink with deli-batch

Fails to work when images are in a gallery - gives red failed message - example page is https://en.wiki.x.io/w/index.php?title=User:Susan.gardner566/CSUCI_Writing_Center&oldid=627074511 Ronhjones  ^(Talk) 21:29, 6 December 2014 (UTC)

It's clearly got a problem. I'll look into it. — This, that and the other (talk) 00:31, 8 December 2014 (UTC)

Merger of two welcome templates proposed

FYI, I have suggested at Wikipedia:Templates for discussion/Log/2014 November 21#Template:Welcome-anon-border that {{Welcome-anon-border}} and {{Welcome-anon}} be merged. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:22, 21 November 2014 (UTC)

The merger has now been completed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:28, 10 December 2014 (UTC)