Wikipedia talk:Twinkle/Archive 15

Archive 10

←

Archive 13

Archive 14

Archive 15

Archive 16

Archive 17

→

Archive 20

CfD Process

The way CfDs are listed has been changed. The new process can be seen here. Basically, it is now done the same way as AfDs. MrKIA11 (talk) 14:12, 25 October 2008 (UTC)

Account "too new"?

I've just installed twinkle but when I try to use it I get an error message: "Your account is too new to use Twinkle". I've been editing two years already so how much longer do I have to wait? andy (talk) 16:02, 25 June 2008 (UTC)

I don't think that should be a problem; I haven't been editing that long and I've been using it with no problems for over a month. Player 03 (talk) 17:01, 3 July 2008 (UTC)

I am also having this issue, and I've had this account for a long time, and done more edits than some admins. What the dilly-yo? ----Адам12901 ^T/_C 14:09, 16 July 2008 (UTC)

I'm having the same problem. Kevin Rutherford (talk) 21:40, 28 July 2008 (UTC)

I'm also having the same problem currently. I've been a Twinkle user for months; perhaps there is problem with the system.--E8 (talk) 01:47, 30 October 2008 (UTC)

Ditto, but do you think that 7 months really isn't old enough? SpecialK 18:31, 10 September 2008 (UTC)

Browser support

If Twinkle does not work with IE, could the installation instructions say this explicitly? At the moment this browser isn't mentioned. Tim Vickers (talk) 16:01, 28 October 2008 (UTC)

Hmm, it has always been stated that there is, and probably will never be any IE support, wonder where that line has gone. _→AzaToth 15:34, 29 October 2008 (UTC)

Question About Tagging

I'm sorry, I'm not sure where to put this, but I have a good question.

Shouldn't the AfD have just a generic "Spam" tag in the Twinkle Pop Up menu? If it does, I've yet to find it.

Having one, or knowing where to find it would help me greatly in new page patrolling.

Thanks,

--Mooshykris (talk) 16:35, 30 October 2008 (UTC)

That's what the "Reason" box is for. The categories in the drop-down list are for categorizing the AfD discussion and page. You have to fill in the reason, so if a page is spam you could type "Article is written like an [[WP:SPAM|advertisement]]", and it will appear as your rationale for nominating the article for AfD. Of course, many instances of spam can just be CSD tagged under criterion G11. Hope this helps! Ioeth _{(talk contribs friendly)} 17:26, 30 October 2008 (UTC)

Reference page of tags twinkle uses

The sandbox mentioned above is fun, but is there already a page that shows all the tags twinkle uses. A sort of reference page where I can see what they all look like?--Sultec (talk) 20:47, 31 October 2008 (UTC)

• There is a page for testing Twinkle here. You can test and see any warning Twinkle can put on a talk page. Beeblebrox (talk) 21:56, 31 October 2008 (UTC)

ARV

I know that twinkle was breaking AIV before, but now the ARV tab is gone for me. Anyone else having this problem? --Terrillja (talk) 22:45, 25 October 2008 (UTC)

Yep. [ roux ] [x] 04:43, 26 October 2008 (UTC) Removed after RTF-two-comments-above. [ roux ] [x] 04:46, 26 October 2008 (UTC)

Is the botched report at User talk:71.72.81.230#Sockpuppetry case my fault or Twinkie's? It shows Wikipedia:Suspected sock puppets/Philscirel (2nd nomination) as a red link, for some reason. --Adoniscik^{(t, c)} 05:20, 11 November 2008 (UTC)

Clear your cache, it's a bluelink for me. --Terrillja _talk 05:41, 11 November 2008 (UTC)

It became blue after I edited it, I think. I'll try switching browsers next time this happens. Thanks for the prompt response. --Adoniscik^{(t, c)} 06:00, 11 November 2008 (UTC)

It's not the local cache that causes this anomaly. Purging the server's cache of the page by appending the "action=purge" URL parameter will instantly resolve it. There is a gadget that makes this even easier that you can add in your preferences. It is listed in the section "User interface gadgets" with the description "A clock in the personal toolbar...". Very handy to be able to purge the server cache of any page on Wikipedia when things like this are prone to happening. Ioeth _{(talk contribs friendly)} 18:10, 11 November 2008 (UTC)

Needs an update

I recently left an issue notice on a talk page here and the second paragraph is completely out of date. It states, Sometimes dates are enclosed in two square brackets, as in [[12 December]] or [[December 12]]. This means that you can set your preferences (if you look around your screen you'll see the word preferences; click on it and follow the instructions) to ensure that you see all dates in the format you want, whether date-month-year, month-date-year or yyyy-mm-dd. Per MOS:SYL, linking dates is a deprecated practice. I think the aforementioned paragraph needs to be removed, or at least updated. DiverseMentality^(Boo!) 03:40, 1 November 2008 (UTC)

That's not a Twinkle problem as much as it is a problem with Template:uw-date. Twinkle substs or transcludes templates, but the templates themselves are not part of Twinkle. You are more than welcome to edit the template as you see fit, but for now, I kind of hacked off the outdated paragraph. So now it gives less information than it did (no discussion of how dates are handled in the system), but it gives no wrong information. SchuminWeb (Talk) 15:16, 1 November 2008 (UTC)

Twinkle and Safari

Hello, I've begun to use Twinkle to respond to vandalism but I don't know if my configuration is correct. I mostly use Safari 3, so do I need to enable the Javascript Library in my Wikipedia preferences or not? Thank you. LovesMacs (talk) 22:32, 9 November 2008 (UTC)

Yes. Ioeth _{(talk contribs friendly)} 18:11, 11 November 2008 (UTC)

CSD bug.

CSD doesn't seem to work. In an error console, I get: Error: TwinkleConfig.notifyUserOnSpeedyDeletionNomination is undefined Source File: https://secure.wikimedia.org/wikipedia/en/w/index.php?action=raw&ctype=text/javascript&title=User%3AAzaToth%2Ftwinklespeedy.js Line: 1116 Any ideas? Thanks -- T^heDJA^tC^lubR^ock :-) ^(T/C) 12:15, 14 November 2008 (UTC).

twinklespeedy.js has code to define TwinkleConfig.notifyUserOnSpeedyDeletionNomination if it is undefined, so this error, in theory, should not be possible. Clear the cache on your browser and see if the problem goes away. Ioeth _{(talk contribs friendly)} 15:03, 14 November 2008 (UTC)

Nope, still fails. :( T^heDJA^tC^lubR^ock :-) ^(T/C) 16:40, 14 November 2008 (UTC)

Switch over to the non-secure server and see what happens. Ioeth _{(talk contribs friendly)} 16:41, 14 November 2008 (UTC)

Nope, still fails. You made me send my password in cleartext. Shame on you! (Just Kidding) -- T^heDJA^tC^lubR^ock :-) ^(T/C) 17:18, 14 November 2008 (UTC)

I just tested it and it seems to work just fine. What browser are you using? Do you have TW installed as a gadget? Ioeth _{(talk contribs friendly)} 17:35, 14 November 2008 (UTC)

That is odd. Perhaps try adding the following line to your monobook.js (in the TwinkleConfig)? (EhJJ)^TALK 17:50, 14 November 2008 (UTC)

notifyUserOnSpeedyDeletionNomination : [ 'g1', 'g2', 'g3', 'g4', 'g10', 'g11', 'g12', 'a1', 'a2', 'a3', 'a5', 'a7', 'a9', 'i1', 'i2', 'i3', 'i4', 'i5', 'i6', 'i7', 'i8', 'i9', 'i10', 'i11', 'u3', 't1', 't2', 't3', 'p2' ],

You could also consider reverting the recent edits you made to your monobook.js file, if it is the cause of the recent failure of Twinkle to function properly. (EhJJ)^TALK 18:03, 14 November 2008 (UTC)

Fixed! Yes, twinkle was installed as a gadget, and now is in my Monobook. That is odd, though. (Firefox 3) T^heDJA^tC^lubR^ock :-) ^(T/C) 18:54, 14 November 2008 (UTC)

Yeah, you can't have TwinkleConfig or FriendlyConfig defined in your monobook.js if you have them installed as gadgets. Causes all sorts of weirdness. Ioeth _{(talk contribs friendly)} 20:48, 14 November 2008 (UTC)

Only for autoconfirmed?

Is Twinkle only for autoconfirmed users? It started working for me only when I got autoconfirmation, but article says its for registered users. -Unpopular Opinion (talk · contribs) 07:11, 15 November 2008 (UTC)

I believe it is the case that Twinkle does not function for non-autoconfirmed users. SchuminWeb (Talk) 12:26, 15 November 2008 (UTC)

I don't need to be informed of my own actions

So Twinkle kindly left a note on my own talk page regarding an RfD I opened. Is this really necessary? Chris Cunningham (not at work) - talk 12:37, 17 November 2008 (UTC)

PROD reasons not being transferred to the authors talk page ?

Hi. I just used Twinkle to PROD 'Ja Nanna'. Although the article includes the line : "Author(s) notification template: {{subst:prodwarning|'Ja Nanna'|concern = Non-notable album. Fails WP:MUSIC.}}", the message added to the authors talk page User talk:Mam1076, reads :"A proposed deletion template has been added to the article 'Ja Nanna', suggesting that it be deleted according to the proposed deletion process because of the following concern:'Ja Nanna'" - there's no sign of the reason (Non-notable album etc.) being passed. CultureDrone (talk) 12:51, 17 November 2008 (UTC)

