Wikipedia

Wikipedia talk:Twinkle/Archive 27

< Wikipedia talk:Twinkle
Latest comment: 12 years ago by Kudpung in topic {{db}} is misleading - remove it?
Archive 20 ← Archive 25 Archive 26 Archive 27 Archive 28 Archive 29 Archive 30

Current pages for un-protection

Latest comment: 12 years ago2 comments2 people in discussion

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))

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)

CSD log

Latest comment: 12 years ago4 comments3 people in discussion

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: [1] -France3470 (talk) 14:59, 20 October 2011 (UTC)

Have you cleared your browser cache? Try clearing out your entire "temporary internet files" folder. Another way to do it is to simply wait; it should eventually update itself with the new preferences for you. LikeLakers2 (talk | Sign my guestbook!) 01:00, 21 October 2011 (UTC)
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)

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)

CSD tagging

Latest comment: 12 years ago8 comments3 people in discussion

Apparently Twinkle still notifies page creators of at least G6 deletions. See here. As you can tell, all it did was leave a signature. LikeLakers2 (talk | Sign my guestbook!) 20:17, 20 October 2011 (UTC)

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)
Please clear your browser cache. — This, that, and the other (talk) 04:07, 21 October 2011 (UTC)
I seriously doubt its a browser cache problem. If it was a cache problem, I would of had to update my preferences. Attempting to update my prefs by not changing anything and hitting "Save changes" results only in a null edit to my twinkleoptions.js page. LikeLakers2 (talk | Sign my guestbook!) 15:45, 22 October 2011 (UTC)
Well, taking a look at User:LikeLakers2/twinkleoptions.js, "g6" is not listed under "notifyUserOnSpeedyDeletionNomination". So either your browser has a old, cached version of twinkleoptions.js, or there is a strange bug in Twinkle. I suspect the former. — This, that, and the other (talk) 02:47, 23 October 2011 (UTC)

Moved to bottom to renew discussion. Also, do you think it might be a good idea to add "This is an message from ~~~ sent to you via Twinkle's automated CSD notification" to {{db-csd-notice-custom}}? LikeLakers2 (talk | Sign my guestbook!) 18:56, 22 October 2011 (UTC)

Why? Users won't care how the message got on their talk page. It's in the edit summary anyway, if they really want to know. — This, that, and the other (talk) 02:47, 23 October 2011 (UTC)
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)

Question on revoking access

Latest comment: 12 years ago5 comments4 people in discussion

Per the discussion here, is it possible to revoke Twinkle access anymore? Sven Manguard Wha? 07:59, 23 October 2011 (UTC)

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)
See Wikipedia talk:Twinkle/Archive 25#Blacklist and particularly the linked discussions. Nil Einne (talk) 11:01, 23 October 2011 (UTC)
The ability to revoke Twinkle was removed in the complete rewrite of the tool earlier this year. ​—DoRD (talk)​ 15:54, 23 October 2011 (UTC)
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 Manguard Wha? 17:33, 23 October 2011 (UTC)

Unlink confirmation

Latest comment: 12 years ago2 comments2 people in discussion

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)

Don't worry, there is a dialog box. — This, that, and the other (talk) 06:14, 24 October 2011 (UTC)

Refresh problem?

Latest comment: 12 years ago1 comment1 person in discussion

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 Bushranger One ping only 05:13, 24 October 2011 (UTC)

Problem hitting cancel

Latest comment: 12 years ago4 comments2 people in discussion

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)

This is more than a bit broken. I'll take a look. — This, that, and the other (talk) 05:50, 20 October 2011 (UTC)
Should be working as intended now. Try it out, on File:Image page sandbox.png, if you like. — This, that, and the other (talk) 07:02, 23 October 2011 (UTC)
Awesome! Thanks! —danhash (talk) 17:10, 27 October 2011 (UTC)

Some new Twinkle stats

Latest comment: 12 years ago3 comments2 people in discussion

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
  1. Uw-vandalism1 (22.6%)
  2. Uw-vandalism2 (12.4%)
  3. Uw-vandalism3 (11.5%)
  4. Uw-vandalism4 (5.7%)
  5. Uw-block (4.3%)
  6. Uw-unsourced1 (4.1%)
  7. Uw-test1 (4.0%)
  8. Uw-delete1 (3.7%)
  9. Uw-spam1 (2.8%)
  10. Uw-delete2 (2.5%)
  11. Uw-vandalism4im (2.3%)
  12. Uw-error1 (1.7%)
  13. Uw-speedy1 (1.7%)
  14. Uw-vblock (1.7%)
  15. Uw-speedy2 (1.5%)
  16. Uw-unsourced2 (1.4%)
  17. Uw-unsourced3 (1.3%)
  18. Uw-editsummary (1.3%)
  19. Uw-spam2 (1.2%)
  20. Uw-test2 (1.1%)
  21. Uw-create2 (1.1%)
  22. Uw-delete3 (1.1%)
  23. Uw-error2 (1.1%)
  24. Uw-voablock (1.0%)
  25. Uw-error3 (0.9%)
  26. Uw-generic4 (0.9%)
  27. Uw-softerblock (0.8%)
  28. Uw-npov1 (0.7%)
  29. Uw-biog1 (0.7%)
  30. Uw-create3 (0.6%)
  31. Uw-advert1 (0.6%)
  32. Uw-create1 (0.6%)
  33. Uw-spam3 (0.6%)
  34. Uw-spamublock (0.5%)
  35. Uw-biog2 (0.5%)
  36. Uw-spam4 (0.4%)
  37. Uw-advert2 (0.4%)
  38. Uw-advert3 (0.4%)
  39. Uw-create4 (0.4%)
  40. Uw-create4im (0.4%)
  41. Uw-nor1 (0.4%)
  42. Uw-tdel2 (0.4%)
  43. Uw-test3 (0.3%)
  44. Uw-ablock (0.3%)
  45. Uw-biog4im (0.3%)
  46. Uw-chat1 (0.3%)
  47. Uw-npa3 (0.3%)
  48. Uw-npov2 (0.3%)
  49. Uw-npov3 (0.3%)
  50. Uw-speedy3 (0.3%)
  51. Uw-tdel1 (0.2%)
  52. Uw-afd1 (0.2%)
  53. Uw-biog3 (0.2%)
  54. Uw-blpprod1 (0.2%)
  55. Uw-blpprod2 (0.2%)
  56. Uw-chat4 (0.2%)
  57. Uw-delete4im (0.2%)
  58. Uw-ewblock (0.2%)
  59. Uw-joke1 (0.2%)
  60. Uw-joke2 (0.2%)
  61. Uw-mos1 (0.2%)
  62. Uw-mos4 (0.2%)
  63. Uw-nor3 (0.2%)
  64. Uw-npa1 (0.2%)
  65. Uw-npa4 (0.2%)
  66. Uw-soablock (0.2%)
  67. Uw-uhblock (0.2%)
  68. Uw-username (0.2%)
  69. Uw-3block (0.1%)
  70. Uw-advert4 (0.1%)
  71. Uw-afd2 (0.1%)
  72. Uw-afd3 (0.1%)
  73. Uw-biog4 ((0.1%)
  74. Uw-blockindef (0.1%)
  75. Uw-chat2 (0.1%)
  76. Uw-joke3 (0.1%)
  77. Uw-joke4 (0.1%)
  78. Uw-joke4im (0.1%)
  79. Uw-mos3 (0.1%)
  80. Uw-move1 (0.1%)
  81. Uw-move3 (0.1%)
  82. Uw-nor2 (0.1%)
  83. Uw-nor4 (0.1%)
  84. Uw-npa4im (0.1%)
  85. Uw-redirect2 (0.1%)
  86. Uw-spam4im (0.1%)
  87. Uw-tdel3 (0.1%)
  88. Uw-tpv2 (0.1%)
  89. 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.

Hope this is helpful, Steven Walling (WMF) • talk 01:46, 21 October 2011 (UTC)

So, WMF loves Twinkle? Interesting to hear.
There have been complaints that the Twinkle warning list is too long, and I have to say, I agree. Will discuss on IRC and report back here.
Thanks for this data. I'm happy to assist with any future studies the WMF wants to conduct in relation to Twinkle, although I don't have a lot of time for coding. — This, that, and the other (talk) 04:12, 21 October 2011 (UTC)
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) • talk 00:01, 25 October 2011 (UTC)

