Wikipedia talk:Twinkle

"WT:TW" redirects here. For For other uses, see Wikipedia talk:Transwiki log, or Wikiprojects talk Torchwood or Taiwan, see WT:TW (disambiguation).

Bugs

Main page: Wikipedia talk:WikiProject User scripts/Scripts/Twinkle/Bugs

Discussion

Twinkle Close Button

{{resolved|No. Amalthea 17:26, 26 March 2010 (UTC)}}

Resolved

 – Yes. Amalthea 15:23, 28 April 2010 (UTC)

{{editprotected}} I'd like to change the Twinkle red "close" button to this: --mono (talk) 23:57, 11 March 2010 (UTC)

Why? SchuminWeb (Talk) 03:55, 12 March 2010 (UTC)

Looks better!--mono 23:57, 1 April 2010 (UTC)

Not really. The close button needs to be red so it can easily be spotted, and this does not have it, I'm afraid. SchuminWeb (Talk) 00:08, 2 April 2010 (UTC)

Please replace img.src = "http://upload.wikimedia.org/wikipedia/commons/thumb/5/52/Nuvola_apps_error.png/18px-Nuvola_apps_error.png"; with img.src = "http://upload.wikimedia.org/wikipedia/commons/d/da/Crystal_button_cancel.png"; as the second image is a newer, nicer icon.--ℳøℕø 00:07, 25 April 2010 (UTC)

We're not changing the close button. The red "X" is functional and easy to spot, and I think that the suggested replacement is inferior to the current one. SchuminWeb (Talk) 02:38, 26 April 2010 (UTC)

Perhaps you would like to look at the proposed image and the old image:

• 
  New
• 
  Old

Thanks, mono^{National Pretzel Day} 23:52, 26 April 2010 (UTC)

Oh, whatever, then. I'm okay with red-to-red. SchuminWeb (Talk) 00:09, 27 April 2010 (UTC)

Did you change it? mono^{National Pretzel Day} 01:35, 27 April 2010 (UTC)

No. Outside my area of expertise. SchuminWeb (Talk) 03:19, 27 April 2010 (UTC)

It's changed to . One red cross for an other. "Newer" is irrelevant. "Nicer" is a matter of taste. Why is this so important to you? Amalthea 23:49, 27 April 2010 (UTC)

I support the change since the proposed image is an svg. The old close button also looks pixely on my iPhone. ~NerdyScienceDude (✉ message • changes) 15:15, 28 April 2010 (UTC)

Level 4 and 4im warning templates have changed their wording

Just as a heads-up: All of the level 4 and 4im warning templates have been reworded to incorporate some discussed changes. As an example, Template:Uw-vandalism4 now reads as follows:

This is the final warning that you are receiving regarding your disruptive edits. If you vandalize Wikipedia again, you may be blocked from editing without further notice.

This doesn't require any changes to Twinkle's code, but Twinkle users should be aware that these templates now say something different than what they've been saying for years. SchuminWeb (Talk) 03:54, 12 March 2010 (UTC)

I was already aware of these changes, and I feel that they are a major improvement. Immunize (talk) 19:34, 30 March 2010 (UTC)

So do I. JamesBWatson (talk) 13:11, 2 April 2010 (UTC)

The level 3 warnings have also now been updated to harmonize with the new wording on the level 4 templates. The changes involved replacing instances of "will" with "may". SchuminWeb (Talk) 23:05, 28 April 2010 (UTC)

Addition of Uw-bioblock template

New template that specifically address blocks for BLP violations, at Template:Uw-bioblock. Could this please be added to the warning section for Twinkle? Thanks. SchuminWeb (Talk) 03:32, 7 April 2010 (UTC)

Y Done. Amalthea 09:28, 28 April 2010 (UTC)

watchWarnings = false

I have been trying to tweak my settings but have had no success. I want to warn vandals without having them get added to my watchlist. In my user preferences, the gadgets section does not have Twinkle checked, so whatever is on my monobook.js page should be active, and it is. However, the last change I made stopped the vandal warning page from coming; a change I did not want to make. I have been sticking code in without understanding what it does: I'm stuck! Binksternet (talk) 21:18, 26 March 2010 (UTC)

Do you have "Add pages I edit to my watchlist" checked in your preferences? Amalthea 23:28, 1 April 2010 (UTC)

Yes, I do. I was hoping Twinkle could override that preference. Binksternet (talk) 13:33, 2 April 2010 (UTC)

Not ... yet. Amalthea 09:42, 5 May 2010 (UTC)

I'm having this same problem and I don't have that option checked in my prefs. Twinkle is installed js not as gadget. The line in my js looks like:

TwinkleConfig.watchWarnings = false;

It's the only autowatch thingie I can't seem to turn off. Ideas? Millahnna (mouse)talk 00:34, 10 April 2010 (UTC)

