Bugs and feature requests can be reported at https://github.com/azatoth/twinkle (you will need to have a github account). This will probably result in the issue being noticed sooner, as an e-mail is sent to all Twinkle developers. Alternatively, start a new discussion on this page. Possibly slower service, but you will be able to gain consensus, etc., if you need to.
Discussion
What happened to the "reason" parameter for blocking?
All of a sudden, the big white box that normally allows one to input the reason for a block has disappeared. It's not the end of the world, because the parameter isn't used for most of the specific templates like uw-vblock but it would be mildly irritating to have to do it the old-fashioned way just so I can type my own reason for the block. HJ Mitchell | Penny for your thoughts? 16:43, 2 September 2011 (UTC)[reply]
The block dialog was overhauled. You can now preview block templates (you don't get that rather pithy error message anymore). Along the way I decided to remove the "reason" box for block templates. The trouble with it was that, unlike for warning templates, the "reason" box used to actually change the wording of the template, rather than add a little note at the end (like the warning templates do). I did always have the intention of re-instating it if any admin came along and wondered about it, which has now happened. So I might add it back for some of the more general block templates... Sorry for the inconvenience. — This, that, and the other (talk)05:06, 3 September 2011 (UTC)[reply]
I removed it because I thought it was a redirect to a "templated block reason" template. It seems I was wrong. Maybe I made a typo when checking the template page on wiki. Sorry for the inconvenience; it should come back soon. — This, that, and the other (talk)00:47, 5 September 2011 (UTC)[reply]
Yes, and here's the deal. I use Twinkle all the time, it's never failed me, but right now, it's not working. I restarted my browser, Google Chrome, and it's still not working. Not much else that troubleshooting page can do for me. Feedback☎08:09, 19 September 2011 (UTC)[reply]
Any script errors? Try clearing your cache. Try disabling and re-enabling the gadget (assuming you use the gadget). If you don't use the gadget, remove the Twinkle code from your skin JavaScript file and enable the gadget instead. — This, that, and the other (talk)07:05, 20 September 2011 (UTC)[reply]
Hello, is it possible to mark new articles as "Patrolled" when you tag them for CSD? It would be quite easier than going to going to New Pages and marking it manually. Thanks. -- Luke(Talk)18:19, 19 September 2011 (UTC)[reply]
IIRC, 1) Twinkle does this automatically when the article is accessed through Special:NewPages; 2) articles cannot be marked patrolled when accessed through other means due to technical limitations in MediaWiki; and 3) there's a bot that auto-patrols articles that have been tagged for CSD or PROD. Anybody care to confirm or correct me on any of these points? jcgoble3 (talk) 22:03, 19 September 2011 (UTC)[reply]
If not mistaken, consensus has been for some time that we only need one TB message, not a list of fifty that all do the same thing. If you want to seek consensus for a change, go for it, but I would oppose it. SchuminWeb (Talk) 20:35, 21 September 2011 (UTC)[reply]
Feel free to hunt around for previous discussions on the matter, but there was never a consensus to add these templates to Twinkle. Not a consensus not to use, but rather no consensus to use. Same result (i.e. not adding the proposed templates), but very different meaning. SchuminWeb (Talk) 04:15, 23 September 2011 (UTC)[reply]
I see that this would probably be archived in a few days without more replies, and I would like to try one more time to get some input here from Twinkle users about whether {{wb}} should be included in Twinkle or not. I will not comment in this section again unless there are replies. ←cimanyD← contact me18:34, 27 October 2011 (UTC)[reply]
DI on files
Resolved
Turns out Twinkle's DI tab does not work correctly. At least, I know it doesn't work on IE9. I have uploaded my browser details here, minus my IP address. (I will give my IP only if needed. If needed, just pm me on IRC. I use LikeLakers2-1 as my main laptop nick, and LL2|JedIRC as my phone nick. Basically, look for a user with the host wikipedia/LikeLakers2) LikeLakers2 (talk | Sign my guestbook!) 14:01, 24 September 2011 (UTC)[reply]
Hi. I just semi-protected Overblood. The protection action by Twinkle went just fine, but the tagging of the page failed with the following: Tagging page: Failed to save edit: Unknown error: "231". I was able to tag the page via a separate "Tag page with protection template" action, but I assume my inability to protect and tag in a single step was a bug. I'm a new admin, and this is my first attempt to do this. Any thoughts? Richwales (talk) 02:35, 26 September 2011 (UTC)[reply]
First of all, welcome to the world of adminship. Good to see that you're giving your newfound abilities a spin. Zordon tells me that you'll be commanding the wise frog ninjazord in battle. :-)
Otherwise, I set up a test page in my own userspace and fired a few test shots at it. The page is located at User:SchuminWeb/Protection target. In running tests, I set it to semi-protect for an hour and put the small tag lock on it at the same time. I discovered the following:
That process also tagged the page with the {{pp-protected}} tag, included the reason and expiration date as a parameter, and set it to small. The template did not appear on the page.
I threw another tag at the page and got one to stick, as the {{pp-semi-indef}} tag managed to show the icon as intended. However, I didn't like that as a reason, so I investigated further.
Going back to the original template, I changed the date on the template to something further in the future. The intended icon showed up.
This brings us to a couple of possible scenarios:
(A) Twinkle is not adding enough information for the template to "expire" (i.e. hide itself) at the right time. I am not sufficiently versed in that particular template's workings to say for sure. This scenario concludes that Twinkle's treatment of the template is incomplete.
(B) The template is not designed to be specific enough in when to expire the template since if the date is set for the same day, the template will expire even though the protection has not. Thus the template has the problem, but if the template is modified, Twinkle would need to be modified along with it to incorporate any new features that get built into the template.
Personally, I vote for B as the more likely of the two.
Considering that these two edits are three minutes apart, it is highly unlikely that Twinkle made both of those edits in the same sweep. Twinkle did my protect-and-tag as two edits, with one applying the protection and a second putting the tag on. Both were done within a minute of each other. So for you, with the information that I found through researching as well as what you said, I can't say with certainty that you properly set the script to tag the page. There's no tagging along with the protection in the edit history that's consistent with the results that I got. I don't know if you made a mistake or if Twinkle dropped the ball somewhere (which sometimes happens).
So first of all, we discovered a potential issue that we may want to fix somewhere related to how specific we want to be with the expiry date on the protection template. That's more likely a project issue, though, and not necessarily a Twinkle issue.
For your specific problem, what specific options in Twinkle's protection box did you set, and what did you set them to? Also, could you please make the same protection action at User:SchuminWeb/Protection target? Would like to see if your specific result with your same actions happens again in a more controlled environment outside article space. I've reverted the page back to its original form so you can test.
First of all, "error 231" is a known glitch, when Twinkle tries to edit too quickly. It needs to be fixed on the server end; bugzilla:29246 has been fixed but the fix apparently hasn't been applied to Wikipedia servers.
Secondly, the protection template not displaying (even though it is present in wikicode) is probably not Twinkle's fault. Twinkle doesn't even add an expiry date to the template (bots come around and remove protection tags from unprotected templates). — This, that, and the other (talk)05:01, 26 September 2011 (UTC)[reply]
I did the second edit (applying the tag) as a separate Twinkle operation, after realizing that my first Twinkle operation (protecting the page) hadn't applied a tag. It took me a couple of minutes to take a screen shot of the page (just in case it might have been useful), then try to edit the page (to see if it had been successfully semi-protected), and finally decide to try tagging the page in a separate Twinkle operation. I haven't tried protecting your sample page yet, but I will in just a minute. FWIW, I semi'ed the Overblood page for two weeks; it's been the object of recurring bouts of vandalism spaced about four days apart — possibly to discourage administrator action at WP:RFPP by always making it look like the problem has gone away and thus doesn't merit intervention. Richwales (talk) 05:19, 26 September 2011 (UTC)[reply]
Protection reason: I added some text after the default message, so it said the following: "Persistent vandalism; testing what I did earlier to see what happens now"
There are two separate issues here, it seems: one is the Error 231, which (as I have said) is waiting to be fixed on the server end. Richwales, since this issue seems to be recurrent for you, you could ask Roan Kattouw, the lead developer of the API, where this fix has ended up.
The other issue is the protection template disappearing. I suspect this occurs when a same-day expiry is set (e.g. protecting for 8 hours at 08:00 UTC), since the template is only passed a date parameter. Does this explain it? — This, that, and the other (talk)10:09, 26 September 2011 (UTC)[reply]
Hi. OK, I'll contact Roan and ask about this fix for error 231. As for your other point, I'm confused — I tried to set a semi-protection on this article to expire after two weeks (not on the same day!); and in any event, I had understood that protection templates were removed by DumbBOT rather than expiring automatically on their own. Or were you talking about something else here? Richwales (talk) 13:40, 26 September 2011 (UTC)[reply]
And Roan (Catrope)'s response: "The fix is in MediaWiki version 1.18, which is scheduled to be deployed to English Wikipedia on October 5th."Richwales (talk) 14:11, 26 September 2011 (UTC)[reply]
According to WP:ABOUT, Wikipedia is now running version 1.18wmf1 (r99094). Anyone who can tell if this bug has in fact been resolved or not, please let us know. Thanks. Richwales (talk) 17:23, 6 October 2011 (UTC)[reply]
Backslash-escaping apostrophe in username leads to bug
Resolved
I just reverted an edit by Jodelle's Acolyte (talk·contribs). This opened a new window for User talk:Jodelle\'s Acolyte - note the stray backslash that's obviously meant to escape the apostrophe character so it's not interpreted by JavaScript. The user talk page doesn't exist because I'm looking at the wrong address for it. Browser info: Chromium 14.0.835.126 (Developer Build 99097 Linux) Ubuntu 11.04. Elizium23 (talk) 22:03, 26 September 2011 (UTC)[reply]
I've had a trawl through the archive here and see that Stub-tagging functionality was switched off about 4 years ago. It would be great to have this option available with - as someone suggested - a required dropdown menu of Stub types. Please? FunkyCanute (talk) 11:52, 27 September 2011 (UTC)[reply]
I don't know if this is just a problems for admins using Twinkle, or all users, but ever since I became an admin, when I report something to RFPP via Twinkle (because I'm too involved to protect the page myself), Even though I fill in a reason in the Twinkly box, the result on RFPP is "undefined." Anyone else experiencing the same problem? Qwyrxian (talk) 05:37, 28 September 2011 (UTC)[reply]
I fooled Twinkle into thinking I was an admin, and encountered the same problem in Firefox 8 beta. I'll get to the bottom of it for you. (By the way, is there any reason you haven't upgraded Firefox to version 7? 3.6 is not new, and IIRC Twinkle doesn't work perfectly on old Firefox version - I only tested on Firefox 4 and IE9 during the big rewrite earlier this year.) — This, that, and the other (talk)10:54, 3 October 2011 (UTC)[reply]
Hmmmm, I thought I had the newest-but-one version; I don't think I'm actually years and years behind. I'll take a look into it tomorrow night. But when I check the About Mozilla Firefox window, it shows 3.6.23.... Qwyrxian (talk) 13:25, 3 October 2011 (UTC)[reply]
That's because Firefox < 4 doesn't check for new versions, just incremental updates (i.e. 3.6.x). You actually need to download and install the latest version of Firefox - the new versions will keep you up-to-date with the very latest releases and features, not just incremental security fixes. — This, that, and the other (talk)02:42, 4 October 2011 (UTC)[reply]
AFAIK the problem still exists even in the latest Firefox version. I was merely suggesting that you upgrade your browser. (See my second reply above.) On my side, I need to do some debugging to find and fix the error. — This, that, and the other (talk)04:55, 4 October 2011 (UTC)[reply]
Please change $.client.profile().versionBase < 9 to $.client.profile().versionNumber < 9; the former tests a string to a number, and returns false on IE <9; the latter tests a number to a number, and returns true on IE <9. —mc10 (t/c)14:24, 30 September 2011 (UTC)[reply]
The option already exists, as there is now a "Tags" menu for files under Twinkle, which is derived from FurMe. Not in the same dialog, mind you (and I would oppose putting the rationale-placing and maintenance-tagging on the same dialog), but both exist. SchuminWeb (Talk) 14:03, 2 October 2011 (UTC)[reply]
RPP and ARV pages on watchlist
RPP and ARV: after a report made to the projects' pages using Twinkle they don't show up on my my watchlist any more. I looked, but I couldn't find this as a reversible option; am I looking in the wrong place? --Old Moonraker (talk) 17:30, 3 October 2011 (UTC)[reply]
Sorry, that's not worded well. The addition to my watchlist after the edit doesn't happen. I haven't made any RPP or ARV requests since so I can't report on the current situation. Thanks for taking a look. --Old Moonraker (talk) 07:04, 5 October 2011 (UTC)[reply]
I've got the second drop arrow behind the "TW", and also the categories box at the bottom of pages looks different. I'm guessing that this has nothing to do with Twinkle directly, and that there was an update of some sort to Mediawiki or to the interface that is causing the weirdness. SchuminWeb (Talk) 01:32, 5 October 2011 (UTC)[reply]
Also getting this from TW while welcoming:
User talk page modification: Unknown error received from API while saving page
Info: Will add the welcome template to the bottom of the user's talk page.
Info: Will create a new heading for the welcome
Info: Will substitute the {{Welcome-anon}} welcome template
Info: Will add your username to the template
Info: Will add article link to the template
Info: Will add your signature after the welcome
Will warn, but will not warn when it requires making a new talk page, same error as above. I use monobook, so no vector issues. Win XP, Firefox 6. --Fiftytwo thirty (talk) 02:40, 5 October 2011 (UTC)[reply]
I've read the box:, but here are some more things that might help:
Tagging page: completed (Topsail Turtle Project)
Opening page "Topsail Turtle Project": Retrieving page creator information
Notifying initial contributor (Rpags): Failed to save edit: Exception Caught: FauxRequest::getRequestURL() not implemented
Adding entry to userspace log: completed (User:Kudpung/User:Kudpung/PROD log)
The requested page or revision cannot be found
The database did not find a page or revision that it was expecting to find.
The relevant page of the wiki was "User talk:Rpags" and the requested data (for error checking purposes) was:
[14:23:10] <anomie> TimStarling- A while ago the creation wasn't working at all. Then someone apparently changed something, it stopped completely crashing on the exception but started creating these pages with page_latest = 0. According to comments on bug 31364, r97291 may fix it.
The rollbacks have just disappeared for me as well – using Safari, vector skin. My Twinkle drop down menu remains, though. Jenks24 (talk) 04:06, 5 October 2011 (UTC)[reply]
Firefox 3.6.23 (what, all the newer ones break FEBE) and no TW here either. Additionally, some stuff I thought was just regular Wiki options seems to be a little borked but I haven't looked it up to make sure it's not something that is actually set with TW yet. Millahnna (talk) 04:11, 5 October 2011 (UTC)[reply]
Update: Twinkle is working again for me. Haven't done anything between my original post and now. Maybe it was fixed on Twinkle's end? Mkdwtalk15:38, 5 October 2011 (UTC)[reply]
OK so it seems I still have part of twinkle but not all of it. Everything looks normal when I'm looking at an actual diff but the vandal/rollback listings next to a "top" on a user's contribs page isn't displaying. Is it possible this is connected to the wiki-wide errors I'm seeing (the stuff I hadn't looked up earlier)? Specifically, using the vector skin, my option under the Appearance tab on preferences to see edits collapsed (watchlist, recent changes) seems to be broken at the moment. This is one of those moments where I'm explaining things really piss poorly isn't it? Millahnna (talk) 08:53, 5 October 2011 (UTC)[reply]
Yeah using it on a diff works fine (haven't used to place a message on a user page yet) but no display on contribution pages. I'm guessing this is connected to the stuff noted in the section above (Strange Underlining). I have the double drop down arrow thing described there, too. Millahnna (talk) 09:10, 5 October 2011 (UTC)[reply]
I have uploaded a fix to this issue (no rollback links on contributions pages) to the repository, but I need an admin (Amalthea, Ioeth, or AzaToth?) to sync the gadget file before anyone here will benefit from the fix. — This, that, and the other (talk)10:19, 5 October 2011 (UTC)[reply]
WikiDan, I notice you are loading Twinkle from monobook.js. Could you please try removing the Twinkle code from your monobook.js file and instead enable Twinkle as a gadget? (BTW, that was almost a perfect problem report: short, to-the-point, included browser name and wiki skin... the OS is generally irrelevant to these sorts of things, but better to tell too much than to tell too little...) — This, that, and the other (talk)10:34, 5 October 2011 (UTC)[reply]
I have no Twinkle either I am using Firefox 6.0.2 Mac OS X version 10.6.8 with Vector skin and have Twinkle enabled through my wiki preferences.Theroadislong (talk) 11:09, 5 October 2011 (UTC)[reply]
Everyone: Please try these things in the hope of restoring Twinkle:
Still the same behavior as reported earlier and I've completed all steps except updating to firefox 7 (breaks my plugins). So it's essentially usable for me, it just looks odd. I'm still seeing the (unrelated to twinkle) errors that I described, as well (which also borked sandbox links for me). So I'm guessing that things will calm down once the mediwiki upgrade is completed and has its kinks ironed out. I have a whole slew of errors related to wikipedia in my error log (again I think this is stuff that's site wide). Consistently all say "expected important but found ie". Millahnna (talk) 12:11, 5 October 2011 (UTC)[reply]
Not working for me: Firefox 7.0.1. Cleared cache. Relogined. I get the following error in console: "Error: Twinkle.prefs is null
It is not working for me at all. I have cleared cache and upgraded to latest versions of Chrome (14.0.835.202) and Firefox (8.0). I am using the vector skin.
Based on the Firefox error, I went to Wikipedia:Twinkle/Preferences to try to set my twinkle preferences, the page. That page told me, "You must have Twinkle installed (either as a gadget or manually as a user script) to use this page." So I checked my Preferences and Twinkle is checked on the gadgets page. GBfan12:58, 5 October 2011 (UTC)[reply]
Running latest version of Google Chrome and have no Twinkle at all currently; very frustrating. Huggle also appears to be hit and miss this morning. Calabe1992 (talk) 13:36, 5 October 2011 (UTC)[reply]
Mine isn't. No sign of it in Chromium or Firefox (newest versions) after clearing cache; I created the .js file per GB Fan and restarted the browser, still nothing. I also have it enabled as a gadget but the preferences page says I do not have it installed. Hope this is resolved soon; Twinkle makes it possible to perform so many tasks that are insanely complex when done by hand.--~TPW14:16, 5 October 2011 (UTC)[reply]
As I previously stated, I copied the code and am still getting the could not parse error. But Twinkle works on any page except for a Special:Contributions page. Oddly, on any of these, it fails to display (typically it shows at least the report user option, correct?). Calabe1992 (talk) 15:40, 5 October 2011 (UTC)[reply]
+1 for "working after c/p'ing the script." I didn't need to restart the browser, but I did bypass cache. Firefox 3.6.18 here. Tckma (talk) 17:48, 5 October 2011 (UTC)[reply]
There seems to have been no posts for a few hours now. Are people still having problems like me? Or has it gone quiet on the front because it's working for everyone? I've tried updating and bypassing, install/uninstall, but still no Twinkle pour moi as yet. Jared Preston (talk) 21:50, 5 October 2011 (UTC)[reply]
It has completely disappeared for me--a major inconvenience. I reverted to Firefox 3.6 after disasters with Firefox 4. An improvement in Twinkle that requires a later version of Firefox is no improvement at all. Please: what's a subpage, and how does one employ it? Hertz1888 (talk) 22:03, 5 October 2011 (UTC)[reply]
P.S. Everything seems to be working, but I'm getting an ever-present "Could not parse twinkleoptions.js" notice at the top of the window; I hope it is not cause for concern. Any advice on making it go away would be welcome. Hertz1888 (talk) 22:47, 5 October 2011 (UTC)[reply]
Tried your advice, GB fan, but unfortunately it doesn't work for me - it's the same no matter what I have in twinkeoptions: I get the top-tabs, but no rollback links on contribution pages or histories.
I'm using Firefox 3.6.23 on Mac OS 10.4.11. Twinkle has gone away, and I'd rather not plough through what looks like several pages of discussion above in order to get it sorted. Any chance of a précis about what's happening, the best way to get it fixed (and hopefully what steps are being taken so this doesn't happen again?) TonywaltonTalk22:59, 5 October 2011 (UTC)[reply]
I followed the above instructions when Twinkle stopped working for me and it has been restored. Much thanks to GB fan and to Chzz for helping me out. Shearonink (talk) 23:16, 5 October 2011 (UTC)[reply]
That almost worked. After doing the above I got most TW tabs back, but the tab I use most (warn) was missing. After going into the Twinkle Preferences panel, making a change to the "Warnings" settings and saving, then clearing my browser, it's all back. And I have a new .js to play with! Thanks for the advice, GB fan. Perhaps those instructions should be put somewhere prominent... Cheers, TonywaltonTalk23:25, 5 October 2011 (UTC)[reply]
I've tried all of this, and on two different computers—one using the http interface and one using the https interface. XP, latest Chrome, Vector, multiply-cleared cache. Any advice? Bongomatic14:03, 6 October 2011 (UTC)[reply]
I am seeing a box on top of most pages on Wikipedia that says "Could not parse twinkleoptions.js". Twinkle seems to work fine. Any hints about what the problem could be and how I can remove the message? --Saddhiyama (talk) 16:51, 6 October 2011 (UTC)[reply]
Same here, intermittently. A browser refresh seems to make it disappear. Two different computers, but both with FF 7.01 on Windows. Andyross (talk) 22:48, 6 October 2011 (UTC)[reply]
Are you using the gadget or a very old javascript inclusion in the skin? Everything worked once I removed the custom inclusion and enabled the gadget instead (on Chrome 15/win). -- Luktalk23:04, 8 October 2011 (UTC)[reply]
I'm still getting this error message too, I'm using the most up-to-date version of Firefox. Also, another thing I've noticed happen in the last few days, whenever I go to cite a reference, if you click the little green thing that usually finds the page title, it's now saving the page?--5 albert square (talk) 00:07, 11 October 2011 (UTC)[reply]
Rollback not working
I haven't been able to get rollback to work over the last couple of days. The buttons are there, but don't achieve anything. Firefox 3.6.23, Windows XP 2002 SP3. Had same issue on a notebook PC. SpinningSpark18:58, 6 October 2011 (UTC)[reply]
Update, I have added the js page discussed above but with no improvement and now the user warning templates are not working - at least in cases were a new talk page is being created. SpinningSpark19:20, 6 October 2011 (UTC)[reply]
You shouldn't need to add the JS page anymore – that problem has been fixed. See WP:TW/DOC#Trouble, in particular, the part about script errors. Do you see any script errors after clicking a rollback link? And please be more specific: in what way is "the user warning templates not working"? — This, that, and the other (talk)05:07, 7 October 2011 (UTC)[reply]
Seems to be working again this evening so you are probably not very interested any more, but here goes anyway. There were no script errors, the page being rolled back changed to display a blank article with just the title showing and the Twinkle pop up box did not appear. The browser status bar said something like "downloading from urlxxx" and just hung there. If I moused-over any link in the menu bar the status changed to "done". Nothing further happened until I navigated off the page and nothing was writtten to the page history. SpinningSpark17:09, 7 October 2011 (UTC)[reply]
Coming and going
Like the others above, I had the same period of cursing when Twinkle was apparently AWOL. Twinkle is back - but playing hide and seek on the machine I'm using. Sometimes the buttons are there, sometimes they wait before appearing (then snap in like kids sneaking into the classroom while Sir isn't looking), other times they don't appear and I have to refresh the page. Occasionally I have to do this with Ctrl Reload before the buttons come up. I'm using Firefox 3.5.17 (being very stubborn about wanting to keep TabKiller - I loathe tabs) on XP Pro 2002 SP3 (set to Classic mode without those Big Bright Buttons and with a nice plain grey instead of that headache inducing blue). Peridon (talk) 19:55, 6 October 2011 (UTC)[reply]
One odd thing is that when it's doing the hide bit, I get all the rolled up sections displayed in full, with the show/hide option missing. It may be nothing to do with Twinkle - but it's funny that it's started at the same time. Peridon (talk) 22:17, 6 October 2011 (UTC)[reply]
Recently, the rollback links disappeared from all user contributions pages. All I see now is (top). I verified the appropriate preference in WP:TWPREFS, even toggled it off/on again. Help? Elizium23 (talk) 05:35, 7 October 2011 (UTC)[reply]
When I open contributions pages there are no TW links. It was not like that yesterday. But when I click "search" the TW links show up. Oda Mari (talk) 06:39, 7 October 2011 (UTC)[reply]
I'm also not seeing TW links on user contributions pages, but they come back when I click the "Search" button. BTW I am seeing the rollback links. —Bruce1eetalk06:59, 7 October 2011 (UTC)[reply]
I'm getting the "Could not parse twinkleoptions.js" notice on Google Chrome v14.0.835.202 m. I check on Firefox v4.0 and I do not get this error. Only other gadget I'm using is Navigation Popups. (from Special:Preferences#mw-prefsection-gadgets.
Wow. I fail. Should've read through everything above. Thanks for pointing out the obvious to me. For others, ctrl+shft+del (or cmd+shft+del on macs I suppose), "Obliterate the following items from the beginning of time", only have to check "Empty the cache." Sorry for the bother!--PolicyReformer(c)22:47, 8 October 2011 (UTC)[reply]
I'm getting the "Could not parse twinkleoptions.js" message, but TW seems to be working fine. I'm runnin Firefox 7.0.1 on W7. Clearing cache isn't helping. Lynch718:08, 8 October 2011 (UTC)[reply]
I mentioned above that user warnings were not working. After some experimenting, it seems the warnings only fail to get posted when the talk page has not previously been written to, that is, are redlinked. Twinkle gets as far as "Info: adding a shared IP notice" and then hangs and does not post the warning. Still not sure if this also applies to registered users. SpinningSpark09:51, 8 October 2011 (UTC)[reply]
I'm not experiencing this issue -- it works for me on FF 3.6.3 as well as later versions (don't have those version numbers handy). —Darkwind (talk) 17:44, 8 October 2011 (UTC)[reply]
Ok, just tried it on a completely different machine; Windows XP V5.01 SP3, Firefox V6. Same result, didn't work (also tried a machine running IE6 but I expect you already know what that did). So its looking like its something to do with my Wikipedia account. Could it be monobook skin related? SpinningSpark19:16, 8 October 2011 (UTC)[reply]
It seems the problem was I only had certain Twinkle functions installed that I commonly use. Is it still possible to do this in some way? It is a nuisance having a lot of tabs on screen that I don't use, especially when I am working from my small screen notebook. SpinningSpark23:03, 10 October 2011 (UTC)[reply]
Yes - those single-function scripts are positively ancient. Don't use them - they could break down at any time, as Spinningspark has discovered.
Possible change of wording in Orphaned non-free "image" warning
I'm not sure which template is being transcluded to the user talk page in the "File for dated speedy deletion" - "Orphaned fair use" (F5) section, however, the message title is "Orphaned non-free image File:Fubar". Can this be changed to "Orphaned non-free File:Fubar" (removing "image" as not all of the Files are Images). Thanks. Skier Dude2 (talk) 02:58, 9 October 2011 (UTC)[reply]
Comment I think using "file" instead would be better than simply removing the word (i.e. "Orphaned non-free file File:Fubar"). That way it's immediately obvious what it is. jcgoble3 (talk) 03:18, 9 October 2011 (UTC)[reply]
I tweaked the option to open a user talk page and set it to be "In a new tab". However, a new window still opens for user talk pages. Now instead of being different geometry from my main Chrome window, it is exactly the same size and placement. I had hoped this would, well, open a new tab in my existing browser session. Chromium 14.0.835.126 (Developer Build 99097 Linux) Ubuntu 11.04. Elizium23 (talk) 05:10, 9 October 2011 (UTC)[reply]
For that matter, I'd like to be able to suppress opening a user talk page entirely, since I prefer to open them on my own after making sure that the reversion is done to my satisfaction first. SchuminWeb (Talk) 18:23, 9 October 2011 (UTC)[reply]
Re Elizium23, I would have hoped so too. Getting things to open in new tabs is notoriously fickle; I'll have a play around and see if I can improve the current functionality, but I may not be able to. — This, that, and the other (talk)06:24, 10 October 2011 (UTC)[reply]
In my experience, that's a goes-at-the-top template, rather than a "real" block template. That usually goes in tandem with a real block template in the usual place. That said, is it really that necessary to have this template on Twinkle, considering it goes in a different place than anything else we've got programmed in? In other words, is it really worth the trouble to design this in, above certain things but below others, etc.? SchuminWeb (Talk) 04:25, 13 October 2011 (UTC)[reply]
This is requested about once every three months or so. I was just thinking that we hadn't heard about this for a while... and now I'm wondering why we haven't given much thought to implementing it. Plenty of reasons have been put forward about why it should not/cannot be added: but I think we could probably integrate this into the Shared IP feature. — This, that, and the other (talk)07:03, 13 October 2011 (UTC)[reply]
Yes, there may be the occasional request for it, but the actual occurrence for its need is very low. besides which, Twinkle menus already have grown in length to the extent of almost defeating their own purpose, and in some instances it's now getting quicker to manually copy and paste a template from the catalogue of templates. However, the best place to discuss new template is at Wikipedia talk:Template messages/User talk namespace - Twinkle is only one of the methods of applying them. --Kudpung กุดผึ้ง (talk) 09:16, 13 October 2011 (UTC)[reply]
If we're talking about adding the option to add the top box with TW, this is the place to have the discussion. If there is a desire to create a "real" blocking template to that effect, then that's a discussion, as Kudpung mentioned, to be had at Wikipedia talk:Template messages/User talk namespace. I've got that page watchlisted as well, and will hold any opinions I might have on that matter until I see a discussion over there. SchuminWeb (Talk) 19:48, 13 October 2011 (UTC)[reply]
Well, what I was trying to say was, the existing Template:Schoolblock is already being used as a blocking template added to the "level-two monthly headings at the bottom when blocked" instead of at the top of a page - see the bottom of this page, for instance. That said, given that apparently it is supposed to be at the top, being able to tag-n-bag with TW with it would be good. :) - The BushrangerOne ping only06:52, 14 October 2011 (UTC)[reply]
Tagging images on Commons from Wikipedia
It would be very useful to have the option of tagging an image from its Wikipedia description page that is actually on Commons. Recently there have been a lot of images I've tagged with {{BadJPEG}} or similar, but had to click through to the description page on Commons and manually edit the page. I know Commons templates are different from Wikipedia's and that adding all of them to Twinkle and keeping up with changes and additions would be an entire project on its own. Perhaps simply adding an extra text box in the config with a newline-delimited list of user-defined Commons templates? —danhash (talk) 16:50, 13 October 2011 (UTC)[reply]
This kind of script should be managed at Commons, not here. Ask the folks there if it can be done; I would certainly be happy to help port such a script to English Wikipedia if it were completed by Commons people, as that particular task would be fairly simple. — This, that, and the other (talk)06:46, 14 October 2011 (UTC)[reply]
Make selecting multiple criteria for speedy deletion the norm
Twinkle supports {{db-multiple}} but makes it hard to use it with multiple windows popping up, one for each criterion, plus the normal window. Can this changed to make multiple selections the norm, for example by using check boxes instead of radio boxes? It has come up multiple times at WT:CSD that taggers seldom use {{db-multiple}} even when it would be warranted (for example to tag copyvio that is also advertising) and I guess one of the reasons for that is that Twinkle, which many people use, does not make it easy for them. Regards SoWhy17:17, 14 October 2011 (UTC)[reply]
There are several reasons against this:
It would make speedy deletion less speedy (more clicks involved);
It would encourage users to select many criteria, when more often than not, one is enough (for example, by far the most common speedy criterion is A7, which nearly always stands alone, although it is sometimes coupled with G10, G11, or G12);
It overestimates the frequency with which specifying multiple criteria are actually helpful;
It could encourage foolish taggings where all (or a lot of) the boxes are mischievously checked.
In my view, Twinkle makes it easy enough to tag with multiple criteria; it is an illusion that multiple boxes are popping up - it is in fact the one box, which is cleared for a specified interval (<0.5 sec) after each selection to give the user visual feedback that Twinkle is ready for their next selection. — This, that, and the other (talk)23:50, 14 October 2011 (UTC)[reply]
Let's see:
"Speedy" in "speedy deletion" does not refer to the amount of time it takes to tag a page; quite the contrary, tagging pages should be done after careful thinking, so having to click "OK" after selecting the criteria is not really harmful. Plus, this way mistaggings due to mistakenly clicking on a certain selection would be avoided.
The point of my request was that users select only one criterion where multiple apply - for example, only A7 instead of A7 and G11. As Blanchardb correctly notes at WT:CSD, this leads to deletions for a certain reason which the creator rectifies only to have it deleted for a different reason afterwards, e.g. G12 tagging => text is released as open source => G11 tagging.
It's more frequently useful than it's used today (see above)
Anything Twinkle allows you to do can be used mischievously. That alone has not nor should ever be a reason to remove or decline any feature. Furthermore, Twinkle could easily limit the number of criteria to be picked.
I know how that it's always the same box but for anyone not tech-savvy, it will look as if multiple boxes are popping up. Regards SoWhy08:52, 16 October 2011 (UTC)[reply]
I'm still not convinced... I think my main issue with this is that admins are intelligent: no matter what tag is applied to an article, the admin should be able to judge whether the article falls under any criterion. (For example, an article tagged with G1, which is coherent and not nonsensical, but still obviously non-notable, can and should be deleted under A7.) So one shouldn't get too hung up about articles being tagged with the wrong criterion (with the possible exceptions of G10 and G12).
Let's see what the others say. (By the way, I don't really understand your second point... how often does a G12 tagging actually lead to release of material under a free license?? I can't say I would expect it to happen, although I suppose it might.) — This, that, and the other (talk)10:00, 16 October 2011 (UTC)[reply]
I guess most admins are intelligent but that's not the point, is it? Admins deleting an article will not notify the user if they apply multiple criteria, so in most cases the user will know about why the page was tagged for deletion by the message the tagging user left them on their talk page (hence it's important to tag correctly). Regards SoWhy18:25, 17 October 2011 (UTC)[reply]
Realize that most admins are super-intelligent beings. When they give you the mop, you see, they also implant a device in your navel that gives you added mental capabilities. It's kind of like your own natural USB port. Thus if you have an "outie", you can't be an admin, because you lack the proper port to accommodate the super-intelligence device that all admins get installed.
Seriously, though, speaking for myself when I do speedies, I don't think I've ever applied multiple criteria to a speedy deletion. I will pick one criterion that applies and go with that to make the deletion, and if others apply as well, so be it, but I'm only coming up with a "main" one. Sometimes I diverge from the nominator's reasoning. One of the most common ways I diverge is in biographical articles. Someone will make an article saying, "Johnny Doe is a student at Angel Grove Elementary School who makes really great mud pies in the playground!" for instance, and while it will be tagged for A7 (which would certainly apply), I'll actually speedy it as G10 (attack page).
So the moral of the story is that it's just not necessary to have the option to tick multiple speedy criteria. An article that is obvious crap is pretty self-evident. Any admin worth their stuff knows what true speedy deletion candidates look like for various categories, and it's not necessary to specify a thousand reasons. It just has to meet one speedy criterion to get deleted, and then we move on. SchuminWeb (Talk) 19:44, 17 October 2011 (UTC)[reply]
Anyway, yes, I checked to see if it was just that that was the only problem, and it seems it is the only part of the TB module that isn't working. Changing the selection to "Administrators' Noticeboard" brings this error up on IEs script debug:
SCRIPT5007: Unable to set value of the property 'value': object is null or undefined
I fail to see the problem in the screenshot. There is not supposed to be a "reason" box for AN/ANI talkbacks, as the templates don't have the capability to insert custom messages. But I'll look into the other error. — This, that, and the other (talk)03:19, 9 October 2011 (UTC)[reply]
I meant that it doesn't do jack when I click Submit Query.
Just make it use {{subst:#ifexist: Template:$1 | {{subst:$1|$2}} ~~~~}}, where $1 is the template name, and $2 is the parameters. This will make it add the template if it exists; on the other hand, if it doesn't, it'll be a generic WP:NULLEDIT. LikeLakers2 (talk | Sign my guestbook!) 01:06, 15 October 2011 (UTC)[reply]
I don't like this change: this means Twinkle will be saying it notifies users when it actually isn't. Also, it doesn't give us the feedback when notification templates are missing. I'm highly tempted to undo it, for that reason.
When moving pages, it would be very helpful if the move dialog didn't occur on a separate page, but instead occurred at the top of the page (like "add to watchlist"). I recently moved several hundred images named DSCto more descriptive names, and most of those new names were based on text on the page itself. Keeping everything on one page makes it a lot easier to double-check, less likely there is a typo, and less likely that one page will be moved to a title intended for another. The dialog doesn't take up much space, so there is no need for a separate page. Could this functionality be added? ▫ JohnnyMrNinja01:47, 16 October 2011 (UTC)[reply]
Twinkle has disappeared for me, right down to the preferences page saying it's not installed (which it is). Am I doing something wrong, or is Twinkle broken? WikiPuppies! (bark) 05:08, 17 October 2011 (UTC)[reply]
If Twinkle was broken, I think there would be a ruckus on this page. But there isn't, which probably means something on your end is at fault. I take it, from your message on my talk page, that it was a sudden loss? Perhaps check your (wiki) preferences, and clear your cache.
I cleared my cache, and it still didn't show up. This is very strange, considering that it's the exact same thing as what happened to other users (explained in other threads). Should I try using Vector? WikiPuppies! (bark) 15:30, 17 October 2011 (UTC)[reply]
Seems to be working fine, from what I can see (it didn't do what you wanted, but it did what it was supposed to do).
By the way, trawling through your contributions to find this edit, I noticed you do a lot of page protection, so you might benefit from Twinkle's PP tab – it actually works properly since the big June upgrade. I'm not an admin, so I don't know of the benefits of Twinkling page protection (other than the fact that it automatically applies the protection lock icon), but it's just a thought. — This, that, and the other (talk)08:47, 17 October 2011 (UTC)[reply]
Does anyone else think the " Deleted because" in the explanation for mass deletions should be removed? The comment in the deletion log is inherently a reason/explanation, there's no need to state it again. — Train2104 (talk • contribs • count) 14:57, 19 October 2011 (UTC)[reply]
I was thinking this the other day too. Batch delete hasn't been fixed up for years, so it could do with a bit of a polish-up. Please do tell me about any other issues you might find with it while I fix this one. — This, that, and the other (talk)05:49, 20 October 2011 (UTC)[reply]
On this edit I started to tag the image with {{Image-Poor-Quality}}, but once the prompt box came up asking for the reason, I wanted to check the image again since, in my scatter-brainedness, I hadn't already figured out what I was going to type. My bad, I know. So I hit cancel, but it still saved with a partial edit. Was using Chrome 14. Generally with Twinkle I've noticed that hitting cancel on a prompt cancels the whole operation. Also take note of the edit summary it left. How hard would it be to change these edit prompt boxes to the same in-page prompts twinkle also uses? This would've helped a lot as I would've been able to switch to another tab and look at the image again; plus, dialog pop-ups that usurp UI control are just annoying. I know that'd be at least a little more code to add though; would it be possible to at least make hitting cancel return an error/abort the edit? —danhash (talk) 15:24, 19 October 2011 (UTC)[reply]
Could we get Twinkle to automatically tag new pages as patrolled regardless of what criteria they've been speedied for? I was just informed that it doesn't do this for all of them, which explains why I've found I've speedied some but not "patrolled" them. Calabe1992 (talk) 15:32, 19 October 2011 (UTC)[reply]
I don't know who told you that, but I think they're wrong. AS for as I can see, Twinkle should patrol the page regardless of the criterion selected; the only deciding factor is whether the page was reached from Special:NewPages or not; if it is not reached from NewPages, there is no way that Twinkle (or a manually-editing user) can mark the page as patrolled. — This, that, and the other (talk)11:04, 20 October 2011 (UTC)[reply]
I just tested it myself. Twinkle is correctly marking CSD nominees as patrolled. It is not, however, marking PROD nominees as patrolled. So it appears there is a bug of some sort, but not as extensive as we originally thought. SchuminWeb (Talk) 13:35, 20 October 2011 (UTC)[reply]
(←) Thanks, I hadn't noticed that point in the to-do list. So Twinkle should (eventually) mark PRODed pages as patrolled when possible, but doesn't at the moment. →Dynamic|cimanyD← (contact me) 21:13, 20 October 2011 (UTC)[reply]
There is a reason that I personally haven't implemented PROD patrolling, and it is that PRODs can be easily removed by anybody, in which case the page languishes without being fixed up. If you can convince me I will implement it - it's only three lines of code (plus config code). — This, that, and the other (talk)04:04, 21 October 2011 (UTC)[reply]
Hello, hoping someone can help. I can't seem to get the CSD log to work. I've made multiple edits to the preferences, changed the location various times- the default location was "CSD log", I changed it to "User:France3470/CSD Log", which seems to make it register in the code but resulted in no page being created. I even went so far as to create the page myself (which may have an a no-no). I've searched extensively through previous discussions but I really haven't any clue as to what the issue is. Here is the most recent diff: [2] -France3470(talk)14:59, 20 October 2011 (UTC)[reply]
I'm fairly sure that what you need to enter is "CSD Log", not "User:France3470/CSD Log", as the TW prompt is asking for a subpage, not the actual page name. Try that, and see if it works for you. —mc10 (t/c)03:24, 23 October 2011 (UTC)[reply]
Thanks for the suggestions. I had previously tried clearing my cache; It didn't seems to make any difference however. As per Mc10's suggestion I did have just as "CSD Log" in the beginning but I saw no effect (so I changed it to the full route path). Perhaps I was just too hasty. I will go an change it back to "CSD Log" and wait a little while and hope it takes effect. Not sure if this is relevant but whenever I go and view the preferences page, everything seems to reset itself. The box to check for CSD logging returns to being unchecked and does not seem to reflect/remember the current changes that were made. Is this normal? France3470(talk)22:44, 23 October 2011 (UTC)[reply]
Current pages for un-protection
Has something been changed recently on the Current pages for un-protection on the page protection notice board. Because I have now tried to submit 2 pages for un-protection reports using twinkle. Twinkle is currently giving an error message off when attempting to use the tool to submit unprotect requests and is not posting at all to the page.(Ruth-2013 (talk) 01:22, 21 October 2011 (UTC))[reply]
Should be fixed by this edit. Twinkle looks for a particular section heading, followed by a template, and wasn't finding a match because of that extra line break tag (I'm not sure why it was there, to begin with). If it turns out the break tag is necessary, we'll need to update Twinkle's code to reflect that, but I think this should do for now. – Luna Santin (talk) 04:06, 21 October 2011 (UTC)[reply]
Some new Twinkle stats
Hey Twinklers. We’ve been doing some research on user warnings in the Community Dept. at the WMF, and I thought I’d share what we compiled this week...
Thanks to jtmorgan and Staeiou, we now have a list of the most commonly issued user warning templates delivered by Twinkle from the past year. The following are the 89 warning templates (ordered most common to least) from a randomized sample of 1,000 Twinkle user talk edits since October 2010. It’s small compared to the huge amount of TW use every month on English Wikipedia, but it’s enough to garner statistical significance in light of how many revisions are generated by TW.
Top TW warnings
Uw-vandalism1 (22.6%)
Uw-vandalism2 (12.4%)
Uw-vandalism3 (11.5%)
Uw-vandalism4 (5.7%)
Uw-block (4.3%)
Uw-unsourced1 (4.1%)
Uw-test1 (4.0%)
Uw-delete1 (3.7%)
Uw-spam1 (2.8%)
Uw-delete2 (2.5%)
Uw-vandalism4im (2.3%)
Uw-error1 (1.7%)
Uw-speedy1 (1.7%)
Uw-vblock (1.7%)
Uw-speedy2 (1.5%)
Uw-unsourced2 (1.4%)
Uw-unsourced3 (1.3%)
Uw-editsummary (1.3%)
Uw-spam2 (1.2%)
Uw-test2 (1.1%)
Uw-create2 (1.1%)
Uw-delete3 (1.1%)
Uw-error2 (1.1%)
Uw-voablock (1.0%)
Uw-error3 (0.9%)
Uw-generic4 (0.9%)
Uw-softerblock (0.8%)
Uw-npov1 (0.7%)
Uw-biog1 (0.7%)
Uw-create3 (0.6%)
Uw-advert1 (0.6%)
Uw-create1 (0.6%)
Uw-spam3 (0.6%)
Uw-spamublock (0.5%)
Uw-biog2 (0.5%)
Uw-spam4 (0.4%)
Uw-advert2 (0.4%)
Uw-advert3 (0.4%)
Uw-create4 (0.4%)
Uw-create4im (0.4%)
Uw-nor1 (0.4%)
Uw-tdel2 (0.4%)
Uw-test3 (0.3%)
Uw-ablock (0.3%)
Uw-biog4im (0.3%)
Uw-chat1 (0.3%)
Uw-npa3 (0.3%)
Uw-npov2 (0.3%)
Uw-npov3 (0.3%)
Uw-speedy3 (0.3%)
Uw-tdel1 (0.2%)
Uw-afd1 (0.2%)
Uw-biog3 (0.2%)
Uw-blpprod1 (0.2%)
Uw-blpprod2 (0.2%)
Uw-chat4 (0.2%)
Uw-delete4im (0.2%)
Uw-ewblock (0.2%)
Uw-joke1 (0.2%)
Uw-joke2 (0.2%)
Uw-mos1 (0.2%)
Uw-mos4 (0.2%)
Uw-nor3 (0.2%)
Uw-npa1 (0.2%)
Uw-npa4 (0.2%)
Uw-soablock (0.2%)
Uw-uhblock (0.2%)
Uw-username (0.2%)
Uw-3block (0.1%)
Uw-advert4 (0.1%)
Uw-afd2 (0.1%)
Uw-afd3 (0.1%)
Uw-biog4 ((0.1%)
Uw-blockindef (0.1%)
Uw-chat2 (0.1%)
Uw-joke3 (0.1%)
Uw-joke4 (0.1%)
Uw-joke4im (0.1%)
Uw-mos3 (0.1%)
Uw-move1 (0.1%)
Uw-move3 (0.1%)
Uw-nor2 (0.1%)
Uw-nor4 (0.1%)
Uw-npa4im (0.1%)
Uw-redirect2 (0.1%)
Uw-spam4im (0.1%)
Uw-tdel3 (0.1%)
Uw-tpv2 (0.1%)
Uw-ublock (0.1%)
Seems to me that this might be useful if you’re ever trying to decide which TW warnings are really being used and you want to keep or make more prominent in the list. As a side note, we’ve also been doing randomized A/B testing with user warnings in Huggle and are now collaborating with WP:UW folks too over at WP:UWTEST. If any Twinkle users would like to see some hard stats on how new editors respond to different kinds of warnings, we’d be more than happy to run a test with Twinkle too.
Just as a quick update: we added this and some further background research to our sub-page of the testing work here. Thanks for the support when it comes to a further study. In terms of coding (of Twinkle's JS), it's actually really easy because to run a test all we do is change which template name the configuration refers to. That's pretty much it, and a switch statement in the template does the rest as far as randomization. When we have any Twinkle templates we'd be interested in studying, we'll post a new thread here with a link to them and make time for discussion. Cheers, Steven Walling (WMF) • talk00:01, 25 October 2011 (UTC)[reply]
Update: After reading #TB problems again, and when I saw this one topic for the third or fourth time today, I think I know what it is. It is still using {{db-csd-notice-custom}}, from what I could tell. Is that template really only used for Twinkle warnings? Or is it used by regular users for non-twinkle csd notices? LikeLakers2 (talk | Sign my guestbook!) 00:46, 21 October 2011 (UTC)[reply]
Except for message place by ClueBot etc, the basic philosophy is to let the users (at least the new users) believe that the messages are hand-written and delivered personally. They'll find out sooner or later, like we all did, that these are just templates that insert our sigs, but research has shown that for new users it has an important effect by letting them believe otherwise.Kudpung กุดผึ้ง (talk) 03:27, 24 October 2011 (UTC)[reply]
No. Users should be blocked instead if they are misusing Twinkle to such an extent that they are creating disruption, since any sort of Twinkle blacklist is easy to circumvent given the determination (as the old one was). — This, that, and the other (talk)10:37, 23 October 2011 (UTC)[reply]
Ah, I see. How very Chzz of Chzz. :D Considering that there's no screaming/blood trails, I suppose we've had any trouble from the 28 people with revoked access who suddenly got TW back? Sven ManguardWha?17:33, 23 October 2011 (UTC)[reply]
Unlink confirmation
Does the "unlink" command ask for confirmation, or does it start unlinking straight away? I don't want to try myself, just in case it is the latter. --Lambda Magician (talk) 04:28, 24 October 2011 (UTC)[reply]
Earlier Wikipedia went into read-only mode for a bit, and since then I've been having problems with Twinkle not refreshing user pages when adding a warning to them. Is anyone else having this problem? - The BushrangerOne ping only05:13, 24 October 2011 (UTC)[reply]
Can't warn or welcome myself
So in my attempt to do a little testing of the warning features for Twinkle in response to the thread right above this one (about warning and refreshing), I discovered that the ability to warn or welcome yourself has been locked out. I do occasionally need to warn and/or welcome myself from time to time, because that's how I test things. The ability to use the warn and welcome functions on one's own user talk page was enabled per my request in the old Twinkle, and so can we have it enabled again? Thanks! SchuminWeb (Talk) 06:04, 24 October 2011 (UTC)[reply]
This issue may already have been addressed, but as the user has now retired from Wikipedia, I'm reproducing the elements of a recent discussion here:
Hi. I notice you do a lot of hard work adding page protection templates. I'm just wondering if this should now be considered for a Twinkle automation. --Kudpung กุดผึ้ง (talk) 11:50 am, 15 October 2011, Saturday (12 days ago) (UTC+7)
The simple answer, I don't like twinkle. It is extremely overused for every action that people can do with their own hands. Tbhotch.™ Grammatically incorrect? Correct it!See terms and conditions. 04:51, 15 October 2011 (UTC)
I meant that this would be an additional automated operation when we admins effect a page protection. It would relieve you of the work... --Kudpung กุดผึ้ง (talk) 04:58, 15 October 2011 (UTC)
I've really no idea what Tbhotch was talking about, but it seems that if a page is protected for one reason, an additional reason should not replace the existing reason, but I guess this template just adds the padlock icon, in which case one padlock icon is more than sufficient - people can look at the log to see the various protect reasons. In which case this would not be a bug at all. Please confirm. Thanks. Kudpung กุดผึ้ง (talk) 09:39, 27 October 2011 (UTC)[reply]
Resolved
Unresolved
Works for me, at least, on Firefox 7.0.1. —mc10 (t/c) 04:09, 5 October 2011 (UTC)
Done 