adding maintain tags below the AfD box

Latest comment: 12 years ago3 comments3 people in discussion

As you can see here twinkle adds new maintainboxes above the AfD box. Can somebody fix twinkle that it adds instead below? mabdul 07:48, 25 October 2011 (UTC)

Interesting, but is this really important? --Kudpung กุดผึ้ง (talk) 09:40, 27 October 2011 (UTC)
Well, it's not unimportant. I'll look into this, but it might be too much of a chore to fix, depending on how friendlytag's hatnote detection code works. — This, that, and the other (talk) 11:13, 27 October 2011 (UTC)

view article link not working

Latest comment: 12 years ago5 comments2 people in discussion
  Disregard
 – Wrong tool! —SMALLJIM  15:18, 29 October 2011 (UTC)

Hovering over a link to an article's talk page and selecting actions|view article shows me the same talk page instead of the article. In other namespaces (user talk, WT) this works as expected, as does viewing the talk page from an article link. I think this has broken fairly recently - can it be fixed, please? —SMALLJIM  13:32, 29 October 2011 (UTC)

Just noticed that the same is true for actions|history and actions|most recent edit too. —SMALLJIM  13:38, 29 October 2011 (UTC)
I assume you're referring to popups? That doesn't have anything to do with Twinkle (as far as I know), but when I tried doing what you said with your link to Talk:Star, I had the same problem. ←cimanyD← contact me 14:36, 29 October 2011 (UTC)
Oops! You know, I've always confused these two useful tools. I'll repost in the right place - thanks for the confirmation that the problem isn't just my own stupidity, at least!  —SMALLJIM  14:46, 29 October 2011 (UTC)

Edit summaries (not a big deal)

Latest comment: 12 years ago3 comments2 people in discussion

Hardly the end of the world, but this Twinkle-generated edit summary doesn't make much sense. HJ Mitchell | Penny for your thoughts? 21:58, 29 October 2011 (UTC)

It's supposed to be "You have been blocked from editing for (disruptive editing, vandalism, spam...) on (linked article)". It seems that for the generic block template, the grammar isn't adjusted. Perhaps the "custom block reason" typed in by the admin in the dialog box could be used in the edit summary, or "abuse of editing privileges" if none is provided? — This, that, and the other (talk) 23:53, 29 October 2011 (UTC)
Well the edit summary doesn't really matter. It could just say "you have been blocked from editing" and leave off the "for..." if that's any easier. HJ Mitchell | Penny for your thoughts? 23:55, 29 October 2011 (UTC)

Transverse

Latest comment: 12 years ago3 comments3 people in discussion

For some time transverse has not worked properly - any chance of repairing it? I looked at using deli-batch instead, but if I'm going through a load of F11, then I need to see the text of both image and talk page to check that there are no proper objections. I can still use transverse - I just have to keep pressing skip after delete as it shows a red (error message post delete as "Grabbing image links: The title parameter must be set". Typical message log... 

Grabbing image links: The title parameter must be set
Skipped: File:Pelvic cavity.JPG
Deleting image: done
Grabbing image links: The title parameter must be set
Skipped: File:Plastination.JPG
Deleting image: done
Grabbing image links: The title parameter must be set
Skipped: File:Plastination2.JPG
Deleting image: done

Originally it used to go to the next image after deletion.  Ronhjones  (Talk) 00:43, 30 October 2011 (UTC)

I've had similar problems, but haven't been dealing with images much recently, so I'd forgotten about it. I haven't seen "the title parameter must be set", but I have had to skip after deleting because it won't load the next image. HJ Mitchell | Penny for your thoughts? 01:11, 30 October 2011 (UTC)
Transverse could need some love. Personally I never finished it in the beginning, and it have been in limbo since then. →AzaToth 01:14, 30 October 2011 (UTC)

{{db-redirnone}}

Latest comment: 12 years ago2 comments2 people in discussion

Why was {{db-redirnone}} removed from the CSD tagging options in the new Twinkle? — Train2104 (talk • contribs • count) 21:29, 31 October 2011 (UTC)

It's there, under "Redirects", where it really should have been all along. — This, that, and the other (talk) 08:00, 1 November 2011 (UTC)

CSD and PROD logs

Latest comment: 12 years ago4 comments2 people in discussion

Seems the Twinkle options page really won't let me choose to not log my CSDs and PRODs... I keep unticking the box, saving, but when I come back the box is ticked again and when I make a CSD request, it logs it. What am I doing wrong? — CharlieEchoTango — 23:38, 1 November 2011 (UTC)

Have you tried clearing your browser's cache? Dr.K. λogosπraxis 23:43, 1 November 2011 (UTC)
Oops. Thanks! — CharlieEchoTango — 23:47, 1 November 2011 (UTC)
You are very welcome. :) Dr.K. λogosπraxis 23:53, 1 November 2011 (UTC)

Problem with Requesting Protection

Latest comment: 12 years ago9 comments3 people in discussion
  Resolved

Tried to request protection for Telopea Park School. Failed with the message:

Requesting protection of page: Could not find relevant "current requests for ..." heading on WP:RFPP. Aborting.

...Tested with another computer, still failed. Cleared cache etc., still failed. ˜danjel [ talk | contribs ] 06:54, 24 October 2011 (UTC)

Someone must have removed the required code from the WP:RPP page. I'll take a look. — This, that, and the other (talk) 07:03, 24 October 2011 (UTC)
Another issue

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)
It is actually a part of the twinkle kit. But it has a bug, when someone adds a pp-semi tag, twinkle removes the {{pp-move-indef}} tag, so it is not really helpful. Tbhotch.™ Grammatically incorrect? Correct it! See terms and conditions. 05:04, 15 October 2011 (UTC)

Kudpung กุดผึ้ง (talk) 02:26, 27 October 2011 (UTC)

OK, so I suppose Twinkle shouldn't remove move protection tags when adding an edit protection tag, and vice versa? — This, that, and the other (talk) 09:19, 27 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)
This has been brought up before, amidst the rather convoluted discussion above at #Tagging page failed when protecting a page. I'm not really sure what to do. (By the way, I must see if I can persuade AzaToth to bump up the archiving speed on this page - a 28 day delay is too long - perhaps 20 days?) — This, that, and the other (talk) 11:11, 27 October 2011 (UTC)
You could also consider flagging threads here more often with the mini templates they could also populate categories, such as for example 'Twinkle bugs unresolved', 'Twinkle bugs resolved', 'Twinkle suggestions made', 'Twinkle suggestions done', 'Twinkle bugs stale', 'Twinkle bugs pending', etc., etc. Kudpung กุดผึ้ง (talk) 00:41, 28 October 2011 (UTC)
That's why we internally use github, and encourage others to use it... it has many of those capabilities built in. — This, that, and the other (talk) 09:15, 29 October 2011 (UTC)
I've never been able to figure out how to use github - it's another one of those wierd external sites like the totally confusing Buzilla. Kudpung กุดผึ้ง (talk) 15:48, 4 November 2011 (UTC)