I'd still like to know what I was doing wrong if anyone knows, but for now I got it to work by just copying the js file in the above section and keeping all of the watch parameters only (i.e. I didn't need other changes for now). Millahnna (mouse)talk 00:44, 10 April 2010 (UTC)

You were missing the first line from WP:TW/DOC#Default Configuration. Amalthea 09:43, 5 May 2010 (UTC)

Rude messages

I recently encountered a dispute over Virgin birth (mythology) [since redirected]. I think a key point where it escalated involved some of Twinkle's messages at the user's talk page (User talk:Hammy64000) (I'm not familiar with Twinkle's range of messages, but these are credited to it in the edit summary; searching, it appears that the warning against blanking content is exceedingly rare, while the talk page threat occurs 578 times) These included:

Please stop assuming ownership of articles such as Virgin birth (mythology). Doing so may lead to disruptive behavior such as edit wars and is a violation of policy, which may lead to a block from editing. Ari (talk) 09:48, 13 April 2010 (UTC)

Please do not attack other editors, as you did here: Virgin birth (mythology). If you continue, you will be blocked from editing Wikipedia. Calm down. Ari (talk) 10:04, 13 April 2010 (UTC)

Please stop. If you continue to blank out or delete portions of page content, templates or other materials from Wikipedia, as you did to Miraculous births, you will be blocked from editing. Ari (talk) 05:27, 14 April 2010 (UTC)

Please stop. If you continue to use talk pages such as Miraculous births for inappropriate discussion, you may be blocked. Ari (talk) 04:49, 15 April 2010 (UTC)

Now you can look at the history of that article and make up your own mind - each was "sort of" justified according to the descriptions given (Hammy64000 deleted Template:disputed and some other notices, and argued some points at the talk page). But when these messages started pouring in, Hammy64000 pretty much went ballistic, and the net impact was to make the situation much worse.

What I think is that things like "owning an article" or "inappropriate talk page discussion" are extremely subjective judgments that many editors disagree about. It isn't right to be mechanically bombarding rather confused inexperienced editors like Hammy64000 with these hard-edged threats. My point here is not to question Ari89's decision making here per se - I don't see any reason why any editor should be phrasing comments about such debatable issues in such severe language, or threatening blocks. The message about deleting "...portions of page content, templates..." is just confusing - I assume it's meant to say don't blank the template itself, not that removing one tag is page blanking? And saying Calm down. in italics really defeats the purpose of saying it, doesn't it. Last but not least, saying that an editor is "owning" an article, therefore he may get into an edit war, therefore he may be blocked, is not merely pulling out the crystal ball but really doesn't sound like it's assuming good faith at all.

While there is a place for stern warnings about clearly improper editing, you should reduce messages about debatable infractions to represent that they are personal opinions - replace the exclamation points with olive branches - and just lose a few of them. Wnt (talk) 18:21, 19 April 2010 (UTC)

Templated user warnings are maintained by the editors organized at WP:UW, Twinkle merely facilitates their placements. The warnings on that user's page you refer to were mostly third-level warnings ({{uw-own3}}, {{uw-npa3}}, {{uw-delete3}}, {{uw-chat3}}, {{uw-agf3}}) and have less urging (or "threatening", as you say) counterparts – visit one of those templates to see the escalations. Twinkle can't and shouldn't enforce that one has to escalate them slowly, this has to be within the discretion of the user.
I haven't researched the issue at all, but generally, you should first approach the editor who placed the warnings and discuss your concerns with them. If it can't be resolved or you find this to be a larger, problematic pattern, you could raise it at the respective administrator's noticeboard, WP:ANI.
Personally, I almost exclusively use Twinkle warnings with vandalistic editors, and it's generally advised to not template the regulars – a brief personal message is much more effective.
Amalthea 18:45, 19 April 2010 (UTC)

Thanks for pointing me to these - I'm not sure why they didn't come up in the search. As I said, I'm not directly criticizing this editor - I'd tell him I didn't like how he phrased himself, but in this case I don't like how the template phrased him. Anyway it is now clear where the templates are, and that they are susceptible individually to discussion, revision, and TfD as appropriate. Wnt (talk) 22:22, 19 April 2010 (UTC)

Well, the third level messages are supposed to start using harsh language. You'll usually use them once you abandoned assumption of good faith, and I'd say that they have their place if used correctly, i.e. typically part of an escalation. That's why I said that if you disagree with the usage in this particular case, you should talk with the editor who placed them. Amalthea 12:15, 20 April 2010 (UTC)

What Amalthea has said is really the point here. Level three warnings should not usually be used until more gentle advice has been offered and ignored. however, once that has happened there comes a point when it is appropriate to get tough. JamesBWatson (talk) 10:46, 27 April 2010 (UTC)

Error message

