Jump to content

Wikipedia talk:XFDcloser

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Yethrosh (talk | contribs) at 13:46, 5 December 2019 (→‎XFDcloser on Urdu WIki). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Shortcut
Possible future features:

These are some features that would be nice to have, but are low priority, may be quite complicated to code, or are otherwise unlikely to be implemented any time soon.

  • For non-admins, make an edit request if a page is protected. [1]
  • When closing as "redirect", remove parameters from the WikiProject talk page templates (so they can auto-categorize) [2]
  • For RfDs, better rcat handling for keep and other non-delete closes – detect existing rcat templates, allow closer to choose to keep/remove/add rcats.
  • More sophisticated handling of old xfd templates: Placement per WP:TPL
  • When opening dialog, check that discussion isn't already closed
  • Multi-relist option when viewing AFD log – checkboxes for each discussion on the log page, click relist once to relist all checked discussions
  • RFD: Remove logpage transclusion if no more discussions are open
  • 'Redirect and fully protect' – just indefinite full protection with a standard "per [link to AFD]" reason
  • CFD: Automated removal of nomination template(s) when closed as keep


"Multiple option" options - no "no consensus"?

light bulb New proposal

Ignoring the duplication of words in the title, is there a reason why "no consensus" isn't included in the "Multiple options" dropdown menus? There have been a few discussions with multiple templates recently where one template gets deleted but there is no consensus on the other, but I can either "keep" or "do nothing" with the latter template. It would be nice to have a "no consensus" option which would also update the pages like the "keep" choice does. Primefac (talk) 01:03, 4 April 2019 (UTC)[reply]

"No consensus" in multi-result closes

When closing Wikipedia:Articles for deletion/Races and creatures in His Dark Materials I've noticed that there is no "no consensus" option when applying several different results to different articles in a bundled AFD nomination. Jo-Jo Eumerus (talk) 12:56, 23 November 2019 (UTC)[reply]

@Primefac and Jo-Jo Eumerus:  Done, "No consensus" is now available in multimode - Evad37 [talk] 10:00, 24 November 2019 (UTC)[reply]
Awesome, thanks! Primefac (talk) 13:27, 24 November 2019 (UTC)[reply]

rcat options hidden when switching from custom

bug   New bug

Just a minor bug: In the interface, when the "custom" close option is first selected, and then if it is changed to "redirect", the option for adding rcats doesn't appear! SD0001 (talk) 18:49, 14 April 2019 (UTC)[reply]

@SD0001: Not quite a bug, just non-intuitive behaviour. When "no automated actions" is selected, the various options are hidden (and can be shown by choosing different "after" action). However, this is unexpected if you're just switching to and then away from a Custom result, so I've changed the default action for Custom closes to "Update pages and talk pages" - Evad37 [talk] 10:04, 24 November 2019 (UTC)[reply]

Add a "mark as closing" button?

light bulb New proposal

It would be nice if the "[Close][quickClose][Relist]" line included as "mark as being closed" button, which would add a {{closing}} template. Sure, you can add the template yourself, but it's enough of an annoyance that I often don't bother, and then get edit conflicted. If it was a one-clicker, I'd be more likely to use it often. -- RoySmith (talk) 15:53, 22 April 2019 (UTC)[reply]

Bug with relisting CfD discussions involving monthly maintenance category

When using XFDcloser to relist a discussion in Wikipedia:Categories for discussion, if the discussion is relisted in a different month that when the discussion was originally started, such as in this edit, the tool also changes the monthly maintenance category the nominated page is in ... which should not happen. In the aforementioned example, the edit change the monthly maintenance category from Category:Categories for discussion from March 2019 to Category:Categories for discussion from June 2019 (March to June). This is problematic because it does not give administrators and discussion closers an accurate picture of how long this discussion has been posted for. I know that there have been issues in the past regarding the community's acceptance of using this tool to relist discussions on CFD; if this cannot be resolved, the functionality on CFD may just need to be disabled again. Steel1943 (talk) 14:56, 7 June 2019 (UTC)[reply]