I'll look into why the prod function did that. On a sidenote, the article that you prodded could have been speedied under the new A9 criterion. Ioeth _{(talk contribs friendly)} 18:29, 17 November 2008 (UTC)

Looks like the code of {{PRODWarning}} got changed on Nov 14th; a change that was not implemented correctly. I have fixed the template so that it works properly now and added the code in Twinkle to specify the concern if one was entered. You should notice everything working correctly now. Ioeth _{(talk contribs friendly)} 20:37, 17 November 2008 (UTC)

Many thanks - and whoopee - another CSD reason that's long overdue ! :-) CultureDrone (talk) 08:35, 18 November 2008 (UTC)

Add no-permission to "di" menu

Is it possible to add Template:Di-no permission, for images with no evidence of permission, to the "di" menu? We recently added it to the speedy menu, but now its process needs to be added to the "di" menu. SchuminWeb (Talk) 10:50, 27 October 2008 (UTC)

• Any update on this? Soundvisions1 (talk) 01:05, 10 November 2008 (UTC)

Loeth added it. Soundvisions1 (talk) 03:55, 21 November 2008 (UTC)

PROD broken?

Yesterday and today prod isn't working for me at all in Twinkle. (Gets hung up right after I click okay for the reason) No changes to my monobook. Anyone else having this issue?--Fabrictramp | talk to me 14:40, 19 November 2008 (UTC)

A change I made broke it. I've reverted the change back out now. It is working again. Ioeth _{(talk contribs friendly)} 16:46, 19 November 2008 (UTC)

Again, you're my hero. I've shoved a plate of chocolate chip cookies into my USB port -- you should have them in a minute or so. :) --Fabrictramp | talk to me 17:11, 19 November 2008 (UTC)

And now what I was trying to do before that broke the script has been fixed! Twinkle's PROD function now checks to make sure that the page hasn't been deleted before it applies a PROD tag to it! Ioeth _{(talk contribs friendly)} 18:43, 19 November 2008 (UTC)

Age

How old must an account be to use Twinkle? I have made over 600 edits. What is the minimum age?
Thanks
Limideen 15:49, 20 November 2008 (UTC)

4 days and 10 edits (see WP:AUTOCONFIRM). Dendodge Talk^Contribs 15:59, 20 November 2008 (UTC)

You should definitely be able to use Twinkle. Let me know if you have problems. Ioeth _{(talk contribs friendly)} 19:25, 20 November 2008 (UTC)

Twinkle's Page Protection feature works for sysops again

I think I've finally got the "pp" tab working for sysadmins in full again. I've tested in my userspace a few times and then went out to WP:RFPP and took care of some of the requests there with it. Let me know if anyone encounters any problems. Thanks! Ioeth _{(talk contribs friendly)} 19:27, 20 November 2008 (UTC)

CSD I11 and I9 issues

• (Brought to my attention by lifebaka++) When you add a CSD for an image and tick the "I11" option it tags the image with {{db-nopermission}} instead of {{di-no permission}} The {{db-nopermission}} tag should be used seven days after the {{di-no permission}} has been in place. Is there a way to option this? i.e - ticking "I11" gives you a drop down for "First Notice", which would add the {{di-no permission}} tag and "Final Notice" which would add the {{db-nopermission}} tag.
• (Brought to my attention by --Moonriddengirl) When you add a CSD for an image and tick the "I9" option Twinkle does not place the {{Db-i9}} image tag on the page it places the {{Copyviocore}}) tag instead, which is for text.

Thanks. Soundvisions1 (talk) 20:52, 24 October 2008 (UTC)

I ran a test on both tags on Image:Ben Schumin at Iwo Jima Memorial.jpg, and here's what I came up with.

For I9, Twinkle tags it with {{db-imgcopyvio}}, so that should be fine.

For I11, that one, and likely along with other speedy tags that require the "di" process, should probably be pulled off the CSD menu for non-admins. For I11, "no evidence of permission" is not on the "di" menu at all, and probably should be added to it.

Does that seem to be a good solution for the problem you've described? SchuminWeb (Talk) 00:35, 25 October 2008 (UTC)

The "I11" comment - not sure I follow you. Why would you pull it from the options for non-admins? The "di" process I mean. Would it be hard to add a "First Warning" or "Final Warning" option? As for the {{Copyviocore}} tag, guess that was fixed? Or maybe it was a glitch the other day. I do have a question however - now as soon as you click on "I9" Twinkle does its' work and you get the tag with the "This image is copied from an unspecified source" message in it. The format for output ideally should be {{db-i9|url=http://somesite.com}} but now there is no input box for the original source like there was when it was outputting the {{Copyviocore}} tag. Thanks. Soundvisions1 (talk) 03:35, 25 October 2008 (UTC)

First of all, re: I9, I'm guessing someone with more Javascript expertise than me just needs to code that in. I wouldn't think it would be all that difficult of an operation to complete.

As for I11, for non-admins, the CSD tab just tags, while for admins, it deletes. Since I4, I5, I6, I7, and I11 are all handled through the "di" process (thus waiting five days before deleting) rather than being speedily deleted right away, there's no reason to ever tag images with the speedy tag directly for these cases, since the di tags categorize the images into speedy deletion categories, which an admin can then go into via CAT:CSD and knock out when the category is of the proper age. I'm not saying to remove the "di" tab or any of its functions for non-admins, since that's a very important tab that serves an important functions for admins and non-admins alike, and I encourage I11's addition on the "di" tab. There's just no need to list those speedies on the CSD tab for non-admins because those criteria require a waiting period before the speedy deletion is completed.

Does that make more sense now? SchuminWeb (Talk) 04:29, 25 October 2008 (UTC)

Yeppers. Thanks. Soundvisions1 (talk) 15:05, 25 October 2008 (UTC)

There is a need to list CSD criteria such as I11 for non-admins. The {{db-i11}} tag in the CSD menu is for images that were tagged with {{di-no permission}} and the uploader notified over 7 days ago and still shows no evidence of permission. So yes, although the I11 criterion itself specifies a 7 day time period, which is what {{di-no permission}} is for, the {{db-i11}} can be used to actually speedily delete the image once the time period has passed. See what I'm saying? Ioeth _{(talk contribs friendly)} 14:42, 21 November 2008 (UTC)

SchuminWeb had explained several weeks ago but thanks for reinforcing what he said. :) Soundvisions1 (talk) 15:54, 23 November 2008 (UTC)

My TWINKLE tabs are gone

Resolved

 – thanks so much

Not sure for how long since I've been less-than-active of late. I tried re-adding it to monobook, removing other scripts. Finally took it out of monobook and added it in gadgets to see if that would work. No dice, I'm tabless. Firefox 3.03 on OSX. Not sure, would it have anything to do with my recent rename? StarM 17:02, 22 November 2008 (UTC)

Note, currently disabled in gadgets, re-added to my monobook. Refreshed cache, this alao happens on another machine, a PC running FF 2. Used to work there with no issue. StarM 17:05, 22 November 2008 (UTC)

Once you took it out of your monobook.js and added it to your gadgets, did you do a cache-clearing refresh by hitting CTRL+F5? Ioeth _{(talk contribs friendly)} 22:41, 22 November 2008 (UTC)

Command F5, Control F5, Control-Shift-R, Command-Shift-R. Tried all. Befuddled me when it happened on the PC as well. I just added back some other scripts, absent one which I'd had some trouble with in the past but I don't think anything ate Twinkle. I am not positive but I think it did work post re-name as I jad some just-expired PRODS: Debra Finerman and Genii magnetic lock that I did with twinkle according to the edit summary. StarM 23:09, 22 November 2008 (UTC)

Of possible relevance, none of my scripts are working. I just went to do some AfD clean up and the AfD close isn't working either. COuld there be something wrong with my monobook or something? StarM 23:33, 22 November 2008 (UTC)

And I've noticed the clock that used to appear in the upper right corner with server time has disappeared as well. I'm not sure what's up, but something is. So it's not just Twinkle but I'm hoping someone is knowledgeable enough. I'm going to post to the help desk and link this post. HD post StarM 00:09, 23 November 2008 (UTC)

It's resolved. Was a javascript error that was getting them all. StarM 04:57, 23 November 2008 (UTC)

Welcome messages

Per discussion at WT:CSD#Suggestion for modification of templates the speedy deletion notification templates will be changed later today so that they automatically leave a {{firstarticle}} welcome message on the article creator's talk page if the notification is the first message they have ever received (i.e. they have a red-linked talk page). Should there be any problems with it please mention them here or at WT:CSD instead of opening a new bug issue.
Cheers, Amalthea^Talk 15:21, 28 November 2008 (UTC)

Invalid password warning

Hi, I ticked the select box for Twinkle in my preferences gadgets, but when I clicked save, a warning banner came up saying my old password is invalid, with enter boxes for new and confirm new password. My current password is still okay otherwise. Btw, it's Firefox 3.0.4 on a Mac (OSX) Can you tell me what's going on? Thanks, Julia Rossi (talk) 02:05, 1 December 2008 (UTC)

That's a FireFox/MediaWiki issue, not a problem with Twinkle. Firefox prefills one of the password input boxes in your first tab in the preferences, which makes MediaWiki think you wanted to change it (or so I heard somewhere, can't reproduce it here). Try making sure those boxes are clear after you turn on Twinkle and before you press OK. --Amalthea^Talk 02:15, 1 December 2008 (UTC)