I've recently been getting "Unable to grab editform" notices, and haven't changed my config lately. I use Zone Alarm, but haven't had problems before. Any ideas? Rodhullandemu 18:27, 22 April 2010 (UTC)

At least one other user had that exact same problem before, and he fixed it by disabling Zone Alarm: WT:Twinkle/Archive 10#Not Working.
Amalthea 11:35, 23 April 2010 (UTC)

Thanks. I'll try that. Rodhullandemu 15:17, 10 May 2010 (UTC)

Vandal tagging

Moved to WT:Friendly#Vandal tagging.

New Page Patrol problem

There have been some complaints again about a handful of new page patrollers not choosing to follow the community's advice about not patrolling pages within seconds of their creation. (See, e.g., Wikipedia:Village pump (policy)/Archive_74#Over-hasty_tagging_of_new_articles_.3D_off-putting_to_new_users.) Spamming tags into articles that someone is actively working on is unfriendly, irritating, and often unhelpful; it also produces edit conflicts and produces public complaints from new contributors. On the flip side, apparently waiting 15 minutes means that some other consensus-rejecting, overly hasty editor may have already speedied the obvious vandalism, so following the directions isn't as much fun.

Some of these hasty NPPers seem to rely on Twinkle and Friendly. Is it possible to change Twinkle or Friendly to make compliance with the community's NPP advice more likely, e.g., by not marking pages as patrolled if they're less than 5-10 minutes old? WhatamIdoing (talk) 22:57, 23 April 2010 (UTC)

That would be awesome. It's a mistake I made when I first starting doing recent changes patrol on more than one occasion. One thing though; what about COI and obvious hoax type new pages (like when some kid makes a page about himself)? The obvious hoax stuff is no big deal, those get grabbed quickly either way. But new pages that are purely adverts of a COI nature I'm not sure about in terms of how quickly they are found if ignored the first 15. Millahnna (mouse)talk 23:28, 23 April 2010 (UTC)

If we patrol exactly the same way that we do now, only delaying the work by 15 minutes, then exactly the same stuff will be caught.

The question is really, "If a user first saves a page at 12:01, do we want to review that page at 12:02 or at 12:16?" IMO the version that is 15 minutes old will give you a much more accurate view of the article than one that is sixty seconds old and being actively edited. WhatamIdoing (talk) 23:51, 25 April 2010 (UTC)

What about adding {{new unreviewed article}} to the Notice template section of Twinkle? This can be added to articles immediately without upsetting the author, and it would give NPP Twinklers something to do with their itchy fingers when they look at a new article and it's too early really to tag for cleanup. Rd232 ^talk 10:57, 26 April 2010 (UTC)

Usually I'm waiting for some additional support for requested additional templates, but this one is Y added to Friendly notice tags now.
I can't promise it will do any good of course, and it might need pointing out if you see overeager tagging. This is our fundamental patrolling dilemma, we want early patrollers for to catch G10s and G12s as early as possible, and on some articles an early SD tag is certainly appropriate and most constructive as far as the encyclopedia is concerned, but many other actions should be delayed. I don't think technical enforcement is really the answer here, but maybe Twinkle/Friendly can better assist in informing that e.g. early issue tags aren't always constructive. I'm open to ideas. Amalthea 23:43, 27 April 2010 (UTC)

How to integrate revision difference links with warnings better?

When I warn someone for vandalism, I have to copy the URL of the revision changes and paste them into the "More:" field. This results in an italicized phrase appended after the warning. For example, Your disruptive edit can be viewed here. This gets kind of old after awhile. I notice Huggle users seem to have their revision differences integrated into the message. Also, I saw (for the first time) someone leaving warnings with Twinkle, but the revision differences appeared as: (diff), and not in italics. Am I missing something? Is there an easier way to plug in the information required? – Kerαunoςcopia^◁_galaxies 01:58, 30 April 2010 (UTC)

Some of the comments above made me realize there may be a difference in coding between users. I don't use the monobook.js option, I just have TW turned on under "Gadgets". Maybe this is a possible explanation? – Kerαunoςcopia^◁_galaxies 02:01, 30 April 2010 (UTC)

With TW, the warnings given are just the plain template. Additionally, I don't know how it would work on the diffs, especially when one reverts multiple edits with one sweep, plus unlike HG, TW's reverting and warning functions are separate (as they should be). If you like the revert-and-warn-in-one-swoop functionality, why not give Huggle a spin and add it to your toolbelt? SchuminWeb (Talk) 04:41, 30 April 2010 (UTC)

And no, Monobook vs. gadget shouldn't make a difference in this case. SchuminWeb (Talk) 04:43, 30 April 2010 (UTC)

The fewer the gadgets, the better. I don't want revert-and-warn-in-one, I was just wondering if I was missing some secret that would allow me to plug in, say, only the Old ID reference number instead of having to do the "copy/paste URL into a sentence" method each and every time. – Kerαunoςcopia^◁_galaxies 04:44, 30 April 2010 (UTC)