...bump... Steel1943 (talk) 17:14, 29 October 2019 (UTC)[reply]
@Steel1943: XFDcloser updates the {{Cfd full}} template so the link goes straight to the current discussion, rather than one or more instances of the {{subst:cfd relisted}} relist note. So {{Cfd full}} and Module:Cfd would need to be edited to allow parameters to specify the original listing date, not just the date of the page the discussion is currently on. (Or possibly the script could add the original monthly maintenance category to the page, but that seems messier, and would put the page in multiple monthly maintenance categories) - Evad37 [talk] 01:26, 20 November 2019 (UTC)[reply]

Watchlist

When closing an AfD, the discussion, the article, and any articles edited to remove backlinks are automatically added to my watchlist because I automatically watchlist articles that I edit. This adds large numbers of articles in which I am not interested at all to my watchlist and I have to spend a lot of time to weed them out. Would it be possible to have an option (like Twinkle does) where users can specify whether or not they want edited articles to be added to their watchlists (regardless of which options they have specified for their watchlists)? Thanks. --Randykitty (talk) 16:49, 16 June 2019 (UTC)[reply]

Update to {{Old XfD multi}}

I've recently had some changes made to {{Old XfD multi}} that allow non-AfD discussions to use the page parameters of the template rather than link. This works by not adding the "Wikipedia:Articles for deletion/" prefix to pages with a namespace prefix. The old method for linking to discussions will continue to work, so no update is needed to handle valid nominations (although non-article AfDs using the page parameter may cause issues). However, updating to use this feature will lead to cleaner wikitext, so it's up to you if you want do this. Danski454 (talk) 18:44, 23 August 2019 (UTC)[reply]

Backup editor to maintain this script?

Just wondering ... is there a "backup" editor who either maintains or could maintain this script in the event that Evad37 disappears for long periods of time? Just wondering since this is a frequently-used script, and this is the second time in a couple of months that Evad37 has not edited in almost two weeks. Steel1943 (talk) 22:59, 23 August 2019 (UTC)[reply]

Failure to delete?

Greetings. I'm a non-admin who follows WP:BADAFD to keep an eye on AfD-related items which may need cleanup. Lately I've seen several cases where admins used XFDcloser to delete articles at AfD, but the articles did not in fact get deleted by the script. Recent examples include:

These closes were made by several different admins. In these cases they were only deleted after I db-xfd tagged them myself. In the cases where an associated talk page existed, the script successfully deleted the talk page but not the article itself.

Thank you for your time and programming efforts. --Finngall talk 15:48, 4 September 2019 (UTC)[reply]

Add Adobe Photoshop version history to the list. Article talk page and several redirects were deleted by XfDcloser, but not the page itself. --Finngall talk 04:35, 5 September 2019 (UTC)[reply]

Also:

If XFDcloser fails to delete a page, it should be reporting that error. Or if the page doesn't seem to exists, a warning: "skipped: does not exist (may have already been deleted by others)". Pinging closing admins @Jo-Jo Eumerus, RL0919, Swarm, Sandstein, and Yunshui for the most recent 7 to see if we can work out what's going on.
You guys are waiting for the tasks to be marked as "Done!", right? Or at least coming back to check if there were any errors/warnings?
- Evad37 [talk] 23:59, 22 October 2019 (UTC)[reply]
I do watch for errors and occasionally have to delete manually. But I've deleted over 500 hundred pages since 18 September, which probably corresponds to a couple hundred closures (allowing that some closures result in multiple pages deleted, but others involve no deletion), so I'm not shocked if I have missed some. Maybe the script failed to flag them, but I wouldn't have any confidence in that theory. I'll try to watch more closely and alert you if there are any that fail without an error message. --RL0919 (talk) 03:43, 23 October 2019 (UTC)[reply]
New: Hound (Transformers) --Finngall talk 18:15, 29 October 2019 (UTC)[reply]
I had at least two deletion failures since the 23rd, but the script presented the errors. If there were any without a visible error message, I haven't noticed it yet. --RL0919 (talk) 18:49, 29 October 2019 (UTC)[reply]
List of Foundation universe planets. Should I continue listing these? --Finngall talk 17:45, 31 October 2019 (UTC)[reply]

With the latest update, the script now retries a second time if the initial delete attempt fails. I'm hoping that will make this issue occur less frequently. - Evad37 [talk] 06:38, 1 November 2019 (UTC)[reply]