Thanks for your help, Julia Rossi (talk) 02:25, 1 December 2008 (UTC)

Anytime. --Amalthea^Talk 03:16, 1 December 2008 (UTC)

New Page Patrolling

Twinkle's CSD feature now has the option to automatically mark a new page as patrolled while you're tagging it for speedy deletion! This is now the default behavior, but it can be disabled by setting the markSpeedyPagesAsPatrolled configuration parameter in your TwinkleConfig to false. Let me know if you have any questions about this new feature! Ioeth _{(talk contribs friendly)} 18:02, 2 December 2008 (UTC)

"The syntax for this template ({{cfd}}) has changed. "

I just listed a category at CFD using Twinkle, and got "The syntax for this template ({{cfd}}) has changed." on the category page. Any chance that could be fixed? Ten Pound Hammer and his otters • ^{(Broken clamshells • Otter chirps • HELP)} 05:38, 3 December 2008 (UTC)

"The template below ({{cfd}}) should no longer be substituted}}. Please use {{cfd|~~~~~}} instead of {{subst:cfd}}, or {{cfd|~~~~~|Archbishops categories}} instead of {{subst:cfd|Archbishops categories}}". --Amalthea 10:30, 3 December 2008 (UTC)

This has been fixed. Ioeth _{(talk contribs friendly)} 14:03, 3 December 2008 (UTC)

CSD I11

Resolved

When notifying a CSD I11, Twinkle posts {{subst:db-nopermission-notice|Image:________}}<!-- Template:Db-csd-notice-custom -->, which doesn't seem to work/exist. --aktsu ^(t / c) 19:33, 5 December 2008 (UTC)

I've created the template and it should be working correctly now. Ioeth _{(talk contribs friendly)} 20:04, 5 December 2008 (UTC)

Bug?

Resolved

I recently requested protection for Untitled Nas album using Twinkle. A few minutes later, I was going request protection for Nas, but it said Untitled Nas album is already on page. Seems like it can't send out the request because 'Nas' is already part of the first article. DiverseMentality 22:59, 8 December 2008 (UTC)

Yes, that would be a bug with the regular expression that checks if an article is already listed for protection. I'll look into it, but I can't guarantee anything...regular expressions have never exactly been my strong suit. Ioeth (talk contribs twinkle friendly) 02:31, 9 December 2008 (UTC)

The currenct code is wrong since it creates both false positives if the new page name is a substring of a page that is already listed, and false negatives since no articles outside articlespace will ever be matched. I suggest changing it to match pretty strictly, which will only create false negatives (→ create duplicate requests) with malformed existing requests. Change:

   var form = self.responseXML.getElementById( 'editform' );
   
   var text = form.wpTextbox1.value;
   
   var rppRe = new RegExp( '====.*?' + RegExp.escape( wgPageName, true ) + '.*?====', 'm' );
   var tag = rppRe.exec( text );
   
   if( tag ) {
   	self.statelem.warn( [ htmlNode( 'strong', tag[0] ) , " is alread placed on the page." ] )
   	return false;
   }
   
   var ns2tag	=	{
   	'0'	:	'la',
   	'1'	:	'lat',
   	'2'	:	'lu',
   	'3'	:	'lut',
   	'4'	:	'lw',
   	'5'	:	'lwt',
   	'6'	:	'li',
   	'7'	:	'lit',
   	'8'	:	'lm',
   	'9'	:	'lmt',
   	'10':	'lt',
   	'11':	'ltt',
   	'12':	'lh',
   	'13':	'lht',
   	'14':	'lc',
   	'15':	'lct',
   	'100':	'lp',
   	'101':	'lpt'
   };

to

   var ns2tag	=	{
   	'0':	'la',
   	'1':	'lat',
   	'2':	'lu',
   	'3':	'lut',
   	'4':	'lw',
   	'5':	'lwt',
   	'6':	'li',
   	'7':	'lit',
   	'8':	'lm',
   	'9':	'lmt',
   	'10':	'lt',
   	'11':	'ltt',
   	'12':	'lh',
   	'13':	'lht',
   	'14':	'lc',
   	'15':	'lct',
   	'100':	'lp',
   	'101':	'lpt'
   };
   
   var form = self.responseXML.getElementById( 'editform' );
   var text = form.wpTextbox1.value;
   
   var rppRe = new RegExp( '====\\s*\\{\\{\\s*'+ns2tag[wgNamespaceNumber]+'\\s*\\|\\s*' + RegExp.escape( wgTitle, true ) + '\\s*\\}\\}\\s*====');
   var tag = rppRe.exec( text );
   
   if( tag ) {
   	self.statelem.warn( [ htmlNode( 'strong', tag[0] ) , " is already placed on the page." ] )
   	return false;
   }

--Amalthea 15:37, 9 December 2008 (UTC)

Excellent coding there, Amalthea! I've changed the script to implement better listing checking. Ioeth (talk contribs twinkle friendly) 15:33, 10 December 2008 (UTC)

"Pseudo-speedy" image tagging edit summaries

Was going to post this as a bug, but thought better of it. I performed an assisted "quasi-speedy" tagging of an orphaned non-free image (notify and non-free both unchecked), and noticed that the edit summary was as follows:

This image is up for deletion per WP:CSD. (TW)

That probably ought to be changed to reflect the fact that those "pseudo-speedy" image tags (no source, no license etc.) aren't in fact speedy deletion, and certainly aren't detailed at WP:CSD. Perhaps each needs a specific edit summary, with a link to the criteria at WP:IFD? haz (talk) 20:58, 9 December 2008 (UTC)

Well, technically speaking, it's correct, since it is up for deletion per WP:CSD, since the process ends with a speedy deletion. The only difference is the waiting period. SchuminWeb (Talk) 06:14, 10 December 2008 (UTC)

Quote WP:CSD: 'In this context, "speedy" refers to the simple decision-making process'. --Amalthea 12:15, 10 December 2008 (UTC)

Would it be more appropriate to link to Wikipedia:Guide to image deletion? Ioeth (talk contribs twinkle friendly) 15:48, 10 December 2008 (UTC)

CSD notifications

There's a discussion about making the CSD notices fit the "uw-" style user warnings at WT:UTM#UW templates for CSD, which would be a good opportunity to unify the three different notices (manual, Twinkle, Huggle) we have a the moment. --Amalthea 14:22, 16 December 2008 (UTC)

Autowatching pages

Resolved

Is there any way with Twinkle to turn off the automatic watching of pages I edit with Twinkle? I'm constantly having to cull from my watchlist anything and everything that I've cleansed of vandalism, as well as the accompanying anon user talk pages. Unschool 05:50, 17 December 2008 (UTC)

See Wikipedia:Twinkle/doc#Configuration and Wikipedia:Twinkle/doc#watchRevertedPages. --Dynaflow babble 05:57, 17 December 2008 (UTC)

Chrome doesn't (seem to) work

Although Safari is supported, Google Chrome (which is based on the same WebKit rendering) doesn't. It does the actual reverting fine (even detecting when there has already been a revert and so on) but doesn't successfully load the reverted user's talkpage. Cynical (talk) 22:44, 13 December 2008 (UTC)

It worked fine for me on both Google Chrome and Internet Channel on the Nintendo Wii, but then again, I rarely edit using these browsers, and I rarely use Twinkle since my prefered browser is Internet Explorer. PCHS-NJROTC ^(Messages) 20:37, 21 December 2008 (UTC)

I may test this myself later. just64helpin (talk) 03:57, 22 December 2008 (UTC)

csd doesn't complete the operation

Resolved

Using Safari, on the Mac, csd has never worked for me. I can click the tab, the javascript-generated window opens, I make my choice among the radio buttons, but then what? There is no 'submit' (or similar) button anywhere in the window. Nothing happens upon clicking a radio button (other than that button visually selecting.) Am I missing a step somewhere? The TW docs aren't too informative on this process. Thanks (and thanks for making patrolling so easy.) --Uncle Milty (talk) 23:09, 24 December 2008 (UTC)

When you click the radio button Twinkle should do its thing. I'll check it out next week when I have access to a Mac. Could you reply with what version of Mac OS and Safari you're using, please? Ioeth (talk contribs twinkle friendly) 04:55, 25 December 2008 (UTC)

OSX 10.5.6, Safari Version 3.2.1 (5525.27.1). It hasn't worked since I began using it back in April on previous versions of both OSX and Safari on multiple computers. Let me know if I can supply any additional diagnostic info. Thanks for your help. --Uncle Milty (talk) 13:31, 25 December 2008 (UTC)

I'm now on a machine that has the Developer menu turned on in Safari. Here is the error shown in the Web Inspector console that occurs when I select a button:

Undefined value
http://wiki.riteme.site/w/index.php?
title=User:AzaToth/twinklespeedy.js&action=raw&ctype=text/javascript (line 1177)

Hope this helps. --Uncle Milty (talk) 00:09, 29 December 2008 (UTC)

SOLVED. I had a bad TwinkleConfig in my monobook.js file. I deleted that (thus going with default settings) and now csd works. (Hopefully I didn't piss anyone off find that out, though.) --Uncle Milty (talk) 00:29, 29 December 2008 (UTC)

Doesn't work when changing the skin

Resolved

If you change the skin of Wikipedia, the tab buttons disappear. Anyway to display them again??? Thank you:) --Zaher1988 · ^Talk 10:35, 30 December 2008 (UTC)