I figured it out. Someone was using two apostrophes before and after their "comments" which un-italicized their (diff) comments. So no special Twinkle trick was involved. Case closed. – Kerαunoςcopia^◁_galaxies 02:06, 8 May 2010 (UTC)

Help with TwinkleConfig.watchWarnings

Resolved

Not sure if this is the place to ask - I have set TwinkleConfig.watchWarnings to false, but whenever I issue a warning to an IP user it still adds their page to my watchlist. My full config (at my monobook.js) is...

importScript('User:AzaToth/twinkle.js');
if( typeof( TwinkleConfig ) == 'undefined' ) TwinkleConfig = {};
TwinkleConfig.watchRevertedPages = [];
TwinkleConfig.showSharedIPNotice = false;
TwinkleConfig.showRollbackLinks = [ 'diff' ];
TwinkleConfig.watchSpeedyPages = [];
TwinkleConfig.watchWarnings = false;

My computer/browser setup = MacBook Pro/OS X 10.5.8/Firefox 3.6.3. Grateful for any suggestions -- Boing! said Zebedee 09:30, 5 May 2010 (UTC)

PS: "Add pages I edit to my watchlist" is unchecked in my preferences -- Boing! said Zebedee 09:41, 5 May 2010 (UTC)

1. WP:NEWSECTION
2. "Add pages I create", too?

Amalthea 09:46, 5 May 2010 (UTC)

Aargh! It was first-time warnings, so it was pages I was creating! Thanks for that - I like it when problems are caused by me being dumb, cos they're easily fixed then ;-) (PS: Thanks for the WP:NEWSECTION heads-up - I'd never seen it before, and I've been committing that sin for years but nobody has ever pointed it out to me before) -- Boing! said Zebedee 10:14, 5 May 2010 (UTC)

XFD tab from newpage patrol page defaults to RFD instead of AFD

One would think that this should default to AFD rather than RFD. Can this be fixed? SchuminWeb (Talk) 02:01, 7 May 2010 (UTC)

YDone, previous redirect check only looked for "redirect=no" in the query. Since apparently Special:Newpages adds that to each entry these days, they were all thought to be redirects. Amalthea 09:18, 7 May 2010 (UTC)

Blacklisting

"Note that disruption only accounts using Twinkle are typically blocked from editing altogether."
What? Svanslyck (talk) 22:30, 8 May 2010 (UTC)

In other words, if Twinkle is being used disruptively, rather than just being blacklisted for Twinkle, they're blocked for disruption.

This does, however, raise a point - considering that disruptive use of Twinkle is more likely to lead to a block from an administrator, and since blocking has more thorough regulation than the blacklist, Twinkle blacklisting is more likely to occur in the case of someone being prohibited from using automated tools by Arbcom. What do people think about turning control over the Twinkle blacklist to Arbcom, and letting them determine the contents of said blacklist? Speaking for myself, I'd be more likely to block someone outright if they're engaging in disruptive behavior using Twinkle rather than revoke the Twinkle, since it's possible that someone could then just hop over to another tool and continue disruption. SchuminWeb (Talk) 00:50, 9 May 2010 (UTC)

Personally I agree with you, I have never used it, and don't see that I would. Some admins use it though, but I have hardly ever checked what prompted Twinkle blacklisting, and never monitored how successful a measure that was.
Concerning Arbcom, I'm not aware of any user being placed on the blacklist due to an Arbcom case, and am only aware of one user being restricted from using Twinkle. In that particular case, a Twinkle blacklisting would be a joke, since it's really *trivial* for any user with some programming experience to figure out how to get by it.
The main case I see where the blacklist is actually useful is with overeager, good-faithed, but often immature editors where warnings, reverts, or taggings with the click of a button is just too quick, and makes them not think about it first. Quite similar to revocation of the rollback right, actually. Amalthea 10:38, 10 May 2010 (UTC)

another customized block notice

We had a discussion last week at the WP:UAA talk page about users who don't think their edits are promotional if they are promoting a "noble cause" such as a charity or other nonprofit organization, and Template:Uw-causeblock was whipped up as a result. Any chance we could get it added to the arsenal? Beeblebrox (talk) 20:37, 10 May 2010 (UTC)

Y Done. Amalthea 22:32, 10 May 2010 (UTC)

Thank you! Beeblebrox (talk) 23:42, 10 May 2010 (UTC)

Any remaining Vector issues?

Seeing that MediaWiki will switch the default skin to Vector in a couple of days, and since I don't use Vector myself: Are there any remaining issues with Twinkle and Vector that any of you know of? Amalthea 21:53, 10 May 2010 (UTC)

Too new

Resolved

