Wikipedia talk:Twinkle/Bugs/Archive 3

Archive 1

Archive 2

Archive 3

Archive 4

Archive 5

TW-B-0201

Status:  Resolved

Resolution:  Fixed

When clicking the "vandalism" link on a user's contributions, it is showing the diff instead of reverting it. --Snigbrook ^(talk) 18:08, 3 September 2008 (UTC)

I am having this same problem. When I click on the "Vandalism" link on TWINKLE, it goes to the current diff and only undoes one edit (not 2, 3 or however many). This also happens with the "Rollback" link as well. This began sometime last night. Is this an ongoing issue? - NeutralHomer • Talk 21:08, 3 September 2008 (UTC)

I don't think it's undoing any edits from user contributions; one example is on Church (building):[1]. I know this happens when the edit has already been reverted, or there is a more recent edit (it also provides a link to the next edit) but on this occasion the vandalism was the most recent edit. It reverted when I went to the diff and clicked on the "vandalism" link there. --Snigbrook ^(talk) 23:33, 3 September 2008 (UTC)

I don't know if it makes a difference what browser is being used; mine is Firefox 3.0.1 on Windows XP. --Snigbrook ^(talk) 23:35, 3 September 2008 (UTC)

Fixed. Ioeth _{(talk contribs friendly)} 19:31, 14 November 2008 (UTC)

TW-B-0202

Status:  Closed

Resolution:  Invalid- Please see Wikipedia:Twinkle/doc#Configuration for information on how to change Twinkle's minor defaults. Post on WT:TW if you need help setting up the configuration. Ioeth _{(talk contribs friendly)} 16:41, 15 October 2008 (UTC)

This could just be because I'm unfamiliar with the interface, having recently installed it, but as far as I can tell, Twinkle does not have an option to choose whether to mark edits as minor. This was causing problems for me, as I had 'mark all edits as minor by default' in my preferences - meaning several edits were marked as minor that really shouldn't have been. I've since disabled this option, but it does seem to highlight a potential problem - or is there a 'minor/not minor' button I'm missing somewhere? Terraxos (talk) 07:51, 12 September 2008 (UTC)

TW-B-0203

Status:  Closed

Resolution:  Fixed

Extra brackets are showing up in the edit summary when I list something at RFD. See this diff as an example. Ten Pound Hammer and his otters • ^{(Broken clamshells • Otter chirps • HELP)} 19:12, 15 September 2008 (UTC)

I mentioned this in TW-B-191 as another typo to be fixed. --Snigbrook ^(talk) 22:34, 21 September 2008 (UTC)

Fixed. Ioeth _{(talk contribs friendly)} 19:42, 12 November 2008 (UTC)

TW-B-0204

Status:  Resolved

Resolution:  Fixed

When I used Twinkle to protect a page and give it an expiry time, it adds the template correctly showing the expiry date [2] but actually carries out the protection as 'indefinite' [3]. — Xy7 (talk) 18:29, 22 September 2008 (UTC)

This just happened to me as well with World War III. This needs to be fixed as it adds additional work to all of us who use twinkle to protect articles. -MBK₀₀₄ 21:46, 5 October 2008 (UTC)

The protection level page has changed somewhat since this script was last updated. I will try to work on this function when I have time. Ioeth _{(talk contribs friendly)} 18:09, 17 October 2008 (UTC)

I have finally fixed this problem. Let me know if it does anything funky; a lot of new code was required. Ioeth _{(talk contribs friendly)} 19:22, 20 November 2008 (UTC)

TW-B-0205

Status:  Closed

Resolution:  Works for me- This is a problem on the user's end, not with Twinkle itself. Ioeth _{(talk contribs friendly)} 19:44, 12 November 2008 (UTC)

On users and IP's with talk pages with existing edits on them do not have the warning tabs. Cocoaguy ここがいい_contribs^talk Review Me! 23:59, 22 September 2008 (UTC)

Cocoaguy ここがいい_contribs^talk Review Me! 00:20, 23 September 2008 (UTC)

I see them, on the page [4]. Have you tried clearing cache/Shift+F5? nneonneo ^talk 22:15, 13 October 2008 (UTC)

TW-B-0206

Status:  Resolved

Resolution:  Fixed

not quite a bug, though it has caused me (and others) some headaches. Twinkle defaults to marking all forms of rollback (agf, vandal, normal, and torev) as minor. not considering this, I got myself a short block for unintentionally marking normal reverts as minor, and I know of at least one other editor who's had this happen. Marking vandalism minor by default is fine, but could we remove the default minor tag from agf and normal (and maybe torev, though I don't know what that means...)? It would save confusion for others down the line. plus, AGF and Normal reverts should probably not be minor in any case. Ludwigs2 20:47, 26 September 2008 (UTC)

I'll be looking into this soon. Ioeth _{(talk contribs friendly)} 14:51, 18 November 2008 (UTC)

The defaults have been changed. By default, agf, norm, and torev reversions will not be minor, and neither will be CSD tagging. vand reverts will still be minor. Ioeth _{(talk contribs friendly)} 20:27, 19 November 2008 (UTC)

TW-B-0207

Status:  Closed

Resolution: none

Whenever I use the A7 (Unremarkable people, group, web content etc.), the script seems to get stuck on checking the page for existing tags. It works for all other tags. I even left it for a long time, and It still for checking the page. It's pretty annoying because I use that tag a lot. Thanks. Olly¹⁵⁰ 21:03, 29 September 2008 (UTC)

Same issue, though it seems to be more prevalent with db-bio. - Realkyhick (Talk to me) 23:37, 29 September 2008 (UTC)

Db-bio definitely has a hitch, as do AFDs not adding the AFD template or AFD log entry. Rob Banzai (talk) 19:26, 30 September 2008 (UTC)

Is this issue still occurring? If so, please post new details; if not, I will close this bug in a few weeks. Ioeth _{(talk contribs friendly)} 14:51, 18 November 2008 (UTC)

TW-B-0209

Status:  Resolved

Resolution:  Fixed- Twinkle relies on the headings on these pages to follow some standard and remain constant. When they are changed, it breaks Twinkle. The changes seem to have been reverted, though. Repost if the issue continues. Ioeth _{(talk contribs friendly)} 19:48, 12 November 2008 (UTC)

Every time I try to do a CFD, I get "failed to find the target page to add the discussion to" and have to add the discussion manually. This is now happening with AFDs as well. Ten Pound Hammer and his otters • ^{(Broken clamshells • Otter chirps • HELP)} 19:49, 3 October 2008 (UTC)

This also just happened to me, and it was my first CfD nom ever... *cries* —Dinoguy1000 21:46, 21 October 2008 (UTC)

This seems to be fixed for CfDs, I used Twinkle to do one yesterday without the error. —Dinoguy1000 18:23, 5 November 2008 (UTC)

TW-B-0210

Status:  Resolved

Resolution: Withdrawn - Working normally.

Occasionally, Twinkle is missing half of a CSD when performed. It is notifying editors of the CSD, but not adding CSD tags to the article concerned. I have been doing new page patrol and had to go back twice tonight to add tags manually, despite the CSD screen showing "Tagging completed". Thor Malmjursson (talk) 02:23, 9 October 2008 (UTC)

Could you please provide some diffs of the problem and list what browser you are using? Thanks! Ioeth _{(talk contribs friendly)} 16:38, 15 October 2008 (UTC)

Withdrawn! Twinkle is now working correctly, no need to proceed with this report :) Thanks! Thor Malmjursson (talk) 15:56, 5 November 2008 (UTC)

TW-B-0211

Status:  Closed

Resolution: User was using IE, and has switched to Firefox. Ioeth _{(talk contribs friendly)} 16:37, 15 October 2008 (UTC)

Well, I bypassed my browser's cache, and everytime I F5 my page, it always says "I'm too new to use Twinkle". Technically, I'm not that new - I've been on Wikipedia for years but had a name usurption a few weeks ago. Is that still old? I don't connect through a Tor network, I have restarted my browser, and fixed my monobook. I simply don't understand why it fails to work for me; thanks, Ay ^{(Reply!,Contribs!)} 21:13, 13 October 2008 (UTC)

Ten days and four edits; I'd say you're probably autoconfirmed. When you go to view source, there's a line starting with "var wgUserGroups = ", what comes after that? nneonneo ^talk 22:13, 13 October 2008 (UTC)

TW-B-0212

Status:  Resolved

Resolution:  Fixed

The tool is listing CSD nominations as "minor edits". Per consensus at WP:ANI, CSD noms shouldn't be listed as minor edits, because many people have set their watchlist to not display minor edits. Could you change it? Erik the Red 2 ~~~~ 02:27, 14 October 2008 (UTC)

I'll be looking into this soon. Ioeth _{(talk contribs friendly)} 14:52, 18 November 2008 (UTC)

CSD nominations are now marked as minor by default. This can still be overridden by preferences. Ioeth _{(talk contribs friendly)} 20:28, 19 November 2008 (UTC)

TW-B-0213

Status:  Closed

Resolution:  Invalid

I have Twinkle configured to not watch talk pages where I place warnings, yet all pages where I leave warnings land in my watchlist.

Unlike B-143 above, with me all the entries in the "Watchlist" tab of my preferences are unchecked, so that's not the reason.

My Twinkle settings:

    TwinkleConfig = 
    {
            watchWarnings           :       false,
            markSpeedyPagesAsMinor  :       false,
            watchSpeedyPages        :   [ 'g1', 'g2', 'g3', 'g4', 'g5', 'g7', 'g8', 'g9', 'g10', 'g11', 'g12', 'a1', 'a2', 'a3', 'a4', 'a5', 'a6', 'a7', 'c1' ],
            watchRevertedPages      :        []
    };

Despite the watchWarnings setting, these pages still end up on my watchlist. עוד מישהו Od Mishehu 15:48, 15 October 2008 (UTC)

What browser are you using and have you made sure that you cleared your cache since you set up the configuration? Ioeth _{(talk contribs friendly)} 16:00, 15 October 2008 (UTC)

I'm using a version of Mozilla 5; yes, I've cleared the cache a number of times. עוד מישהו Od Mishehu 16:29, 15 October 2008 (UTC)

You mean this? Ioeth _{(talk contribs friendly)} 16:34, 15 October 2008 (UTC)

No. When I go into the about page, I get the following:

• Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061205 Iceweasel/2.0.0.1 (Debian-2.0.0.1+dfsg-2)

עוד מישהו Od Mishehu 16:38, 15 October 2008 (UTC)

Yeah, that's a supported browser, since it's just a rebranded version of Firefox 2. I made this change to your monobook.js file. It's a longshot and I don't think it will have any effect, but do a CTRL + F5 to clear your cache and see if the problem still occurs. Ioeth _{(talk contribs friendly)} 17:00, 15 October 2008 (UTC)

Alright, I made some adjustments to Twinkle. Clear your cache by doing a CTRL + F5 and see if the problem is still occurring. Ioeth _{(talk contribs friendly)} 18:03, 15 October 2008 (UTC)

Problem still present. עוד מישהו Od Mishehu 06:05, 16 October 2008 (UTC)

Just to be clear, please walk me through exactly what you are doing with specific examples of the page that was added to your watchlist that should not have been. Ioeth _{(talk contribs friendly)} 22:24, 17 November 2008 (UTC)

I wrote a general description, linking to the relevant pages for a specific case:

1. Look at a diff which I believe needs a rollback.
2. Rollback the edit. This brings me to the user's contribs.
3. Go to the user's talk page.
4. Click on the "warn" link at the top of the page.
5. Select the appropriate level and scheme of warning, and enter the linked article.
6. Click on the "Submit" button.

The user talk page is now on my watchlist, even though it shouldn't be according to the settings. עוד מישהו Od Mishehu 08:34, 18 November 2008 (UTC)

Out of curiosity, you don't have Twinkle installed in your monobook and as a gadget, do you? Ioeth _{(talk contribs friendly)} 14:19, 18 November 2008 (UTC)

Also, head over to User talk:Sandbox for user warnings and place a warning there and see if it gets added to your watchlist. I left a warning there and the page did not get added to my watchlist. Ioeth _{(talk contribs friendly)} 17:45, 18 November 2008 (UTC)

It did get added to mine. עוד מישהו Od Mishehu 06:51, 19 November 2008 (UTC)