Twinkle is only compatible with the monobook skin or the modern skin. If you want to use the modern skin, you need to enable the "Compatibility function" gadget to get it to work. Ioeth (talk contribs twinkle friendly) 13:58, 30 December 2008 (UTC)

Thank you:) --Zaher1988 · ^Talk 14:14, 30 December 2008 (UTC)

Reworded speedy deletion for A7 company

I've gone in and slightly reworded the way the A7 speedy deletion is listed on the dialogs and on the deletion log rationales to include "organization", since nonprofits fall under A7-company as well. Thus in the note placed in the deletion log rationale, I've swapped out "corporation" for "organization" (thus it now reads, "Article about a company or organization that does not assert the importance or significance of the subject"), and the menu now says "A7: Unremarkable company or organization".

So all in all, it's not a HUGE change, but a change nonetheless to make things a little more clear. It always felt strange to do nonprofits under A7-company, so this fixes the wording. SchuminWeb (Talk) 20:09, 3 January 2009 (UTC)

Rfd template

Resolved

I have updated {{Rfd2}} to make the whole page more universal. Could twinkle and other tools be updated to reflect this? The new section of action has been added. Simply south not SS, sorry 17:16, 4 January 2009 (UTC)

Since that change was reverted twice and is still being discussed at WT:RfD#Action and rfd2 I guess that has to be belayed. Can you get back here if it get changed again? Cheers, Amalthea 21:03, 4 January 2009 (UTC)

mfd funtion posts red links

see this & thiswhich were both made with Twinkle.Alexnia (talk) 17:49, 5 January 2009 (UTC)

Since Twinkle did create the page it is a caching issue. It could be worked around by delaying Twinkle between creating the XfD page and adding tag and notification, which isn't that great either. You can always force the Squids to recache if you WP:PURGE the pages (which they should eventually do on their own). --Amalthea 18:00, 5 January 2009 (UTC)

A null edit fixes that I've found--Jac16888 (talk) 18:06, 5 January 2009 (UTC)

Yes, that too, since it will in turn have the page recached. --Amalthea 18:16, 5 January 2009 (UTC)

User talk page templates when issuing I8

Hi, I posted this at the Village Pump but I think it is partly a Twinkle problem.

When tagging an image with an I8 via Twinkle it does two things that aren't great:

1. Twinkle inserts Template:Firstarticle if the Talk page is blank. This isn't appropriate for an I8 as it includes text like "Unfortunately, one or more of the pages you created, like ***.JPG, may not conform to some of Wikipedia's guidelines for page creation, and may soon be deleted". I think this is a Twinkle issue. It shouldn't really include this template for an I8.

1. It then includes Template:Db-nowcommons-notice. Which is fine, except this template includes Template:db-notice which has text about modifying the article to include a hangon notice, and so on. This isn't a Twinkle problem per se, so I've asked at VP if someone better at templates than me can fix it.

Basically the whole effect of this is to make it look like the editor has done something wrong as opposed to it being a technical move of a good quality image to Commons.

For an example, see this diff.

If this doesn't make sense, let me know. Thanks. Unusual? Quite ^TalkQu 17:47, 3 January 2009 (UTC)

What do you want to happen? I'd think that it shouldn't leave *any* notice on the uploaders talk page. --Amalthea 16:35, 4 January 2009 (UTC)

That's certainly an option. Either that or just a simple "your image has been moved to Commons and will soon be deleted from Wikipedia - don't worry, because it's at Commons it will still appear in all the articles where it is currently used." or words to that affect. Not leaving any notice seems better though - why would the uploader care? Unusual? Quite ^TalkQu 20:32, 4 January 2009 (UTC)

Seems to make sense to me, we also don't notify with a number of other criteria. We'll need to wait for Ioeth to make the change to the script, you can if you want disable it in your personal configuration right away:

TwinkleConfig.notifyUserOnSpeedyDeletionNomination = [ 'g1', 'g2', 'g3', 'g4', 'g10', 'g11', 'g12', 'a1', 'a2', 'a3', 'a5', 'a7', 'a9', 'i1', 'i2', 'i3', 'i4', 'i5', 'i6', 'i7', 'i9', 'i10', 'i11', 'u3', 't1', 't2', 't3', 'p2' ];

Note that this will override any future changes to the global list, so you probably should remove it again sooner or later.
Cheers, Amalthea 21:00, 4 January 2009 (UTC)

Ah, cool, will do that - had a couple of people already try and "hang on" an image deletion following a Commons move, changing the config., which I should have thought of, will at least stop that. Thanks. Unusual? Quite ^TalkQu 21:43, 4 January 2009 (UTC)

←I've changed Twinkle's default for user notifications of speedy deletions to not notify in the case of i8. I've also updated the documentation to reflect this. Ioeth (talk contribs twinkle friendly) 17:36, 8 January 2009 (UTC)

Table sorting does not work when either Friendly or Twinkle is enabled

Resolved

I noticed that table sorting (like the table here, which can be sorted by clicking the arrows) will not work, at least for me, when either Friendly or Twinkle is enabled. I tested this and have boiled down to these two; when either one, or both, are enabled, then table sorting will not work anymore (the JS for the table sorting does not do anything; "#" is simply appended to the URL). Since both scripts share some libraries, could there be a common problem here? I don't know when this began, but it was probably within the last week or two. From a cursory check, it looks like the problem might be related to Friendly more than Twinkle as the Friendly scripts seem to have had more updates recently than Twinkle.

Thoughts, please? I've disabled both scripts until this issue is resolved because I deal with table sorting fairly often. Gary King (talk) 18:08, 3 January 2009 (UTC)

Weird. I tried it myself on List of Washington Metro stations with TW and Friendly enabled, and got the same result. I'm running Windows Vista and Firefox 3. SchuminWeb (Talk) 19:34, 3 January 2009 (UTC)

See Wikipedia:Village pump (technical)#Sortable tables & Firefox 3.0.5 for more on that. --Amalthea 17:24, 4 January 2009 (UTC)

It's working again with yesterday's update. --Amalthea 17:19, 7 January 2009 (UTC)

Deprecated CSD options?

Resolved

Twinkle is an excellent tool, especially in parallel with Friendly, thank you. I noticed that several deprecated CSD options are still listed on the CSD popup (R1 for example which is now included in G8; also A1, A6, A8). Regards, Chuckiesdad 02:48, 5 January 2009 (UTC)

Okay... I've gone in and twiddled with Twinkle (combined diffs), and here's what I came up with:

• R1 has been removed from the list per WP:CSD. Along with that, G8's wording has been modified to reflect its new functions.
• A1 is not listed on WP:CSD as being deprecated. Therefore, no action was taken.
• A6 and A8 are not listed for Twinkle's speedy delete box. Therefore, no action was taken.
• Unrelated, but I fixed a capitalization issue that has been bugging me for a while, where G8 would render as "g8" in deletion summaries for deletion of talk pages for freshly deleted articles.

I tested things, and my changes seem to work well, and hopefully I've not introduced new flies into the ointment. SchuminWeb (Talk) 07:03, 5 January 2009 (UTC)

Looks good, the "redirnone" edit summary is still in, but that won't hurt. Cheers, Amalthea 10:42, 5 January 2009 (UTC)

I've gone ahead and removed the unused edit summary. Thanks, Schumin! Ioeth (talk contribs twinkle friendly) 17:40, 8 January 2009 (UTC)

malfunction?

Twinkle seems to be malfunctioning. A little while ago, I used Twinkle to do a "vandalism rollback" on Big Moe. The tool opened a new window for the user's talk page, where I posted a message, but the actual rollback edit was not completed. --Orlady (talk) 21:26, 8 January 2009 (UTC)

That happens occasionally. If it continues to happen, please let me know. Ioeth (talk contribs twinkle friendly) 21:42, 8 January 2009 (UTC)

Internet Explorer

If I have internet explorer, can I still use Twinkle? And if so how other than monobook as I already did that.--Iamawesome800 01:17, 9 January 2009 (UTC)

I'm afraid not, sorry. See WP:TW#Browser support for supported browsers. Maybe installing a second browser is an option? --Amalthea 01:27, 9 January 2009 (UTC)

Epiphany

Seems to work in Epihany too. TheresaWilson (talk) 06:15, 10 January 2009 (UTC)

Twinkle not working?

I am using Mozilla Firefox 3.0.5 and twinkle doesn't seem to be working. I tried clearing the cache and reloading my browser but to no avail. I looked in the error console and keep seeing a "twinklefluff is not defined" message with a link to this: Error: twinklefluff is not defined Source File: http://wiki.riteme.site/w/index.php?title=User:AzaToth/twinklefluff.js&action=raw&ctype=text/javascript Line: 574. Can anyone help? CoreFinder (talk) 22:43, 10 January 2009 (UTC)

Ditto in FF 3.0 on OSX. My twinkle tabs are wholly gone. StarM 03:56, 12 January 2009 (UTC)

Opera Mini

I'm using Opera Mini right now, and I'm noticing that twinkle is somewhat working, but not quite. Should it be? PCHS-NJROTC ^(Messages) 00:16, 11 January 2009 (UTC)

Twinkle is not officially supported in Opera Mini. Sorry. Ioeth (talk contribs twinkle friendly) 14:49, 15 January 2009 (UTC)

Parts of the UI are AWOL