I have been using Twinkle for sometime now but now it is telling me that I am too young to use Twinkle. Why is this?--Curtis23's Usalions 23:27, 10 May 2010 (UTC)

Seems to work again. I can't quite say how this happened for you, there are a couple of possibilities. I've just tweaked your monobook.js a bit to remove one possible cause for it. If it ever happens again, please just bypass your browser cache once and try again. Amalthea 10:36, 11 May 2010 (UTC)

Twinkle menu on Vector

As kicked off by TheDJ a few weeks back in WT:Twinkle/Archive 18#Vector menu, the Twinkle tools are now by default organized in a separate drop down menu if you use the Vector skin. If you don't like it, you can configure where the tools are placed for you using some new config options. Use TwinkleConfig.portletId to define the portlet menu Twinkle adds its links. Existing portlet menus are:

• Monobook: "p-cactions", "p-personal", "p-logo", "p-navigation", "p-interaction", "p-tb", "p-coll-print_export"
• Vector: "p-navigation", "p-interaction", "p-tb", "p-coll-print_export", "p-namespaces", "p-variants" (menu), "p-views", "p-cactions" (menu)
• Modern: "p-cactions", "p-navigation", "p-interaction", "p-tb", "p-coll-print_export"

You can also place them in a new, dedicated portlet menu (which is the default in Vector, as mentioned). The skins have several portlet menu areas:

• Monobook: "column-one" (the sidebar; p-personal and p-cactions are in here, too, they just have customized styles to layout them)
• Vector: "panel" (sidebar), "left-navigation", "right-navigation"
• Modern: "mw_portlets" (sidebar), "mw_contentwrapper"

You can use the TwinkleConfig object to have a new portlet menu created, like in the sidebars, or as a separate navigation row in Modern, or as a new drop down menu in Vector. Config options are:

TwinkleConfig.portletArea = <ID of the portlet menu area to add the new portlet menu>;
TwinkleConfig.portletId   = <ID of the new portlet menu. Typically "p-twinkle" for new portlet menus, or an existing portlet menu id>;
TwinkleConfig.portletName = <Display name of the portlet menu. Only visible in the sidebar or with drop down menus>;
TwinkleConfig.portletType = <Only useful for the left and right navigation areas in Vector. Set to "menu" to make the portlet menu a drop down menu>;
TwinkleConfig.portletNext = <ID of an existing element in the portlet menu area, Twinkle portlet menu will be inserted before it. Or undefined to place the Twinkle menu last>;

Creating drop down menus in Monobook and Modern would be doable, but someone else will have to figure out CSS styles for it first. :)

Examples:

Twinkle in the Monobook sidebar, right above the search

if( typeof( TwinkleConfig ) == 'undefined' ) TwinkleConfig = {};
TwinkleConfig.portletArea = 'column-one';
TwinkleConfig.portletId   = 'p-twinkle';
TwinkleConfig.portletName = 'Twinkle';
TwinkleConfig.portletNext = 'p-search';

Twinkle in Vector, one tab per tool, next to the namespace tabs

if( typeof( TwinkleConfig ) == 'undefined' ) TwinkleConfig = {};
TwinkleConfig.portletId = 'p-namespaces';

In the actions drop down on the left in Vector

if( typeof( TwinkleConfig ) == 'undefined' ) TwinkleConfig = {};
TwinkleConfig.portletId = 'p-variants';

Anyone willing to add this to the documentation? I'll carve you a barnstar if you do. :)

I've tested the menus in recent versions of Firefox, Chrome, Opera, and Safari. If you have any problems, please say so here. I'd really like it if a few people could test it in Vector, before the rollout on the 13th.

Cheers, Amalthea 22:20, 11 May 2010 (UTC)

It looks fantastic, great job. Tommy2010 01:19, 12 May 2010 (UTC)

So much better - thanks Amalthea! Now the only thing left not to like about the beta is the lack of a CITE button (anyone know how to fix that?). Figured it out: If anyone is interested see WP:REFTOOLS and disable the enhanced editing toolbar in beta.  7  01:42, 12 May 2010 (UTC)

Actually, you can get a cite button using the new toolbar. See User:Mr.Z-man/refToolbar 2.0. ~NerdyScienceDude (✉ message • changes) 03:31, 12 May 2010 (UTC)

Truly amazing. This could very well solve the age old issue I have with modern aka "The final five disappear." Anyway, I wrote a non-comprehensive and crap documentation - definitely not barnstar worthy - and threw it on the bottom of the page. ~ Amory (u • t • c) 03:01, 12 May 2010 (UTC)

Quick little thing - when I put it in the sidebar in vector (gadget install) the menu name displays twice, the second as a link to TW#. The namespaces one looks sweet. ~ Amory (u • t • c) 03:18, 12 May 2010 (UTC)

Fixed. Amalthea 10:09, 12 May 2010 (UTC)