Okay, what about my other question. Do you perchance have Twinkle installed as a gadget as well? Ioeth _{(talk contribs friendly)} 13:57, 19 November 2008 (UTC)

No, none of the editing gadgets are installed via the preferences page. עוד מישהו Od Mishehu 14:10, 19 November 2008 (UTC)

Change your monobook so the only line it has in it is importScript('User:Ioeth/monobook.js');, then clear your cache (CTRL + F5) and try again at User:Sandbox for user warnings. Ioeth _{(talk contribs friendly)} 16:55, 19 November 2008 (UTC)

When I do that change to my monobook, I loose all the Twinkle tabs. עוד מישהו Od Mishehu 06:00, 20 November 2008 (UTC)

←Od Mishehu, the problem has got to be on your end. I've tested and retested this and the watchlisting always works as it should. Plus, when you import my monobook.js into your monobook.js, you shouldn't lose all of your tabs. I have Twinkle, Friendly, and an assortment of other javascript utilities loaded in there. Unless you can come up with something that may be interfering on your end, I'm probably going to close this bug as "works for me". Ioeth _{(talk contribs friendly)} 16:25, 20 November 2008 (UTC)

All your scripts are in an "if" statement. Is it possible that this is the reason that I fail to see any of the scripts? The browser I use isn't exactly Firefox, this may make a difference. עוד מישהו Od Mishehu 06:32, 23 November 2008 (UTC)

I just checked this possibility, and it seems to be correct. If you want me to be able to test your monobook, I'd recommend the following:

1. Move the contents (except for the if surrounding it) to a separate .js page in your own namespace. Have your monobook.js import it inside the if.
2. I can then test that separate .js script without your if command interfering. עוד מישהו Od Mishehu 07:53, 23 November 2008 (UTC)

I took a slightly different approach - I hard-copied your monobook.js, without the "if" statement, into my monobook.js page. That would solve the issue. However, I want to know how to fix my monobook to keep my settings while get this issue fixed. עוד מישהו Od Mishehu 10:39, 23 November 2008 (UTC)

I can't debug the problem because I can't reproduce it. If you have experience with JavaScript, you may want to try to debug it yourself using the Firebug extension for Firefox. Ioeth _{(talk contribs friendly)} 18:13, 24 November 2008 (UTC)

I have no JavaScript experience. I did figure out, however, that it seems to be caused by the line which I believe imports the User:Sander Säde/quickpreview.js script. עוד מישהו Od Mishehu 09:00, 25 November 2008 (UTC)

Could be. The problem is most likely caused by an incompatibility between Twinkle and another script you're running. Ioeth _{(talk contribs friendly)} 15:11, 25 November 2008 (UTC)

TW-B-0214

Status:  Resolved

Resolution:  Fixed (diff). --Amalthea 14:39, 18 March 2009 (UTC)

Twinkle throws an error when on the edit form:

document.getElementById("mw-diff-otitle1") is null

on twinkefluff.js line 180:

 try {
180 var otitle = document.getElementById('mw-diff-otitle1').parentNode;
181 var ntitle = document.getElementById('mw-diff-ntitle1').parentNode;
182 } catch( e ) {
183 // no old, nor new title, nothing to do really, return;
184 return;
185 }
186

 — Mike.lifeguard | ^@en.wb 21:57, 15 October 2008 (UTC)

Actually, might not be just the edit form, but I'm having issues with Firebug :\  — Mike.lifeguard | ^@en.wb 22:02, 15 October 2008 (UTC)

Can you give an example of where this is happening, please? Ioeth _{(talk contribs friendly)} 22:22, 17 November 2008 (UTC)

On every page, I think.  — Mike.lifeguard | ^@en.wb 06:26, 2 December 2008 (UTC)

I'm not getting that error running Firefox 3.0.4 on Windows XP with Firebug 1.2.1. What OS, browser, and version of Firebug are you using? Have you cleared your cache in a while? Ioeth _{(talk contribs friendly)} 16:32, 2 December 2008 (UTC)

On every page, using FF3.0.4, WinXP SP2, Firebug 1.2.1. I have most definitely cleared my cache.  — Mike.lifeguard | ^@en.wb 04:49, 9 December 2008 (UTC)

I'll look into it. In the meantime, what skin are you using? Ioeth (talk contribs twinkle friendly) 14:57, 9 December 2008 (UTC)

Monobook (& now FF3.0.5)  — Mike.lifeguard | ^@en.wb 21:22, 15 January 2009 (UTC)

←I loaded up your monobook.js into mine to do some testing again today since we are on the same versions of just about everything (SP3 instead of SP2 for Windows XP here) and still can't get this error to reoccur. Is there anything else that you know of that could possibly be interfering? Other Firefox plugins, the other scripts you import, etc? Ioeth (talk contribs twinkle friendly) 21:31, 15 January 2009 (UTC)

On reading this again: Mike, I'm assuming you just have "Break on All Errors" turned on in Firebug? That's not really a bug then. It can be fixed with this change, which prevents the Exception from being thrown. The Exception is part of the normal control flow on non-diff pages. --Amalthea 17:28, 21 January 2009 (UTC)

TW-B-0215

Status:  Closed

Resolution:  Works for me- There doesn't seem to be any malfunction in the code here. If you are still having the problems, post a message on WT:TW for support. Ioeth _{(talk contribs friendly)} 22:21, 17 November 2008 (UTC)

Twinkle has basically stopped working entirely over the last few days. It started working for a few minutes a few days ago, and then stopped entirely.

There are two main failures:

• If I try to mark a page for CSD, I see the Twinkle screen with radio buttons for difference CSD criteria. But if I select one, nothing happens - it does not mark the page, the button is filled in and that is all.
• If I try to revert vandalism, Twinkle will open the user's talk page but it will not actually revert the edit anymore. It just hangs at the point of reverting the edit and does not finish.

I'm using a Mac and have been trying in Firefox3.0 and 3.0.1+ and personal Firefox builds and Safari. -FlyingToaster (talk) 07:14, 18 October 2008 (UTC)

TW-B-0216

Status:  Closed

Resolution:  Invalid

Creating an AfD with Chrome (possibly the problem) the AfD discussion shows as a red link - see [5], and 'keep' shows up in the template. Doug Weller (talk) 17:02, 18 October 2008 (UTC)

That's actually fairly common. It's not a problem with Twinkle or how you did anything. Sometimes it just takes a while for the MediaWiki software to catch up and realize that the AFD discussion page has actually been created and display it as a bluelink instead of a redlink. Purging the cache of the page with the AFD template on it fixes the problem too. If you'll look at Sanford Holst now you'll see that nobody has edited the article, but the discussion page is now a bluelink. Heh, unless I'm misunderstanding your problem. Ioeth _{(talk contribs friendly)} 17:20, 18 October 2008 (UTC)

Thanks. I only noticed it because someone on the AfD page suggested the AfD was defective because of the redlink. Doug Weller (talk) 20:02, 18 October 2008 (UTC)

TW-B-0217

Status:  Closed

Resolution: Working again

When clicking rpp, dialog indicated that the page had been added to the current list, but when it redirected, the page was not there. This was with the settings of semiprotect-vandalism set to temporary. Tried it twice, and neither one worked.--Terrillja (talk) 21:26, 20 October 2008 (UTC)

Just tried it again and now it's working. Go figure. Anyways, love the tool, keep it up! --Terrillja (talk) 23:58, 21 October 2008 (UTC)

TW-B-0218

Status:  Resolved

Resolution:  Fixed