At the risk of being annoying a new one: Pyras Technology. --Finngall talk 17:36, 14 November 2019 (UTC)[reply]
@Finngall: I've been watching for this for three weeks now (almost 700 page deletions). Although it does occasionally fail to delete a tagged page, I have not seen it do so without giving an error message. This doesn't happen often; I'd guess about 1% of the time. A 100% success rate at scripted deletion is too much to expect, so I'm happy with the tool as long as the rare failures produce a visible error that I can then act to correct. I can't be sure, but I continue to suspect you are finding occasional mistakes by admins who have not noticed the error message, rather than non-visible script failures. In terms of development suggestions, I will say that if a user chooses to remove backlinks, sometimes there are a very large number of messages related to those. This can distract from the far more important message about not deleting the nominated page. If there is a way to more clearly emphasize the deletion failure, that might help. --RL0919 (talk) 21:50, 14 November 2019 (UTC)[reply]

Another feature request: WP:INVOLVED warnings.

I close a lot of AfDs and don't always remember if I've commented on them before (which would make me ineligible to close it). I usually search for my signature before closing to make sure, but sometimes I forget to do that. I once (somewhat harshly, which I regret) took somebody to task for closing an AfD they had participated in and it turned out to be exactly the same thing; they had innocently forgotten their earlier involvement. It would be cool if XFDcloser could examine the XfD edit history and note somehow that you've already been involved. -- RoySmith (talk) 15:06, 4 October 2019 (UTC)[reply]

@RoySmith: Hey, aren't you supposed to be reading the xfd to determine the consensus before closing it? How would you miss your own !vote if you do that? SD0001 (talk) 07:30, 6 October 2019 (UTC)[reply]
Sure, but having this would be a safety feature to prevent accidents. It would also save time; it's annoying to spend time reading through a long discussion, only to find a comment by yourself that you'd long forgotten about. It's not a huge thing, just a "nice to have". -- RoySmith (talk) 14:27, 6 October 2019 (UTC)[reply]
I could imagine this happening in a case where there are, say, 5 or more participants who all !vote either "keep" or "delete". Not really necessary here to waste time on reading all arguments in detail, as the outcome is pretty clear. And an admin who does a lot of editing may have forgotten that they already !voted themselves and even though the outcome is clear, it is not appropriate for them in that case to close the AfD. It will be rare, but I can see it happen. --Randykitty (talk) 14:51, 6 October 2019 (UTC)[reply]
Sometimes there are AfDs in which all the keep or delete comments are not within policy. We can't close as keep or delete against the consensus vote (as that would be a supervote, given that the relevant policy based argument has not been brought up), but we can leave our own keep/delete comment pointing out the relevant policy so the next admin to come along can do the appropriate thing. We do more than just count the !votes, otherwise a bot could close AfDs. If it's too much of an effort to read all the comments, no worries, just leave it and go to the next AfD. There is no pressure on any of us to close an AfD, and we shouldn't be closing an AfD if we haven't read the arguments. There are some of us who do go though the old AfDs to close the tricky ones that require a lot of reading. I don't mind doing that. Indeed, I do that rather than close the easy ones, as it's the tricky ones that I find more interesting and satisfying. The great thing about this being an open wiki, is that there is a task for everyone, so nobody need feel under pressure to do something they don't want to. SilkTork (talk) 10:29, 28 November 2019 (UTC)[reply]

Rename option for CfD

Hi, I was wondering if it's possible to add a rename option to the possible default results. This would be equivilent to using the custom option with the text "Rename". ‑‑Trialpears (talk) 23:04, 4 November 2019 (UTC)[reply]

Gadget now available

XFDcloser is now available as a gadget! Visit Special:Preferences § Gadgets and scroll down to the "Maintenance and administration" section to find it. Just remember to remove the line importScript('User:Evad37/XFDcloser.js');, or importScript('User:Mr.Z-man/closeAFD.js');, from your common.js (or skin-specific js such as vector.js, monobook.js, etc), otherwise XFDcloser will load twice.

The gadget version should be faster, more bandwidth-efficient, and more maintainable (see the archived gadget proposal discussion). - Evad37 [talk] 00:00, 15 November 2019 (UTC)[reply]

I had some difficulty closing an AfD using XFDcloser