I've noticed that I'm now missing the various rollback options that usually sit beside each rollbackable edit listed on "Special" pages, such as Special:Contributions. Anyone else noticing this? I'm using FF 3.0.5 on Ubuntu 8.10. --Dynaflow babble 22:43, 12 January 2009 (UTC)

I'm guessing you can't see them at your own contributions. Can you see them at my contributions at Special:Contributions/Amalthea? Which other special pages are suddenly missing them? --Amalthea 23:00, 12 January 2009 (UTC)

I wasn't seeing anything on anyone's Special:Contributions before, but now I can see others', but not mine. I'm actually not sure if there really was supposed to be anything at Special:RecentChanges (I'm an infrequent visitor, usually only going there when I see the DefCon rise to 2 or 1), but if there was, there isn't now. --Dynaflow babble 00:06, 13 January 2009 (UTC)

I can't see them at my own contribs, but I can see them at other user's contribs. I was thinking this might be because of admin rollback, but I'm not so sure about that. -MBK₀₀₄ 00:15, 13 January 2009 (UTC)

OK. The change that the rollback links aren't shown anymore on your own contributions only happened a couple of days ago, see the section #'my contributions' page. The list of recent changes and the watchlist have never shown the Twinkle rollback links, as far as I know. They are also not providing WP:ROLLBACK links. I'm not sure why though, with WP:NAVPOP they'd be useful everywhere (including the page history, where the MediaWiki rollback links are shown, but Twinkle's aren't). Cheers, Amalthea 00:25, 13 January 2009 (UTC)

I think I'm having the same problem - no TW rollback links on my own contributions list (but I do have them on others' contributions list), and no rollback links on diffs. Thus all I have is administrative rollback, but not TW rollback. SchuminWeb (Talk) 00:29, 13 January 2009 (UTC)

But Friendly's welcome function, which is in the same place as Twinkle's, shows up just fine. I figure that might be worth noting, since TW and Friendly are sister scripts. SchuminWeb (Talk) 00:30, 13 January 2009 (UTC)

The behaviour with the contributions is OK, but none on diffs? That's new. Just to make sure, you did look at one that could be rolled back, like this one? --Amalthea 00:53, 13 January 2009 (UTC)

Yes - it's consistent across the board on edits that are able to be rolled back (such as your most recent reply when I saw it). As for the contributions, however, I like having that on my own contributions and would support having it back, since I occasionally do need to roll myself back with explanation from there. SchuminWeb (Talk) 00:56, 13 January 2009 (UTC)