Nice job! Works great. ~NerdyScienceDude (✉ message • changes) 03:27, 12 May 2010 (UTC)

Can I just have the code for the old Twinkle menu in the Vector beta, in the same drop-down menu as the Friendly tools? —fetch·comms 20:54, 13 May 2010 (UTC)

Change the portletId you already have in your vector.js from "p-variants" to "p-cactions". Amalthea 16:11, 15 May 2010 (UTC)

How could I code it so that the TW text was replaced by File:Police_man_Twinkle_Head.svg?--moɳo 03:29, 15 May 2010 (UTC)

Stick something like

#p-twinkle { background-image:url('http://upload.wikimedia.org/wikipedia/commons/thumb/a/a5/Police_man_Twinkle_Head.svg/29px-Police_man_Twinkle_Head.svg.png');}

in your vector.css file while setting the portletName to an empty text, like described above. Amalthea 16:11, 15 May 2010 (UTC)

Got the first part; can't figure out what to put for the 2nd part.--moɳo 00:51, 16 May 2010 (UTC)

twinkle doesn't work on Monobook anymore?

My twinkle top menus disappeared yesterday. I haven't futzed with my modern.js monobook.js or .css in a while, nor do I see any reason they would not work. Were they broken in order to support Vector? Am I the only one? It's making me much less effective in my adminly duties. tedder (talk) 17:16, 12 May 2010 (UTC)

Most probably related to the section directly above, and they were not intentionally broken, no. Amory above is using Modern, and it works for me, so it doesn't appear to be a general problem. I assume you've switched skins now, since I notice you making Twinkle edits right now?
Can you do the following, please:

1. Tell me what browser you are using
2. WP:BYPASS your browser cache and try again so that I can be sure you have the latest versions of everything
3. If it's still not working, check your javascript console (Ctrl+Shift+J in Firefox) for Twinkle-related errors

I have to run in about 20 minutes and will then be offline for about 24h, so hopefully we can resolve this before then. :)
Amalthea 17:49, 12 May 2010 (UTC)

I shouldn't say 'intentionally' broken, just that it became broken. I'm on Firefox, tried bypassing, and it's been this way for at least 12 hours. Part of twinkle is up, but (for instance) what is missing is the [warn] and [xfd] tabs at the top of the page. I think all of the tabs are gone, but I can't remember what other tabs Twinkle gives. I'll pull up the console and see what happens. (and isn't the talkback actually from Friendly, not Twinkle?) tedder (talk) 17:56, 12 May 2010 (UTC)

Followup- the three things listed in the js console: "Unknown property 'column-count'. Declaration dropped.", "Unknown property 'column-width'. Declaration dropped." and "Error: element is null; Source File: http://bits.wikimedia.org/skins-1.5/common/mwsuggest.js?276z57 ; Line: 158" tedder (talk) 17:59, 12 May 2010 (UTC)

Hmm, that doesn't really help. Can you please deactivate Twinkle and Friendly in you gadgets, put

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

into User:Tedder/modern.js, bypass your cache again, and see if it helps?
FWIW, on a user talk page you should have Warn, ARV, CSD, Last, PP, XFD, Unlink, Deli-batch, D-batch, and P-batch. Amalthea 18:21, 12 May 2010 (UTC)

I had AzaToth/twinkle.js in my monobook.js as of this morning. Removed that, put in Amalthea/twinkle.js now. Also removed friendly and twinkle from the gadgets preferences. I knew there were other tabs I was missing! Anyhow, it looks like that change restored the tabs at the top. The only mystery is, why are the tab names back to the 'stock' length now? For instance, "user page", "discussion" instead of "user", "talk". tedder (talk) 18:30, 12 May 2010 (UTC)

So you're using monobook, not modern? Amalthea 18:33, 12 May 2010 (UTC)

Yeah- doh, sorry for the red herring on the title. tedder (talk) 18:35, 12 May 2010 (UTC)

Ah, OK, that leaves me with some things that might have gone wrong then, maybe some interference with your other scripts. I'll have to try and figure the rest out tomorrow evening though, I'm afraid, now that your adminly productivity is back to normal. Cheers, Amalthea 18:38, 12 May 2010 (UTC)

Thanks for the help. I know you are on a timeline, and it's nice to not have to look up the warning templates and try to make AFDs by hand. tedder (talk) 18:39, 12 May 2010 (UTC)

sorry

But I'm the same way with my computer that I am with my car, I just drive the thing, I don't know or want to know squat about how it works. I'd like to be able to use the new features, but I need someone to tell me in plain, techno-idiot English what to do to make Twinkle work again. I'm using Safari 4.0.5 on OSX 10.5.8, I've never activated Twinkle via gadgets, I have it my monobook.js page. Do I need to just move that or something? Beeblebrox (talk) 22:44, 13 May 2010 (UTC)