Move to Commons Assistant

Latest comment: 12 years ago12 comments4 people in discussion
  Unresolved
 – Can't do anything, without some love from the devs

Hi there. I noticed "Add commons move helper: Wikipedia_talk:Twinkle/RFA#Move_to_commons_assistant." on the to do list. I was wondering if there was any chance that it would be done by the last day of 2011. I ask because there is a Transfer to Commons drive in January 2012 that I'd love to have this feature ready in time for. As someone that's done hundreds of transfers and works primarily with files, I'd also be willing to consult with you on tactics and be an alpha tester, if either are needed. Sven Manguard Wha? 05:34, 30 October 2011 (UTC)

That RFA is now archived: Wikipedia_talk:Twinkle/RFA/Archive_2#Move_to_commons_assistant
The proposal that Magog made there seems mostly do-able; whether it should be a part of Twinkle is another matter. He suggests it should be based on the traverse module, which I have never used (and which is buggy anyway, as AzaToth admitted in the previous discussion on this page, so it probably should not be used as a basis). But it sounds interesting.
I notice that User:Fran Rogers/CommonsHelper Helper is apparently now obsolete. Did you ever use that tool? What were its advantages and disadvantages? What exactly caused it to become obsolete?
Also, what is wrong with CommonsHelper (or CommonsHelper2) exactly? — This, that, and the other (talk) 06:48, 30 October 2011 (UTC)
CommonsHelpler and CommonsHelper are both massively unreliable. They go down without warning, occasionally experience unexplainable slowdowns when they're not down, and they are very finicky about what they will and will not do. CommonsHelper and CommonsHelper2 work off of whitelists. If the file on Wikipedia dosen't have a licensing template on the whitelist, the tool won't do the transfer. CommonsHelper2 has a publicly editable whitelist, although finding it isn't that easy. Before I got to it, the whitelist contained about 5% of the free use templates that Wikipedia actively uses, meaning that only the most common licenses (CCs, PD-self, the GNU family) worked with CommonsHelper2. I added a bunch, but it's probably only 50% complete. I have been unable to find the Original CommonsHelper's whitelist, if it is publicly editable, and I estimate that that whitelist is maybe 40% complete. I'd really like to go after some of the smaller, more obscure licensees, because those require expert attention, but that means that there are no tools available for me at this time. Transferring manually is tremendously inefficient. Sven Manguard Wha? 08:09, 30 October 2011 (UTC)
One file of commons helper is called "common_data.php" - I've extracted part at User:Ronhjones/Sandbox3 - looks like it's a list of good and bad templates to me.  Ronhjones  (Talk) 15:54, 31 October 2011 (UTC)
Oh, one more thing: CommonsHelper and CommonsHelper2 occasionally break SVGs when they transfer, and I don't have the technical ability to transfer those at all. I've also heard stories, although this never happened to me personally, that when CommonsHelper transfers .ogg and .ogv videos, it strips the sound away. Sven Manguard Wha?
Ah, I see: I had been imagining a script wrapper for CommonsHelper (a tool of which I am not a great fan).
Well, it may be possible to do this, essentially amounting to a JavaScript-based implementation of CommonsHelper using the upload API (which was a bit flaky at one point - it may have been fixed). I wouldn't be surprised if someone on some wiki somewhere has already written such a script. But if not, you might just find that one exists before the last day of 2011... — This, that, and the other (talk) 08:54, 30 October 2011 (UTC)
Actually I don't think upload from URL is enabled on WM wikis. Will check. — This, that, and the other (talk) 09:21, 30 October 2011 (UTC)
I have no idea how any of that would work, I'm not coding literate. However, if something were to appear that performed the transfer function reliabally, that would be a huge improvement over what we have now. On a totally unrelated not, I could easily see myself giving out a barnstar on the last day of 2011 to a certain coder... or something. :D Sven Manguard Wha? 11:30, 30 October 2011 (UTC)
In my experience, The commons helpers have both been much worse since the MediaWiki 1.18 upgrade! Every time I try using it - I'm lucky if I can get 1 image transferred in 15 minutes of trying - it just waits ages and goes to blank screen. I did find this - http://commons.wikimedia.org/wiki/Commons:Bots/Requests/SreeBot - It looks like someone has written a utility to move images (program running from his PC) - I did drop him an e-mail requesting the source code, but no reply. Anything would be better than commonshelper.  Ronhjones  (Talk) 15:27, 31 October 2011 (UTC)
Any new alternative tool would require that the devs enable upload-by-URL on Commons. As is usual with Wikimedia devs, this request has been forgotten about for the past few months - I did try to ping some bugs on bugzilla, but with no response as yet. So, without that, I can do very little. — This, that, and the other (talk) 09:12, 1 November 2011 (UTC)
I don't know if upload-by-URL would go over well. I, for one, would support allowing it only for authorized programs, such as TW, and not for users. That's just me (an experianced file worker) being paranoid about anything that makes it easier for people who don't understand copyright to upload copyvios. Sven Manguard Wha? 09:43, 1 November 2011 (UTC)
Well, apparently the Wikimedia web servers don't have internet access (?!). So enabling upload-by-URL there would presumably still allow upload-by-URL from upload.wikimedia.org, but not from external sites. It's also possible that the server do now have internet access, in which case, a site whitelist would be needed unless/until Commons decides to allow global upload-by-URL. — This, that, and the other (talk) 23:00, 3 November 2011 (UTC)
CommonsHelper is using the TUSC account system, so why not integrating TUSC into twinkle/let twinkle use TUSC as confirmation? That would at least solves the problems about unexperienced users. Although I think this would have then similar problems like the CommonsHelper. (Oh I'm so happy that it isn't my fault. I wondered why CommonsHelper isn't working for me any longer... It didn't come into my mind that's the fault of the really buggy 1.18 update!) mabdul 14:27, 3 November 2011 (UTC)

RFPP problem?

Latest comment: 12 years ago3 comments2 people in discussion
  Resolved

Since last night, I've been having some problems reporting articles for protection. When I submit the form to WP:RFPP, it tells me this:
Requesting protection of page: Could not find relevant "current requests for ..." heading on WP:RFPP. Aborting.
I've bypassed my cache and nothing. -- Luke (Talk) 15:21, 4 November 2011 (UTC)

An IP removed a critical line from the page. I have fixed it, and according to this test, it seems to be working again. jcgoble3 (talk) 17:01, 4 November 2011 (UTC)
Much appreciated. -- Luke (Talk) 17:05, 4 November 2011 (UTC)

{{ygm}}

Latest comment: 12 years ago5 comments5 people in discussion

I think it should be added as an option to the tb tab. →Στc. 05:17, 3 November 2011 (UTC)

#Talkback options... ←cimanyD← contact me 13:44, 3 November 2011 (UTC)
A mail notification might actually be a useful addition to the TB feature. It's having multiple tags that all do the same thing that I oppose because that is when things start getting cluttered up. SchuminWeb (Talk) 02:25, 4 November 2011 (UTC)
I think most people notice they got mail before they even look on their talk page. Thus I oppose this feature. →AzaToth 01:14, 6 November 2011 (UTC)
Actually, in my experience, a lot of people don't, especially the ones who used a dedicated email for signing on with Wikipedia, but are not in habit of receiving email from us, so they may not check that mail box regularly. . Unfortunately, most people these days seem to base their communications on web mail rather than on a proper PoP3 mail client. --Kudpung กุดผึ้ง (talk) 01:34, 6 November 2011 (UTC)

FYI: Template:Uw-3rr has been overhauled

Latest comment: 12 years ago1 comment1 person in discussion
  Resolved

As an FYI for Twinkle users, {{Uw-3rr}} has been given a significant rewrite. Please familiarize yourself with the new template before using. Thanks! SchuminWeb (Talk) 16:17, 5 November 2011 (UTC)

ADF

Latest comment: 12 years ago3 comments3 people in discussion
  Resolved

What are ADF Rollbacks? I'm confused by these. Jamcad01 (talk) 06:56, 6 November 2011 (UTC)

Actually AGF => WP:AGF. — This, that, and the other (talk) 09:03, 6 November 2011 (UTC)
I know of two notable features of this function: one is that it leaves an edit summary that contains the words and link good faith, and if the same editor has made edits to the article after the one you're trying to rollback, it will fail. (This is different from the vandalism rollback which will assume vandalism for all subsequent edits by the same editor, and roll them all back.) Elizium23 (talk) 20:48, 6 November 2011 (UTC)

Merge should always have a target

Latest comment: 12 years ago1 comment1 person in discussion

I note a couple of Twinkle users have used it to insert {{merge}} templates without targets. I have not used Twinkle myself so I don't know how easy it would be to do this. Can it be made harder, or not possible, to do? Mark Hurd (talk) 15:04, 6 November 2011 (UTC)

Can't warn or welcome myself

Latest comment: 12 years ago11 comments7 people in discussion

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)