← I don't know what's causing those problems then (yours, the ones in #Twinkle not working?, and the one in WT:TW/BUG#TW-B-0241 (new) which are all almost certainly connected), in particular since some of the functionality from twinklefluff seems to be working for you and some isn't - and I can't reproduce any of it. Let's see if Ioeth has an idea.
Concerning the rollback links in your own contributions, the change from above will have to be made configurable then. I could give you the necessary change here, but assuming that you're in no hurry I'll let Ioeth make the change directly. --Amalthea 01:11, 13 January 2009 (UTC)

No hurry whatsoever. Ioeth can work his magic on it as time permits. SchuminWeb (Talk) 02:20, 13 January 2009 (UTC)

I can work on making the change to suppress TW rollback links in your own contributions configurable. I'll probably make it configurable to show rollback links on all contribs pages, all but your own, and hide them all so that everyone can configure it just how they like. As far as the other problems reported in this thread, I have not been able to reproduce them. I still see TW's rollback and vandalism links on another user's contributions page, and still see all 3 options when on a diff page. Do a CTRL+F5 just to make sure you're running on the latest version of the script and let me know if these problems persist. Ioeth (talk contribs twinkle friendly) 14:01, 13 January 2009 (UTC)

Twinkle's rollback links are now configurable. See the updated documentation! Ioeth (talk contribs twinkle friendly) 16:41, 13 January 2009 (UTC)

Time for a love fest at village pump

Let's all get together and figure it out :) thisaway ---> Wikipedia:Village_pump_(policy)#Twinkle Casliber (talk · contribs) 05:30, 19 January 2009 (UTC)

Automatic welcome messages configurable

Ioeth, could you please overwrite the live twinklespeedy.js with my version, if you have no objections, to make the automatic welcome messages configurable (diff)? I've changed the notification templates, have tested it, and will bring the documentation up to date once it's live.
Thanks & Cheers, Amalthea 13:55, 19 January 2009 (UTC)

Done! Thanks for making the change, Amalthea! I'll go update the documentation now. Ioeth (talk contribs twinkle friendly) 13:59, 19 January 2009 (UTC)

Wow, that was fast, thanks! Amalthea 14:04, 19 January 2009 (UTC)

SPI

With the recent merge of WP:SSP and WP:RFCU into WP:Sockpuppet investigations, twinklearv will need to be adapted. I haven't had a much closer look yet, only stumbled across it at WT:SPI#Help. --Amalthea 14:34, 18 January 2009 (UTC)

I've disabled sockpuppet reporting in Twinkle for the time being until the script is updated to handle reports at WP:SPI. Ioeth (talk contribs twinkle friendly) 14:39, 18 January 2009 (UTC)

And I think it'll have to wait a bit until it can be adapted, since the notification process doesn't seem to be quite worked out yet. There aren't any notification templates yet, for example. --Amalthea 15:06, 18 January 2009 (UTC)

Alright, I think I've got Twinkle set up to report to the new WP:SPI, including optional CheckUser requests. Please let me know of any bugs you may encounter and forgive me if it doesn't work, since I didn't do any live testing. Ioeth (talk contribs twinkle friendly) 22:23, 19 January 2009 (UTC)

Unfortunately not! WP:SPI works like WP:RFCU, in that a second investigation should NOT be created as a new page, but as a new section on the previous page. The current set-up is fine for first SPI reports, but the first time we come to report somebody who has been reported before, it will break the system 217.35.113.241 (talk) 12:59, 21 January 2009 (UTC)

Hm, okay I'll look into it. Ioeth (talk contribs twinkle friendly) 14:28, 21 January 2009 (UTC)

Alright, I think I have the script set up to work with the whole new SPI system. If Twinkle does not find a page created for the SPI you want to start, it will create it. If it does find a page, it checks to see if the latest report has been archived. If it has, Twinkle will append a new report to the bottom of the page; if it has not, Twinkle will alert you and ask you if you want to continue. If you do, the script will proceed to tag and notify sockpuppets as it has in the past, and will then attempt to add your information (additional unlisted sockpuppets, additional evidence, additional RFCU) to the open request. We'll see if it works...I have a feeling there will probably be some bugs to work out. Ioeth (talk contribs twinkle friendly) 20:09, 21 January 2009 (UTC)

Doesn't seem to work

I've added the code from the installation instructions to my monobook.js page and purged my server's cache, and yet there seems to be no effect. Any help? Richard BB 18:28, 20 January 2009 (UTC)

I'm assuming you purged your browser's cache, not your server's, with Ctrl+F5 or something similar? What browser are you using? And what skin? --Amalthea 20:30, 20 January 2009 (UTC)

Sorry, browsers, my mistake. And I'm using Mozilla Firefox - what do you mean by what skin? Richard BB 21:21, 20 January 2009 (UTC)

Twinkle only works under some 'skins', the default one, which is called 'monobook' and I think the 'modern' one. Otherwise it doesn't show up at all. Check in your preferences which skin (appearance of the site, colours etc) you've set. It's the second tab along inside your preferences. I had to give up using the 'classic' skin because of this :( I wish Twinkle worked on all the skins. But I got used to the default one after a short time. Sticky Parkin 01:47, 21 January 2009 (UTC)

The reason Twinkle doesn't work is you are a newbie. See this. Oda Mari (talk) 06:29, 21 January 2009 (UTC)

Quite right. You need to be autoconfirmed before using Twinkle. --Amalthea 12:47, 21 January 2009 (UTC)

Ah, I thought that might be the problem, Oda. I did search for any reason that that might be the reason, but couldn't find any. Thanks anyway! Richard BB 17:41, 21 January 2009 (UTC)

TW has stopped running

Hi Twinkle stopped running for me a few days ago and I can't figure out why. Here's the error log:

Error: TwinkleConfig.showRollbackLinks is undefined Source File: http://wiki.riteme.site/w/index.php?title=User:AzaToth/twinklefluff.js&action=raw&ctype=text/javascript Line: 210

Any advice please. Graham Colm ^Talk 18:38, 21 January 2009 (UTC)

It looks like everything should be working based on your monobook.js file. Other folks have the change where that configuration parameter was added and they aren't seeing errors. Please clear your cache and refresh (CTRL + F5) to see if the problem goes away. Ioeth (talk contribs twinkle friendly) 18:42, 21 January 2009 (UTC)

Thanks, but I tried that a few times, but it didn't help :( Graham. Graham Colm ^Talk 18:47, 21 January 2009 (UTC)

? Four minutes before you posted here, you made this revert with Twinke. Seems to be working just fine. Where are you getting the error? --Amalthea 19:10, 21 January 2009 (UTC)

This is weird, I didn't use Twinkle ?? I used "Restore this version" Graham. Graham Colm ^Talk 21:58, 21 January 2009 (UTC)

The "restore this version" link is put there by Twinkle, see WP:TW/DOC#Additional links. Ioeth (talk contribs twinkle friendly) 22:01, 21 January 2009 (UTC)

I mentioned above that I thought it was fixed -- but my tabs have gone AWOL again. All Twinkle tabs, gone :( FF 3, Mac OSX, no changes to anything StarM 01:54, 22 January 2009 (UTC)

TwinkleConfig disables Twinkle on contribution and diff pages?

When I use TwinkleConfig to configure Twinkle, it disables Twinkle on contribution and diff pages. Why is this happening? Here is my configuration: User:Gary King/config.js Gary King (talk) 06:38, 22 January 2009 (UTC)

Try adding the following to your TW config section:

showRollbackLinks			:	[ 'diff', 'others', 'mine', 'contribs' ],

--Dynaflow babble 09:31, 22 January 2009 (UTC)

That would work, but is only a workaround. Gary, the reason is that you are overwriting all default values in your config.js. Replace

TwinkleConfig = 
{
	userTalkPageMode : 'tab',
	summaryAd : "",
	deletionSummaryAd : "",
	protectionSummaryAd : "",
	watchSpeedyPages : [],
	watchProdPages : false,
	watchRevertedPages : [],
	watchWarnings : false,
	offerReasonOnNormalRevert : false,
};

with

if( typeof( TwinkleConfig ) == 'undefined' ) TwinkleConfig = {};
TwinkleConfig.userTalkPageMode = 'tab';
TwinkleConfig.summaryAd = "";
TwinkleConfig.deletionSummaryAd = "";
TwinkleConfig.protectionSummaryAd = "";
TwinkleConfig.watchSpeedyPages = [];
TwinkleConfig.watchProdPages = false;
TwinkleConfig.watchRevertedPages = [];
TwinkleConfig.watchWarnings = false;
TwinkleConfig.offerReasonOnNormalRevert = false;

and it will work.
Ioeth, I would actually recommend that we change the documentation to not suggest overwriting the TwinkleConfig in toto, but do it similar to the above. That way, new config values will still survive, while currently users will end up with a lot of undefined config values. For example, I didn't make sure to test if welcomeUserOnSpeedyDeletionNotification is defined before use in twinklespeedy, so I expect that editors with a customized configuration will get an exception there and won't be notifying users about speedy deletions at all now. Not quite what I had in mind. :| --Amalthea 13:16, 22 January 2009 (UTC)

Actually, that might just be the reason why the Gadget description used to say that you can't configure it if used that way. When I look at the html code for this page, the gadget js is probably executed before the monobook.js is. In contrast, if you import Twinkle.js in your monobook and then define TwinkleConfig, it is most probably going to finish execution of the monobook.js, and will only then start executing Twinkle.js and friends (due to the way importScript works).
The reason why it isn't working for Gary above is that he defines the TwinkleConfig in an imported script, too, which will in turn be executed after Twinkle.js even though he doesn't use the gadget.
I'm just going to go ahead and change the documentation, since configuring the gadget version was explicitly discouraged until recently I don't think that there are that many broken configurations at this point (meaning that I don't think it's necessary to fix the twinkle scripts, to make sure that a config value is defined before use). --Amalthea 13:37, 22 January 2009 (UTC)

All of the Twinkle scripts check to make sure that not only TwinkleConfig is defined, but each of the configuration variables that the script uses within TwinkleConfig are defined as well. If any are not defined, it will define them to the default values. Have a look at my monobook.js file and you'll see that I'm only defining a handful of the configuration variables for both Twinkle and Friendly, and it works fine because both scripts check for this. Ioeth (talk contribs twinkle friendly) 14:04, 22 January 2009 (UTC)

Yes, but you are importing User:AzaToth/twinkle.js in your monobook.js, which means that e.g. twinklefluff.js will also be executed afterwards, and it will then pick up all undefined config values and initialize them.
However, if twinklefluff.js is executed *first*, it will initialize all config values (since they are all undefined); afterwards, your monobook.js is executed, and will set a new version of TwinkleConfig. I'm sure that if you try removing the import statement from your monobook and enable the Gadget version instead, then e.g. TwinkleConfig.notifyUserOnSpeedyDeletionNomination will not be defined (test it in Firebug). --Amalthea 14:18, 22 January 2009 (UTC)

Ah, excellent point. You are correct. Ioeth (talk contribs twinkle friendly) 14:26, 22 January 2009 (UTC)

Thanks, that fixed it. Why did Twinkle only break on diff and contribution pages, but still worked on others? Gary King (talk) 16:34, 22 January 2009 (UTC)

It didn't really break; you implicitly configured TwinkleConfig.showRollbackLinks = [];which in turn suppressed the rollback links on diffs and contributions. --Amalthea 16:56, 22 January 2009 (UTC)

Ah; well, nice to know it doesn't break easily. Gary King (talk) 17:16, 22 January 2009 (UTC)

Disable batch deletion tabs

Greets, is it possible to deactivate and remove the d-batch, p-batch, and und-batch tabs? Given I never use this functionality and that they take up quite a bit of real-estate, this would be very useful. — Huntster (t • @ • c) 18:14, 22 January 2009 (UTC)

If you import the scripts individually rather than using the gadget or importing the whole thing, you can pick and choose which ones you like. See my monobook for an example of this. –xeno (talk) 18:18, 22 January 2009 (UTC)

I'm not using the gadget, just importing the entire package rather than individual modules. I was hoping there was a config bit somewhere to allow deactivation, but I'll take your advise and use the individual modules. Thanks. — Huntster (t • @ • c) 18:39, 22 January 2009 (UTC)

oh, I must've surfed to the wrong page, I thought you had a blank monobook Not that I know of, but I could be wrong. what I do is just comment out the ones I don't use on a regular basis so I can easily activate them on a one-off basis. –xeno (talk) 18:42, 22 January 2009 (UTC)

Very good idea, thanks for the feedback :) — Huntster (t • @ • c) 18:58, 22 January 2009 (UTC)

Xeno is right, there is no config option. I'd recommend taking the individual script imports from User:AzaToth/twinkle.js, xeno apparently has already removed a bunch. Cheers, Amalthea 19:08, 22 January 2009 (UTC)

Twinkle and Safari

I've been using Twinkle with Safari for a long time. Mostly, I have had a good experience with it, with just a few hiccups. However, starting on Monday, something strange has been happening. Usually, when I get a diff in an article, I get a few buttons (I'll call them buttons for a lack of better term) that say Rollback AGF, Rollback and Rollback vandalism. Then suddenly, without updating Safari (there hasn't been an update for awhile now), I no longer see those buttons unless I reload the page. I have cleared the cache, restarted (something we Mac people rarely do), etc. Nothing works, except a reload. Any ideas? Maybe I've got some bad code in my monobook, but since I'm not an expert on that, I wouldn't know. OrangeMarlin ^{Talk• Contributions} 17:14, 14 January 2009 (UTC)

Same for me, twinkle doesn't work in Firefox 3.0.5. I'm using Windows XP so its not an isolated case. I think there is something wrong with the code in Twinkle. CoreFinder (talk) 00:02, 15 January 2009 (UTC)

Your problem, CoreFinder, is that your user account is new and you have very few edits, so you is not autoconfirmed yet. Twinkle only works for autoconfirmed users. The problem that Orangemarlin is having is something different. Ioeth (talk contribs twinkle friendly) 14:00, 15 January 2009 (UTC)

OrangeMarlin, I took your monobook.js file on a test drive this morning and everything seems to be working just fine with it. I checked with a number of articles to make sure that the rollback links were available on the top diff, and they were. Do you have Firefox installed on your system to do a test with that? Ioeth (talk contribs twinkle friendly) 14:06, 15 January 2009 (UTC)

Yes, it works on Firefox. Not on Safari. I prefer Safari, since all my bookmarks are synchronized across multiple computers. Why would it suddenly quit working on Safari? OrangeMarlin ^{Talk• Contributions} 01:00, 16 January 2009 (UTC)

I'm not sure. It probably has something to do with the way that Safari processes JavaScript. My guess is that for some reason it's not processing the onLoad instructions correctly, or processing them before the page is fully loaded, resulting in the links not being displayed. Ioeth (talk contribs twinkle friendly) 14:39, 16 January 2009 (UTC)

It's getting worse. Early this week, I could just hit a reload, and the buttons magically appear. Now it doesn't. The thing is, I haven't changed a thing with my computer, there haven't been any updates to Safari or javascript (for the Mac), etc. It's like magic, but WP:FRINGE applies. Well, if anyone thinks of anything, I'm willing to try it. I'm using Firefox for the time being. Thanks for the ideas.OrangeMarlin ^{Talk• Contributions} 17:30, 16 January 2009 (UTC)

←I'm having the same problem - I use Safari, it's been working fine for months, and now it isn't. Very irritating... _TalkIslander 12:05, 19 January 2009 (UTC)

I just tried it with your monobook.js and my Safari on Win XP, and it's working fine here. Assuming that you tried clearing your cache and it's still not working: Do you have any kind of web filtering software, or a personal firewall running? Any ad blocking extensions? If you have a look at the error console (you might have to enable the developer menu first in the advanced settings), does it say anything? --Amalthea 12:28, 19 January 2009 (UTC)

I use a Mac. We don't need no steenking firewall.  :) Anyways, I think there's enough difference between Safari on Win XP and on the Mac (possibly as a result of the javascript implementation) that we might need a Mac OSX user with Safari trying it out. And to seriously answer your question, I do not have a firewall running, and I don't use web filtering of any sort. OrangeMarlin ^{Talk• Contributions} 18:02, 20 January 2009 (UTC)

For me it's the other way around

Twinkle not working for me at all in Firefox (have no XfD or other realted tabs - Adblock disabled since that was causing problems some months ago) but if I log in using Safari, it's all there. I prefer not to use Safari since I'm not as familiar with it. Oddly, my other scripts appear to work fine. StarM 06:54, 18 January 2009 (UTC)

I'm noticing the same thing. I have no tabs or any other Twinkle (or Friendly) elements showing up in either Firefox or Opera. --Dynaflow babble 20:49, 18 January 2009 (UTC)

all appears fixed. Thanks to whomever's been hard at work! StarM 05:04, 19 January 2009 (UTC)

Turns out my problem is unrelated, but interesting

What seems to have happened to me was that, by adding Friendly's full configuration script and keeping everything in the default configuration but the three variables I wanted to change (to get rid of the new clock thing and to stop it from adding things to my watchlist), I completely hosed TW somehow. These are the settings I was using:

importScript('User:Ioeth/friendly.js');
FriendlyConfig = {
	summaryAd			:	" using [[WP:FRIENDLY|Friendly]]",
	enableClock			:	false,
	clockStyle			:	"dynamic",
	topWelcomes			:	false,
	watchWelcomes			:	false,
	markWelcomesAsMinor		:	true,
	insertHeadings			:	true,
	welcomeHeading			:	"== Welcome ==",
	insertUsername			:	true,
	insertSignature			:	true,
	quickWelcomeMode		:	"auto",
	quickWelcomeTemplate		:	"Welcome",
	maskTemplateInSummary		:	true,
	markSharedAsMinor		:	true,
	groupByDefault			:	true,
	watchTaggedPages		:       false,
	markTaggedPagesAsMinor		:	true,
	markTaggedPagesAsPatrolled	:	true,
	idsToRename = [
		{ id: 'ca-nstab-main', name: 'Main', mainPageOnly: true },
		{ id: 'ca-nstab-help', name: 'Help' },
		{ id: 'ca-nstab-special', name: 'Special' },
		{ id: 'ca-nstab-project', name: 'Project' },
		{ id: 'ca-nstab-user', name: 'User' },
		{ id: 'ca-edit', name: 'Edit' },
		{ id: 'ca-viewsource', name: 'Source' },
		{ id: 'ca-talk', name: 'Talk' },
		{ id: 'ca-undelete', name: 'Undelete' },
		{ id: 'ca-addsection', name: '+' }
	]
};

Anybody have some insight on what might have happened here? As soon as the above goes into my monobook, all TW and Friendly functionality immediately disappear. Get rid of FriendlyConfig, clear the cache, and they come back. --Dynaflow babble 11:06, 19 January 2009 (UTC)

There's a syntax error, "idsToRename" should be followed by a colon, not an equals sign: "idsToRename : [". --Amalthea 11:38, 19 January 2009 (UTC)

Durp; I'm blind. I'll head over and change it at WP:FRIENDLY's documentation. --Dynaflow babble 11:43, 19 January 2009 (UTC)

Thanks. I wonder how many recent Twinkle problems have been caused by dual users of TW and Friendly who hurriedly pasted in the faulty config script from the Friendly page in order to get rid of Friendly's new clock feature. --Dynaflow babble 11:49, 19 January 2009 (UTC)

I'm afraid that honor is yours and yours alone, I just checked the monobook.js pages of all who made a mention of weird problems, but none had that part of the configuration in it. :) --Amalthea 12:03, 19 January 2009 (UTC)

Drat, uniqueness persists. Just out of curiosity, I'm wondering how a bad line in FriendlyConfig was able to completely cripple Twinkle. Is it technically feasable to keep problems in one of these closely-related programs from interfering with the other program? As a non-sequitor, are any of the above users using the "Modern" skin? Under My Preferences -> Gadgets there's a checkbox for a compatibility function that TW and Friendly supposedly require to run under that skin. Also in the same place, there are a couple more options that Safari users apparently might need to enable, such as the JavaScript Standard Library and DejaVu Sans. --Dynaflow babble 12:39, 19 January 2009 (UTC)

Dyanflow, the reason that a problem with Friendly's config like you had will cripple Twinkle is actually not specific to these two tools. Any time a browser's JavaScript processor detects an error, it halts the script that the error occurred in. Since this error is in your monobook.js file, that means that nothing in your monobook.js file is processed, including Twinkle's configuration or any other import statements you might have had. Sorry for the bug! Ioeth (talk contribs twinkle friendly) 14:54, 19 January 2009 (UTC)

My safari TW was broken too suddenly the past week, I had no rollback links anymore. I just fixed it by moving the importScript('User:AzaToth/twinkle.js'); line to the bottom of my monobook.js file, below the TwinkleConfig section. It has lived happily above that section for a year or so so who knows what changed but the instructions said to make sure it was at the bottom and moving it fixed it. My working monobook.js Mfield (talk) 18:18, 24 January 2009 (UTC)

This worked. I'm ecstatic. Thanks!!!!!! OrangeMarlin ^{Talk• Contributions} 05:06, 25 January 2009 (UTC)

Twinkle gone in Safari

I've asked at the help desk but so far, nobody has been able to help me. So, I'm wondering if someone here might have a better idea of what's going on.

Lately, the "Rollback (AGF)" and "Vandalism" links that appear in green and red in a comparison of article versions don't show up. The "Restore this version" link is still present but neither of the others. Does anyone have a clue as to why? I'm running the latest Safari and OS X versions. All software is up to date according to the system's software updater. I've tried resetting Safari but that didn't work. Dismas|^(talk) 01:11, 25 January 2009 (UTC)

I had this problem and I fixed it today by moving the order of things in my monobook file so that the Import lines were below the TwinkleConfig section as suggested on the Twinkle page. I posted more on the section further up, you'll find it a few entries ago in the history of this page. Mfield (talk) 01:15, 25 January 2009 (UTC)

That got it. After resetting Safari, of course. Thanks! Dismas|^(talk) 05:01, 25 January 2009 (UTC)

Fix the message sent to WP:RPP for reports

When sending a page to WP:RPP with Twinkle, the message sent is currently "<MESSAGE>.<SIGNATURE>". Could the fixed period be removed, and a space be added between the message and the signature? Gary King (talk) 04:25, 24 January 2009 (UTC)

To make these changes, edit this page: User:AzaToth/twinkleprotect.js

Remove the following (to remove the extra period):

		if( reason != '' ) {
			reason += '.';
		}

And find this:

+ "\~\~\~\~";

Replace it with (to add a space before the signature):

+ " \~\~\~\~";

Done Gary King (talk) 18:36, 24 January 2009 (UTC)

Fixed. Sorry about that. I probably made that typo when I fixed the protection script. Ioeth (talk contribs twinkle friendly) 20:17, 24 January 2009 (UTC)

You're not going to remove the extra period though? Most people type messages out in full sentences, so they end up with two periods at the end. The script shouldn't assume that the user will not include the final period; in fact, scripts should do the least tampering with messages submitted by users. Gary King (talk) 20:35, 24 January 2009 (UTC)

Any particular reason why the extra period will not be removed? Gary King (talk) 01:49, 26 January 2009 (UTC)

How about this. That way, if you include a period, Twinkle won't, and if you forget it, Twinkle will add it for you. Sound good? Ioeth (talk contribs twinkle friendly) 15:34, 26 January 2009 (UTC)

Okay Gary King (talk) 17:21, 26 January 2009 (UTC)

Twinkle and my watchlist

I usually patrol recent changes, and when I revert vandilism on an article, the article is added to my watchlist. When I don't use twinkle it doesn't happen. Does anybody know why? ♣PrincessClown♥ 23:53, 25 January 2009 (UTC)

Standard rollback is marked as minor. Twinkle rollback is not. Same with me. I have my settings so that anything I edit gets added to my watchlist, but since normal rollback is marked as minor, it does not get added. Not sure why normal rollback doesn't get added while regular minor edits do, though. Enigma^msg 03:47, 26 January 2009 (UTC)

See Wikipedia:TW/DOC#Configuration and Wikipedia:TW/DOC#watchRevertedPages for an explanation of why this happens and how you can configure it to not happen. Ioeth (talk contribs twinkle friendly) 15:30, 26 January 2009 (UTC)

Just as a point of order the fact that it's a minor edit has nothing to do with why native rollback doesn't add pages to watchlists... –xeno (talk) 15:34, 26 January 2009 (UTC)

Group noms

Is there any particular way to perform group noms automatically with Twinkle, or is it a manual process? I've tried looking for documentation with no luck, and also tried looking at how actual group noms were done, but couldn't really figure it out - there seem to be a number of methods. Am I missing something obvious (or not-so-obvious) here? (this applies to XfDs in general, really, not any specific one) 「ダイノガイ千？！」^{(Dinoguy1000)} 20:06, 27 January 2009 (UTC)

You'd have to nom each one separately I believe. How many are you planning to nom at the same time, anyways? Gary King (talk) 20:14, 27 January 2009 (UTC)

Actually, I'm not asking out of present necessity, this is a problem I've had before and couldn't really figure out. I finally decided to just ask about it. 「ダイノガイ千？！」^{(Dinoguy1000)} 20:24, 27 January 2009 (UTC)

If you need to nominate ten articles to AfD at the same time, then perhaps you aren't doing research on their notability long enough :) If it's ten related articles that should be sent to AfD, then you could just AfD one of them and link to the others in the nomination. Gary King (talk) 20:27, 27 January 2009 (UTC)

Well, like I said at first, I'm asking about XfDs in general, AfD group noms actually seem fairly straightforward (although I'm hesitant to nom a single article for AfD, much less ten at once @_@ ). Specifically, is there any special trick to TfDs or (particularly) CfDs? 「ダイノガイ千？！」^{(Dinoguy1000)} 20:30, 27 January 2009 (UTC)