Hey. I just closed the AfD Wikipedia:Articles for deletion/List of scientists who disagree with the scientific consensus on global warming using the XFDcloser. It was frankly a bit unnerving. I was repeatedly warned that it had not yet been seven days since the article was listed, though it had (admittedly not by much of a margin). In the end, I overrode the warning and went ahead and closed anyway, but it didn't do anything for my nerves. :-( Then there were a lot of redirects and backlinks to delete — really a lot — and I had to answer many many questions about them. I hope I did that all right. But the remaining problem is that XFDcloser couldn't or wouldn't delete the article's talkpage; I got the message "API error: bigdelete — could not delete page". Am I supposed to do something about that? Bishonen | talk 21:51, 19 November 2019 (UTC).[reply]

The talk page is 200k and has more than 5k revisions, which means a steward likely has to delete it. It will need to be manually deleted, but normally XFDC can handle it. The warnings are intentional, because when the template first came out there were a lot of misclicks and so we asked for more checks before "pulling the trigger". Primefac (talk) 21:54, 19 November 2019 (UTC)[reply]
OK — so who should ask a steward to delete the talkpage? Would that be me? Bishonen | talk 22:15, 19 November 2019 (UTC).[reply]
I'm chatting with some on IRC. Primefac (talk) 22:29, 19 November 2019 (UTC)[reply]
Oh, that's good. Somebody just tagged the talkpage for speedy. I was going to remove that, but if you've already hooked a steward, there's probably no need. Bishonen | talk 22:34, 19 November 2019 (UTC).[reply]
@Bishonen: Done by me, but there’s plenty of subpages left: Special:PrefixIndex/Talk:List of scientists who disagree with the scientific consensus on global warming. Regards --Schniggendiller talk 22:41, 19 November 2019 (UTC)[reply]
D-batched. Thanks for taking care of the talk page, Schniggendiller. Primefac (talk) 22:43, 19 November 2019 (UTC)[reply]

Adding stuff to watchlist?

This is something I've seen often. Sometimes, when I close the AfDs as keep or merge, the script adds the articles to my watchlist automatically. This is probably a bug? --Tone 08:59, 26 November 2019 (UTC)[reply]

Limits on closing bundled nominations with too many nominations?

Just wondering ... what is the limit for how many entries in a discussion can be closed at once with XFDcloser, specifically for WP:RFD? Just wondering because I just attempted to close a discussion with 67 entries on WP:RFD, and it would not remove/close the tags on each individual redirect since apparently 67 was too many. Steel1943 (talk) 04:26, 28 November 2019 (UTC)[reply]

50 is the limit, as that keeps the API queries relatively simple, and XfDs with that many pages aren't too common. - Evad37 [talk] 05:09, 28 November 2019 (UTC)[reply]

"Soft delete" rationale at AfD

The default soft delete rationale in the tool's AfD closure should probably reference WP:SOFTDELETE. Instead of "WP:REFUND applies", thoughts on this alt default text?

Based on minimal participation, this uncontroversial nomination is treated as an expired PROD (a.k.a. "soft deletion"). You can request the article's undeletion.

czar 08:11, 29 November 2019 (UTC)[reply]

Referring to "you" in the closing rationale doesn't quite feel right to me... perhaps Undeletion may be requested at Wikipedia:Requests for undeletion. for the second sentence? - Evad37 [talk] 08:54, 30 November 2019 (UTC)[reply]
To avoid the passive voice and redundancy ("request" twice), how about Editors can request the article's undeletion. or alternatively, to show the link, but clunkier, Visit Wikipedia:Requests for undeletion to restore the article. I'm also realizing that we could potentially just link directly to the RFU preload and fill in the name/reason parameters... That's a better experience for someone requesting restoration but perhaps not enough friction if they should be reading about how the process works first? If we're serious about PROD being easy to reverse, I think it'd be a good move. Thoughts? czar 18:57, 30 November 2019 (UTC)[reply]
Less redundancy is better. The preload idea is definitely feasible. And because of the way the preloading works, we can create and use versions of Wikipedia:Requests for undeletion/Intro and Wikipedia:Requests for undeletion/Example that are specific to soft deletion. - Evad37 [talk] 02:50, 1 December 2019 (UTC)[reply]

Exclude Wikipedia:Articles for deletion/Common outcomes

