Wikipedia talk:Twinkle/Archive 9
This is an archive of past discussions on Wikipedia:Twinkle. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 5 | ← | Archive 7 | Archive 8 | Archive 9 | Archive 10 | Archive 11 | → | Archive 15 |
AFD Problems
For some reason the last two times I nominated a page for AFD twinkle failed to add the AFD notice to the nominated article. Ridernyc 20:14, 1 November 2007 (UTC)
CSD Question
I haven't been able to get Twinkle to successfully do a CSD in some time. IIRC, the problem started about the time I became an admin, so that may have something to do with it. It used to be when I clicked the CSD tab, the box would open, I'd pick a reason, and Twinkle would immediately scurry off to work. Now I pick the reason, nothing happens, and I can't find anything else I need to choose to make something happen. Do I have a setting wrong? Does Twinkle have it in for me? Help, please! --Fabrictramp 20:37, 31 October 2007 (UTC)
- Works fine for me - you might need to ctrl-f5. As an admin TW works differently for CSDs; unless you have the "tag only" button checked, selecting any of the criteria will immediately delete the page as soon as you tick the radio button. — iridescent 22:09, 2 November 2007 (UTC)
- Any other hints? I've tried both a test subpage of my user page and a real live page that sorely needs deleting. Doing ctrl-F5 seems to be doing something (there's a lot of communication between Firefox and Wikipedia), but nothing happens to the article itself whether I have "tag only" checked or not (unchecking "orphan backlinks" also isn't making a difference.) I also tried disabling the pop-up blocker in Firefox to no avail. *sigh*--Fabrictramp 22:48, 2 November 2007 (UTC)
- UPDATE -- hooray, it must have been a setting of some kind! I took out everything from the settings except the two or three items I didn't want to be default behavior, and CSD is working like a dream. I'm in heaven. :) --Fabrictramp 23:40, 2 November 2007 (UTC)
- The most obvious hint is be VERY careful with the Twinkle CSD button as it's very (I'd say far too) hairtrigger; no "are you sure" or "click here to continue" boxes as there are with the "proper" delete button, no "this page has a history" warning etc. I'd also stay clear of the G12 button; because it doesn't allow you to choose the delete summary, there's no way to give any indication of what you think the material's a copyvio of. — iridescent 23:57, 2 November 2007 (UTC)
- Yeah, CSD with TW is touchy. There are numerous times where I've inadvertently hit the WRONG reason, and then had to restore it, just to speedy it again under the correct criterion. SchuminWeb (Talk) 00:26, 3 November 2007 (UTC)
- The hints are much appreciated! --Fabrictramp 00:27, 3 November 2007 (UTC)
- I designed it so possible speed up the time needed to delete a page/image (it was when the CSD backlogs where more than month old). As a way to speed up the 99% of the cases when there is a certain outcome. But if there are too many admins with the habit of clicking wrong too often, perhaps it could be changed :) →AzaToth 00:56, 3 November 2007 (UTC)
- Well, there could be another user preference for confirmation... Perhaps a Boolean named
confirmSpeedyDelete
? Tuvok[T@lk/Improve me] 05:46, 3 November 2007 (UTC) - How would that help? I cant think of any admins not setting that to false, just getting tired of the confirmation dialog all the time. →AzaToth 10:55, 3 November 2007 (UTC)
- It would be one of those self-help kind of things, where if you know you're likely to inadvertently click on the delete button (or the wrong category) you turn on the confirmation. Tuvok[T@lk/Improve me] 17:14, 3 November 2007 (UTC)
- Even though I'm the one criticising it, I'd agree that it would be a waste having a confirm button, providing you've enough sense to realise when your finger slipped & you notify the creator of the actual reason. Although I would personally love a way to add comments to the deletion summary for G12s, as mentioned above. — iridescent 17:27, 3 November 2007 (UTC)
- My wish list would include being able to set a default value for whether the page just gets tagged or not. (Default of tag only is safer, IMHO).--Fabrictramp 19:20, 3 November 2007 (UTC)
- Strong support for at the very least having that as an option. I actually tag more than I delete; unless there's no possibility at all that it's controversial IMO they should always get tagged rather than deleted. — iridescent 19:24, 3 November 2007 (UTC)
- My wish list would include being able to set a default value for whether the page just gets tagged or not. (Default of tag only is safer, IMHO).--Fabrictramp 19:20, 3 November 2007 (UTC)
- Even though I'm the one criticising it, I'd agree that it would be a waste having a confirm button, providing you've enough sense to realise when your finger slipped & you notify the creator of the actual reason. Although I would personally love a way to add comments to the deletion summary for G12s, as mentioned above. — iridescent 17:27, 3 November 2007 (UTC)
- It would be one of those self-help kind of things, where if you know you're likely to inadvertently click on the delete button (or the wrong category) you turn on the confirmation. Tuvok[T@lk/Improve me] 17:14, 3 November 2007 (UTC)
- Well, there could be another user preference for confirmation... Perhaps a Boolean named
Sockpuppets not transcluding
Hi, I made Wikipedia:Suspected sock puppets/Earthenboat with TW today, but it didn't transclude. I just did it a few hours later by hand. • Lawrence Cohen 22:04, 2 November 2007 (UTC)
- I just made Wikipedia:Suspected sock puppets/Rlk89 and had the same problem - everything goes fine, but it doesn't transclude to WP:SSP. — iridescent 17:28, 3 November 2007 (UTC)
New template for speedy warnings
As you know, there's been past discussion about how Twinkle's use of {{db-csd-notice}} results in warnings that are too general and potentially confusing, especially to new editors. I'm currently developing a new version of this template, which I'll put under the title {{db-csd-notice-custom}} when it's done. This template will use the exact same format and syntax as the current db-csd-notice template, but it will use the more customized warnings found at Wikipedia:Criteria for speedy deletion/Templates instead of a generic warning message.
Perhaps you could use this template in Twinkle for CSD warnings once I finish writing it? I plan on designing the template with all the parameters identical to the old one, so that you wouldn't need to change Twinkle any more than changing the name of the template used. Personally, I'm getting a little tired of those generic warnings that only list the CSD code number. Pyrospirit (talk · contribs) 00:41, 31 October 2007 (UTC)
- The template is now complete and ready for use! The only change you need to make to Twinkle should be changing the name of the template you use for the warnings; I set it up so that everything else, such as the order of parameters, won't need to be changed. I hope you like it! Pyrospirit (talk · contribs) 01:34, 31 October 2007 (UTC)
- Yes, please use this template as the default, the current one doesn't give nearly enough information. --Closedmouth 06:29, 2 November 2007 (UTC)
- The only issue that I see here is that all the CSD A7's resolve to a person or group of people. (Ie, db-band doesn't mention a band on the warning notice). Otherwise it works. --Bfigura (talk) 03:26, 3 November 2007 (UTC)
- Yes, please use this template as the default, the current one doesn't give nearly enough information. --Closedmouth 06:29, 2 November 2007 (UTC)
- The reason I created {{db-csd-notice-custom}} was because I think that {{db-csd-notice}} seems very unclear and confusing to new editors, and perhaps even unfriendly. It uses the codes for the CSD rather than actually explaining the reason, while the "custom" version of the template actually explains why the page was tagged for speedy deletion. About the different A7 criteria, I'll make {{db-csd-notice-custom}} work with those by calling them criteria 7.1 for bands/singers, 7.2 for clubs/groups, 7.3 for companies, and 7.4 for web content. AzaToth can easily change twinklespeedy.js to include those changes. Note that this won't change the actual numbering of the criteria; the 7.X is just a trick I'd use to separate them for the template. Pyrospirit (talk · contribs) 15:50, 3 November 2007 (UTC)
- I'm going to put this together as a feature request, so hopefully it'll be implemented soon. Pyrospirit (talk · contribs) 16:05, 3 November 2007 (UTC)
- Sounds good to me. The template should probably be indef protected before it goes into wide usage though. Best, --Bfigura (talk) 16:52, 3 November 2007 (UTC)
- This template is now in use, and I've moved the documentation to a subpage and requested full protection. Pyrospirit (talk · contribs) 16:52, 5 November 2007 (UTC)
Just a little request
Now that there is the option to notify if possible, is it possible to make the window one line longer? I don't know about others, but the A7 unremarkable people option is the most used personally, and now I keep going to press transwikied article by mistake. Yeah I know, I'm just whining... ARendedWinter 19:03, 5 November 2007 (UTC)
- Haha, I can see what I can do. →AzaToth 19:17, 5 November 2007 (UTC)
Reverting pagemove vandalism
If one reverts a pagemove, one is the only contributor listed in the history, and nominating the page for deletion ({{db-pagemove}}) consequently results in this. Would that be fixable, or should we just revert our own warning every time? --Closedmouth 04:17, 10 November 2007 (UTC)
Speedy deletion and templates
When one tags a template for speedy deletion using twinkle, should it not wrap the notice in <noinclude></noinclude> tags ? Jackaranga 11:34, 10 November 2007 (UTC)
Removing backlinks as minor
When I delete a page, it automatically removes backlinks (which is good, there's nothing wrong with that). However, the act of removing backlinks should be marked as a minor edit. How can I make the edit be marked as minor? -- King of ♥ ♦ ♣ ♠ 20:07, 11 November 2007 (UTC)
- Piggybacking on here, is there a way to have Twinkle remove backlinks when deleting expired prods? --Fabrictramp 20:46, 11 November 2007 (UTC)
- It was deliberate to not remove backlinks for prods, as they easily can be overturned. →AzaToth 21:02, 11 November 2007 (UTC)
SockPuppet Reporting
I used Twinkle to file a sockpuppet case. When I did, it properly created the case, and tagged the user's talk page, but it also tagged their user page with the {{sockpuppeteer}}. I have since received a note from two different admins that I should not have put that tag on that user's page, it is something an admin does and only if the user is indefinitely blocked. If that is something only an admin should do, why did twinkle do it automatically and how do I stop it from happening in the future? Collectonian 15:13, 12 November 2007 (UTC)
- The templates doesn't say that, if the user is blocked, it should be changed to
{{sockpuppeteer|blocked}}
and{{sockpuppet|blocked}}
→AzaToth 15:21, 12 November 2007 (UTC)
Is it possible to have Twinkle check and see if a user name has been reported there already, so that duplicate reports aren't made. I have duplicated reports already made by bots or other users. Thanks!
Gonzo fan2007 talk ♦ contribs 23:51, 9 November 2007 (UTC)
- Good idea since it does that for AIV. - Rjd0060 06:16, 10 November 2007 (UTC)
- H's bot already merges duplicate reports on UAA. east.718 at 22:10, 11/10/2007
- True, for the most part, yet it does not always merge bot reports and user reports, and sometimes it takes a long time. I once went to WP:UAA and saw the same user name reported 3 times!! Since TWINKLE does this for WP:AIV already, how hard would it be to add this in for WP:UAA? Just a suggestion.
Gonzo fan2007 talk ♦ contribs 08:28, 14 November 2007 (UTC)
- True, for the most part, yet it does not always merge bot reports and user reports, and sometimes it takes a long time. I once went to WP:UAA and saw the same user name reported 3 times!! Since TWINKLE does this for WP:AIV already, how hard would it be to add this in for WP:UAA? Just a suggestion.
- H's bot already merges duplicate reports on UAA. east.718 at 22:10, 11/10/2007
Salt
Have updated the salting now, and I've also moved it to User:AzaToth/twinklesalt.js →AzaToth 20:31, 13 November 2007 (UTC)
Problem
Whenever I click any of the tabs (csd, warn, etc.), nothing happens. What's up? The Chronic 23:09, 12 November 2007 (UTC)
- Never mind. Was using IE. Now using Firefox. The Chronic 06:15, 20 November 2007 (UTC)
Error On Page
I put Twinkle in my monobook but whenever I push any tab besides last it says "Error on Page" anyone know how I can fix this. (is it because im using internet explorer and not Mozilla?} Thanks for any help.Sirkad 02:13, 16 November 2007 (UTC)
- Yes. As the front page says, Twinkle is only usable in Firefox. In IE, you'll just get JS errors and none of the tabs and links will work. Collectonian 02:15, 16 November 2007 (UTC)
- Ok, ThanksSirkad 02:21, 16 November 2007 (UTC)
- There is a known workaround for this issue: use Firefox! It's a way better browser. Pyrospirit (talk · contribs) 02:59, 16 November 2007 (UTC)
CSD minor edit?
Is it just me or has TW started marking CSD notices as minor edits? I've already had one person complain on my talk page. ---- WebHamster 23:19, 18 November 2007 (UTC)
- I just did a CSD G12 with TW, and it's not marked as minor.--Fabrictramp (talk) 23:23, 18 November 2007 (UTC)
- Perhaps you ticked "make all edits minor by default" by accident. Jackaranga (talk) 23:28, 18 November 2007 (UTC)
- Not knowingly, and it's only just started happening even though I've been using TW for a while now. ---- WebHamster 23:30, 18 November 2007 (UTC)
- Just checked my preferences and no it isn't ticked. I noticed someone else's CSD edits earlier were also marked as minor. Buggered if I can find who it was now :( ---- WebHamster 23:33, 18 November 2007 (UTC)
- CSDs I've done with Twinkle have been marked minor as well. [1] & [2] for two examples. Collectonian (talk) 01:03, 19 November 2007 (UTC)
- Just checked my preferences and no it isn't ticked. I noticed someone else's CSD edits earlier were also marked as minor. Buggered if I can find who it was now :( ---- WebHamster 23:33, 18 November 2007 (UTC)
- Not knowingly, and it's only just started happening even though I've been using TW for a while now. ---- WebHamster 23:30, 18 November 2007 (UTC)
- Perhaps you ticked "make all edits minor by default" by accident. Jackaranga (talk) 23:28, 18 November 2007 (UTC)
- Twinkle marks CSD tagging as minor be default. You need to change the parameter in your monobook: This is explained here. Also, see my monobook settings, and notice I've changed mine to false:markSpeedyPagesAsMinor : false,
- Just replace the word "true" with "false" on that line, leaving the comma alone. That should do it. - Rjd0060 (talk) 23:00, 23 November 2007 (UTC)
- Yup, that was already in place, there was a semi-colon there though as opposed to a comma. Would that make a difference? --WebHamster 23:11, 23 November 2007 (UTC)
- Looking at your monobook, it isn't there. That other thing with the semi-colon is for page Assessments (not related to twinkle), not CSD. You'll need to add the individual configuration settings to your monobook, which are located here, then just replace that one (and others if you wish). - Rjd0060 (talk) 23:16, 23 November 2007 (UTC)
- You are of course totally correct, and I must have been having a major brain fart (along with a dog mithering for a pee and food). I saw the page assessments script line, saw the word "minor" and the rest is history. I've now
nickedused your settings. Very many thanks for the help, it's mucho appreciated. --WebHamster 23:41, 23 November 2007 (UTC)- No problem! - Rjd0060 (talk) 00:03, 24 November 2007 (UTC)
- You are of course totally correct, and I must have been having a major brain fart (along with a dog mithering for a pee and food). I saw the page assessments script line, saw the word "minor" and the rest is history. I've now
- Looking at your monobook, it isn't there. That other thing with the semi-colon is for page Assessments (not related to twinkle), not CSD. You'll need to add the individual configuration settings to your monobook, which are located here, then just replace that one (and others if you wish). - Rjd0060 (talk) 23:16, 23 November 2007 (UTC)
- Yup, that was already in place, there was a semi-colon there though as opposed to a comma. Would that make a difference? --WebHamster 23:11, 23 November 2007 (UTC)
New templates fully up and running? {{db-csd-notice}} redundant?
As some of you may know, the above template was proposed for deletion by me, concerned about users getting tailored warnings through Twinkle. This resulted in an collaboration to implement tailored warnings for each csd basis; I created multiple new tailored warnings for all necessary csd criteria (listed here) adding to some Azatoth had previously created, Pyrospirit created {{db-csd-notice-custom}} for their use and, as far as I'm aware, Azatoth implemented them all. However, That's really the question; are they all implemented now and it is completely redundant? The reason I ask is that the the TFD resulted in a close which would delete {{db-csd-notice}} as soon as it became redundant, and I was asked to notify the closing administrator once that event ocurred. I do not want to do this prematurely, and I'm not sure it's important in any event, since my concern has already been addressed.--Fuhghettaboutit (talk) 02:06, 21 November 2007 (UTC)
- I think I've updated it. →AzaToth 19:58, 21 November 2007 (UTC)
- I'm pretty sure {{db-csd-notice}} isn't used anywhere now, but just in case it is, we could redirect it to {{db-csd-notice-custom}}. I designed the template so that they use the same parameters in the same order, so there shouldn't be any compatibility issues if it's transcluded somewhere. Pyrospirit (talk · contribs) 20:19, 21 November 2007 (UTC)
- I have redirected per the above (thanks for the feedback) and have informed the closing admin of this thread.--Fuhghettaboutit (talk) 23:53, 23 November 2007 (UTC)
- I'm pretty sure {{db-csd-notice}} isn't used anywhere now, but just in case it is, we could redirect it to {{db-csd-notice-custom}}. I designed the template so that they use the same parameters in the same order, so there shouldn't be any compatibility issues if it's transcluded somewhere. Pyrospirit (talk · contribs) 20:19, 21 November 2007 (UTC)
Does this work with dial up?
I broadband but it does break down, so will this work with my backup dial-up? Just in case. Elassint (talk) 21:41, 21 November 2007 (UTC)
- I had dial up when I first started using Twinkle, and it works just the same, except you get beat to reversions and warnings a lot more often. - Rjd0060 (talk) 22:52, 23 November 2007 (UTC)
Typo
When reporting a user at WP:UAA, Twinkle says "processing UUA request". Jackaranga (talk) 15:05, 18 November 2007 (UTC)
- Yeah all an admin needs to do is edit this to correct it. Oysterguitarist 19:46, 22 November 2007 (UTC)
Cologne Blue and other layout sets
How about other stylesets than Monobook, such as Cologne Blue? Which I'm using. I installed the script and did a deep reload, but nothing seems to have changed. --Bisqwit (talk) 15:30, 27 November 2007 (UTC)
got any advice?
hi could you please give me some advice on clean up? Thanks. Greenjuice4 (talk) 17:08, 26 November 2007 (UTC)
- Cleanup of what? Oysterguitarist 23:08, 29 November 2007 (UTC)
Canceling a Twinkle reversion apparently caused trashing of a page.
In this edit, I had changed my mind about doing a Twinkle reversion and clicked "Cancel" on the confirmation popup. The result was a trashed page. I've fixed the page in subsequent edits. -- Boracay Bill (talk) 05:11, 30 November 2007 (UTC)