Twinkle messes up the [[WP:MFD|MfD] page when transcluding a nomination.[6][7].Tikiwont (talk) 14:31, 28 October 2008 (UTC)

TW-B-0219

Status:  Resolved

Resolution:  Resolved

When placing AfD notices on the author's talk page, it is double signing the notice (leaving two signatures). See [8], [9], [10], [11]. -- Mufka ^{(u) (t) (c)} 12:01, 29 October 2008 (UTC)

Fixed. {{AFDWarning}} and its relatives were extended about a month ago to automatically include the signature. I undid that change for now. Not only did Twinkle add duplicate signatures now, but the code copied from {{afd1}} did, too. --Amalthea^Talk 15:03, 29 October 2008 (UTC)

TW-B-0220

Status:  Resolved

Resolution:  Fixed

With the user I'MSKYHiGH, Twinkle doesn't escape the apostrophe, and results in the following JavaScript error:

Error: missing ) after argument list
Source File: javascript:twinklefluff.revert('norm'%20,%20'I'MSKYHiGH')
Line: 1, Column: 32
Source Code:
twinklefluff.revert('norm' , 'I'MSKYHiGH')

~~ [ジャム]^[talk] 19:50, 1 November 2008 (UTC)

Fixed with this change. Thanks for the report! Ioeth _{(talk contribs friendly)} 21:02, 3 December 2008 (UTC)

Cheers Ioeth :). ~~ [ジャム]^[talk] 21:07, 3 December 2008 (UTC)

TW-B-0221

Status:  Closed

Resolution:  Works for me- There doesn't seem to be any malfunction in the script here. If you are still having the problem, leave a message on WT:TW. Ioeth _{(talk contribs friendly)} 22:19, 17 November 2008 (UTC)

The "csd" tab seems to open OK and present a set of radio buttons for the different criteria, but there's no way to submit the choice of criterion, nor does it submit automatically (as it used to). I'm using Firefox 1.5 (yes, I know it's ancient). Pseudomonas_(talk) 13:41, 10 November 2008 (UTC)

Seems to do it with FF3 as well Pseudomonas_(talk) 23:54, 10 November 2008 (UTC)

TW-B-0222

Status:  Closed

Resolution:  Dupe (bug TW-B-204)

I tried to set semi-protection for one week on Circus (Britney Spears album), yet Twinkle semi-protected the article indefinitely. This is not the first time that this has happened for me either. Kurt Shaped Box (talk) 02:31, 12 November 2008 (UTC)

TW-B-0223

Status:  Resolved

Resolution:  Fixed

A new parameter was added yesterday to Template:Prodwarning. Apparently Twinkle does not handle it correctly, as it writes the article title instead of the deletion concern. (Manual operation of the template works just fine.)  Blanchardb -^{Me•MyEars•MyMouth}- timed 18:03, 14 November 2008 (UTC)

The problem was mostly because the person that made the change to {{prodwarning}} did not do it correctly. I have altered the template's code to handle parameters correctly and also added the functionality in Twinkle to support the new parameter. Ioeth _{(talk contribs friendly)} 22:14, 17 November 2008 (UTC)

TW-B-0224

Status:  Resolved

Resolution:  Fixed

Twinkle inserts an extra line break when requesting protection. This is unsightly and unnecessary. Examples here, here. Chris Cunningham (not at work) - talk 13:02, 20 November 2008 (UTC)

I think I've fixed it with this change. Please let me know if it is working right now. Ioeth _{(talk contribs friendly)} 15:51, 20 November 2008 (UTC)

 Fixed Thanks! Chris Cunningham (not at work) - talk 16:11, 20 November 2008 (UTC)

TW-B-0225

Status:  Closed

Resolution:  Works for me

The nomination of இராவுத்தர் for AfD did not go well. Redlink on the article page to the deletion discussion, and I had to add it manually to 23 November AfDs. No error messages appeared during the process which seemed to run normally Fiddle Faddle (talk) 15:49, 23 November 2008 (UTC)

The redlink sometimes happens because of the MediaWiki software's cache, which is not a bug. Do you have any more information about what happened? Ioeth _{(talk contribs friendly)} 18:40, 24 November 2008 (UTC)

I'm sorry, I suspect the special characterset. Only the article history will give a clue. Fiddle Faddle (talk) 19:27, 24 November 2008 (UTC)

Okay. Maybe next time you come across a weird one like this, leave a message on my talk page or IM me (contact info on my userpage) and I'll see if I can get it to break. For now, I'm going to close this bug, though. Let me know if there is anything else I can help you with! Ioeth _{(talk contribs friendly)} 19:43, 24 November 2008 (UTC)

TW-B-0226

Status:  Resolved

Resolution:  Fixed

Twinkle can currently only tag with the album variant of WP:CSD#A9, it uses {{db-album}}/{{db-album-notice}} instead of the more general {{db-a9}}/{{db-a9-notice}} for all musical recordings. An easy fix, all three occurances of 'album' should be changed to 'a9'.
It could also be expanded to tag with all three {{db-a9}}, {{db-album}} and {{db-song}} but I don't think it's necessary, they are not nearly as common as A7.
Thanks & Cheers, Amalthea^Talk 21:03, 23 November 2008 (UTC)

Done. Ioeth _{(talk contribs friendly)} 18:19, 24 November 2008 (UTC)

Thanks a lot. :) --Amalthea^Talk 18:22, 24 November 2008 (UTC)

TW-B-0227

Status:  Closed

Resolution:  Works for me

I nominated Audible DRM for AfD. It warned the originator. It created the entry on the main AfD list page but it failed to create Wikipedia:Articles for deletion/Audible DRM which I had to perform manually. No error messages seen during the process. Fiddle Faddle (talk) 10:28, 24 November 2008 (UTC)

Do you have any more information that you could give about what happened? Ioeth _{(talk contribs friendly)} 18:41, 24 November 2008 (UTC)

I guess not. All there is to go on is the logs, sorry. Fiddle Faddle (talk) 19:25, 24 November 2008 (UTC)

Same as the one above, let me know if I can help with anything else. Ioeth _{(talk contribs friendly)} 19:44, 24 November 2008 (UTC)

TW-B-0228

Status:  Resolved

Resolution:  Fixed

Semiprotection requests for high-visibility templates are poorly formatted. The current output is:

'''semi-protection''' ''High-visible template'', rationale

This is missing a capital letter and punctuation and "high-visible" isn't a word. Proposed output:

'''Semi-protection''', ''high-visibility template''. rationale

Chris Cunningham (not at work) - talk 10:36, 24 November 2008 (UTC)

Done! Ioeth _{(talk contribs friendly)} 18:28, 24 November 2008 (UTC)

Gracias! Chris Cunningham (not at work) - talk 09:34, 25 November 2008 (UTC)

TW-B-0230

Status:  Resolved

Resolution:  Fixed

The comment when reporting a vandalism-only account contains a typo: "vandalis-only account". This is probably caused by a recent change to User:AzaToth/twinklearv.js: [12]. —Snigbrook 00:08, 3 December 2008 (UTC)

Fixed. Ioeth _{(talk contribs friendly)} 15:35, 3 December 2008 (UTC)

TW-B-0231

Status:  Closed

Resolution:  Won't fix

When in Special:NewPages, if I am CSDing an article and while in the middle, the article is changed, Twinkle does not notice the change and subsequently, doesn't alert me to it. Twice this happened when an article was created, and while CSDing, another was created with a similar name and the first was turned into a redirect. This resulted in me CSDing a redirect instead of the article in question. Grika Ⓣ 19:37, 4 December 2008 (UTC)

This is just a facet of editing in a client-server model. If it takes you some time to assess an article for CSD, the best thing to do would be to refresh or purge the page before you click the "csd" tab in Twinkle to tag it for speedy deletion. Ioeth _{(talk contribs friendly)} 19:42, 4 December 2008 (UTC)

TW-B-0232

Status:  Resolved

Resolution:  Fixed

Unprotection requests have a spurious space between the word "Unprotection" and the comma leading to the rationale. [13] [14] Additionally, suggest that the comma is replaced with a full stop/period. Chris Cunningham (not at work) - talk 13:28, 7 December 2008 (UTC)

This change should fix the problem. Re-open the bug if it does not. Thanks! Ioeth _{(talk contribs friendly)} 14:24, 8 December 2008 (UTC)

TW-B-0233

Status:  Resolved

Resolution:  Fixed

Nominating a category for deletion does not substitute the template, which is required ({{cfd}} displays an error if not substituted). [15] Chris Cunningham (not at work) - talk 15:24, 9 December 2008 (UTC)

It was changed following Wikipedia talk:Twinkle#"The syntax for this template (.7B.7Bcfd.7D.7D) has changed. ", but that change was reverted a day later. Aargh. --Amalthea 15:51, 9 December 2008 (UTC)

So does {{cfd}} need to be substituted again? Ioeth (talk contribs twinkle friendly) 17:20, 9 December 2008 (UTC)

At this particular point in time: yes, and the discussion at Template talk:Cfd has died down. --Amalthea 17:36, 9 December 2008 (UTC)

Alright, fixed for now. Let me know if this changes again. Ioeth (talk contribs twinkle friendly) 22:30, 9 December 2008 (UTC)

TW-B-0234

Status:  Resolved

Resolution:  Fixed

Nominating userbox templates in the user: namespace is messy with Twinkle, because it doesn't noinclude the {{mfdtag}} template. It shoudl either noinclude said template, or else switch it with something similar to {{tfd-inline}} when it's being transcluded. [16] Chris Cunningham (not at work) - talk 12:29, 10 December 2008 (UTC)

There is now a checkbox in the work area for AFDs and TFDs that will allow you to specify that you would like the template wrapped in noinclude tags. Ioeth (talk contribs twinkle friendly) 15:22, 10 December 2008 (UTC)

TW-B-0236

Status:  Closed

Resolution:  Invalid

Most likely this is caused by incompetency on my part, but I just changed my Twinkle (and Friendly) script on my monobook.js page from the importScript('User:AzaToth/twinkle.js'); to the full configurable script, and they stopped working. I just thought of readding the importScript('User:AzaToth/twinkle.js'); to it, but it still doesn't work. Also, is this the place to report this? Someone on the userscripts IRC Channel directed me here. Thanks, Genius101^Guestbook 22:20, 12 December 2008 (UTC)

Please do not post a bug if you're not 100% sure that the problem you're having is a bug. You can request help at WT:TW. Ioeth (talk contribs twinkle friendly) 21:34, 15 December 2008 (UTC)

TW-B-0237

Status:  Closed

Resolution:  Invalid

This is a problem I've been trying to fix for awhile, and many others seem to have it.

I am unable to make Twinkle not automatically have me watch pages. I've been following the instructions on the Twinkle Config page to try and make the parameters not watch: in my monobook, you'll see the last four are set to not watch. However, still Twinkle sets pages I revert edits on as well as users I revert edits of to watch. This makes my watchlist full and unusable. Is there any fix for this? I'm using OSX and Firefox. FlyingToaster 02:12, 15 December 2008 (UTC)

You're using Twinkle via the gadget in your preferences, aren't you? If you want to configure Twinkle's behavior, you have to add importScript('User:AzaToth/twinkle.js'); to your monobook.js file. I was going to refer you to a section of the documentation for more information, but this particular caveat seems to be currently undocumented there. —Dinoguy1000 20:10, 15 December 2008 (UTC)

Please do not post a bug if you're not 100% sure that the problem you're having is a bug. You can request help at WT:TW. Ioeth (talk contribs twinkle friendly) 21:35, 15 December 2008 (UTC)

TW-B-0238

Status:  Resolved

Resolution:  Fixed

Using Twinkle to create an MfD when one already exists will overwrite the current MfD page, rather than creating a second MfD for the page in question. — The Hand That Feeds You:^Bite 01:07, 18 December 2008 (UTC)

diff. --Amalthea 05:50, 18 December 2008 (UTC)

Very strange. The twinklexfd.js script has code to check and see if the page exists before it is created. I wonder what went wrong. If you can give me an example page that I can MfD that's been MfD'd before I'd like to try it out myself. Thanks! Ioeth (talk contribs twinkle friendly) 21:01, 18 December 2008 (UTC)

Well, we'd probably just have to create a null MfD, to avoid overwriting a real one (like I did in the diff above!). — The Hand That Feeds You:^Bite 02:02, 22 December 2008 (UTC)

SQUISH goes this bug! Ioeth (talk contribs twinkle friendly) 20:24, 15 January 2009 (UTC)

Awesome. Thank you! — The Hand That Feeds You:^Bite 20:37, 15 January 2009 (UTC)

TW-B-0239

Status:  Resolved

Resolution:  Fixed

Could you remove T1 from twinklespeedy, it was recently deprectated following discussion. Thanks & Cheers, Amalthea 00:58, 22 December 2008 (UTC)

Given the tiny number of people involved in that discussion, I reject the idea that a consensus to change policy was shown, and have reverted the deprecation. Mayalld (talk) 07:51, 22 December 2008 (UTC)

I'll close this then while it's being discussed for another round. Ioeth, I'll get back and reopen this one once/if there is consensus. --Amalthea 10:52, 22 December 2008 (UTC)

Well, since the renewed discussion has long since been archived again, Mayalld never gave a reason why he opposes this change, one additional editor has supported the change, the policy has been changed since December 22 with no opposition which usually happens instantly at WP:CSD if there is opposition, and all of the templates needed for this criterion are deleted since December 22 anyway I say that we quite certainly have consensus for this change.
Ioeth, could you throw it out please? Thanks. --Amalthea 21:12, 4 January 2009 (UTC)

Removed from script, defaults, and documentation! Ioeth (talk contribs twinkle friendly) 17:24, 8 January 2009 (UTC)

TW-B-0240

Status:  Resolved

Resolution:  Fixed

When requesting page protection on a template page, it does not insert "Template:" in the page name in the edit summary. Therefore, it creates a broken link. See my RPP's edit summary. Thanks! shirulashem (talk) 12:40, 8 January 2009 (UTC)

This should do it. Thanks for letting me know! Ioeth (talk contribs twinkle friendly) 17:19, 8 January 2009 (UTC)

TW-B-0241

Status:  Resolved

Resolution:  Fixed

When clicking the vandalism link from a user's contribs, I am redirected to the page history instead. -- Mufka ^{(u) (t) (c)} 15:03, 10 January 2009 (UTC)

This can happen if the page has been edited after the edit you wished to revert. If this continues to happen, please look at the history page you are presented with and let me know if the page has not been edited after the edit you wished to revert. Ioeth (talk contribs twinkle friendly) 16:47, 13 January 2009 (UTC)

I have paid particular attention to this possibility and this is not the case. -- Mufka ^{(u) (t) (c)} 16:48, 13 January 2009 (UTC)

Tried to do it here about 2 minutes before it was ultimately reverted by someone else. -- Mufka ^{(u) (t) (c)} 17:22, 13 January 2009 (UTC)

Same issue here. -- Mufka ^{(u) (t) (c)} 17:25, 13 January 2009 (UTC)

I've also noticed this issue for awhile. -- Collectonian (talk · contribs) 17:30, 13 January 2009 (UTC)

This bug has been SQUISHED! Ioeth (talk contribs twinkle friendly) 14:48, 15 January 2009 (UTC)

Not that confirmation is necessary, but it works now. -- Mufka ^{(u) (t) (c)} 15:07, 15 January 2009 (UTC)

TW-B-242

Status:  Resolved

Resolution:  Fixed

Just got a nasty note on my talk page accusing me of intentionally breaking redirects. It appears that the "unlink" function is also removing the brackets on redirects, breaking those redirects, instead of ignoring them. See here, here, and here for ones it did when I was unlinking an article the other day. I've also noticed that it does not always catch links if they have a # in them, resulting in some manual unlinking still being required. -- Collectonian (talk · contribs) 19:20, 12 January 2009 (UTC)

Is this happening when you speedily delete a page using Twinkle with the unlink option selected? Just want to be clear. Thanks! Ioeth (talk contribs twinkle friendly) 16:42, 13 January 2009 (UTC)

No, I'm not an admin so I don't have that option :) Its happening when I click the unlink tab to delink articles that have been AfDed or redirected. -- Collectonian (talk · contribs) 16:54, 13 January 2009 (UTC)

I'm not exactly sure what should happen to redirects when using the unlink function, so for the meantime I have disabled redirects from being unlinked. It seems to make the most sense. If anyone has a better idea of how to handle redirects here, please let me know. Ioeth (talk contribs twinkle friendly) 15:28, 15 January 2009 (UTC)

←Tag them for speedy deletion automagically (and provide a check box so that you can disable redirects entirely). --Thinboy00 @127, i.e. 02:02, 5 February 2009 (UTC)

TW-B-243

Status:  Closed

Resolution:  Dupe (bug TW-B-0229)

Lately (past 2-3 days) when placing multiple warnings on a vandal's page, each new warning overwrites the previous one[17]. NJGW (talk) 03:21, 16 January 2009 (UTC)