Showing [Close] [Relist] on an informational page's headings czar 17:11, 29 November 2019 (UTC)[reply]

 Done. It's actually a regex rather than a list, but still relatively easy to add exceptions. Moving the Common outcomes pages to subpages of WP:Common outcomes is still an interesting idea, but should be discussed in a broader forum than this talk page. - Evad37 [talk] 03:18, 1 December 2019 (UTC)[reply]

FfD double relist error

[3] fyi @Jo-Jo Eumerus czar 08:27, 1 December 2019 (UTC)[reply]

And the matching diff from the old log page: [4]. Not too sure what caused this to happen yet. - Evad37 [talk] 09:39, 1 December 2019 (UTC)[reply]
I was unable to reproduce using a sandbox copy of the November 21 log page [5][6] - Evad37 [talk] 10:04, 1 December 2019 (UTC)[reply]
I admit that I am not sure what exactly went awry. Jo-Jo Eumerus (talk) 10:32, 1 December 2019 (UTC)[reply]

XFDcloser on Urdu WIki

Urdu wikipedia just installed XFDcloser, copying from en.wp. Now gadget works properly on XFD venues, but some features do not work. 1) It does not delete pages after closing discussion by admins. 2) Relisting feature does not work at all. 3) And after closing discussion, Gadget does not update article and talk pages (core gadget is here). Any help would be highly appreciated, Thanks. Muhammad Shuaib (talk) 17:57, 1 December 2019 (UTC)[reply]

@Muhammad Shuaib: Do the task names you defined in the Task class constructor (lines 3665 to 3732) show up? And are there any errors shown, either on the screen or in the console (see item 6 of WP:JSERROR)? - Evad37 [talk] 01:49, 2 December 2019 (UTC)[reply]
Yes, they are shown up. I think relisting fails because log page does not exist. When I try to relist closed discussion it throws "discussion has been closed", and aborted.
And No, there are no errors on screen nor on console. Now I came to know that "Redirect" is also not working. Muhammad Shuaib (talk) 03:33, 2 December 2019 (UTC)[reply]
@Evad37: Any assistance? It will not delete pages as well. Muhammad Shuaib (talk) 06:52, 5 December 2019 (UTC)[reply]
@Muhammad Shuaib: I'm really not sure. Without any visible or console errors, its hard to determine why it isn't working. Does the userscript version at ur:User:محمد شعیب/XFDcloser.js work? - Evad37 [talk] 06:58, 5 December 2019 (UTC)[reply]
No this version also does not work. Could you please check using this link? Muhammad Shuaib (talk) 13:46, 5 December 2019 (UTC)[reply]

How to handle "closing" templates

Is it possible to have XFDCloser remove a {{closing}} template when closing a discussion? I've noticed on Wikipedia:Articles for deletion/I'm a Celebrity...Get Me Out of Here! (British series 1) that it leaves these templates in. Jo-Jo Eumerus (talk) 09:47, 3 December 2019 (UTC)[reply]

@Jo-Jo Eumerus: Yes, it should already do so, but the template needs to be placed under the section heading rather than the top of the page (and the same for {{AfDh}} and {{AfDb}}). - Evad37 [talk] 02:56, 4 December 2019 (UTC)[reply]

Failed removal of list entries

I've noticed a couple of cases where the delinking function prompted me about keeping or removing a list entry, I said to remove it, but it was not removed. The entry is delinked, but still on the list. I think this happened with List of accidents and incidents involving commercial aircraft when I closed Wikipedia:Articles for deletion/Air China Flight 818. Another editor subsequently removed the entry and pinged me about it, so I started paying closer attention. It definitely happened on List of rifle cartridges when I closed Wikipedia:Articles for deletion/.70-150 Winchester. There was no error message that I noticed in either case. --RL0919 (talk) 21:34, 4 December 2019 (UTC)[reply]

@RL0919:  Fixed. I made a typo a month ago while updating the code to prevent edit conflicts, and this resulted in links only being unlinked, and no item removals. Edits in which the closer intended to remove a list item (or items) can still be identified by having the edit summary "Removing link(s) / list item(s)" and not being a minor edit. - Evad37 [talk] 03:00, 5 December 2019 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:XFDcloser&oldid=929384265"