The standard manual procedure for doing a bulk XfD is not that much different than XfDing a single page. You follow all of the same steps, then go around and place {{afd|FIRST PAGE TITLE}} (or relevant XfD template) on all of the pages you wish to be part of the same discussion, replacing "FIRST PAGE TITLE" with the title of the first article you nominated. After that, just write a bulleted list of all of the articles on the XfD discussion page. We could probably include support for bulk nominations in Twinkle, but it would ask you for all of the other pages you wish to include in the nomination (kind of like how TW's sockpuppet reporting works). I have a feeling, though, that it would get misused because people would forget that bulk noms are supposed to be related in some way. Ioeth (talk contribs twinkle friendly) 20:33, 27 January 2009 (UTC)

Perhaps this would be a good time, then, to remind you of the "you take full responsibility" notice at the top of WP:TW? ;) Regardless, it's not like I'm going to press you to add that feature, but if you did care to add it, it could be something along the lines of a link in the popup box saying "Add additional [articles/categories/templates/etc.] to this nomination" (I've never filed a sockpuppet report, so I don't really know how that works). Depending on the type of XfD, it would come up with a variable number of initial fields (I haven't seen very many recent AfDs where more than one article was nominated, and even then, it's usually just two or three articles; on the other hand, CfD rename discussions seem to routinely involve five to ten or even more categories at once), with a link to add even more if necessary. If it worries you that much, you could also plop a big disclaimer or something restating the whole "you are responsible" tidbit. (gah, and when I said I wouldn't press you... XD ) 「ダイノガイ千？！」^{(Dinoguy1000)} 20:47, 27 January 2009 (UTC)

Heh, sounds like you HAVE thought it out so much! You and I are on the same page. You can check out what I mean about the sockpuppet reporting functionality of Twinkle without actually filing a sockpuppet report. Go to someone's user page and click the "arv" tab, then change the selection box to "Sockpuppeter". Then check out how you can click the "more" button to add more sockpuppets to the report. I'm sure I could do something very similar for XfD nominations as well. Sound good? Ioeth (talk contribs twinkle friendly) 20:52, 27 January 2009 (UTC)

Aah, very clean, simple interface. I'm normally leery of checking stuff like that out, because I'm afraid I'll accidentally do something when I don't mean to. Altogether, though, it sounds quite nice (a feature to automatically list the discussion on delsort pages would also be cool, but there's plenty of tools that can already do that, so it's no big deal). 「ダイノガイ千？！」^{(Dinoguy1000)} 21:20, 27 January 2009 (UTC)

account

it says my account is to young to use this! —Preceding unsigned comment added by JDOG555 (talk • contribs) 01:16, 28 January 2009 (UTC)

Yes, you need to have been here a few days and made some constructive edits. Note that your contributions includes vandalism. Twinkle is to fight vandals, not enable them. Please show that you can be trusted with this by making only constructive edits to the Wikipedia project. Thanks! (EhJJ)^TALK 01:48, 28 January 2009 (UTC)

"Warn" as a button similar to Friendly's "welcome" feature

I use Twinkle regularly in regards to vandalism, mainly in issuing warnings. When reverting vandalism, I use the administrative rollback rather than TW's, so I don't get the pop-up talk page. What I've found myself doing is using Friendly's "Welcome" button to leapfrog over to the talk page, close the welcome box, and then hit the "warn" tab to issue my warning, rather than giving the welcoming that the button was designed for. I do this mainly because it pre-fills the article title. Would it be possible to add a "warn" button like that similar to Friendly's "welcome" so that the article title is pre-filled? I'd stop short of having the warn box automatically pop in when jumping to the talk page with such a command, however, since often I need to peruse what other warnings have been given before I place my own warning, but having the title box pre-filled would be the main benefit. Perhaps the decision about whether or not to pop the box automatically could be made configurable.

What does everyone else think? Is this a good addition to Twinkle? SchuminWeb (Talk) 03:45, 31 January 2009 (UTC)

I'd enjoy that, too. I'd think that Twinkle should either open the talk page in preview mode automatically after a rollback (just as it does after a Twinkle rollback), or as you recommend providing a warn tab or a [Warn] link. Another variant would be to only extend the user talk link after a successful rollback with "vanarticle=TheRevertedArticleName", which will enable prefilling it in the dialog once you followed it.
I personally would go with consistency, and have it behave just like with Twinkle rollback. Not sure if that should be the default behaviour though. Also, I'd have the warning dialog pop open immediately, since I'll use it more often then not and can still see existing warnings in the background to choose an appropriate warning level. --Amalthea 13:34, 3 February 2009 (UTC)

Ix CSD criteria now Fx

Having noticed that the "I" CSD criteria have been renamed to "F" criteria due to the Image namespace's change to File, I have adjusted Twinkle accordingly for this and fixed a bunch of double redirects. I've tested things, and they seem to work, but please say something if I inadvertently broke something. SchuminWeb (Talk) 04:43, 1 February 2009 (UTC)

'my contributions' page

on the 'my contributions' page, is there a way to get rid of the: " [rollback] [vandalism]" links? i don't find them useful and it's otherwise very distracting. --emerson7 21:08, 22 December 2008 (UTC)

No easy way for you, but Ioeth might be willing to change Twinkle accordingly. It makes sense to me to generally suppress the links for the own contributions, without a config switch. They are still visible in the diff view where it's far more likely that one wants to revert ones own edit (although the "rollback (vandal)" link won't ever be used).
Ioeth, if you're interested, in User:AzaToth/twinklefluff.js change

  if( wgNamespaceNumber == -1 && wgCanonicalSpecialPageName == "Contributions" ) {

to

  if( wgNamespaceNumber == -1 && wgCanonicalSpecialPageName == "Contributions" ) {
  
  	//Get the username these contributions are for
  	username = document.evaluate( 'substring-after(//div[@id="contentSub"]//a[@title="Special:Log"][last()]/@href, "user=")', document, null, XPathResult.STRING_TYPE, null).stringValue;
  
  	if( wgUserName != username )
  	{

... and close the block again right before the } else {
Amalthea 03:39, 23 December 2008 (UTC)

...i'm sorry, am i supposed to try this on my monobook.js page? --emerson7 03:52, 6 January 2009 (UTC)

That would take a little more effort. Let's wait until Ioeth has a little more time again, and can have a look at it. If he doesn't want to change Twinkle accordingly we can still set you up with a private version of twinklefluff. --Amalthea 03:59, 6 January 2009 (UTC)

In August, someone expressed a desire to suppress those links in all user contributions pages (not just "my contributions"), so I set up my alternate account to do that. If you're interested in implementing this for yourself, just replace the line importScript('User:AzaToth/twinkle.js');   in your monobook.js with importScript('User:Xaradnam/twinkle.js');

I have since updated that file several times to mirror edits made to the "official" version.

Remember to refresh your browser and bypass your cache the first time.  mandarax • xɐɹɐpuɐɯ  11:46, 7 January 2009 (UTC)

←I've changed Twinkle so that the rollback links it usually adds to contributions pages are not added if you are on your own contributions page. Thanks for the code, Amalthea! Ioeth (talk contribs twinkle friendly) 17:31, 8 January 2009 (UTC)

While you're in a changing mood, please consider adding an option to suppress the rollback links on all Contributions pages.

I've never used them because I want to see what I'm reverting before I revert it. I've only reverted from a Contributions page once. A vandal had rapidly made the same destructive edit to many templates and I reverted them from the vandal's Contributions page, but I used WP:Rollback which is much, much faster than Twinkle's.

Implementing this would be simple. Just add a configuration parameter, say rollbackOnContributionsPages. Set its default value to what you think is appropriate (false, as far as I'm concerned, or true for continuity), then change the same line above to read:

  if( TwinkleConfig.rollbackOnContributionsPages && wgNamespaceNumber == -1 && wgCanonicalSpecialPageName == "Contributions" ) {

Thanks,  mandarax • xɐɹɐpuɐɯ  22:40, 8 January 2009 (UTC)

There is now a configuration parameter to define where you would like to see Twinkle's rollback links. Please see the updated documentation page. Ioeth (talk contribs twinkle friendly) 16:40, 13 January 2009 (UTC)

Thanks! I've changed my workaround mentioned above so that it simply sets the new parameter and imports the official twinklefluff. I don't know how many people were using my version besides the person who originally requested it, but now I don't have to keep updating it whenever the official twinklefluff is updated. Thanks again! mandarax • xɐɹɐpuɐɯ 20:10, 15 January 2009 (UTC)

I prefer to have the rollback links on my contributions page, because it's easier to see where I have the top revision. I've tried putting in the configuration that would put it back, but it doesn't seem to work. Can someone help me out? seresin ( ¡? )  03:41, 26 January 2009 (UTC)

Seresin, this was almost correct, but you forgot to end the line above it with a comma. If you do that and reload the script with Ctrl+F5 they will show again. --Amalthea 15:38, 12 February 2009 (UTC)