Pretty sure that this is a duplicate of bug TW-B-0229 above. Ioeth (talk contribs twinkle friendly) 14:16, 19 January 2009 (UTC)

This is still happening, so I don't see how it's resolved.[18] The supposed duplicate bug is listed as invalid; why is that? NJGW (talk) 19:33, 20 January 2009 (UTC)

Your link leads to a revert with Huggle, which quite obviously has the same problem then. That actually supports Ioeths guess, I'm assuming that Huggle is trying to detect edit conflicts just as Twinkle does. --Amalthea 20:28, 20 January 2009 (UTC)

Before this, Twinkle would say that you've left a warning on the same page within the same minute, but I haven't seen that message lately. What's the next step in trying to get this resolved? NJGW (talk) 20:50, 20 January 2009 (UTC)

Well, Twinkle uses a regex to detect recently left warnings on user talk pages from the contents of the edit box that it receives from the WP servers. If the WP servers are returning incomplete or incorrect contents to users (which I have noticed on a couple of pages recently when editing manually), then there is nothing I can do; it's a server problem. Since Huggle is experiencing the same thing and I have seen out-of-date edit boxes when editing manually, my best guess at this point is that it is some kind of server caching problem, which I can do nothing about. Ioeth (talk contribs twinkle friendly) 20:54, 20 January 2009 (UTC)

My question is (assuming this is something that can be solved on the servers side) who can do something about it and where do I pose the problem (I'm assuming wikimedia?) NJGW (talk) 17:09, 21 January 2009 (UTC)

This is getting annoying. Who should I be taking this to? NJGW (talk) 21:52, 21 January 2009 (UTC)

WP:VPT, perhaps? Ioeth (talk contribs twinkle friendly) 21:55, 21 January 2009 (UTC)

OK... Thanks. Here's the thread in case you want to know what they say. NJGW (talk) 22:10, 21 January 2009 (UTC)

Well, one week later and no body has made any suggestions at that thread. Any other noticeboard I could take this to? NJGW (talk) 20:17, 28 January 2009 (UTC)

←You can post a bug to [19], but check for dupes first -- developers don't always respond well to duplicate bugs. If the bug already exists, vote for it. --Thinboy00 @130, i.e. 02:07, 5 February 2009 (UTC)

TW-B-0244

Status:  Resolved

Resolution:  Fixed

When adding a WP:SPI report, the script goes through the motions. All the notifications on the user pages are done, but the actual case page isn't created (the script claims it has, but it isn't there!). This has happened twice now, so doesn't look like a one-off glitch! Mayalld (talk) 10:12, 3 February 2009 (UTC)

This sounds the same as Wikipedia talk:Twinkle#ARV failed to create Sockpuppet Investigations page. 「ダイノガイ千？！」^{(Dinoguy1000)} 19:30, 3 February 2009 (UTC)

This should be fixed now. You will need to refresh your cache (CTRL + F5) to get the revised code, though. Ioeth (talk contribs twinkle friendly) 20:31, 4 February 2009 (UTC)

TW-B-0245

Status:  Resolved

Resolution:  Fixed

See http://wiki.riteme.site/wiki/Wikipedia_talk:Template_messages/User_talk_namespace#INCONSISTENT:uw-biog4im_for_any_CONTROVERSIAL_content_or_just_DEFAMATORY_content.3F as I think there is a wording bug best fixed by change to Twinkle. Elvey (talk) 20:37, 4 February 2009 (UTC)

{{uw-biog1}} and {{uw-biog2}} start out warning about "controversial" content, {{uw-biog3}} mentions both "controversial" and "defamatory", and {{uw-biog4}} and {{uw-biog4im}} only speak of "defamatory". They've always been that way so you're right, the wording in Twinkle needs to be adapted. --Amalthea 20:48, 4 February 2009 (UTC)

Fixed! Ioeth (talk contribs twinkle friendly) 22:28, 4 February 2009 (UTC)

TW-B-0246

Status:  Resolved

Resolution:  Fixed

The csd tool on images etc. has an out of date tooltip for I8. It specifies that {{nowcommons}} must have been present for at least a week, which is not mentioned at either WP:CSD or at the template itself (which says that images can be deleted immediately). On an unrelated note, the bug reporting preload should use {{FULLURL}} so as to work right on the secure server. --Thinboy00 @109, i.e. 01:37, 5 February 2009 (UTC)

I took the liberty of fixing the bug reporting interface myself. If I broke anything, please revert me immediately. --Thinboy00 @114, i.e. 01:44, 5 February 2009 (UTC)

Could you link me to the script that has a problem and what you did to fix it? Thanks! Ioeth (talk contribs twinkle friendly) 14:00, 5 February 2009 (UTC)

I'm thinking Thinboy refers to this change following this discussion from July 2008, where the wording of I8 was changed. The current tooltip in twinklespeedy.js wasn't updated accordingly, in particular: "4: The file has been marked with Template:NowCommons for at least one week." --Amalthea 14:55, 5 February 2009 (UTC)

Fixed! Ioeth (talk contribs twinkle friendly) 21:17, 6 February 2009 (UTC)

TW-B-0247

Status:  Resolved

Resolution:  Fixed

When marking a User Talk page for speedy deletion (such as {{db-spam}}), the template gets placed and then promptly deleted by the "speedy deletion" warning that normally goes on talk pages. See User talk:Loan Oppertunity (sic). -- Tckma (talk) 19:41, 5 February 2009 (UTC)

Certainly a duplicate of #TW-B-0243. This is one that could probably be worked around with a wpSection=new since placing a new section on a talk page can be done without grabbing the content first. But I'm having a hard time believing that there are that many random glitches all of a sudden; this has to be a bug somewhere, either in Twinkle or in MediaWiki, the timestamps are supposed to prevent such conflicts. --Amalthea 20:30, 5 February 2009 (UTC)

I thought this was a different problem than 243, however upon reading 243 again, you could be right. --Tckma (talk) 15:56, 6 February 2009 (UTC)

For this particular instance, we can effectively ignore what is causing the problem. If you're tagging a user talk page with any CSD template, it seems illogical to place a CSD notice on the same page. So, I've added logic to twinklespeedy.js to check and see if the first contributor's talk page is the same as the page you are currently tagging and if so to not leave a notification. Sound good? Ioeth (talk contribs twinkle friendly) 21:03, 6 February 2009 (UTC)

Works for me. --Tckma (talk) 21:21, 6 February 2009 (UTC)

TW-B-0248

Status:  Resolved

Resolution:  Fixed

When reporting an offensive username to WP:UAA, the text reads "because it's a offensive username." It should say "because it's an offensive username." --Tckma (talk) 19:44, 5 February 2009 (UTC)

Perhaps there should be a section somewhere expressly for reporting message typos in Twinkle (and Friendly, together)? 「ダイノガイ千？！」^{(Dinoguy1000)} 23:43, 5 February 2009 (UTC)

Agreed. This seems like a very easy fix, and having a section to report this stuff could prevent lots of silly bugs like this. --Tckma (talk) 15:58, 6 February 2009 (UTC)

I found what I think was a regular expression error that was causing the problem, so it should be fixed now. You can feel free to report simple typos to WT:TW instead of here, but it's personal preference. You never know what typo might actually be a bug, like this one! Ioeth (talk contribs twinkle friendly) 20:33, 6 February 2009 (UTC)

TW-B-0249

Status:  Closed

Resolution:  Invalid

Certain articles do not have any tabs for me for some reason. For example, I would like to send Knights of Honor to AfD, but the little tab I've become so dependent on won't show, no matter what I try.... ~ JohnnyMrNinja 19:41, 9 February 2009 (UTC)

It shows up for me... What browser are you using? 「ダイノガイ千？！」^{(Dinoguy1000)} 06:21, 10 February 2009 (UTC)

Firefox beta. It shows up for me now too... It also didn't show up on Food Fight Bowl for me, but now it does. I've also restarted my computer a few times and updated Vista in the meantime, but that's weird right? It showed up on every page and image I'd gone to except those two. Oh well. ~ JohnnyMrNinja 06:38, 10 February 2009 (UTC)

All right then, I've gone ahead and closed this as invalid (not a bug). Here's hoping you don't get the problem again... 「ダイノガイ千？！」^{(Dinoguy1000)} 08:15, 10 February 2009 (UTC)

re-closed as fixed. This wasn't a bug with TW, it was a bug in the page assessment gadget (the gadget in preferences that displays the article assessment from the talk page at the top of the article). Basically, that script bombed on any article that didn't have a talk page (so, just about every new page). The assessment gadget has now been fixed, and the tabs are back. Mayalld (talk) 08:59, 10 February 2009 (UTC)

Well, in that case this bug should still be closed as invalid, since it wasn't an issue with Twinkle, but I'm not about to fight you over it. ;) 「ダイノガイ千？！」^{(Dinoguy1000)} 09:04, 10 February 2009 (UTC)

Thanks! I'm just glad to hear that I'm not crazy. ~ JohnnyMrNinja 09:29, 10 February 2009 (UTC)

TW-B-0250

Status:  Closed

Resolution:  Invalid

Copied from Wikipedia talk:Twinkle#Reverting on my talk page is broken

I have tried numerous times in the last hour to revert various edits on my talk page, but every time, I get an error message stating that the element "editform" could not be found. I recently created an editnotice for my talk page, but I'm not sure if that could be affecting it or not. 「ダイノガイ千？！」^{(Dinoguy1000)} 22:10, 12 February 2009 (UTC)

Since I also recently created an Editnotice, I tested this on my talk page. I get the same result. The exact error message is: Reverting page: couldn't grab element "editform", aborting, this could indicate failed respons from the server.  MANdARAX • XAЯAbИAM  22:49, 12 February 2009 (UTC)

I can reproduce it, but I don't understand it. I too have an edit notice, but don't see that this is related. For some reason, the document returned in self.responseXML when Twinkle edits the old revision of the page is empty (twinklefluff, line 484), although the text is returned (and can be found in self.responseText).
Ioeth, is there any reason you're aware of why this and similar requests aren't done with action=raw, e.g. [20]? --Amalthea 22:55, 12 February 2009 (UTC)

Given the further input, I'm going to move this to a bug report (hope no one minds). 「ダイノガイ千？！」^{(Dinoguy1000)} 23:43, 12 February 2009 (UTC)

This is not a bug with Twinkle. The XML parser is bombing out when parsing the document returned from the server because of invalid XML (HTML). In particular, it looks like the processing for the {{fmbox}} template is placing a </td> tag incorrectly when used in an editnotice (it does not do this normally) which is messing everything up. Have a look at the HTML for yourself by doing a "View Page Source" in Firefox. If you scroll down to the section where the unordered list in the editnotice section (<ul> tag), you'll see that the </td> is clearly coming before the </li></ul> for some reason. It looks like a proper bug report might need to be filed. Ioeth (talk contribs twinkle friendly) 20:16, 13 February 2009 (UTC)

I've started a discusson on WP:VPT entitled Editnotices generating invalid XML (HTML). Ioeth (talk contribs twinkle friendly) 20:31, 13 February 2009 (UTC)

I've gone ahead and filed a bug in Bugzilla regarding this behavior here. Ioeth (talk contribs twinkle friendly) 20:53, 13 February 2009 (UTC)

Per my posts on the VPT thread, this issue affects all wikimarkup lists, but not HTML ones (although HTML definition lists have a similar problem with the P tag for some reason). 「ダイノガイ千？！」^{(Dinoguy1000)} 21:57, 13 February 2009 (UTC)

TW-B-0251

Status:  Closed

Resolution:  Invalid

I use FF3, and i get this error:

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: 584

SparksBoy (Counter Vandalism)(talk) 06:34, 14 February 2009 (UTC)

Hmm... I'm inclined to say this is related to how you have Twinkle installed... Try deleting the extra 'morebits.js' lines from your monobook.js page, and move the first one above the 'twinklefluff.js' line. --Dinoguy1000 as 66.116.12.126 (talk) 06:57, 14 February 2009 (UTC)

I did that is why it is like that, i had it just normal before :X —Preceding unsigned comment added by SparksBoy (talk • contribs) 07:25, 14 February 2009 (UTC)

No, you didn't. Specifically, I am asking that you replace your monobook.js with the following code, clear your cache, try using Twinkle again, and report back here:

importScript('User:AzaToth/morebits.js');
importScript('User:AzaToth/twinklefluff.js');
importScript('User:AzaToth/twinklewarn.js');
importScript('User:AzaToth/twinklearv.js');
importScript('User:AzaToth/twinklespeedy.js');
importScript('User:AzaToth/twinkleprotect.js');

(and by the way, please do not remove other users' comments from talk pages) --Dinoguy1000 as 66.116.12.126 (talk) 09:10, 14 February 2009 (UTC)

Dino's advice is quite correct, I recommend changing it back to

importScript('User:AzaToth/twinkle.js');

. However, it still won't work since you have to be autoconfirmed to use Twinkle, and your account is too new. --Amalthea 12:17, 14 February 2009 (UTC)

TW-B-0252

Status:  Closed

Resolution:  Invalid

When I attempted to create the MFD page for Wikipedia:Art...e of Waziristan, a problem occurred: the link to "this page's entry" in the page's MFD tag is a redlink, and clicking it immediately takes you to editing the page. Unscented (talk) 18:59, 14 February 2009 (UTC)

Update: a similar problem has also occurred with its listing in today's MFD log, which consists simply of a redlink and none of the actual discussion.--Unscented (talk) 19:02, 14 February 2009 (UTC)

Duplicate of TW-B-0119 and others: It's not a bug with Twinkle, it's a caching issue with MediaWiki.
It could be workarounded on Twinkle's side, but I'd hold off since there are some current changes with the job queue that might actually help here, too.
In the meantime, if you WP:PURGE the cached page it will turn into a blue link. There's a gadget in your preferences that can auomize that somewhat if you don't like fiddeling with the URL. --Amalthea 19:27, 14 February 2009 (UTC)

TW-B-253

Status:  Resolved

Resolution:  Fixed

When listing usernames at WP:UAA, TW doesn't check if the username is already reported. See this diff for example. -- Mufka ^{(u) (t) (c)} 16:42, 15 February 2009 (UTC)

• I'm pretty sure this one is a dupe of another report, but I can't remember if it was a bug report, or just a general discussion on WT:TW. In any case, I think the result was that this wasn't going to be fixed, for some reason. 「ダイノガイ千？！」^{(Dinoguy1000)} 19:09, 18 March 2009 (UTC)
• YDone. Amalthea 21:03, 4 July 2009 (UTC)

TW-B-0255

Status:  Closed

Resolution:  Invalid

Firefox's error console is now complaining that form.wpAutoSummary is undefined when using Twinkle to revert edits. This is probably related to the MediaWiki software update, which has been causing other problems as well, so it may magically fix itself as the fallout from the update gets resolved. 「ダイノガイ千？！」^{(Dinoguy1000)} 07:00, 18 February 2009 (UTC)

Possibly caused specifically by rev:47202; I'm still looking through all the changes. 「ダイノガイ千？！」^{(Dinoguy1000)} 07:18, 18 February 2009 (UTC)

I can confirm this. I can also expand and say that it appears to have critically broken Twinkle!!! I have tried userwarnings, AIV-reports, and vandalism-reversions. Of the three, nothing works, all giving the wpAutoSummary error in various twinklewarn / twinklefluff etc. scripts. If others can confirm that Twinkle is, as of now, not working at all, I think it should be made a top priority to fix this somehow, as vandalism fighting efforts on Wikipedia may otherwise be severely compromised. -Lilac Soul ^{(talk • contribs • count)} 08:43, 18 February 2009 (UTC)

Safe to say it's been acknowledged, no need for others to confirm as well. AFAIK, all Twinkle edits have ceased completely for the past couple of hours. 「ダイノガイ千？！」^{(Dinoguy1000)} 08:57, 18 February 2009 (UTC)

Yep, you're right, that's the one. Looks like a mistake, and probably won't need fixing here once the devs are up again. --Amalthea 09:50, 18 February 2009 (UTC)

Just a general note, Friendly and several other user scripts have also been reported as broken after the upgrade, see the VPT discussion for more info. 「ダイノガイ千？！」^{(Dinoguy1000)} 19:22, 18 February 2009 (UTC)

All back to normal now that rev:47457 is live. Cheers, Amalthea 19:32, 18 February 2009 (UTC)

TW-B-0256

Status:  Resolved

Resolution:  Fixed

The automatic generation of Sockpuppet case pages now results in formatting for the user signature which is funky. This behaviour did not exist prior to today. For an example, see Wikipedia:Sockpuppet_investigations/71.171.88.220 Thanks for all your work on this tremendous aide. Quaeler (talk) 19:58, 18 February 2009 (UTC)

Well, it could have happened before, too. It actually depends on whether you end the comment you enter with a line break, or not. :)
@Ioeth: User:AzaToth/twinklearv.js, replacing all three occurances of "self.params.evidence +" with "self.params.evidence.rtrim() + " should fix all but one case of funky signature (new case with no evidence at all). --Amalthea 20:22, 18 February 2009 (UTC)

Should be fixed, except for the one case I mentioned. But I don't want to be too daring with my first edit to Twinkle. ;) --Amalthea 22:57, 22 February 2009 (UTC)

TW-B-0258

Status:  Closed

Resolution:  Dupe of 235

Attempted to propose a page for deletion. TW reported success but only created the AfD subpage and did not send notification to the original authors, or add the templates to the page or the AfD daily page. Browser I use is Omniweb (which is webkit based similar to Safari). Second attempt at using the xFD button said it did a whole bunch of things but did nothing. PaleAqua (talk) 18:28, 19 February 2009 (UTC)

• It did notify the author, but didn't list it. This is a duplicate of #TW-B-0235 (acknowledged), so I'll close this. --Amalthea 14:49, 20 February 2009 (UTC)

TW-B-0259

Status:  Resolved

Resolution:  Fixed

I'm running Opera in WinXP on two different machines. In the last week or so, Twinkle has not been opening user talk pages when I revert. I've tried messing with my monobook.js settings, even rolling back quite a ways (and I do clear cache whenever I mess with it). Jomasecu ^talk _contribs 18:38, 19 February 2009 (UTC)

Is your browser configured to block popups? If so, try adding an exception for Wikipedia. 「ダイノガイ千？！」^{(Dinoguy1000)} 20:54, 19 February 2009 (UTC)

Yeah, there's always been an exception for Wikipedia, and I also tried disabling the blocker entirely to see if there was a problem with the exception. Jomasecu ^talk _contribs 20:58, 19 February 2009 (UTC)

I can confirm that with Opera 9.24. Twinkle doesn't even claim to be "Opening user talk page edit form for user", but the revert was successful. I'm thinking this might connected with WT:TW/RFA#Wait for revert completion. --93.104.84.71 (talk) 15:19, 23 February 2009 (UTC)

The strange thing is that this did work. I'd been using TW for a few months and it just suddenly stopped. I haven't upgraded Opera, so I'm thinking something must have changed in WP or TW. Jomasecu ^talk _contribs 18:05, 23 February 2009 (UTC)

Yes, it did work until the change that was mentioned above. Opera seems to behave slightly differently than other browsers; the xmlhttp.onload = function(e) { in morebits.js is getting an undefined object, which causes an error, which prevents the talk page from being opened since the change. I'm hoping that Ioeth has an idea about that. --Amalthea 12:43, 25 February 2009 (UTC)

I believe the problem is with User:AzaToth/twinklefluff.js. I saved an old version of morebits.js to my user space and used that, importing the individual TW modules rather than the whole thing, and I had same problem, but I saved an old version of twinklefluff.js (User:Jomasecu/twinklefluff.js) and used that with the latest morebits.js, and that solved the problem (User:Jomasecu/monobook.js). I have absolutely no experience with Javascript, so I don't know what change caused this, but using the revision of twinklefluff.js from 14:45, 15 January 2009 user pages open. Jomasecu ^talk _contribs 19:18, 25 February 2009 (UTC)

Yes, the change was in twinklefluff, but the problem surfaced in morebits. --Amalthea 20:17, 25 February 2009 (UTC)

I've been having the same problems using Opera 9.63. The revert stops at the 'data loading' stage but appears to be successful. Also, the user warning procedure suffers the same problem - as the user talk page doesn't open automatically, the name of the page has to be entered manually, and again the procedure doesn't complete - it simply stops at the 'adding level 2 heading' stage, but the edit still seems to succeed. Bettia (bring on the trumpets!) 12:12, 24 February 2009 (UTC)

Since the change turned out to be ineffective I've undone it for now, so Opera should be behaving as it was previously (after a local browser cache flush). --Amalthea 20:17, 25 February 2009 (UTC)

Confirmed. Thanks! :) Jomasecu ^talk _contribs 20:24, 25 February 2009 (UTC)

TW-B-260

Status:  Closed

Resolution:  Invalid

When I clicked the csd tab, a window appeared. That is perfectly normal, but there is no button to submit my query. Jackl 04:02, 22 February 2009 (UTC)

I use Firefox 3, with the monobook theme. I tried to resize the text, but the button did not appear. Jackl 04:04, 22 February 2009 (UTC)

That window shouldn't have a submit button, or it never has for me, anyway. As soon as I select a CSD type it begins adding the tag. Jomasecu ^talk _contribs 05:59, 22 February 2009 (UTC)

Exactly. --Amalthea 23:00, 22 February 2009 (UTC)

TW-B-262

Status:  Closed

Resolution:  Dupe of #229

When Twinkle both tags an image as being up for deletion and then notifies the user on the same page the image is displayed, the edit conflict destroys the other edit. See here. — neuro^(talk) 16:18, 11 March 2009 (UTC)

Gnah. Most probably a duplicate of #TW-B-0243, which mentions overwriting talk page warnings if two are placed within a short time period. I'd really like to do some testing here, but don't know when I'll get around to it. It's either a MediaWiki problem, as mentioned above, or a Twinkle problem. Switching to the API might solve this, or at least Twinkle can give better feedback then. Twinkle is guarded against edit conflicts and should of course just not go through with the edit instead of seemingly ignoring the conflict, and there's at least one example where Huggle had a similar problem, which indicated a MediaWiki bug. --Amalthea 16:39, 11 March 2009 (UTC)

TW-B-264

Status:  Resolved

Resolution:  Fixed

When I TfD a template with TW, TW wraps {{tfd}} in <noinclude> tags. But it shouldn't, because a reader of main space isn't informed then that the template is up for TfD. – sgeureka ^t•c 10:14, 14 March 2009 (UTC)

Fixed. I also added a checkbox to allow tagging a template with {{tfd-inline}} instead of {{tfd}} while I was at it. --Amalthea 21:41, 14 March 2009 (UTC)

There may be instances where you wouldn't want the tag transcluded at all (not often enough to have a dedicated option, but there could still be times). I think it wouldn't be a bad idea to add a config option which would add a setting to hide the notice when sending a template to TfD. Of course, this has probably been discussed somewhere, but I'm not the one to ask about that. =P 「ダイノガイ千？！」^{(Dinoguy1000)} 19:23, 16 March 2009 (UTC)

TW-B-265

Status:  Closed

Resolution:  Resolved

Twinkle locks up and fails to do any user talk page modifications. Will issue speedy delete warnings, but locks up and fails to notify original article author. Will lock up while attempting user warnings. Using Firefox 3.0.7, have bypassed cache, restarted computer, restarted Firefox, tried both gadget and self install versions of TW. Wuhwuzdat (talk) 21:42, 14 March 2009 (UTC)

I see a number of notification in your contribs today that went through. On which page did you notice it? What does "lock up" mean? It just stopped going on? Did it say it notified the user? Did you notice an error message in your error console? --Amalthea 21:57, 14 March 2009 (UTC)

It appeared that the script just stopped running, there was no error message, but no user talk notification either, waited over a minute on several occasions. I marked several pages for speedy deletion (gone from my contrib summary now), but I can still see 1 Page I tagged for speedy, The Eternal Love, where that talk page modification failed, and after I reverted Matt Damon, TW just stopped when I attempted to place a user warning on user talk:Boomhauer2. It did work ONCE after speedying My Knowledge about using DOORS. I had switched from the self installed to the gadget installed version immediately before that single success, but had the same issue on the next page I marked. VERY bewildering. Wuhwuzdat (talk) 23:33, 14 March 2009 (UTC)