Ask User:Ioeth. — This, that, and the other (talk) 06:15, 24 October 2011 (UTC)
You could also use User talk:Sandbox for user warnings. jcgoble3 (talk) 06:24, 24 October 2011 (UTC)
Indeed. Occasionally gun owners need to test their firearms: the correct solution is a concrete block, not a lucky crash helmet and a willing friend. Chris Cunningham (user:thumperward) - talk 11:16, 27 October 2011 (UTC)
I just have to say, I was trying to test some warnings on my own page, and the message that popped up, along with the ones for welcome and talkback, completely made my day. Well played! Writ Keeper ⚇♔ (talk) 14:30, 28 October 2011 (UTC)
The gun analogy is a little disturbing, but it does seem really ill-advised to lock out the feature for one's own talk page, really for no good reason. MediaWiki won't prevent me from accidentally blocking myself, and unlike a self-block, self-warnings and welcomes for testing purposes do have value, especially when one's own talk page is easy to reach, always being one click away. Seriously, disable that self-warn/welcome block, please. SchuminWeb (Talk) 06:33, 29 October 2011 (UTC)
If you want it disabled, ask User:Ioeth, as I said earlier. — This, that, and the other (talk) 09:16, 29 October 2011 (UTC)
I've got no problem with this change being backed out. I was just having a bit of fun, but it's the functionality that should be considered paramount. I won't have time to do it, though, if someone else wants to tackle the revert. Ioeth (talk contribs twinkle) 16:12, 7 November 2011 (UTC)
Okay, good - let's get that "feature" disabled as soon as possible. All told, "Warn", "Welcome", and "TB" have that lockout on them that needs to come off. SchuminWeb (Talk) 20:04, 7 November 2011 (UTC)
No need, as you can use User talk:Sandbox for user warnings for testing. Even if we were to remove this "feature", it won't happen "as soon as possible" as it's not something that is important to do. I wont make a quick change just to make one user happy. →AzaToth 20:29, 7 November 2011 (UTC)
Please do, however, put this in the queue of things to do. Even though the warning sandbox exists, it is far more convenient to just do it on my own talk page. SchuminWeb (Talk) 03:12, 8 November 2011 (UTC)

Proposal for testing to improve AFD/PROD notifications, as a start

Latest comment: 12 years ago6 comments3 people in discussion
  Resolved

Hey everyone, per the comments in the "stats" note I left above, Maryana and I have been working with folks to run randomized, A/B tests of user warnings content in order to improve them.

So far, by testing with Huggle, we've seen some statistically significant improvements in stopping vandals from editing, reducing retaliatory vandalism on user/user talk pages, and communication between newbies and more experienced editors. All our documentation is at WP:UWTEST, since we're working ostensibly with the slightly dormant WikiProject on user warnings.

To cut to the chase: Twinkle is way more popular and used for a much more diverse set of tasks than Huggle, and we'd like to try and do some similar experiments involving the notifications it leaves, starting with AFD and PROD. See here for the documentation on the details. We'd like to start a test on Friday or Saturday, if that's okay.

Please let me know if you have any questions or concerns. I have some open questions still, which I left on the talk pages of the related templates. Our general goal is try and improve these user talk templates while not changing or disturbing how tools like TW/HG operate, so if a test goes on you won't see any changes in how they work. Thanks, Steven Walling (WMF) • talk 23:46, 1 November 2011 (UTC)

So, do we need to do anything? — This, that, and the other (talk) 01:41, 2 November 2011 (UTC)
Nope, not at this stage. I'm happy to edit the gadget js myself, since all we're doing is substituting in a different pair of templates. Steven Walling (WMF) • talk 02:07, 2 November 2011 (UTC)
Go right ahead, as far as I'm concerned. If you'll just have to make one or two edits then it's OK if you modify the gadget, but please let someone here know so that the changes can be duplicated in the github sources. Amalthea 11:00, 2 November 2011 (UTC)
Awesome. Well the way we've done it with Huggle is dropping a note every time we start and stop a test, so we'll continue that here. I'll plan on doing that as soon as we start a test with PROD/AFD. If we ever do a test that's more complex than this one, I actually would be happy to fork the git repo and the commit any changes we make if that would be easiest. Steven Walling (WMF) • talk 22:05, 3 November 2011 (UTC)
Just a heads up that we're starting this test shortly. We figured out that probably the best way to do this is to simply replace the redirects that the gadget refers to with our new template randomizers, rather than needing to edit the js file itself. That should preserve the ability for all the parameters (like BLP PROD) to work correctly. Steven Walling (WMF) • talk 21:19, 8 November 2011 (UTC)

Stupid bug in a couple templates

Latest comment: 12 years ago3 comments2 people in discussion
  Resolved

For some reason {{AfD-notice-rand/new}} and {{AfD-notice-rand/default}} are, unlike the PROD templates being tested in a similar format, making the signatures added by TW preformatted. There has got to be an extra space or line break in those, but I cannot figure this out for the life of me. You can see the tracking templates ({{z81}} and {{z82}}) if you want to see examples, though I have fixed some that produced this error. I tried them manually in the sandbox and they look fine. Steven Walling (WMF) • talk 23:38, 8 November 2011 (UTC)

Sorry, but I can't understand what is the problem is, and what has to be done. are the templates so similar to each other that the signature gets preformated? →AzaToth 00:08, 9 November 2011 (UTC)
  Fixed thanks to AzaToth spotting our dumb mistake in the main {{AFDWarning}}. Steven Walling (WMF) • talk 01:09, 9 November 2011 (UTC)

Drop-down menus disappear

Latest comment: 12 years ago2 comments2 people in discussion

Hi, I've just been testing the updated version of TW enabled from the gadgets section, but every time it's checked these menus disappear, and only reappear if it's disabled again. Anyone encountered this before? -- Mentifisto 20:35, 6 November 2011 (UTC)