Just copy what you have in User:Beeblebrox/monobook.js into User:Beeblebrox/vector.js. I'm not sure if ALL the scripts you have listed there are compatible with Vector however. Twinkle definitely should be. —TheDJ (talk • contribs) 22:50, 13 May 2010 (UTC)

Thank you very much, that is exactly what I needed. Beeblebrox (talk) 23:13, 13 May 2010 (UTC)

as an aside, I've now tested all those scripts and they do all seem to work Beeblebrox (talk) 01:01, 14 May 2010 (UTC)

Twinkle boxes' fonts too big on Vector

It appears that the TW boxes, such as for AFD, CSD, etc. are now using a font that's a couple sizes larger in Vector than it used to be in Monobook. Can this be configured to use the small size fonts for the dialog boxes in Vector?

BTW, it does the same thing in Friendly, so it appears likely that it's something in a shared component. SchuminWeb (Talk) 15:23, 13 May 2010 (UTC)

The underlying framework, morebits.js drives the engine for both WP:TW and WP:FR.--moɳo 23:59, 13 May 2010 (UTC)

I figured as much. Can we fix that size issue? SchuminWeb (Talk) 01:58, 14 May 2010 (UTC)

Y Fixed, bypass your cache to see the change. Amalthea 19:19, 14 May 2010 (UTC)

Muchas gracias. SchuminWeb (Talk) 23:42, 14 May 2010 (UTC)

Shrunken font

I just used TW to request protection, and the text has shrunk significantly. Why? Same thing for Friendly. ~NerdyScienceDude (✉ • ✐) 00:15, 16 May 2010 (UTC)

I had the same issue; see above section. I think that messed it up.--moɳo 00:52, 16 May 2010 (UTC)

Yeah, we brought the size down to match the size we were used to in the Vector skin. Are you still using Monobook? How small does the font look now? SchuminWeb (Talk) 02:04, 16 May 2010 (UTC)

I have been using Vector since I first created my account in December. I haven't used TW under Monobook. ~NerdyScienceDude (✉ • ✐) 03:40, 16 May 2010 (UTC)

In that case, what you see is a direct result of the above thread. I requested that the font be sized down to match what we were used to in Monobook. SchuminWeb (Talk) 05:16, 16 May 2010 (UTC)

What Schumin said: That's the size it was always supposed to have. Amalthea 09:22, 16 May 2010 (UTC)

CSD user warnings

I don't see the various CSD user warnings in Twinkle. Are they there? If not, they should be added. - UtherSRG (talk) 10:48, 18 May 2010 (UTC)

The notices are automatically placed on a user's page with a nomination via Twinkle. Do you regularly need to only add the notice? Amalthea 12:15, 18 May 2010 (UTC)

Yes. Sometimes I do the actual delete, sometimes I just place the CSD tag. When I do the delete, I have to manually place a tag. - UtherSRG (talk) 05:14, 19 May 2010 (UTC)

CSD Listing Update request

In Twinkle's Popup UI, can the listing for CSD#G10 (Attack Page) and it's associated description under the ? be updated to mention that it can also be used to Speedy Unsourced BLP's please? I started this without realising that G10 could be used to mark an article for Negative Unsourced BLPs, cause the description and the associated help don't mention it :) Thanks! BarkingFish ^{Talk to me} | _{My contributions} 22:51, 18 May 2010 (UTC)

In my experience most editors understand that BLPs can be attack pages, its more common to find editors assuming that only BLPs can be G10s. So I'd be careful about rephrasing this to give more emphasis to BLPs. ϢereSpielChequers 23:36, 18 May 2010 (UTC)

I'm not asking for it to give more emphasis to the BLP thing, simply to mention the fact that it can be used *for* BLPs. I'm an experienced editor of almost 6 years, and I wouldn't have started that conversation had I have known I could use G10 to do that. I barely touch BLPs, but I think it should be mentioned in the UI at a bare minimum. BarkingFish ^{Talk to me} | _{My contributions} 00:00, 19 May 2010 (UTC)

CSD G10 can't be used to speedy just any unsourced BLPs. G10 does cover unsourced and purely disparaging BLPs, but that's pretty much what the tooltip already says: "Pages that serve no purpose but to disparage their subject or some other entity (e.g., "John Q. Doe is an imbecile"). This includes a biography of a living person that is negative in tone and unsourced, where there is no NPOV version in the history to revert to. Administrators deleting such pages should not quote the content of the page in the deletion summary!" (emphasis mine). Amalthea 12:03, 20 May 2010 (UTC)

Opera support

Resolved

The page states that for Twinkle to work with Opera, the Javascript Standard Library must be enabled. Is the issue here that Twinkle requires the array extras from Javascript 1.6? Because Opera supports that. Does the article need to be updated? I ask because I've been using Opera and Twinkle, and haven't noticed any problems.
--Gyrobo (talk) 03:13, 19 May 2010 (UTC)