It would appear that the bug only occurs when trying to place a user warning on an EMPTY user talk page, I successfully tagged my own page, then had a failure COI tagging User talk:Kfrykman (page empty at the time) , then successfully tagged my own page with a COI warning. Wuhwuzdat (talk) 00:08, 15 March 2009 (UTC)

Yes I have had the same issue... problem only happens on empty user talk pages.--Cerejota (talk) 00:16, 15 March 2009 (UTC)

BTW I am using the gadget version.--Cerejota (talk) 00:17, 15 March 2009 (UTC)

I just had TW stop for over 3 minutes at "User talk page modification: data loaded..." on empty (non-existant user) User talk:I hope this user doesn't exist on a test edit. Wuhwuzdat (talk) 00:20, 15 March 2009 (UTC)

Just hangs on "Notifying of initial contributor (Username): data loaded..."--Cerejota (talk) 00:24, 15 March 2009 (UTC)

This could be a problem with some dev level changes, it might not be a bug in twinkle but some change in the API?--Cerejota (talk) 00:32, 15 March 2009 (UTC)

Fixed, was a change in MediaWiki:Newarticletext, which through bugzilla:17486 caused invalid HTML (like WT:Twinkle/Bugs/Archive 3#TW-B-0250), which made Twinkle stutter. Man, it's time to start working on #TW-B-0257 (new). :\ --Amalthea 00:58, 15 March 2009 (UTC)

I replied there... BTW thank you for the prompt fix.--Cerejota (talk) 01:50, 15 March 2009 (UTC)

TW-B-266

Status:  Closed

Resolution:  Invalid

I have tried two different browsers, and when I rollback changes and choose vandalism, it rolls back the page, but does not open the user's talk page with the warning notice. Mr. moose (talk) 20:33, 17 March 2009 (UTC)

More information, please. What browser are you using? Has it never worked for you (I see you have used Twinkle to place warning templates for a while now)? What is the last thing Twinkle says when you're rolling back? Are you getting any errors in the Javascript console? --Amalthea 21:27, 17 March 2009 (UTC)

I have used Firefox and Safari on a PC, and Safari on a Mac. It used to work until I tried it now. It shows this:

Grabbing data of earlier revisions: revision 277635244 that was made 2 revisions ago by 189.180.89.72

Reverting page: completed (Mike_Burkett)

Info: Opening user talk page edit form for user 74.225.213.175

Reversion completed: completed

It then directs me to the page that was edited, not the talk page. Mr. moose (talk) 23:31, 17 March 2009 (UTC)

Do you have any kind of popup blocker enabled? That seems to me the most likely explanation, since there apparently are no javascript errors happening if it is refreshing the page that was edited. Of course that would mean that you'd have one on all three Browsers you tested. Maybe an overeager firewall is doing that for you?
It isn't a bug with Twinkle, in any case, so I'm going to close this. I don't really have other ideas why this stopped working for you, or how you figure it out short of you installing Firebug and debugging it on your PC.
Feel free to ask at WT:TW though, maybe someone who's watching there has any ideas.
Cheers, Amalthea 14:54, 18 March 2009 (UTC)

TW-B-267

Status:  Closed

Resolution:  Dupe of #235

When I attempted to nominate WP:Scary transclusion for RFD, it was not added to the log. I have verified that this is most likely not a caching issue, as it did not appear even after purging the page, and no edit adding it appeared in the edit history (although one does now, as I have since added it manually). Unscented (talk) 00:54, 22 March 2009 (UTC)

TW-B-268

Status:  Resolved

Resolution:  Fixed

PUI has been renamed; see WT:PUI#Poorly-planned move for details. Twinkle needs to be adjusted to post nominations to subpages of Wikipedia:Possibly unfree files instead of Wikipedia:Possibly unfree images. Thanks. Anomie⚔ 04:55, 23 March 2009 (UTC)

Fixed, thanks. --Amalthea 10:57, 23 March 2009 (UTC)

TW-B-269

Status:  Resolved

Resolution:  Fixed

Quick typo fix: on the entry for {{unencyclopedic}} (maintenance tags window), the description's version of that word is missing the letter d. --- Jarry1250 ^{(t, c)} 21:35, 26 March 2009 (UTC)

• A Friendly bug, but fixed anyway. --Amalthea 22:25, 26 March 2009 (UTC)

TW-B-270

Status:  Closed

Resolution:  Won't fix

Twinkle deletes the wrong images. About once a month one of the protected, high-use, high-risk {{imbox}} default images are erased. One of the affected files is File:Imbox deletion.png. (That is, I think it happens to several images in the mbox family, but I haven't kept notes about it and I couldn't find other examples right now.) Every time when I ask the admin that erased the image they claim to have used Twinkle and that they were aiming for some other image. But most of them can't remember which image they were aiming for. But now one admin did remember. See his comment at User talk:Valley2city#File:Imbox deletion.png. This has been going on for a long time. So it seems it really is a Twinkle bug, and not just a poor excuse. See for instance the log for File:Imbox deletion.png. --David Göthberg (talk) 21:49, 26 March 2009 (UTC) --David Göthberg (talk) 21:49, 26 March 2009 (UTC)

Well, that's not a bug. If people use the image batch deletion tool which expressly deletes all images found on a page, then that's what happens. Normal speedy deletions should be done with the CSD tab.
I've just renamed the "deli" tab to "deli-batch" so that it is more clear and hopefully less inviting, but it does list the images that are going to be deleted right above the button one has to press. If you want (and have Twinkle loaded) you can look at the dialog at User:Amalthea/test4 where I've placed the warning template.
Cheers, Amalthea 22:43, 26 March 2009 (UTC)

I don't use Twinkle myself, so I can't take a look. But I understand what you mean by "image batch deletion tool which expressly deletes all images found on a page". So now I see why it is mostly our "delete" images that are deleted all the time. They are shown in the deletion and speedy deletion boxes, so they are shown on the file description pages of images that are up for deletion. And I guess that is what you mean with that example at User:Amalthea/test4.

But deleting all images on a page is a pretty dangerous and clumsy operation. And we protect high-use images exactly since they are important high-use images. Other images have been deleted the same way, and it will happen again. I guess this means that all images that are used in boxes on image pages are at risk. So you guys need to do something about it. So let me brainstorm for a bit, and you might be able to use or improve on one of these ideas:

1: Could you make it so the batch delete function doesn't delete protected images? Since I can't imagine any situation where one would want to batch delete protected images. I think it is a bug that Twinkle allows batch deleting protected images.

2: Also, not all of the images used in message boxes are protected. I know javascript can detect if an object is inside a box with some given class. So we could give you a short list of those classes and you could make it so Twinkle doesn't batch delete images in such boxes. This would also help when people batch delete images in categories, so the images used in the category message boxes aren't deleted.

3: And you should probably make it so batch delete doesn't work on file pages. I mean, why would you use batch delete on a file page at all? I think batch delete normally is used when you have a list of images somewhere, and such a list is of course not kept on a file page.

4: Or as a last resort, could you add a stop list to Twinkle of images that it should never batch delete? There we could add the images that we use in the image message boxes. And preferably have that stop list as a page somewhere that we admins can edit.

5: And can you make it so Twinkle adds some word in its deletion summary that explains it did a batch delete? So we can see why it happened and tell those users to not use batch delete.

--David Göthberg (talk) 01:27, 27 March 2009 (UTC)

At the very least, it would probably be best (or at least better) for Twinkle to stop and prompt for confirmation if a batch delete operation encounters a protected image. 「ダイノガイ千？！」^{(Dinoguy1000)} 04:19, 27 March 2009 (UTC)

All good points. FWIW, at File:Twinkle-delimages-dialog-admin.png is an image of what the dialog looks like. At the bottom of the list is the submit button that triggers deletion of all checked images.
That image possibly also shows the last time this function was useful: batch deleting a category full of copyrighted, non-fair-use images. I'm actually of half a mind to remove the function altogether; it could still be activated manually by those who know what they are doing. But I'm going to check first if anybody is using this purposefully, and how they are using it, before I change anything. For example, it's plausible that one does want to deleted protected images with it, e.g. if someone has a category or list of images, uploaded from commons and protected for display on the main page, which become obsolete once they are off the mainpage.
In any case, I do believe that renaming the tab will make almost all of those accidental deletions go away already (once everyone has the refreshed version of the script at least). --Amalthea 10:01, 27 March 2009 (UTC)

Well, nobody has deleted File:Imbox deletion.png in the last 4 months, since the tab was renamed, so I do think we can mark this as resolved, although none of the aditional suggestions from David have been implemented. Amalthea 15:23, 4 July 2009 (UTC)

File:Imbox deletion.png was just accidentally deleted via Twinkle again. I think that David's suggestions are excellent, and I hope that as many as possible will be implemented. —David Levy 18:13, 18 July 2009 (UTC)

I know. Amalthea 18:20, 18 July 2009 (UTC)

Ah, thanks for promptly following up on this. —David Levy 18:34, 18 July 2009 (UTC)

TW-B-271

Status:  Resolved

Resolution:  Fixed

Minor issue, but the warn/notify menu descriptions and edit summaries for {{uw-unsourced1}}, {{uw-unsourced2}}, {{uw-unsourced3}} and {{uw-unsourced4}} all say "addition of unsourced material without proper citations". However, if the material had proper citations, would it not be sourced? Something like "addition of unsourced or improperly cited material" would be better. --—/Mendaliv/^2¢/_Δ's/ 22:56, 28 March 2009 (UTC)

Done using your wording. --Amalthea 12:00, 30 March 2009 (UTC)

TW-B-272

Status:  Closed

Resolution:  Resolved by Mendaliv

While placing a final warning (level 4) for addition of unsourced material (this edit), Twinkle instead put in a redirect to the template. --~~ [ジャム]^[t - c] 12:27, 29 March 2009 (UTC)

The problem is that someone flipped the redirect of {{uw-test4}} to {{uw-generic4}}. —/Mendaliv/^2¢/_Δ's/ 20:20, 29 March 2009 (UTC)

I've fixed the template redir issue since lots of other level 4 warnings use generic4... —/Mendaliv/^2¢/_Δ's/ 20:25, 29 March 2009 (UTC)

TW-B-273

Status:  Resolved

Resolution:  Fixed

If you use vandalism rollback to make a revert, the user talk page is opened and the linked article is automatically populated. If you change from a warning to a block notice, the linked article (which is usually greyed out) retains the linked article from the reversion. When placing the block note, it leaves an odd edit summary and it puts it under a month heading. See this. ---- Mufka ^{(u) (t) (c)} 15:08, 3 April 2009 (UTC)

YFixed the mention of the article with most block notices (it's appropriate with EW/3RR-blocks). Block notices have always been placed under monthly headings, you typically just don't notice cause the warnings have already created one, so I didn't change anything there. Amalthea 21:18, 4 July 2009 (UTC)

TW-B-274

Status:  Closed

Resolution:  Dupe of #36

If I click the 'rollback' link on a diff page, it opens the user page to leave a warning but it doesn't actually rollback the article to the previous version. --Anshuk (talk) 23:06, 4 April 2009 (UTC)

Just realized that this is because the resulting page was trying to save a blacklisted link. TW could have given an indication or something. --Anshuk (talk) 23:09, 4 April 2009 (UTC)

Yep. This isn't the only time Twinkle silently fails; it has a problem of not warning the user most times it's unable to save an edit for some reason. This has been brought up before, but AFAIK there's not really anyone working on fixing it. 「ダイノガイ千？！」^{(Dinoguy1000)} 20:24, 6 April 2009 (UTC)

TW-B-275

Status:  Closed

Resolution:  Invalid

Twinkle generates edit summaries containing the word "undefined" (e.g., this edit where it spat out Creating deletion discussion page for Argireline.undefined as summary. Using latest stable Safari on latest OS X, also using popups, wikEd etc. --WnC? 18:28, 9 April 2009 (UTC)

I just realized I have both Friendly and Twinkle enabled as gadgets; might this be a problem (or perhaps duplicated functionality)? WnC? 18:31, 9 April 2009 (UTC)

Not a bug, but a bad configuration. I fixed it, it became apparent after your recent switch from monobook inclusion to gadget. --Amalthea 18:55, 9 April 2009 (UTC)

Oh, had no idea that the configuration would need changing after that. Thanks for fixing it! WnC? 19:28, 9 April 2009 (UTC)

TW-B-276

Status:  Closed

Resolution: Seems to have fixed itself, or is connected with #235

I have started 2 AfDs this week and I have had to complete them manually as TW failed on both occasions. It looks like it is going throug the whole process and at each stage it is saying Data Loaded but it isn't completing them. --BigDunc^Talk 18:55, 9 April 2009 (UTC)

Having tried to open two AfDs via Twinkle, both have failed. It tags the page and lists the other actions as "completed", but, after checking, I discovered it had not notified the authour, created the discussion page or added it to the day's log, meaning the rationale for deletion I entered in the Twinkle box is lost. If it's going to do that every time I try to open an AfD, it's a fat waste of time. HJMitchell You rang? 08:41, 30 April 2009 (UTC)

It's not doing this every time I start an AfD- my most recent appeared to have been sucessful without having to go back and do it all manually. HJMitchell You rang? 08:59, 30 April 2009 (UTC)

TW-B-277

Status:  Resolved

Resolution:  Fixed

{{uw-username}} needs special handling on the warn menu. "Linked article" should probably be grayed out, and the "optional reason" should be required, as otherwise the template doesn't function as intended. --—/Mendaliv/^2¢/_Δ's/ 03:30, 12 April 2009 (UTC)

YFixed Hacked. Amalthea 11:38, 21 September 2009 (UTC)

TW-B-278

Status:  Resolved

Resolution:  Fixed

Twinkle keeps repeatedly adding {{nowcommons}} instead of {{db-f8}}--Ipatrol (talk) 23:10, 13 April 2009 (UTC) --Ipatrol (talk) 23:10, 13 April 2009 (UTC)

Y Fixed! The F8 selection now uses {{db-f8}} rather than an old deprecated version of {{nowcommons}}. Ioeth (talk contribs twinkle friendly) 16:19, 23 September 2009 (UTC)

TW-B-280

Status:  Closed

Resolution:  Dupe of #229

After I added a welcome message to a new user's talkpage using Friendly, when I warned him/her about adding signatures to the article space using Twinkle, it removed the welcome, as can be seen here. --Computerwiz908 | Talk 20:15, 15 April 2009 (UTC)

This is a known (and previously reported (but I'm too lazy to look for previous bugs to justify marking this a dupe)) issue, but I'm not sure if anyone has pinpointed the exact reason for it yet. In any case, it's one of several known, longstanding issues that will probably be fixed simply by switching Twinkle (and Friendly) over to using the API. 「ダイノガイ千？！」^{(Dinoguy1000)} 20:23, 15 April 2009 (UTC)

TW-B-281

Status:  Closed

Resolution:  Invalid

When notifying an article's original creator that the article has been nominated for deletion, Twinkle currently does not take into consideration where the article was originally created as a redirect and that redirect was later turned into an article. This can lead to situations where someone is notified of the deletion nomination of an article they have no interest in. However, there's really no way for Twinkle to be able to tell this, so a better behavior would probably be for it to notify the original creator and anyone who turned the redirect into an article (with some checking to eliminate cases where people are reverting back and forth between article and redirect, for one reason or another). This request was spurred by this notification and discussion. 「ダイノガイ千？！」^{(Dinoguy1000)} 17:23, 16 April 2009 (UTC) --「ダイノガイ千？！」^{(Dinoguy1000)} 17:23, 16 April 2009 (UTC)

To the best of my knowledge, there is no way to get to that information short of examining every revision in the page history. While the MediaWiki page table has a is_redirect flag, the revision table does not, and consequently the API can't deliver one.
A possibility is to go through all revisions and devise some algorithm to determine the main contributors to an article, probably based on the number of edits to a page and the number of bytes added to it (size is only retrievable since around 2 years though). If you come up with a good strategy I'd be open to implement it, it's not that hard and I'd like the feature since quite often the main contributor is someone else than the original creator. I'd rather discuss that at WT:TW or WT:TW/RFA though, to get wider input, so I'll close this since its not a bug: typically (and as you agreed) we should assume that the editor who created the initial redirect is interested in the fate of the article that grew from it, so Twinkle should err on the side of notification. Amalthea 18:59, 16 April 2009 (UTC)

Hmm... I should have realized this wasn't a bug, but... meh. At least I got it down in writing. =) I'm not sure what I can do about offering good strategies for it, but an extremely naive approach would be simply to count revisions by a particular user, and when their last contribution to the page occurred (both of which could be done with just the page history). 「ダイノガイ千？！」^{(Dinoguy1000)} 19:57, 16 April 2009 (UTC)

TW-B-282

Status:  Resolved

Resolution:  Fixed

The TW edit summary used with {{uw-error1}} says "deliberate" factual errors. While that's the appropriate usage for the template, level 1 templates are worded in such a way to assume good faith while informing of the reason for the revert. But the word "deliberate" implies a strong assumption of bad faith. I think it would be better if the word "deliberate" were omitted or replaced with "apparent", either at just level 1 or at all levels. --—/Mendaliv/^2¢/_Δ's/ 16:15, 21 April 2009 (UTC)

Maybe, but it's the same summary Wikipedia:UTM#Multi-level templates displays for all levels of the template, so I'd rather stick with it. If they want to change it I'm happy to reflect that in Twinkle. --Amalthea 09:54, 22 April 2009 (UTC)

Alright, I'll go over there and bring it up. —/Mendaliv/^2¢/_Δ's/ 13:10, 22 April 2009 (UTC)

Ah, you know what, I misunderstood you, I thought your summary referred to the summary presented to the Twinkle user, but you of course meant the edit summary. I removed the "deliberate" there at level 1 and 2.
Thanks & Cheers, Amalthea 14:34, 22 April 2009 (UTC)

TW-B-283

Status:  Resolved

Resolution:  Fixed

{{uw-tempabuse}}, which TW uses, has been redirected and has also grown into a full series of templates from {{uw-tempabuse1}} to {{uw-tempabuse4im}}. --—/Mendaliv/^2¢/_Δ's/ 13:29, 22 April 2009 (UTC)

Done. --Amalthea 14:43, 22 April 2009 (UTC)

TW-B-284

Status:  Closed

Resolution: Not a bug

For the past two days, every time I have created an AfD the AfD template left on the page is left as a redlink with AfD listing instructions below in the box, even though it links to an existing AfD discussion. Everything else works correctly and I can fix the problem manually with a null edit. See examples here here and here. I'm not 100% certain whether this is a Twinkle, personal, or Wikipedia problem, though. KhalfaniKhaldun 20:51, 22 April 2009 (UTC) --KhalfaniKhaldun 20:51, 22 April 2009 (UTC)

I'm pretty sure this is a caching issue that shouldn't affect the behavior of the AfD notice; the redlinks would probably be fixed simply by purging the page's cache. Twinkle could *probably* avoid this by creating the discussion page first, waiting for about a second, and then posting the notice to the article, but I'm not sure how it does it currently, and there's really nothing critical to be fixed here. 「ダイノガイ千？！」^{(Dinoguy1000)} 21:48, 22 April 2009 (UTC)

Hmm... guess I hadn't thought about that, but you're right. That's why the null edits work. As for the, umm... order of operations(?) Twinkle goes through, I'm pretty sure it tries to do it all semi-parallel, since fairly often it finishes each part (notify, create afd, list, tag article) in a seemingly random order. It's probably not worth the effort to force it to go in a specific order. KhalfaniKhaldun 22:12, 22 April 2009 (UTC)

As far as I know, Twinkle basically just shoves everything through once you submit the AfD notice, and then claims it's been finished whether the edits actually go through or not. Forcing a particular order probably wouldn't be a lot of trouble once Twinkle has been updated to use the API. 「ダイノガイ千？！」^{(Dinoguy1000)} 22:26, 22 April 2009 (UTC)

Correct, once the writeAPI is used, it becomes much easier to verify wether updates and edits have gone trough successfully. However I can tell you now, it's gonna be a lot of work to implement that. Most importantly, there will have to be some UI changes, and that is more work than implementing the writeAPI itself (I'm working on writeAPI now for HotCat, and that definitely proved more challenging than I had anticipated.). --TheDJ (talk • contribs) 09:15, 23 April 2009 (UTC)

It's not that surprising that updating to the API would actually be so involved, but it should also result in much more compact, manageable, and error-resistant code (as I understand it). Coincidentally, I opened a bug report a while back in regards to updating Twinkle (and Friendly) to use the API; see bug 257. *goes to look at some of the changes TheDJ is doing to HotCat just to see some of what updating to the API entails* 「ダイノガイ千？！」^{(Dinoguy1000)} 09:32, 23 April 2009 (UTC)

TW-B-286

Status:  Closed

Resolution: stale, user no longer active, and might be resolved with recent changes anyway

I keep getting a pop-up saying I can't use twinkle becuase my account is too new, but I have used twinkle before and my account isn't what I would describe as new. --Wikipedian2 (talk) 10:18, 29 April 2009 (UTC)

I don't know. Apparently you aren't autoconfirmed, but I can't see why. I've raised the question at WP:VPT#Autoconfirmation.
However, this is not a Twinkle bug. It deliberately requires autoconfirmation, so I'm going to close this issue. --Amalthea 11:54, 29 April 2009 (UTC)

Since per your post at WP:VPT your preferences say that you are autoconfirmed, can you please go to my user talk page, and try to warn me there? If it doesn't work, can you please:

• Check your javascript error console for any entries? You might want to clear it first and then refresh the page, so that you only have relevant entries.
• Have a look at the page source code, search for wgUserGroups, and confirm that it contains "autoconfirmed"?
• Copy&paste the following into your address bar while your still on my user talk page, press enter, and then copy the text in the inputbox and paste it here?

javascript:void(prompt("",wgUserGroups.join("/")+" | "+twinkleConfigExists+" | "+userIsInGroup('autoconfirmed')+" | "+twUserIsWhitelisted()))

• Post what browser you're using anyway? There shouldn't be compatibility issues at this point, from the code, but you never know.

That will hopyfully help getting behind this, cause I can't see any way why this logic would suddenly stop working (and when I just tested it with an alternate account it worked just fine). Amalthea 10:40, 2 May 2009 (UTC)

Thank-you for your help, here is the output of the code (that comes up in the imput box): ipblock-exempt/*/user/autoconfirmed | true | true | true Also I use Mozilla FireFox. I'm pretty sure that the problem is because I'm IP-Exempt.

Wikipedian2 (talk) 10:20, 3 May 2009 (UTC)

• That's what I thought, which is why I gave my alternate accout User:Amalthea2 IP-block-exemption, but there was no problem there. The values you posted are also all as they should be, so it must work. Did you test it again, as I asked? Which tab are you using, the "warn" tab? Did you check the javascript console (Ctrl+Shift+J in Firefox)? Which version of Firefox are you using?
  Amalthea 10:51, 3 May 2009 (UTC)
  • This might also be a timing issue, although I've never seen this with Firefox before. Could you try and use

    importScript("User:TheDJ/twinkle.js")
    

    in you monobook instead of the normal script, and make sure you have the Twinkle-Gadget disabled in your preferences? Amalthea 21:22, 4 July 2009 (UTC)

TW-B-287

Status:  Resolved

Resolution:  Fixed

When using the CSD tab to delete pages, the popup box never goes away or refreshes to the normal post-deletion page. It reports that the action is completed, but it just stays there forever. Additionally (and possibly a separate issue) there is no option to uncheck the notify if possible box when deleting pages. -- Mufka ^{(u) (t) (c)} 19:38, 29 April 2009 (UTC)

You're reporting two separate issues here. The first (Twinkle window stays open) is a dupe of TW-B-263 (and possibly one or two others). The second has not been reported before AFAIK. 「ダイノガイ千？！」^{(Dinoguy1000)} 19:46, 29 April 2009 (UTC)

You're right, it looks like the same thing as #263, I didn't see that in my search. I'll cross that out, slightly refactor, and make the second issue the topic of this bug since there has only been one response. Sorry if it makes a mess. -- Mufka ^{(u) (t) (c)} 19:56, 29 April 2009 (UTC)

You mean the disabled box? The one you can toggle if you check "Tag page only, don't delete"?
If so, then that's intentional behavior, although there's a feature request to change it. For sysops, Twinkle's CSD tab will delete the page immediately by default. If it does that, it will never notify the author, no matter what the "notify" checkbox says, which is why it's greyed out. Of course, it should ideally be disabled in the unchecked status.
Is that what you're referring to? Amalthea 10:54, 2 May 2009 (UTC)

Yes, that is the box. Disabling it in the unchecked state would be preferred. -- Mufka ^{(u) (t) (c)} 12:20, 2 May 2009 (UTC)

OK, Yfixed the notify-checkbox for sysops to reflect the actual behaviour. Amalthea 21:31, 4 July 2009 (UTC)

TW-B-288

Status:  Resolved

Resolution:  Fixed

First - I love Twinkle, and thanks for the great work. The bug: When seconding an existing PROD nomination the PROD2 tag is SUBST'd, but per Template:Prod2 it should not be SUBST'd. Here is an example of it in action [21]. Thanks. --JCutter (talk) 22:58, 1 May 2009 (UTC)

Y Fixed, thanks. Amalthea 10:45, 2 May 2009 (UTC)

TW-B-289

Status:  Resolved

Resolution:  Fixed

Reporting usernames appears to be broken - sometime within the last 24 hours. It lists the page data as being loaded and then locks up. --JCutter (talk) 13:05, 5 May 2009 (UTC)

• Followup - I'm not the only one with the problem - see edit description here [22] -- JCutter (talk) 02:57, 6 May 2009 (UTC)
  • YFixed, the editnotice contained invalid XHTML, which made Twinkle fail parsing the page. Thanks for the report, Amalthea 14:39, 6 May 2009 (UTC)

TW-B-290

Status:  Resolved

Resolution:  Fixed

Just a slight tweak: CSD's G11 and G12 are now Unambiguous [...] rather than Blatant [...]. Not really a big deal, but should probably be changed over for consistency. The rollovers might need updating as well, I haven't checked them yet. - Jarry1250 ^{(t, c)} 15:45, 5 May 2009 (UTC) --- Jarry1250 ^{(t, c)} 15:45, 5 May 2009 (UTC)

•  Done: [23], [24]. Thanks, Amalthea 14:48, 6 May 2009 (UTC)

TW-B-291

Status:  Closed

Resolution:  Dupe of #289. Amalthea 14:39, 6 May 2009 (UTC)

The UAA reporting functionality does not work anymore, it returns a "Failed to retrieve edit form" error instead. First noticed the problem last night.--Terrillja _talk 14:13, 6 May 2009 (UTC) --Terrillja _talk 14:13, 6 May 2009 (UTC)

TW-B-292

Status:  Resolved

Resolution:  Fixed

I tagged an article for deletion and when twinkle notified the creator it left the notice like this any ideas why? --BigDunc^Talk 22:27, 8 May 2009 (UTC) BigDunc^Talk 22:27, 8 May 2009 (UTC)

This is because no one has created the {{db-hoax-notice}} warning template yet. —TheDJ (talk • contribs) 02:49, 9 May 2009 (UTC)

Man, how stupid am I? I knew I had to build it, but didn't.
I've created it as a redirect to the g3 notice, and will flesh it out tomorrow. Thans, Amalthea 13:37, 9 May 2009 (UTC)

Or not, it's good enough as it is, really. Amalthea 15:11, 4 July 2009 (UTC)

TW-B-293

Status:  Resolved

Resolution:  Fixed

This one may be quite rare, but it seems that if you use twinkle to prod-2 an existing prod, and if that existing prod has nested curly brackets to describe the problem then twinkle puts the prod-2 within the outer curly brackets, as opposed to after the outer curly brackets. Maybe it needs to search for the last curly brackets for it's insert... Example here [25]. JCutter (talk) 02:28, 9 May 2009 (UTC) --JCutter (talk) 02:28, 9 May 2009 (UTC)

It's a problem with Twinkle counting (or not counting) brackets, as you sort of said. I don't know enough to fix it myself, but it should be a pretty easy fix. 「ダイノガイ千？！」^{(Dinoguy1000)} 04:03, 12 May 2009 (UTC)

Counting brackets would certainly be an improvement, but would still leave a number of openings, like nowiki and pre tags or interleaving brackets. From the top of my head:

<nowiki>}}</nowiki>

<pre>}}</pre>

<!--}}-->

 }}

[[}}]]

[[foo | {{ bar | ]] }}

{{ bar | [[foo | }} ]]

In the end, the only real solution would be to duplicate the MediaWiki parser.
FWIW though, it should hardly ever happen. The change that caused it in this case has been reverted. Amalthea 09:17, 12 May 2009 (UTC)

YFixed for simple, non-nested template transclusions in the prod reason. Amalthea 21:54, 4 July 2009 (UTC)

TW-B-294

Status:  Closed

Resolution:  Won't fix, sorry.

Internet Channel on Wii, on the "csd" (WP:SPEEDY) tab, won't let me complete the process. (By that I mean it lets me fill in the bubble for type, but nothing else.) Help!!!!!!! Dalekusa (talk) 01:06, 16 May 2009 (UTC) --Dalekusa (talk) 01:06, 16 May 2009 (UTC)

Well... this is a challenge, if only because I'm not sure how many people around here actually access the internet from a Wii (and that's assuming any of us has one). I'm sure CSDs aren't the only thing that fail though... 「ダイノガイ千？！」^{(Dinoguy1000)} 05:56, 16 May 2009 (UTC)

Have you activated the Javascript Standard Library in your preferences? As far as I know that's necessary for Opera browsers, and Internet Channel appears to be a variant of that. If that doesn't work then I'll probably close this as WONTFIX, unless you send me a Wii where I can test this. Attempting IE compatibility would be far higher on my ToDo list then Wii compatibility, I'm afraid. Amalthea 14:23, 27 May 2009 (UTC)

I can test this on my Wii tonight. —TheDJ (talk • contribs) 15:27, 27 May 2009 (UTC)

Yes, the Wii does use an Opera browser.[26] So turn on JavaScript standard library and see if that works. If this is fixed for this, it should work on all opera browsers.--Ipatrol (talk) 14:45, 24 June 2009 (UTC)

I Do use the Javascript standard library; I installed Twinkle before the Gadgets tab was added. —Preceding unsigned comment added by Dalekusa (talk • contribs) 18:50, 24 June 2009 (UTC)

Without a proper way for me to test this, and with the expected target audience of 1, this just won't be addressed happen anytime soon. If you want, you can nonetheless check your javascript error console for error messages, next time you run into that issue, and post any messages regarding twinkle here. Without that there's nothing I can do. Amalthea 15:09, 4 July 2009 (UTC)

TW-B-295

Status:  Closed

Resolution:  Works for me

Promotional Username reporting via ARV is not working. Did something just change (like in the last 10 min). All of a sudden ARV username reporting doesn't work - it returns a prompt that it has worked but nothing gets posted. Tried twice.    7   ^{talk | Δ |}   06:20, 20 May 2009 (UTC) --   7   ^{talk | Δ |}   06:20, 20 May 2009 (UTC)

MuZemike reported one a minute after you posted this (at my talk), there has been no change to Twinkle itself, and I could successfully report the one you tried, so I guess it was just a glitch. Twinkle isn't very reliable when it comes to problems, I'm afraid. Amalthea 06:23, 20 May 2009 (UTC)

Thanks - I tried again too and now it works :( Oh well - sorry for the confusion.    7   ^{talk | Δ |}   06:27, 20 May 2009 (UTC)

TW-B-297

Status:  Resolved

Resolution:  Fixed, larger issues persist and need to be fixed by getting the page source a smarter way, either through API or raw format.

For some reason, I cannot use the "rollback" or "rollback vandal" functions on my user/talk page. When I do, I get the following message: "Reverting page: couldn't grab element "editform", aborting, this could indicate failed response from the server." These functions do appear to work on other pages. Apologies if this has been reported before/elsewhere. --TNXMan 14:05, 27 May 2009 (UTC)

• Vote for bugzilla:17486! I've tweaked your editnotice so that it should work now. Will leave you a talkback in a second to check. Amalthea 14:13, 27 May 2009 (UTC)

• Hmm, it doesn't seem to have worked, as I'm getting the same message. Would removing the editnotice fix this? Thanks for your attention! TNXMan 14:19, 27 May 2009 (UTC)

Yes, I missed one. Works now. :) Cheers, Amalthea 14:28, 27 May 2009 (UTC)

Indeed it does. Thank you very much! TNXMan 14:29, 27 May 2009 (UTC)

The same issue I am facing in bengali wikipedia.- Jayanta Nath ^{(Talk|Contrb)} 08:54, 29 May 2009 (UTC)

The same issue? You said something else at WT:TW. What is it? Amalthea 09:42, 29 May 2009 (UTC)

this is diff. from that. I mean that when I use "rollback" or "rollback vandal" functions in bengali wiki, I get the following message: "Reverting page: couldn't grab element "editform", aborting, this could indicate failed response from the server." - Jayanta Nath ^{(Talk|Contrb)} 11:00, 29 May 2009 (UTC)

TW-B-298

Status:  Closed

Resolution: one-time glitch.

Even when I select a specific {{notability}} template to use, half the time it only places the basic {{notability}} instead of "Notability/Biographies" or some other. See this diff, where I actually selected "Notability/Biographies" but it only put "Notability --Ten Pound Hammer, his otters and a clue-bat • ^{(Many otters • One bat • One hammer)} 15:27, 31 May 2009 (UTC)

A WP:Friendly bug, but certainly a bug. Will look into it. Amalthea 15:46, 31 May 2009 (UTC)

Bleah. I keep forgetting that the templates are Friendly not Twinkle. Ten Pound Hammer, his otters and a clue-bat • ^{(Many otters • One bat • One hammer)} 17:09, 31 May 2009 (UTC)

Yeah, but maybe we should just generalize this for bug reports from either script? Enough people already report Friendly bugs here, and Friendly doesn't have its own bug report page anyways... =) ···「ダイノガイ千？！」^{? · Talk to Dinoguy1000} 19:58, 1 June 2009 (UTC)

Is it possibly that you have slightly mischaracterized the frequency with which you encounter this issue? From a look through your contributions of this year, this has happened exactly once.
Unless you can direct me towards other occurrences of this problem, I'll write it off as a one-time glitch, since there's nothing in the code I see that could explain this behavior.
Amalthea 15:02, 4 July 2009 (UTC)

TW-B-299

Status:  Resolved

Resolution:  Fixed

As a result of the corporate name RfC, we had consensus to make some policy changes. One of them included an express prohibition on explicit company names as user names, along with the removal of any implication that the username policy regulates user behavior. To this end the policy has changed:

• Promotional usernames are used to promote a group or company on Wikipedia.

Has changed to:

• Promotional usernames are advertisements for a company or group.

Twinkle reflects this section in the help popup under ARV->UAA, it should be updated to the new text to reduce inappropriate UAA reports. --Gigs (talk) 18:25, 10 June 2009 (UTC)

Hmm. Not that I see the difference, but Y done. If it's being changed again, please come back here and leave a note – I wouldn't be surprised if the wording is changed again. Amalthea 20:49, 10 June 2009 (UTC)

You are right about that, we may go back and tweak this based on how this affects reports at UAA/AIV/etc. Thanks. Gigs (talk) 21:20, 10 June 2009 (UTC)

BTW- When should this show up live? I'm not seeing it. Gigs (talk) 21:22, 10 June 2009 (UTC)

If you want to see it immediately, you'll need to refresh your browser cache. Amalthea 21:34, 10 June 2009 (UTC)

I did, don't know why it didn't work at first. In any case I do see the changes now, so it's all good. Thanks. Gigs (talk) 00:04, 11 June 2009 (UTC)

TW-B-300

Status:  Resolved

Resolution:  Fixed

Twinkle currently uses {{db-notability}} to tag articles for WP:CSD#A7, but that's a redirect to {{db-a7}}, and the redirect will shortly be deleted. Twinkle needs to switch the tag it uses, ASAP. --Aervanath (talk) 20:25, 10 June 2009 (UTC)

Y Done. Amalthea 20:43, 10 June 2009 (UTC)

WHY is the redirect going to be deleted might I ask? It's much more convenient. ηoian ‡orever ηew ‡rontiers 01:30, 16 June 2009 (UTC)

Discussion. Amalthea 06:42, 16 June 2009 (UTC)