I'm confused. You have importScript('User:Haza-w/cactions.js'); //[[User:Haza-w/cactions.js]] in your monobook.js, but it is configured not to display drop-down menus (the line itabs = false). So perhaps try rectifying that configuration, if you do in fact want to see the drop-down menus. — This, that, and the other (talk) 08:54, 10 November 2011 (UTC)

Non-existent image templates

Latest comment: 12 years ago5 comments3 people in discussion
  Resolved

Template:Redundant and Template:Shadows Commons have been deleted, and Template:Should be text does not exist, but they are on the Twinkle's list of options for tagging images. —danhash (talk) 18:45, 8 November 2011 (UTC)

Thanks for notifying us; I will remove them. Possibly {{should be text}} could be created?
Also, this reminds me that the documentation subpages of those image tag templates need {{twinkle standard installation}} added to them. — This, that, and the other (talk) 23:23, 8 November 2011 (UTC)
Probably should have been {{ShouldBeText}}. Maybe {{should be text}} should be created as a redirect? I wonder why it hasn't already been. —danhash (talk) 22:31, 9 November 2011 (UTC)
  Redirected jcgoble3 (talk) 22:52, 9 November 2011 (UTC)
Hmm... I thought I was going mad for a moment there, when I saw that {{should be text}} didn't exist. Thanks for fixing this up. — This, that, and the other (talk) 06:46, 11 November 2011 (UTC)

Drop-down menus disappear 2

Latest comment: 12 years ago4 comments2 people in discussion
  Resolved

See Drop-down menus disappear above. The drop-down admin's menu for blocking has disappeared. (in vector). --Kudpung กุดผึ้ง (talk) 04:57, 10 November 2011 (UTC)

What is this "menu for blocking" you speak of? Is it User:Animum/easyblock.js? A screenshot would be helpful. — This, that, and the other (talk) 08:59, 10 November 2011 (UTC)
I can't give you a screenshot, because it's gone ;) It looks as if all my admin Twinkle dropdowns have disappeared - tried in bot FF and Safari, tried clearing the cache. --Kudpung กุดผึ้ง (talk) 09:20, 10 November 2011 (UTC)
Update: It seems to be OK now. I simply reverted the edit I made yesterday to get rid of the strange grey page warning. That's gone too. --Kudpung กุดผึ้ง (talk) 09:52, 10 November 2011 (UTC)

Talkback options

Latest comment: 12 years ago14 comments5 people in discussion

Would it be possible for Twinkle to have some sort of functionality for using {{tbt}} and/or {{wb}}? Right now, as far as I know, it can only use {{tb}}. Dynamic|cimanyD contact me ⁞ my edits 18:20, 21 September 2011 (UTC)

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)
Where is there consensus not to use {{wb}} or {{tbt}} in Twinkle? Dynamic|cimanyD contact me ⁞ my edits 21:28, 21 September 2011 (UTC)
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)
I'd still like {{wb}} to be in Twinkle. Dynamic|cimanyD (contact me ⁞ my edits) 22:50, 2 October 2011 (UTC)
My guess is that it most likely won't be going in there any time soon... SchuminWeb (Talk) 23:04, 2 October 2011 (UTC)
If everyone else keeps ignoring this section, it never will... →Dynamic|cimanyD← (contact me) 13:32, 3 October 2011 (UTC)
Also, I don't use email on WP, but those that do might want {{YGM}} to be in Twinkle also. Dynamic|cimanyD contact me ⁞ my edits 21:28, 21 September 2011 (UTC)

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 me 18:34, 27 October 2011 (UTC)

I still oppose it. SchuminWeb (Talk) 19:41, 27 October 2011 (UTC)
It's a puzzling case. — This, that, and the other (talk) 23:57, 27 October 2011 (UTC)
I support the addition of {{wb}}. I only use {{tb}}, because {{wb}} is not in Twinkle. Armbrust Talk to me about my editsreview 03:03, 17 November 2011 (UTC)
I greatly support the inclusion of {{tl|wb}) in Twinkle. The current tb is too big and blatant. Kudpung กุดผึ้ง (talk) 03:09, 17 November 2011 (UTC)
I believe that a better idea would be to make this a customizable selector, similar to the way the welcome options are customizable. This way, Twinkle is, by default, clean, and those users who wish to junk it up can feel free to junk it up all they want via their preferences page and let the rest of us have the section clean. SchuminWeb (Talk) 05:12, 17 November 2011 (UTC)

{{Not English}}

Latest comment: 12 years ago1 comment1 person in discussion
  Resolved
 – A note for Twinkle users.

See this edit I made to {{Not English}}. If needed, I can give somewhat of a better explanation, but in general, it allows, say, zh to be used as an alternative to typing Chinese in. LikeLakers2 (talk | Sign my guestbook!) 17:32, 13 November 2011 (UTC)

Linked article (if supported by template)

Latest comment: 12 years ago4 comments3 people in discussion

WP:TWINKLE gives users the option to instantly add welcome templates as chosen from a menu. It asks for a "Linked article (if supported by template)" so that the template can reference an article on which the user to be welcomed had been working. I noticed that for some templates this field works and for others, such as Template:Welcome-COI, even when the field is completed the automated mechanism does not populate the template and instead just gives the default response.

I was thinking of fixing this, but I wanted to ask first - is there a reason why things are as they are? Also, does anyone know offhand where I am going to look to fix this and make it consistent for all templates? All of this works on the template side and TWINKLE knows how to respond, right? Has there ever been a "Best practices" talk about this? Blue Rasberry (talk) 15:00, 15 November 2011 (UTC)