Right, that appears to be outdated. When I just played around with it I had some significant problems with the current Opera version, not sure why that doesn't appear to have happened to you, but I seem to have fixed it.
Do you know of any problems with Opera? Like WP:TW/BUG#306, WP:TW/BUG#325, or WP:TW/BUG#348?
Thanks, Amalthea 12:56, 20 May 2010 (UTC)

I haven't yet nominated an article for deletion, an I just switched to Vector, so I can't really give solid testimony on any of those bugs yet.
--Gyrobo (talk) 20:12, 20 May 2010 (UTC)

Alright, if you notice something please let me know. Cheers, Amalthea 20:36, 20 May 2010 (UTC)

A2 template should take iw parameter

The CSD A2 template takes an iw link as a parameter. It would be good if we could specify that in Twinkle instead of having to go back and manually update the article and the warning placed on the editor's page. Either an entry field next to the A2 radio button, or a popup would work. Better would be that if the iw link exists in the article, to find it and grab it. (See the recently deleted Jorge leon garduño as an example.) - UtherSRG (talk) 05:55, 19 May 2010 (UTC)

Another CSD idea

Twinkle is missing {{db-multiple}}. It would be great to add this. Make it a check box at the top of the CSD dialogue, checking it turns the radio buttons into check boxes and allows multiple reasons for tagging. - UtherSRG (talk) 06:54, 19 May 2010 (UTC)

I agree.--moɳo 05:49, 22 May 2010 (UTC)

XFD doesn't remove {{hang on}}

I just used Twinkle to AFD an article, and responded positively to having it remove the speedy tags. It didn't remove {{hang on}}. Perhaps it only looks for {{hangon}}? - UtherSRG (talk) 08:18, 20 May 2010 (UTC)

Y Twinkle now recognizes the common redirects. Amalthea 08:39, 20 May 2010 (UTC)

XFD oddness

Does XFD now automatically add links to previous XFDs? I just created a new AFD at Wikipedia:Articles for deletion/Buenos Aires Cricket & Rugby Club via Twinkle, and it added a self-link that shouldn't be there, I don't believe. - UtherSRG (talk) 08:16, 21 May 2010 (UTC)

Y Workarounded, issue was with {{Afd2}} and page names with some special characters like "&". Base issue is IIRC bugzilla:13288, namely usage of some magic words inside parser functions. Amalthea 09:04, 21 May 2010 (UTC)

Twinkle welcomes users along with their AFD notification?

I noticed in this revision on User talk:81.168.1.36 that Twinkle dropped a welcome message along with the AFD notification when it notified the IP editor of an AFD nomination. Can we lose the welcome message? The welcome message seems to be Friendly's jurisdiction, and I would have preferred that Twinkle just drop the notice and be done with it, and let people add any welcome notices separately. SchuminWeb (Talk) 05:41, 22 May 2010 (UTC)

It does the same thing for CSDs as well, using {{firstarticle}}. I like it; it helps new users and is really quite automated. Btw, what was an AfD notice doing on an IP's talkpage? IPs can't create articles!--moɳo 05:48, 22 May 2010 (UTC)

IPs used to be able to create articles, therefore it is feasible that an AfD notice will get posted to an IPs talk page. Mjroots (talk) 10:43, 22 May 2010 (UTC)

Only is placed if the page doesn't exist when you send the AfD notification, and is actually a feature of the template, not Twinkle, to reduce the impact of getting ones first article deleted. The whole notice doesn't make sense here of course, but why don't you like the welcome? Amalthea 11:54, 22 May 2010 (UTC)

I'd just prefer to choose whether or not to place it. That's all. SchuminWeb (Talk) 15:02, 22 May 2010 (UTC)

Twinkle and AfD cats

It seems that there is a problem with adding AfD cats when using Twinkle. Would all those who use Twinkle to create AfDs please then edit the created AfD so that it appears in the correct AfD category? Thanks in advance, Mjroots (talk) 10:45, 22 May 2010 (UTC)

All those AfDs you categorized were opened by the same editor, I assume they just didn't select one from the drop down. Worked here, for example. Amalthea 11:45, 22 May 2010 (UTC)

Image tagging question

Hi, most of the image deletion tags have an indication to add a template to the image caption (in the article that the image is used). For example, Template:Di-no source and Template:Di-no license both say "Add following [sic] to the image captions: {{deletable image-caption|date}}." I think this is very important ... image uploaders may not be around, and images (or lack thereof) often affect the quality of the article. Adding a tag to the article gives those working on the article notice of the issue and time to address the tag, to find a new image, etc. Would it be possible to add functionality to Twinkle to automatically add the appropriate tag to the caption, or to remind the person tagging an image to add the appropriate tag? Sincerely, --Iamunknown 19:07, 22 May 2010 (UTC)