Without actually going in and looking, I would guess that the problem likely lies in inconsistency in what variables parameters the template uses to insert the article name into the message. Should probably check one that doesn't work against one that does work, and then modify the one that doesn't work accordingly to standardize it (and don't forget to change the template documentation). That seems the most likely scenario, since if it works on some templates but not others, the problem likely isn't with Twinkle, but rather with non-standard template parameters. SchuminWeb (Talk) 20:26, 15 November 2011 (UTC)
It doesn't make sense for some templates, like {{W-link}}, to include an article name. (I'm not sure why anyone would ever use that welcome template, actually, but it's always been in Friendly/Twinkle, so it might as well stay.) — This, that, and the other (talk) 00:53, 16 November 2011 (UTC)
It takes all kinds, I suppose, when it comes to {{W-link}}. But if the template doesn't support it for whatever reason, then of course let's not bother with it, but if the template does support it, then it should be consistent so that TW populates it correctly. That's the main thrust of what I'm saying. SchuminWeb (Talk) 18:22, 16 November 2011 (UTC)

Categories for speedy renaming

Latest comment: 12 years ago4 comments3 people in discussion
  Resolved

It would be nice if Twinkle supported speedy renaming nominations of categories, see Wikipedia:Categories for discussion/Speedy. --The Evil IP address (talk) 11:19, 31 October 2011 (UTC)

I agree. Just was coming there to propose this.   Armbrust Talk to me about my editsreview 03:06, 17 November 2011 (UTC)
I agree too. — This, that, and the other (talk) 05:54, 17 November 2011 (UTC)

This works now. There is a new entry in the "Deletion venue" dropdown (CFD/S). Give it a go, and see if you like it. — This, that, and the other (talk) 00:06, 18 November 2011 (UTC)

AfD tag formatting errors are occurring

Latest comment: 12 years ago9 comments5 people in discussion
  Resolved

It appears that within the AfD template when placed in articles, there needs to be spaces between the vertical bars "|" where the page name is within the template. Otherwise, the link to the AfD is a red link. When the spaces are present, the link functions properly. I have noticed this error in the template in many instances, and have been manually correcting the link. It would be nice to have this addressed in the Twinkle script/software itself. Northamerica1000(talk) 23:42, 15 November 2011 (UTC)

Not sure that this is a TW issue, I think that it is most likely related to a server cache issue - try WP:PURGE. Mtking (edits) 23:50, 15 November 2011 (UTC)
Thanks for the response. Next time I see a red link as mentioned, I'll try purging and check out the results. Northamerica1000(talk) 23:53, 15 November 2011 (UTC)
  • Resolved. The matter was regarding the server cache. Upon purging, the red link turns into a blue link. Northamerica1000(talk) 23:59, 15 November 2011 (UTC)

That said, is it possible (or in fact desirable) for Twinkle to cause the target page to be purged after the creation of the XfD page to avoid the appearance of the red-link. Mtking (edits) 00:42, 16 November 2011 (UTC)

It would probably have no effect if purged immediately after adding the AFD tag (which is the only opportunity Twinkle has to do anything, really). — This, that, and the other (talk) 00:50, 16 November 2011 (UTC)
What about telling it to trigger a purge as soon as the AfD/MfD page is created? What I mean is that the successful creation of the discussion page would instantly trigger the purge, while the dialog box is still up. Would it be possible to code that in? jcgoble3 (talk) 01:54, 16 November 2011 (UTC)
The edits are made asynchronous, thus it's impossible to tell if the AFD listing or the tagging is made before or after each other. →AzaToth 12:29, 17 November 2011 (UTC)
OK, I figured it couldn't hurt to ask. jcgoble3 (talk) 16:22, 17 November 2011 (UTC)

Urgent problem: Twinkle eating FfD submissions

Latest comment: 12 years ago4 comments3 people in discussion
  Resolved

Please see this diff. I placed the first two items, and then when I placed the third item, TW removed the first two when it placed the third in. It's done this multiple times now, with the first caught one yesterday.

This is rather problematic. Is it on my end or TWs? If it's on my end, how do I fix it? Sven Manguard Wha? 11:30, 17 November 2011 (UTC)

The "yesterday" one was Twinkle randomly cutting off half the page. We hear about this issue from time to time; however Twinkle can't do much about it – it's some sort of transmission error, either between the user's computer and the server, or between the different servers running Wikipedia. The only solution at the moment, unfortunately, is to revert the edit manually.
The other one happened because you tried to submit two FFDs at the same time. Normally, if doing this manually, you would get an edit conflict with yourself, but the API doesn't seem to catch these. The moral of the story is, don't submit multiple XFDs at the same time with Twinkle. — This, that, and the other (talk) 00:04, 18 November 2011 (UTC)
Ewww. So what really happened in the first one is that I had listed them one after the other, not at the same time, but my internet is so crappy that it ended up grinding to a halt, pausing both of them, and then restarting 30 or so seconds afterwards, apparently posting them both at the same time. This problem will be solved when I get back to the states at the end of the year. Sven Manguard Wha? 02:17, 18 November 2011 (UTC)
You can't blame Twinkle for being hungry and eating the submissions. I heard they're especially scrumptious. Logan Talk Contributions 02:18, 18 November 2011 (UTC)

Still having problems with the CSD Log

Latest comment: 12 years ago5 comments3 people in discussion
  Resolved

Hello. I'm afraid many weeks later I'm still having the same issue (please see above Wikipedia talk:Twinkle#CSD log). After it was suggested that I leave some time for the changes to register, I waited about a week, but still had no luck. No CSD log was written. I later edited the code again, diff, at which time I choose an alternative location for the logs to be. But that produced no new pages either. I have also cleared my cache, history, cookies, everything many times over to no effect. I don't have any good thoughts as to why this might be but would be very appreciate if someone could have another look. Thanks, France3470 (talk) 14:37, 9 November 2011 (UTC)

What browser are you using? Try visiting [2] and pressing Ctrl+F5 (Cmd+F5 on a Macintosh machine). — This, that, and the other (talk) 00:53, 10 November 2011 (UTC)
I got it to work. To be honest it was just a rather silly mistake on my part (which I thought might be the case). When I changed the code for the preferences I did this in the Twinkle.js file but I didn't edit the vector.js file to match. By simply putting in the simpler code in the vector.js it seems to have solved it. Thanks everyone for all the suggestions, France3470 (talk) 16:03, 10 November 2011 (UTC)
You're actually adding Twinkle twice. Just remove the last importScript('User:AzaToth/twinkle.js');, and you should be fine. Cheers, —mc10 (t/c) 06:58, 21 November 2011 (UTC)
So I did. I fixed that so hopefully I should be okay now. Thanks, France3470 (talk) 13:31, 21 November 2011 (UTC)

SimpleWindow

Latest comment: 12 years ago3 comments2 people in discussion
  Resolved

I wrote a custom script that piggybacks on Twinkle, located at User:CBM/ratemath.js. I haven't used it in a while, and when I went to use it today I noticed it no longer works. The error I get is that 'SimpleWindow' is not defined.

I then tried loading Twinkle in my vector.js, before the custom script, using importScript, but that did not seem to work at all.

What is the easiest way to get this working again? I'm not very strong in Javascript - I'm not even sure where SimpleWindow is defined, to re-load that library in my vector.js. Thanks for any ideas, — Carl (CBM · talk) 14:55, 21 November 2011 (UTC)

The simplest way is to prepend the script file with the line
importScript("MediaWiki:Gadget-morebits.js");
That ought to work. Also you should probably remove the TwinkleConfig business, as it will interfere with Twinkle's new preferences system.
In addition (yes, more!), you will receive a big error box whenever you run the script (although it should still work). If you want this to go away, we are happy to help by rewriting the script. (It looks short, so this shouldn't be too much of a problem.) — This, that, and the other (talk) 09:50, 22 November 2011 (UTC)
If you have time to do it, it would be wonderful. The script essentially just pops up a box that lets people select assessment values - a glorified talk page tagging job. I am just barely able to write in Javascript, and I am completely unfamiliar with the libraries and general framework of Twinkle, so essentially all I can do is change other scripts here and there. Thanks! — Carl (CBM · talk) 04:37, 23 November 2011 (UTC)

Welcoming templates

Latest comment: 12 years ago2 comments2 people in discussion
  Resolved

Hello, I love that I can add a welcoming template that I particularly like to the array the Twinkle already offers. However, there is a certain parameter in this template that I always have set a certain way. I can't figure out how to have a template given on the options list that has a parameter set a certain way. Without this ability, the welcoming feature for me is largely ineffective because I have to, in order to add the parameter, put the template on the page manually. Any help from the Twinkle gurus here would be of great assistance. Thank you,  M   Magister Scientatalk (22 November 2011)

I suggest you create a simple substitution subpage in your userspace, like so:
{{ {{{|safesubst:}}}template name goes here|params=foo|moreparams=567}}
Then add the full page name of that subpage to the TWPREFS dialog. Hope that makes some kind of sense. — This, that, and the other (talk) 22:38, 22 November 2011 (UTC)
It does and it works. Very much appreciated, Magister Scientatalk 23:24, 22 November 2011 (UTC)

{{Multiple issues}}: Over detailed?

Latest comment: 12 years ago4 comments3 people in discussion
  Unresolved
 – Someone needs to be given one of these for breaking multipleissues. It's very frustrating for us. — This, that, and the other (talk) 10:28, 23 November 2011 (UTC)

Hi.

This is an edit of mine in which I tried to insert three tags into the article via Twinkle. However, I noticed that Twinkle only inserted two. Then I realized that instead of inserting "over detailed" parameter into {{multiple issues}}, Twinkle must have added "overly detailed". See this edit.

Regards, Fleet Command (talk) 06:45, 6 November 2011 (UTC)

Someone's gone and tweaked {{multiple issues}}   — This, that, and the other (talk) 09:04, 6 November 2011 (UTC)
Has this issue been fixed? I haven't tested it. OlYeller21Talktome 15:54, 18 November 2011 (UTC)

Leaving myself CSD notices

Latest comment: 12 years ago4 comments3 people in discussion

Since I'm not an admin, the method I usually employ to "move without redirect" is to move the page, and then place a CSD R2/R3/G6 tag on the former title as appropriate. Since the old title becomes recreated as a new redirect to the new title, with the user who performed the move as the creator, when I use Twinkle to place such a CSD tag, I get automated CSD notifications from myself indicating that that article is up for speedy deletion (example). This is hardly a crisis and I usually just delete such messages, but is it possible/practical to modify the code so I don't receive CSD notifications from myself? —KuyaBriBriTalk 18:22, 9 November 2011 (UTC)

The answer is simply to not use db-reason (the "custom reason" option). Use R3 instead, or "G6: Housekeeping", which has a pop-up reason box. These will not cause any notifications. — This, that, and the other (talk) 00:50, 10 November 2011 (UTC)
Can we have a separate configuration/preference not to inform oneself? I notified myself after tagging an orphaned fair use image, which was uploaded by me (I was aware of that). mabdul 10:56, 21 November 2011 (UTC)
This would take a fair amount of work, for any benefit? Notifying oneself is such exhilarating fun, after all... — This, that, and the other (talk) 10:28, 23 November 2011 (UTC)

AfD closes

Latest comment: 12 years ago6 comments3 people in discussion
  Resolved
 – Issue fixed. —mc10 (t/c) 04:48, 24 November 2011 (UTC)

The Twinkle page tells me that admins have extra functionality: closing AfDs in the twinkle of an eye. A while ago Ed (THE Ed, haha) did something in some .js thing I have (sorry, I'm a luddite) to make it work, but it never did. I can't find out what needs to be done or what's wrong. In a related matter (for me, as a luddite), I've cleared and completely cleared my cache, but something in the world still can't parse twinkleoptions.js. Your geeky and necessary help will be much appreciated, and if you fix all these problems, I'll arbitrarily block an editor of your choosing for 24 hours. Drmies (talk) 15:00, 12 November 2011 (UTC)

The solution to your woes would be to remove the TwinkleConfig and FriendlyConfig stuff from either User:Drmies/vector.js or User:Drmies/monobook.js (depending on whether you use the Vector or Monobook skin). This would leave you with only two lines, both referencing Mr.Z-man's scripts (one of which is the closeAFD one which you are talking about).
You seem to have copied someone else's twinkleoptions.js to your userspace, at User:Drmies/twinkleoptions.js. If you don't need it, you can delete it; or you can customize your Twinkle preferences at WP:TWPREFS. — This, that, and the other (talk) 06:28, 13 November 2011 (UTC)
I may have, or someone else may have, haha. Ed? Honestly, I don't have a clue. I'll give you two free blocks if you clean up my mess... Oh, I went through the Twinkle options but didn't see "close AfD" as an option. Thanks, Drmies (talk) 23:00, 13 November 2011 (UTC)
I'm not an admin... — This, that, and the other (talk) 00:03, 14 November 2011 (UTC)
Steps (nice and simple):
  1. Go to User:Drmies/vector.js.
  2. Remove the following lines: 
    if( typeof( TwinkleConfig ) == 'undefined' ) TwinkleConfig = {};
TwinkleConfig.watchRevertedPages	= [];
TwinkleConfig.watchWarnings		= false;
TwinkleConfig.watchSpeedyPages		= [];
TwinkleConfig.watchProdPages		= false;
FriendlyConfig.watchTaggedPages		= false;
FriendlyConfig.watchWelcomes		= false;
  3. Repeat with User:Drmies/monobook.js.
  4. Clear your cache.
Now Twinkle should be working again. —mc10 (t/c) 07:06, 21 November 2011 (UTC)

Changed block link in {{uw4}} to match {{uw4im}}

Latest comment: 12 years ago2 comments2 people in discussion
  Resolved
 – Simple notification to Twinkle users. Shouldn't affect the use of Twinkle. —mc10 (t/c) 23:36, 24 November 2011 (UTC)

I've changed the block link in {{uw4}} to match {{uw4im}} by extending the link to the blocking policy page to cover the phrase "blocked from editing" and not just the word "blocked". This affects all templates using {{uw4}}, including {{uw-vandalism4}} and {{uw-delete4}}. DRAGON 280 (TALK/CONTRIBS) 16:38, 24 November 2011 (UTC)

Problems in getting TWINKLE to do RFD's

Latest comment: 12 years ago2 comments2 people in discussion
  Resolved
 – No feedback; error was apparently transient.

Apparently the feature in TWINKLE to do RFD's has busted, as it complains about not being able to find the relevant point at which to insert the entry.

Please look into this and comment. Sfan00 IMG (talk) 18:30, 24 November 2011 (UTC)

This is likely related to the section above, #AFD. See the above section for more information. —mc10 (t/c) 19:32, 24 November 2011 (UTC)

WP:FURME integration

Latest comment: 12 years ago2 comments2 people in discussion

I found a post from mid-summer 2011 that there is consensus to integrate WP:FURME into TW and a later one that it was done but since I cannot find it anywhere, I'd like to know the status of this project. Since FurMe doesn't work anymore (for me at least), it would be really great to have TW provide that functionality. Regards SoWhy 20:24, 24 November 2011 (UTC)

No way is it done. I would estimate it would take at least 6 hours of solid work in order to finish the merge, which is a long time for a volunteer coder. I simply haven't had that time, but I should be able to finish working on it in the upcoming weeks. — This, that, and the other (talk) 05:00, 25 November 2011 (UTC)

Template:Uw-coi-username

Latest comment: 12 years ago4 comments3 people in discussion
  Resolved
 – Already in Twinkle. —mc10 (t/c) 04:04, 28 November 2011 (UTC)

I couldn't see this template in the list. Could it please be added? How are templates selected from Category:Standardised user warning templates? Thanks. -- Trevj (talk) 03:53, 27 November 2011 (UTC)

It is in single-issue warnings, between uw-username and uw-userpage. Elizium23 (talk) 03:56, 27 November 2011 (UTC)
Yes, I've just noticed that myself and returned here with the intention of striking through my comment! Thanks very much. -- Trevj (talk) 04:44, 27 November 2011 (UTC)

Twinkle suddenly stopped working

Latest comment: 12 years ago4 comments2 people in discussion
  Resolved

Suddenly I find that Twinkle isn't working at all. It was working yesterday. I haven't changed my preferences or anything. (In case I haven't made myself clear: help!!!) ScottyBerg (talk) 15:25, 2 December 2011 (UTC)

It's working fine for me. Calabe1992 16:30, 2 December 2011 (UTC)
Well, it isn't for me, and I made no change in my settings. I tried another browser, and the same result. Not working anywhere. Any suggestions would be appreciated. ScottyBerg (talk) 17:58, 2 December 2011 (UTC)
Aha! I cleared my cache. Now it works. Whew! Any idea why that happened? ScottyBerg (talk) 18:01, 2 December 2011 (UTC)

Mass protect

Latest comment: 12 years ago4 comments2 people in discussion
  Resolved

I used the mass protect function a minute ago to a bulk RfPP request, and I got the following message:

{{red|This user script is using the deprecated "Wikipedia.wiki" class to edit the wiki. It may cease to function in the near future.

Please pass this message on to the script's maintainer, to ensure the script is upgraded.

(The developers of Twinkle are happy to assist script maintainers with updating scripts.)

Any chance this could be fixed? It's an incredibly useful function, if not one I need every day. HJ Mitchell | Penny for your thoughts? 03:51, 18 November 2011 (UTC)

The protection seemed to work, which is the main thing. Although the message is right: batch protect might cease to fail in the future. It wasn't updated in the big rewrite earlier this year (I ran out of stamina after doing the protect module!), but it will receive attention in due course. — This, that, and the other (talk) 05:57, 18 November 2011 (UTC)
A bit of a Freudian slip there: I have fixed the batchprotect module up a bit (the changes aren't live yet). But it now will indeed cease to fail (when the changes go live)... — This, that, and the other (talk) 10:02, 21 November 2011 (UTC)
Done. — This, that, and the other (talk) 02:27, 11 December 2011 (UTC)

AFD

Latest comment: 12 years ago8 comments4 people in discussion
  Resolved

I'm getting "failed to find the target" when I try to list an AFD. What got screwed up? Anyone know? Ten Pound Hammer • (What did I screw up now?) 00:18, 24 November 2011 (UTC)

I guess you refer to Twinkle not updating the AfD log so you had to do it manually.[3] Twinkle also failed to update the AfD log here: [4]. In both cases the AfD log page for the day had been created but had no entries yet: [5][6] I guess that confuses Twinkle. PrimeHunter (talk) 00:43, 24 November 2011 (UTC)
Perhaps something has changed about the format of each daily log page, since Twinkle should be able to handle this sort of case. I'll have a look. — This, that, and the other (talk) 06:21, 24 November 2011 (UTC)
Ah, I see; those daily log pages lack a line-break at the end. Twinkle fails without this. I am tempted to be a touch selfish here and request that Mathbot (talk · contribs) be fixed to add a trailing line break at the end of the log pages it creates, since it would be useful for users as well as tools like Twinkle. — This, that, and the other (talk) 09:40, 24 November 2011 (UTC)
That should not be hard. Could you please edit one such log page to make it look exactly as you want (trailing line break and all). I'll make sure the bot replicates your desired change to all future pages. Please ping me on my talk page after you do that. Oleg Alexandrov (talk) 20:10, 24 November 2011 (UTC)
It appears that MW strips trailing line breaks: so my request is actually not possible. Perhaps I'll have to fix Twinkle's code after all. — This, that, and the other (talk) 04:57, 25 November 2011 (UTC)
OK. Oleg Alexandrov (talk) 17:53, 29 November 2011 (UTC)
Fixed. — This, that, and the other (talk) 02:27, 11 December 2011 (UTC)

TP CSD tagging

Latest comment: 12 years ago3 comments2 people in discussion
  Resolved

...is doing strange things. See [7] and [8]. HurricaneFan25 19:47, 1 December 2011 (UTC)

Quite so. Notifying the user is probably not necessary in this case. I will fix this soon. — This, that, and the other (talk) 10:54, 2 December 2011 (UTC)
Fixed. — This, that, and the other (talk) 02:27, 11 December 2011 (UTC)

g4 bug/feature request

Latest comment: 12 years ago3 comments2 people in discussion
  Resolved

When you select CSD g4 via twinkle, it does not prompt for the previous deletion discussion. This would be valuable if the previous deletion discussion was not for the exact same title (page move, or group deletion). I had 4 g4's reverted today because I forgot the link to a group delete. A prompt would be very nice. Gaijin42 (talk) 21:20, 6 December 2011 (UTC)

I'll see if I can implement this. — This, that, and the other (talk) 00:28, 7 December 2011 (UTC)
A prompt has been added. — This, that, and the other (talk) 02:27, 11 December 2011 (UTC)

AFD and PROD notifications test finished

Latest comment: 12 years ago1 comment1 person in discussion
  Resolved
 – We thank Steven for this testing.

Hey, just a heads up that both the PROD and AFD tests (previous thread) have been reverted back to their default state. If you see anything weird in nominations/notifications please speak up, though I don't think there will be any issues. Thanks! Steven Walling (WMF) • talk 18:13, 9 December 2011 (UTC)

twinklespeedy.js

Latest comment: 12 years ago2 comments2 people in discussion

Very minor, but on line 1199, deldisc.substring(0, 9) !== "Wikipedia" should probably be deldisc.substring(0, 10) !== "Wikipedia:", as we're testing for a namespace. The page Wikipedia would not get an error message if inputted into the box. Cheers, —mc10 (t/c) 18:21, 10 December 2011 (UTC)

I did that to allow linking to "Wikipedia talk" pages, in case you really want to do that. (By the way, thanks for reviewing my changes! It's good to know someone looks at the commits other than me and AzaToth.) — This, that, and the other (talk) 01:26, 11 December 2011 (UTC)

{{db}} is misleading - remove it?

Latest comment: 12 years ago5 comments4 people in discussion

In the CSD options, Twinkle offers "{{db}} Custom rationale using {{db}} template". If you follow the "?" for guidance, it says "{{db}} is short for "delete because". At least one of the other deletion criteria must still apply to the page, and you should (must?) make mention of this in your rationale. This is not a "catch-all" for when you can't find any criteria that fit.", but on the face of it this option offers a misleading opportunity to use a "Custom rationale" to propose something for Speedy Deletion which does not fit any of the criteria, and will therefore fail. I suggest that this option should be removed, as likely to lead editors astray! There is no such thing as a valid "Custom rationale" for Speedy Deletion. PamD 13:25, 6 December 2011 (UTC)

Well, if multiple CSD reasons fit, it's usually done here, isn't it? (talk→ BWilkins ←track) 13:32, 6 December 2011 (UTC)
Well no, it isn't any more because the latest release has a multiple choice criteria feature. --Kudpung กุดผึ้ง (talk) 13:39, 6 December 2011 (UTC)
It is very useful for those editors who know how to use it. The tooltip help is a bit doomsday-ish, to try to scare unfamiliar newbies away from this option.
For example, if I want to nominate a page for CSD G8, and I wish to add a specific explanation/reason to the tag, the only way I can do that is to use the {{db}} option, and enter something like "CSD G8: __________". That's what is meant by "custom rationale". If you have any suggestions for improving the wording, I'm happy to consider them. — This, that, and the other (talk) 00:25, 7 December 2011 (UTC)
Ah, I see your point, although having CSD'd thousands of pages and summarily deleted hundreds of others from the Twinkle interface, I've never needed a use for it. As I said, for those who understand them, the CSD criteria are quite clear, and if they don't , they shouldn't be tagging pages, and the tooltip is quite clear thoug 'must' would be appropriate. However, to avoid misleading the newbs on NPP, perhaps it could be reworded as:
"Expanded rationale (also include the criterion such as CSD G8, etc.) Note, this is not a catchall - only clear criteria cases should be used)"
Does that make sense? Kudpung กุดผึ้ง (talk) 07:27, 18 December 2011 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Twinkle/Archive_27&oldid=1144526505"