![]() | This is an archive of past discussions. 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 1 | ← | Archive 3 | Archive 4 | Archive 5 | Archive 6 |
When closing Wikipedia:Redirects for discussion/Log/2021 January 2#Akira (2009 film), I got the below error and had to add the talk page template manually.
TypeError: date.getUTCDate is not a function error: could not edit page Talk:Akira (2009 film)
fwiw, this followed a pop-up indicating that adding the Old RfD template would overwrite a redirect, though apparently Talk:Akira (2009 film) was not a redirect? It also threw an error rather than passing me the template code to add myself.
Not sure if related, but XFDC also didn't redirect to the section I specified in the form Akira (planned film)#Film rights and conception. Instead it just dropped the section and redirected to the article itself. czar 21:37, 2 January 2021 (UTC)
It also threw an error rather than passing me the template code to add myself– that's because the error occurred while trying to create the wikitext (template code) for the talk page. - Evad37 [ talk 09:15, 20 January 2021 (UTC)
{{ resolved}}
{{ resolved}}
Unlinking after deleting an article and got a prompt to process a bulleted link in the section "List: LA}}LA Giltinis", referring to
List of 2020–21 Major League Rugby transfers § LA Giltinis but struggling with the section heading, which contains an anchor tag: =={{anchor|LA}}LA Giltinis==
czar 21:50, 25 December 2020 (UTC)
{{ resolved}}
Both when loading the closer on the daily AfD page and after the AfD closes, I'm losing my place often with the beta when I generally want to refer to the discussion I was reading. There appears to be some page resituating when the closer is first loaded. And when the AfD is closed, v3 had more visual indication of the closed action, like it was easier to tell which one I just closed and where, if I scrolled through the page and looked at a glance. If there was some way to change the background of the section or otherwise indicate which discussions have been addressed, would help contextualize the change. czar 21:50, 25 December 2020 (UTC)
{{ resolved}}
It would be great if the beta XFDcloser defaulted to using Wikipedia:XFDcloser/Soft deletion rationale when closing as 'soft delete' Eddie891 Talk Work 17:55, 16 January 2021 (UTC)
{{ resolved}}
ProcrastinatingReader ( talk) 13:23, 23 January 2021 (UTC)
Received this in my watchlist:
Mai Minokoshi diffhist -4 Spartaz talk contribs Removing link(s): Wikipedia:Articles for deletion/Cinema Today closed as delete (XFDcloser) rollback
Doesn't make sense, as one article has nothing to do with the other. Regards,
GenQuest
"Talk to Me" 07:42, 7 June 2020 (UTC)
{{ User:ClueBot III/ArchiveNow}}
I keep getting spammed by this entity with a pop-up ad that says "Hey its now a gadget, here's how to enable that". Well I did that, and the ad keeps popping up anyway. What's more, there's not even an X to close the pop-up window, and I haven't figured out a way to do that -- I have to leave the page, which impacts my productivity. Is there any way to make this stop? Herostratus ( talk) 14:35, 21 June 2020 (UTC)
{{ User:ClueBot III/ArchiveNow}}
When closing as 'redirect', it would be cool if the tool auto-changed the assessed class to 'redirect'. Just a thought. Eddie891 Talk Work 23:05, 17 November 2020 (UTC)
{{ resolved}}
In the past, I've been able to close multiple AfDs at once, which is especially useful when one is taking a while to unlink. Doesn't look like a second instance loads in v4. czar 21:50, 25 December 2020 (UTC)
{{ resolved}}
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)
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)
{{ resolved}}
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)
{{ resolved}}
I'd like:
to both be changed either to
or
Reason: more explanatory and word-flowy. Also we don't put a period after deleting a talk page when the associated page is deleted per PROD/CSD, and we should explain what reason to delete redirects AFD or not, not bring up what is already happening in our eyes. (Disclaimer: Fat (song) is a placeholder and that AFD is actually a run-of-the-mill April Fools joke. ミラ P 04:13, 26 December 2019 (UTC)
{{ resolved}}
I know this has been discussed before somewhere, but I just couldn't find the discussion. Doing the usually automated actions of removing nom-templates and adding {{ old cfd}} takes quite a lot of time and really should be automated here as well. It looks like a lot of ground work is done for these features with old cfd formatting and nom-template regexs appearing in the source code so is there and I don't really see anything that different about CfD compared to other venues in this area. What would happen if the code handling CfD in basic mode was removed? -- Trialpears ( talk) 21:44, 11 July 2020 (UTC)
{{ resolved}}
I don't quite see what that void subst-ing is being used for in this script, but since subst-ing doesn't work inside references it results in this string appearing in articles, see here and here. Not a very common problem, I've just fixed about 20 instances of this, but maybe this can be avoided. – Thjarkur (talk) 16:44, 27 July 2020 (UTC)
{{ resolved}} In my More tab XFDC Prefs appears (and I can access those), but I can no longer see/use the tool. I have not knowingly changed anything. Thoughts, please? Ping me on answers, or I may miss it. FiddleTimtrent FaddleTalk to me 11:37, 20 June 2021 (UTC)
{{ resolved}} I wish to withdraw my nomination from an AfD. I am trying to use my XFD closer. But the only button I have for this is "xfdc preferences." When I click on that I don't get the box that asks me to choose what kind of close. Instead I see something about enabling Beta version, add edited pages to my watchlist, collapse task warnings if at least:, and collapse task errors if at least. Is the xfd closer malfunctioning or is my particular closer malfunctioning? I am unable to close this AfD using the XfD closer. --- Steve Quinn ( talk) 21:01, 10 August 2021 (UTC)
If someone wants to look at the page, here is the AfD [1]. I am not interested in having the AfD closed. I am interested in having my XFD closer work. Thanks. --- Steve Quinn ( talk) 21:10, 10 August 2021 (UTC)
{{ resolved}} I can't currently use the script because the text fields for the result and the rationale don't show up. Screenshot: https://imgur.com/a/i6Z1WOW. I'm using the current Chrome browser on Windows 10. Sandstein 11:18, 21 January 2022 (UTC)
Investigating now. My suspicion is a breaking change to mw:OOUI. (Please continue to ping me and/or leave talk page messages when reporting urgent issues, or if I'm taking a long time to reply. My watchlist is too big to be useful given that I'm less active then I used to be.) - Evad37 [ talk 01:13, 22 January 2022 (UTC)
{{ resolved}} I'm seeing an admin use XFDcloser to remove links from deleted articles that are not deleted through XFD discussions. How is that possible? I'd like to find a tool to use to do that but reading over the tool page, I don't see how XFDcloser can be used to remove links from articles deleted through PROD or CSD. I'd appreciate any information anyone familiar with the tool can provide. Many thanks. Liz Read! Talk! 00:34, 2 May 2022 (UTC)
{{ resolved}} See this. It should have an exception for this. Piotr Konieczny aka Prokonsul Piotrus| reply here 02:59, 18 August 2022 (UTC)
{{ resolved}} Hello, all,
I'm having no luck with XFDcloser closing AFD nominations where there are a lot of articles bundled together. These have been nominations proposed by different editors so I know it isn't just one person not understanding how to do this. XFDcloser deleted the primary, first article mentioned in the nomination and ignores all of the articles listed (sometimes they are hatted, sometimes they are not). This requires a manual deletion of sometimes dozens of separate articles which can be a little time-consuming. Or, you can make a huge blunder, like I did last night, and try to batch delete them using Twinkle and end up with a huge mess to clean up. That's a mistake you only make once.
What do you think might be the problem here? Is it XFDcloser or is it the way that the bundled nomination is formatted that XFDcloser can't "see" all of the other articles that are proposed for deletion? I've discussed this with the nominators and maybe there just has to be a better explanation in the instructions for bundled nominations. Thanks for any ideas you can offer. Liz Read! Talk! 21:27, 21 August 2022 (UTC)
{{ resolved}} Hello, XFDCloser
The daily deletion log pages are not loading correctly. But it's not a good sign though that apparently the maintainer, Evad37, is inactive. There should really be a backup contact person as when the systems fail, they seem to fail spectacularly and affect the work of a lot of editors. Help! Liz Read! Talk! 01:29, 1 January 2023 (UTC)
not loading correctly- what do you mean? Primefac ( talk) 13:08, 1 January 2023 (UTC)
{{ resolved}} Add a delete button when closing a discussion, instead of having to add manually via the custom button. Preferably put it after the third tab/button, "soft redirect". Qwerty284651 ( talk) 02:58, 2 February 2023 (UTC)
{{ resolved}} I have the ability to close as a "regular" delete, but no option to soft-delete. Running on Chrome. Joyous! | Talk 19:59, 12 February 2023 (UTC)
![]() | This page is an archive of past discussions. 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. |
I've opened multiple AfD pages in the last 15 minutes, using two different browsers on different devices, but XFDCloser doesn't appear to be loading on any of them. No close/relist links, and or the option to show/not show closed discussions. I've not had this problem previously. RL0919 ( talk) 06:59, 22 January 2024 (UTC)
mw.util.addPortletLink ( 'p-tb', "javascript:importScript('MediaWiki:Gadget-XFDcloser-core.js')", 'Load XFDCloser', 'pt-loadxfdc', 'Manually loads XFDCloser');
Uncaught Error: inheritClass: Origin is not a function (actually undefined)
at OO inheritClass (oojs.js:85:9)
at 164.../../globals (<anonymous>:21:126600)
at o (<anonymous>:21:254)
at <anonymous>:21:288
at 170.../../globals (<anonymous>:21:145875)
at o (<anonymous>:21:254)
at <anonymous>:21:288
at 225.../../globals (<anonymous>:21:469338)
at o (<anonymous>:21:254)
at <anonymous>:21:288
Parse error: Unexpected: ( on line 21
css @ ext.gadget.XFDcloser-core-beta-script-0.js:24
runScript @ startup.js:1275
(anonymous) @ startup.js:1353
flushCssBuffer @ startup.js:606
requestAnimationFrame (async)
addEmbeddedCSS @ startup.js:637
execute @ startup.js:1367
doPropagation @ startup.js:757
requestIdleCallback (async)
setAndPropagate @ startup.js:830
impl @ startup.js:2009
(anonymous) @ load.php?lang=en&modules=ext.gadget.XFDcloser-core-beta&skin=monobook&version=1t9io:1
Extended content
|
---|
(Large block of minified code, removed as not relevant) |
/* jshint esversion: 5, esnext:false, laxbreak: true, undef: true, eqnull: true, maxerr: 3000 */
and here's line 24: (function(){
voorts (
talk/
contributions) 23:38, 19 February 2024 (UTC)
MediaWiki:Gadget-XFDcloser-core-beta.js. Clicking on the source mapping, it takes me to load.php?lang=en&modules=ext.gadget.XFDcloser-core-beta&skin=monobook&version=1t9io which contains this function:
mw.loader.impl(function() {
return ["ext.gadget.XFDcloser-core-beta@1svn5", function($, jQuery, require, module) {
mw.log.error("Parse error: Unexpected: ( on line 21");
}
, {
"css": [".xfdc-status{font-size:small;margin-left:13px;font-weight:normal}.skin-timeless .xfdc-status{font-size:0.98rem}.skin-minerva .xfdc-status{font-size:0.98rem;display:block;margin:-1rem 0 1rem}.xfdc-action{font-weight:normal}.xfdc-action a{cursor:pointer}.xfdc-qc-cancel{cursor:pointer;border:1px solid #777;border-radius:10px;font-weight:bold;font-size:90%;color:#777;padding:0;margin:0 1px} .xfdc-old .xfdc-action{background-color:#c6ffc6}.xfdc-notOld .xfdc-action{background-color:#ffc6c6}.xfdc-unknownAge .xfdc-action{background-color:#ffffc6}.xfdc-notOld.xfdc-relisted .xfdc-action{background-color:#ffe9c6} .xfdc-actioned-heading{text-decoration:line-through double black;opacity:75%}.xfdc-actioned-discussion{opacity:50%} html body.ooui-draggbleWindow-open{position:unset;overflow:unset;margin-right:unset !important; }html body.ooui-draggbleWindow-open .oo-ui-windowManager-modal \u003E .oo-ui-dialog.oo-ui-window-active{position:static;padding:0} html body.ooui-draggbleWindow-open .oo-ui-dialog.oo-ui-window-active \u003E div{z-index:110;transition:all 0.25s ease-out 0s,transform 0s !important} .oo-ui-textInputWidget.oo-ui-textInputWidget-labelPosition-before.padLeft2em .oo-ui-inputWidget-input{padding-left:2em !important}.oo-ui-textInputWidget.oo-ui-textInputWidget-labelPosition-before.padLeft4em .oo-ui-inputWidget-input{padding-left:4em !important} .xfdc-menuOptionWidget.oo-ui-decoratedOptionWidget{padding:7px 12px} .xfdc-taskItemWidget \u003E .oo-ui-fieldLayout-messages{clear:both} #XFDcloser-showhide{bottom:0;display:block;position:fixed;right:0;z-index:100;padding:5px;box-shadow:0 2px 4px rgba(0,0,0,0.5);background-color:#fef9e6;border:1px solid #aaa;border-radius:5px;font-size:85%}"]
}];
});
// Saved in localStorage at 2024-02-12T22:09:25.448Z
//# sourceURL=https://en.wikipedia.org/w/load.php?lang=en&modules=ext.gadget.XFDcloser-core-beta&skin=monobook&version=1t9io
//# sourceMappingURL=/w/load.php?lang=en&modules=ext.gadget.XFDcloser-core-beta&skin=monobook&sourcemap=1&version=1t9io
Not sure how helpful this is, but I'll collect any additional data you need. The Wordsmith Talk to me 20:46, 19 February 2024 (UTC)
Parse error: Unexpected: ( on line 21. That might have an error message that could be further debugged. – Novem Linguae ( talk) 23:29, 19 February 2024 (UTC)
Anybody else not seeing "[Close] [quickClose] [Relist]" and getting "Parse error: Unexpected: ( on line 21" in console? Seems to be happening on every XfD page. I tried disabling all gadgets except XFDcloser and still got it. The console says it's coming from ext.gadget.XFDcloser-core-script-0.js:24:1 (not 21!), which is not helpful. Works on every other skin and, worse, in debug mode. Nardog ( talk) 17:35, 8 February 2024 (UTC)
mw.loader.impl(function(){return"ext.gadget.XFDcloser-core@30cwo",function($,jQuery,require,module){mw.log.error("Parse error: Unexpected: ( on line 21");
},{"css":".xfdc-status{font-size:small;margin-left:13px;font-weight:normal}.skin-timeless .xfdc-status{font-size:0.98rem}.skin-minerva .xfdc-status{font-size:0.98rem;display:block;margin:-1rem 0 1rem}.xfdc-action{font-weight:normal}.xfdc-action a{cursor:pointer}.xfdc-qc-cancel{cursor:pointer;border:1px solid #777;border-radius:10px;font-weight:bold;font-size:90%;color:#777;padding:0;margin:0 1px} .xfdc-old .xfdc-action{background-color:#c6ffc6}.xfdc-notOld .xfdc-action{background-color:#ffc6c6}.xfdc-unknownAge .xfdc-action{background-color:#ffffc6}.xfdc-notOld.xfdc-relisted .xfdc-action{background-color:#ffe9c6} .xfdc-actioned-heading{text-decoration:line-through double black;opacity:75%}.xfdc-actioned-discussion{opacity:50%} html body.ooui-draggbleWindow-open{position:unset;overflow:unset;margin-right:unset !important; }html body.ooui-draggbleWindow-open .oo-ui-windowManager-modal \u003E .oo-ui-dialog.oo-ui-window-active{position:static;padding:0} html body.ooui-draggbleWindow-open .oo-ui-dialog.oo-ui-window-active \u003E div{z-index:110;transition:all 0.25s ease-out 0s,transform 0s !important} .oo-ui-textInputWidget.oo-ui-textInputWidget-labelPosition-before.padLeft2em .oo-ui-inputWidget-input{padding-left:2em !important}.oo-ui-textInputWidget.oo-ui-textInputWidget-labelPosition-before.padLeft4em .oo-ui-inputWidget-input{padding-left:4em !important} .xfdc-menuOptionWidget.oo-ui-decoratedOptionWidget{padding:7px 12px} .xfdc-taskItemWidget \u003E .oo-ui-fieldLayout-messages{clear:both} #XFDcloser-showhide{bottom:0;display:block;position:fixed;right:0;z-index:100;padding:5px;box-shadow:0 2px 4px rgba(0,0,0,0.5);background-color:#fef9e6;border:1px solid #aaa;border-radius:5px;font-size:85%}"]}];});
vector
to
vector-2022
or
monobook
or
remove &version=m2csj
, you get the whole script with no errors. This suggests something is wrong with the validation and/or the server caching. @
SD0001: Do you have a clue why this is?
Nardog (
talk) 10:54, 9 February 2024 (UTC)
I've got good news. phab:T359014 patch is written and merged, and will be deployed soon. This will likely fix this bug. May take a week to deploy though. Feel free to check the phab ticket for updates. – Novem Linguae ( talk) 20:12, 6 March 2024 (UTC)
The [Close] option is not appearing on AfD, CfD, FfD, or TfD discussions for me. I'm using Firefox 122.0.1 (64-bit) to browse, vector-2022 with dark mode, and these userscripts. voorts ( talk/ contributions) 19:17, 19 February 2024 (UTC)
{{ resolved}} I just noticed a new bug with XFDcloser: It now seems that on some pages of RFD where there are closed discussions, XFDcloser Now completely hides some of these discussions. This is quite problematic because it makes it so closed discussions cannot be reviewed; In fact, sometimes, this problem will make it so the evidence of a discussion even existing on that subpage is hard to find, unless one looks through the table of contents (provided one even shows up) or edits the page. Steel1943 ( talk) 14:24, 28 April 2024 (UTC)
Did you have closed discussions hidden?" Yes, and I don't know when I clicked that thing since it's in a really inconspicuous spot. Dang it XFDcloser. Steel1943 ( talk) 15:11, 28 April 2024 (UTC)
I am writing up a close for a TFD, and while writing I used a {{ tq}} for a quote. In the preview box it (for some reason) triggers the {{ FormattingError}} in the template ("Template:Tq is only for quoting in talk and project pages. Do not use it in actual articles."), but that's only triggered when the template is used in the article space (NS0). Why would this script, when previewing the content, make the template think that it's in the mainspace? If the answer is "who knows" that's totally fine (I can still read what I wrote in the edit box!) but I'm curious is there's a line of code somewhere that might be making the environment think that the preview is in ns0. Primefac ( talk) 11:20, 30 August 2021 (UTC)
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)
The script doesn't detect the bundled articles in this nom (just tested in sandbox) czar 19:04, 5 December 2019 (UTC)
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)
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)
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)
This has probably been brought up before, but just curious: Any chance this script can be configured to also handle closing WP:RM requests? Steel1943 ( talk) 16:21, 20 December 2019 (UTC)
Hi. A while ago I closed a discussion as delete but it looks like the script failed to delete (and I failed to notice it, but someone pointed it to me and deleted the page afterwards). Links: the MfD page, and the page itself: Talk:IQ classification/Archive 1 (which exists, again, because it was recreated as a move from some other page). Maybe the script does not like to delete "Talk:.*", or "Talk:.*/.*", pages? Thanks! - Nabla ( talk) 15:59, 17 February 2020 (UTC)
Hi. A (very low priority) suggestion. Is it possible to add a link to the retargeted to page when closing a RfD as retarget? I like to add it, because I think it is important information about the closure, I do not know if it is common enough, and wanted enough, to be worth the effort; but as it probably is not a huge effort, you already have all the info, it is probably "only" adding it to one string. See a example diff. - Nabla ( talk) 16:05, 17 February 2020 (UTC)
Noting there's a suggestion at [3] that XFDcloser should handle closing of WP:Deletion review discussions, including adding {{ olddelrev}} to talk pages as appropriate - Evad37 [ talk 00:45, 26 February 2020 (UTC)
It would be useful if all the automated actions associated with closing an AfD as delete could be logged, probably to the article's talk page (and creating one if necessary). That way, if the deleted article is ever restored, you'd have a record of what incoming links had been removed, making it easier to restore them. It's probably not possible to fully automate the restoration process (even if the log was machine parsable), but at least having a human-readable log would be useful.
Hmmm, as I'm writing this, it occurs to me that the information actually already exists. It should be possible to datamine the deleting user's contribution log to discover this. I need to think on that. -- RoySmith (talk) 15:39, 26 February 2020 (UTC)
When deleting redirects to other deleted pages, XFDcloser incorrectly handles redirects that are currently at
RFD. Rather than deleting those as well, it simply removes the link so that the pages look like this: "[
Template:rfd, which for technical reasons shouldn't be transcluded]
#redirect Foo"
This is obviously not desirable, so can it be fixed? (I don't know precisely how XFDC works, so excuse any errors in that department.)
Glades12 (
talk) 10:57, 25 February 2020 (UTC)
#REDIRECT [[Article]]
line within the RFD template is changed to #REDIRECT Article
Could the procedure for non-administrator close (nominator withdrawal) be added as an option?-- Goldsztajn ( talk) 12:13, 12 March 2020 (UTC)
I've noticed that when re-listing files at FfD ( example), the "delete" link is not updated to the current listing's date. Could this please be fixed? Thanks, FASTILY 03:35, 22 April 2020 (UTC)
Looks like this example came up in the unlinker/delinker. If possible, would be nice to add these cases to be excluded from the logic that asks whether the line should be removed. czar 11:56, 26 May 2020 (UTC)
I would like to know how this gadget can be used in other Wikis. Will it only require importing MediaWiki:Gadget-XFDcloser.js to the target wiki? Adithyak1997 ( talk) 10:33, 1 June 2020 (UTC)
User:Evad37, It would be great to have a "do not merge" option for merge discussions. Right now, I use "custom" with "do not merge" as the result and then I subsequently edit the talk pages to add the |merge=
or |mergeX=
parameter to the XFD result template. For example,
here and
here. Thanks for script/gadget, its been big timesaver.
Plastikspork
―Œ(talk) 14:11, 4 June 2020 (UTC)
If I'm not mistaken, XFDcloser only adds {{ Old AfD multi}} etc. if the page is kept. But the template is also useful (perhaps more useful) for recording when a page is deleted at XfD and subsequently recreated. Would it be possible to get the gadget to add the old XfD templates to the talk page immediately before it is deleted? – Joe ( talk) 12:14, 12 June 2020 (UTC)
I closed AfDs for the first time in a while today, and the script keeps skipping the "unlinking backlinks" step, saying that I've cancelled it, when I haven't. Is this a bandwidth issue? Because it doesn't happen every time...or is it something else? Vanamonde ( Talk) 16:25, 20 July 2020 (UTC)
I recently closed the RfD associated with the redirect Software Entertainment Company using XFDcloser. However, when I did so, it did not recognize the RfD template in this revision. Because of that, XFDcloser claimed there was no RfD template on the redirect, and did not remove the template from the redirect. (Of course, I ended up removing the template manually.) I'm assuming the issue is related to the template the Page Curation tool uses to tag pages for RfD, which seems to be {{ Rfd-NPF}}. Steel1943 ( talk) 00:23, 30 August 2020 (UTC)
Consider this scenario:
XFDcloser will disallow this close, saying "Non-admin closure is not appropriate when the result will require action by an administrator (per WP:BADNAC)". We should adjust it to allow non-admins to choose the "delete" reason if the page in question is already deleted. Jackmcbarn ( talk) 21:50, 10 August 2020 (UTC)
This issue has been raised before. Perhaps the non-admin view should have a little note saying to use the custom close option if a page has already been deleted. - Evad37 [ talk 01:02, 31 August 2020 (UTC)
So I just closed this discussion as a merge to Module:ISO 639 name, but the script put {{ being deleted}} on that module's /doc. I know the module handling is already a little odd, but it should (in theory) work the same as template mergers, and just remove the TFD tags from the merge target. Primefac ( talk) 01:22, 6 August 2020 (UTC)
Notice: Discussion is taking place at Wikipedia talk:Non-admin closure#Proposal - limiting use of WP:XFDCloser to those on a list, similar to WP:AFC tool user list ( permalink). davidwr/( talk)/( contribs) 17:27, 23 September 2020 (UTC)
If you close an XfD as "speedy delete", the page's deletion reason will just be a link to the XfD discussion, as if it were just closed as "delete". I think it would make more sense for the deletion reason to contain the given reason in that case, though. Jackmcbarn ( talk) 16:50, 3 October 2020 (UTC)
When selecting the merge option, XFDcloser would currently add the following to WP:TFDH:
What do we think about organising this slightly differently? Along the lines of:
When closing, the closer is required to select a single merge target (which would be line one). All other templates would be sub-bullets. Would help TFDH look less like this. Technically, it would be done in Task.prototype.doTask.addToHoldingCell I think. ProcrastinatingReader ( talk) 17:34, 26 September 2020 (UTC)
Clicking relist button, cancelling, then taking a quick delete action shows "reload page to see the actual relist" rather than "reload page to see the actual close" I'm guessing it's maybe because the relisting var isn't unset after closing the dialog, but haven't looked closely enough. Minor thing, don't think it's taking any relist actions after the close, but just pointing it out. ProcrastinatingReader ( talk) 00:29, 20 October 2020 (UTC)
Preceding discussion: User_talk:Pppery#Noinclude_list_and_XFDCloser
Closing a TfD as "quick-delete" causes the template to be listed at "to orphan" in TfD Holding, rather than tagging it for deletion. I figured it may be because User:Pppery/noinclude list transcludes every template which would fit that category, but not sure. If that is indeed the case, is there any way this template can exclude "User:Pppery/noinclude list" for the "has transclusions" check (I assume one is taking place when deciding where in holding to put the page, but I haven't looked at the source)? ProcrastinatingReader ( talk) 17:58, 23 October 2020 (UTC)
There's something odd in this deletion log (the entry from earlier today) – judging from the edit summary, this was part of the closure of one MfD discussion, but the result was the deletion of another, unrelated, page (whose MfD had concluded as "keep" several hours previously). What has happened here?
An unrelated incident from a few days ago (which involved the same admin) had resulted in the G8 deletion of Talk:Islamic languages, a page that I seem to recall having tagged with {{ G8-exempt}}. Was this an automatic action that wasn't supposed to happen, or could it have been a deliberate action by the admin? – Uanfala (talk) 21:01, 31 October 2020 (UTC)
In Wikipedia:Templates for discussion/Log/2020 November 7#Template:Ethiopian-Eritrean Cultural and Historical Community, presumably since Gyrofrog used Template:Lt when discussing a template in a comment, XFDCloser (when closing) thought that template was part of the TfD and hence tried to take automated actions on it ( Special:Diff/988714563). Perhaps it should only try to detect Template:Tfd links (and that too, at the start of the nomination)? ProcrastinatingReader ( talk) 22:22, 14 November 2020 (UTC)
"Unlinking backlinks: Done! (3/4)" is counterintuitive (4/4 is "done"). I've never been dissatisfied with anything the closer has skipped. I think it's fine to mark this as "4/4"/fully processed. It's fine to have a collapsed/unfurlable "show skipped" but otherwise hide the hazard/warning triangle symbol and save that only for something that warrants action. Having the status is nice when I want to click through, but all I really need to know after the close is whether it was successful or needs manual intervention. czar 21:56, 25 December 2020 (UTC)
See the edit in the middle
here with the edit summary "Relisting
Wikipedia:Articles for deletion/Cathy Tie (2nd nomination)". For some reason, neither updateDiscussion
nor updateNewLogPage
ran successfully, but updateOldLogPage
did, so the discussion wasn't transcluded anywhere until Cyberbot noticed it a couple of weeks later.
Probably extremely uncommon for this to happen, but possibly updateOldLogPage
could be deferred until the others have finished successfully?
– Thjarkur (talk) 22:09, 22 January 2021 (UTC)
Also no "soft delete" option (works in v3, not v4-beta). ProcrastinatingReader ( talk) 13:29, 23 January 2021 (UTC)
I planning to deploy version 4 of XFDcloser next week, probably MondaySunday. It has been available as a beta version since last November. While there are some minor issues still to be worked on, I don't think they are significant enough to delay rolling out the new version. As well as a new user interface, the introduction of some preferences, and making the "unlink backlinks" functionality available for any non-existent page, version 4 fixes various issues reported above, including
Thank you to the editors who have been testing out the beta version. At this stage I intend to keep the beta version around for trialling any new features and other non-urgent updates prior to the main version. - Evad37 [ talk 03:47, 26 January 2021 (UTC) Updated 10:54, 30 January 2021 (UTC)
It looks like when updating talk page links, the script currently tries to access logs at Wikipedia:Redirects for discussion/Log/DD Month YYYY
instead of Wikipedia:Redirects for discussion/Log/YYYY Month DD
. Examples from my recent closures are
Talk:Complete list of species in genus Persea,
Talk:Complete list of Grewia species,
Talk:Red Indians,
Talk:Red Indians. signed,
Rosguill
talk 17:53, 31 January 2021 (UTC)
Closed Wikipedia:Articles for deletion/Stirrings Still (journal) as quick delete and received a notice that the unlinking failed (so I did it manually) czar 10:01, 30 January 2021 (UTC)
Extended content
|
---|
load.php?lang=en&modules=jquery|jquery.ui&skin=monobook&version=1bti2:144 JQMIGRATE: Migrate is installed with logging active, version 3.1.0 |
So I just closed this discussion, which resulted in a merge to {{ Infobox officeholder}}. However, that template was subsequently tagged with {{ being deleted}}, despite the fact that it, well, isn't being deleted. Pre-version-4 versions of this tool would just remove the {{ tfm/dated}} template for any merge target. Is this new procedure intentional or a bug? Primefac ( talk) 13:50, 8 February 2021 (UTC)
It's great that CfD has some support for automated actions, I've started closing CfDs again partly because of it. I just have some feedback on how to make it even better without a huge time investment. I think the option to remove nomination templates and tag talk pages should be available for renames, merges and redirects to, now I've closed them using custom to actually get the option. Also worth noting that closing CfDs as redirect is very rare since category redirects don't work properly. By my count only 7 of the over 5000 CfDs in 2020 were closed as redirect. I would probably replace it with upmerge which is a lot more common. -- Trialpears ( talk) 21:37, 11 February 2021 (UTC)
Not a fan of having to click through two panes to close as opposed to one, especially since the second pane seemingly has so few options; could this not simply be included in the first pane for expedience and convenience? That aside, the option to make the close result part of a new sentence or not was sorely needed and is much appreciated. — Godsy ( TALK CONT) 15:09, 12 February 2021 (UTC)
This edit by Rosguill is not how XFDcloser ought to behave. Is that because of this change by JJMC89, i. e. because the module was renamed? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 ( 𝗍𝗮𝘭𝙠) 13:24, 19 February 2021 (UTC)
So! I just closed Wikipedia:Articles for deletion/Lloyd Yancey, an article about a man who didn't do enough sports to become notable. Super. Imagine my surprise when he had several dozen links to his name. Now imagine my surprise when a bunch of them turned out to be links to Chestnut Hill Academy. That's weird, because that article isn't a redirect to Lloyd Yancey. It does feature, interestingly, a redirect to Springside Chestnut Hill Academy, except somebody didn't actually remove the content from the Chestnut Hill Academy article when they added the redirect link to Springside. And, surprise surprise, Chestnut Hill Academy contained a link to Lloyd Yancey!
So it turns out that in the unlikely event that the article being deleted is wikilinked in an article that contains redirect markup as well as article content, the unlink function of XfDcloser will treat that second article as a redirect target to the article being deleted, even if the redirect link points elsewhere. Damned unlikely, but one never knows. I'll clean up the mess myself; this is mostly to inform anyone else who has this issue in the future. ♠ PMC♠ (talk) 22:40, 2 March 2021 (UTC)
trying to do a speedy withdrawal, but the 'next' button is greyed out. what do? -- Ysangkok ( talk) 16:55, 10 March 2021 (UTC)
While unlinking Sunday Driver (film), which was PROD-deleted in December, XFDcloser put " undefined" (including the link) as the unlink reason (cf. [8] [9] [10]). In the popup, the reason was automatically set to the page's delete reason and not altered. The page was open in Visual Editor mode (i.e. [11]), which could be the cause of this bug, although it would be an odd one. IceWelder [ ✉] 11:13, 18 March 2021 (UTC)
In the last few days I've seen a large number of templates that were closed as "delete" and listed at the Holding Cell (pretty much everything from 13 Mar and 14 March) where the {{ Template for discussion/dated}} template was not removed. I wasn't aware of any major/recent changes to XFDC, so... any idea what happened? Did this set of changes or this change mess up the language the script was looking for? Primefac ( talk) 18:02, 21 March 2021 (UTC)
|otherpages=
, as
this close didn't have that parameter and it worked as normal.
SMcCandlish, what was the intention behind
Special:Diff/1010900409, as I don't quite follow the logic or see the need (especially since Twinkle doesn't add this param anyway?).
Primefac (
talk) 18:10, 21 March 2021 (UTC)
I noticed that both in the selection menu (for selecting which Rcats to use) and in the actual wikitext generated, XFDcloser uses {{R from less specific name}}}
(note the extra closing curly bracket). See
diff #1020394565 as an example.
Tol |
Talk |
Contribs 20:57, 28 April 2021 (UTC)
Actions will be applied to this redirect's target page. To use the nominated page instead, undo the redirection before continuing.
I just started using this gadget, and I'm having problems understanding the unlinking part. The first part is telling it to unlink backlinks; what exactly does that do? The next part is it gives me a list of pages with the unlinked badlinks saying that they can be edited unless they are transcluded. The problem is there's no way to tell which pages listed can in fact be edited. The it unlinks the backlinks (again not sure what that means). Usually it then gives me options as to what to do with the unlinked badlinks (the one I'm doing right now doesn't give me any options, not sure why). What I want to do depends on the page. If, for example, it's a page that lists notable people, I'd want to remove the entry. If, however, it's an actor and they're in a cast section of the page, I want to leave the item but remove the redlink. I don't see how to do the latter.
Thanks for any help.-- Bbb23 ( talk) 15:28, 3 June 2021 (UTC)
And it is said that bar won the race...it would just turn bar into bar.
It would be nice to hit the /sandbox, /doc, and /testcases subpages when a TFD is closed as delete (now, rather than holding), and possibly associated redirects. (Maybe with checkmarks? Not sure.) In almost all my recent deletes there I've had to open the 'subpages' link and then manually G8 the remaining subpages. Izno ( talk) 16:47, 24 May 2021 (UTC)
So XFDC should only perform the unlink and not remove AfD tags. If it does the latter, it might need some sort of check to make sure the AfD tag matches the AfD in question. czar 13:37, 23 July 2021 (UTC)
TfD is currently experiencing some quite severe PEIS issues with {{
Tfd links}} being the main culprit. By using the module directly instead could reduce the size significantly. Therefore I believe XfDCloser should on top of the * {{tfd links|__PAGE__}}\n
format also recognize * {{#invoke:tfd links|main|__PAGE__}}\n
. --
Trialpears (
talk) 22:04, 3 August 2021 (UTC)
Please take a look at Wikipedia:Articles for deletion/Log/2021 August 7 - there are entries which were relisted but which were not properly commented out ( manual fix) nor copied over ( idem) to the next log page. RandomCanadian ( talk / contribs) 17:27, 15 August 2021 (UTC)
Please see
this discussion. It appears that XFDcloser is unable to delete pages in the Wikipedia talk:
namespace if they are nominated directly.
Evad37, is there an easy way to solve this issue?
✗
plicit 06:47, 16 September 2021 (UTC)
When I closed Wikipedia:Articles for deletion/Living presidents of the United States, XFDCloser deleted the secondary article ( Living vice presidents of the United States), but not the main one. I haven't closed any other multi-AfDs to be able to tell you if this is a recurrent problem, but this behaviour was unexpected. Did I do something wrong, or is this a bug? – bradv 🍁 23:43, 4 September 2021 (UTC)
Some excess colons were removed {{ Cfd2}}, {{ Cfm2}}, {{ Cfr2}} and {{ Cfs2}}, per Template talk:Cfd2#Remove leading colons. I don't know if this would break XFDcloser, but if something starts going wrong in CfD closure process, this could be the reason. – SD0001 ( talk) 03:14, 25 October 2021 (UTC)
Special:Diff/1055247133-- not sure what happened, bu it wasn't me... Eddie891 Talk Work 19:31, 14 November 2021 (UTC)
working on the merge backlog, I'm coming across quite a few articles (in the May list I'm working on) where
Afd-merge to was added without adding
Afd-merge from on the target, and these seem to be generate by the use of XFDcloser. For example:
I wonder whether XFDcloser might include this step (as suggest in the Adf-merge to documentation) to include this step, as it should help to advertise the need for a merge on the high-traffic target pages.
Klbrain (
talk) 13:23, 9 October 2021 (UTC)
Review unlinked list item
A backlink has been removed from the following list item:
List:
List of children's television series by country#Australia
I saw this today, and when I clicked through the link it brought me to this broken link. So there's an error in the URL encoding/escaped character. Note that in my example I replaced the ampersand character (as it was displayed to me) with the character reference so that it would display properly here. But as it reads to you, that's how it looked to me. czar 16:21, 25 November 2021 (UTC)
See Special:Diff/1064766039. Some well-meaning person, apparently not realizing that {{ subst:rfd2}} includes an anchor to serve as a fallback for when the redirect's name isn't the same as the header, added a bunch of anchors to this RfD section heading. When I went to close the RfD, it aborted because it could not find the section heading, showing a grayed-out abort button and a blue close button, without any message (like Twinkle has and SPIhelper have for failed-to-saves) giving me a copy of what I'd written.
The failure seems like a bug—the script shouldn't rely on the displayed section heading being the same as the wikitext section heading, because that's not a guarantee with MediaWiki—but would be less of an issue if the feature I referenced were implemented. -- Tamzin cetacean needed (she/they) 03:30, 10 January 2022 (UTC)
Hi, it was brought to my attention that XFDcloser is not updating the dates on templates when relisting WP:RFD discussions, as it failed to do here. This is an issue I noticed when a second relist was performed, but now it doesn't seem to update the date at all. ✗ plicit 00:51, 26 June 2021 (UTC)
I love the little "Show/Hide closed discussions" button but it would be even better to have its corrolary now that XFDC can see closure-eligible discussions. It would only show the "amber" and "green" discussions (i.e., ready for closure), filtering out the "red", when viewing any given AfD log. I imagine there are a few different ways to approach, but one idea would be to use the same button and toggle between the three filtered states (Show all discussions/Hide discussions ineligible for closure/Hide only closed discussions). Another option would be to ignore that third option and only toggle between the first two. czar 00:34, 10 January 2022 (UTC)
TODO - investigate this issue when an AFD'd page is moved. Situation can also occur if the page is just replaced with a redirect to an already-existing page (an out-of-process redirection, since that shouldn't be happening during the AFD discussion) XFDcloser should be asking the closer if the actions should be applied to the redirect's target or the redirect. My suspicion is that the wording presented to the closer using XFDC isn't clear enough, so the option they choose results in the old afd template being placed on the wrong page. Another possibility is something going wrong within the script itself. Ping @ Wbm1058: who has come across several, see their contributions on 2022-01-11 approx 05:00 to 06:00UTC - Evad37 [ talk 14:15, 11 January 2022 (UTC)
Just had an idea: the script should be able to check the age of redirect. If created as the result of a move, it would have been created after the xfd discussion started. Whereas an out-of-process redirection would just be an additional edit, so the page would have been created before the xfd discussion started. - Evad37 [ talk 14:25, 11 January 2022 (UTC)
Extracted from Wikipedia talk:Articles for deletion#Bug/edge case in XFDcloser tool ( permalink):
By the time Wikipedia:Articles for deletion/İkinci Ərəbcəbirli closed as "speedy keep" the page had been moved to Arabdzhabirli Vtoroye "per WP:NCGN."
When Buidhe closed it using the XFDcloser tool, it put the {{ Old AfD multi}} template at the top of the redirect page, breaking the redirect.
I removed it from the redirect and added it to the renamed page.
Please consider fixing this issue in a future release. If a fix is not feasible, please consider detecting it as an error or warning if that is not already being done.
davidwr/(
talk)/(
contribs) 16:27, 27 February 2020 (UTC)
#REDIRECT
line (and any other existing content). -
Evad37 [
talk 00:38, 28 February 2020 (UTC)
Found this thread while following up on the unusual situation discussed at User talk:Sandstein § Article still around six months after delete close ( Special:Permalink/1067398279). Was going to suggest a feature similar to what Evad37 says is meant to already happen. Sandstein, I know it was six months ago, but I don't suppose you recall if you got any warning message when deleting that page? And @Evad, is the warning in this case just the generic "not tagged" warning, or does it explicitly say that the page is now a redirect? Because, if the former, I could see that bamboozling a closer who gets the "not tagged" warning, clicks the link, gets redirected to the new page, doesn't notice that they've been redirected, sees the XfD tag, and thinks "Huh, XFDcloser being weird I guess". -- Tamzin cetacean needed (she/they) 08:20, 23 January 2022 (UTC)
Following this discussion it was determined that new TFD discussions should be added to the bottom of the relevant daily log page. At this discussion it was mentioned that XFDC wasn't updated, and when relists occur they are being added at the top of the page. I don't know how easy a fix this will be, but changing it would be much appreciated so that XFCD is in line with current TFD practices. Thanks! Primefac ( talk) 15:44, 5 February 2022 (UTC)
The "Result is a new sentence" checkbox does not really mean what it says. What it actually does is "Rationale is a new sentence". That's had me confused for years. Spinning Spark 17:29, 3 February 2022 (UTC)
I closed a CfD at Wikipedia:Categories for discussion/Log/2021 December 4#Recording artists using XfDcloser with consensus to rename all 5 categories, and the outcome wasn't implemented automatically. See also this AWBREQ report, where I have filed a request to clean this up. – LaundryPizza03 ( d c̄) 05:08, 11 February 2022 (UTC)
An issue came up at WP:AN involving outstanding AfD closures. Upon investigation, I found that a user had re-listed seven AfDs using XFDcloser, but whilst they were all removed from the February 3 log, only two of them had been added to the February 10 log ( Link). Is this likely to be a glitch at the user's end, or is it something that might happen again? Black Kite (talk) 22:59, 14 March 2022 (UTC)
So ... there's been some bugs with this gadget for a while, especially bugs with matters which pertain to WP:RFD. In addition, the only editor who seems to maintain this tool has not edited for about 3 months now. Unless someone else wants to take over responsibility for maintaining this gadget, I think it's time for it to no longer be a gadget. Steel1943 ( talk) 03:28, 28 April 2022 (UTC)
Hi! At Wikipedia_talk:XFDcloser#Advance_notice:_Version_4_deployment, it was noted that @ Randykitty's request re: not having backlinks clutter watchlist was addressed. Do any of the gadget users know where to toggle that? I hadn't much worried about it, until Wikipedia:Articles for deletion/Futsal positions murdered my watchlist. Thanks! Star Mississippi 16:47, 30 April 2022 (UTC)
Can anyone produce a list of pages in the "Template:" namespace which XFDcloser is reliant on? I'm wanting to create a template similar to {{ Twinkle standard installation}} to put on those pages to notifying editors to take care when editing those templates to make sure the edits don't break XFDcloser if they are major. Steel1943 ( talk) 02:09, 1 May 2022 (UTC)
Hello, folks,
I closed some deletion discussions at Wikipedia:Redirects for discussion/Log/2022 March 13 and noticed that the redirects that were supposed to be deleted were not and the RFD tags were still on the pages. I thought, of course, this must be me but then I noticed other discussions closed as "Delete" by Explicit also had existing redirects that were supposed to be deleted but were not. XFDcloser closes the discussion properly, just doesn't follow through on the deletion decision. I'm not sure if this is also an issue on other deletion discussion forums but if it was, I'd expect to see messages here already. Thanks for any help you can provide. Liz Read! Talk! 22:19, 20 March 2022 (UTC)
The title says it all. Steel1943 ( talk) 22:08, 25 March 2022 (UTC)
Evad37 is the sole developer, and last made an edit on January 22. MediaWiki:Gadget-XFDcloser.js last updated on 31 January 2021, deploying version 4, and MediaWiki:Gadget-XFDcloser-core.js last updated 22 January 2022 (fix missing rationale input). MediaWiki:Gadget-XFDcloser-core.css was deployed 31 January 2021 (version 4), and hasn't been changed since. I don't know what could have changed around March 20 that would have broken anything that previously worked, other than maybe a MediaWiki software update. Anyone with a good working knowledge of javascript might investigate to better diagnose the issue. – wbm1058 ( talk) 02:05, 28 March 2022 (UTC)
I can't imagine this could be a bug in XFDcloser. My bet is that the gadget fails to figure out the name of the redirect from the nomination, and that in turn is probably down to the changes that were made to {{ rfd2}} in early March. – Uanfala ( talk) 21:53, 30 April 2022 (UTC)
Fixed ...sort of. XFDcloser will now work on any nominations at RFD that are opened after this time stamp. (Please see the above discussion or further details.) Thanks again to
Uanfala for finding the issue that caused XFDcloser to break on closing RFD nominations.
Steel1943 (
talk) 02:12, 1 May 2022 (UTC)
neither @ Liz nor I are able to close this AfD. I'm not sure if it's space exclamation point or another issue. It says there's an edit conflict, but none actually present. Star Mississippi 00:36, 8 April 2022 (UTC)
"
instead of ''
when this title was created was someone who should have known better as an editor with a permission to bypass the title blacklist. Also, in most cases recently, such titles have qualified for
WP:G6 due to causing technical issues since consecutive apostrophes are interpreted as wiki markup (provided the title is a redirect, of course.)
Steel1943 (
talk) 01:21, 16 July 2022 (UTC)Is there a way to allow a clickthrough on this failure message? I often use XFDcloser to relist orphaned AfD discussions, which definitionally don't have an old logpage. Currently, this requires me to add them to a logpage and then relist it, which is fairly time-consuming. jp× g 23:35, 21 July 2022 (UTC)
Hello,
Midway through looking through today's expiring AFD log page ( Wikipedia:Articles for deletion/Log/2022 August 4), XFDcloser stopped completing relistings. It would relist the discussion on today's log page, for August 11th, but not remove them from the log for August 4th. So, I handled this manually. I had noticed that ocassionally, XFDcloser would do this with relistings (it's probably happened with me about 6 or 7 times) but doing this to two relistings in a row makes me worried that this will become a regular problem. Of course we can go edit the log page ourselves but XFDcloser is normally so reliable, I thought I'd bring the issue to the talk page. Liz Read! Talk! 22:55, 11 August 2022 (UTC)
I added this to the main XFDC page for now; XFDC removes all other content, including WP:RCAT templates, whenever a WP:RFD is closed to any result that alters the nominated redirect. ( Here is an example.) I think the fix here is to remove XFDC's ability to tag redirects with RCAT templates during a close (or fix XFDC's apparently greedy regex used when replacing the content of the redirect being retargeted), but I have no idea how to go about doing or suggesting that. Steel1943 ( talk) 17:14, 19 August 2022 (UTC)
Edit summary links to undefined here: https://en.wikipedia.org/?title=Unified_Payments_Interface&diff=1108464577&oldid=1107719925 – SD0001 ( talk) 09:31, 17 September 2022 (UTC)
Please fix the bug in XFDcloser that sometimes omits the action parameter in {{ Old CfD}}, e.g. [14]. I highlighted this as my "top request" for 2022 above.– Fayenatic London 08:06, 29 August 2022 (UTC)
This relisting edit recorded that a CFD discussion was removed from the 23 September log, but it was not inserted into the 1 October log. I have relisted it today.
Pinging Qwerfjkl in case they have any recollection of the event, although I doubt it after 3 weeks.
This talk page shows that similar failings have been occurring earlier this year with AfD relistings. Are these malfunctions linked? – Fayenatic London 17:57, 21 October 2022 (UTC)
I was wondering how I can get The Revels Group Wikipedia back up. CarsonHolland ( talk) 19:12, 6 February 2023 (UTC)
Close is aborting for
WP:Redirects for discussion/Log/2023 February 8#Invisible Child : Poverty, Survival & Hope in an American City. The error is Possible edit conflict detected, found section heading"Invisible Child : Poverty, Survival & Hope in an American City"
. Note that there is only one section header with that title. Perhaps something to do with the colon or space or space near the colon?
Jay
💬 16:47, 15 February 2023 (UTC)
Hi, I've noticed that XFDcloser automatically removes templates on a redirect page that aren't wrapped in {{ Redirect category shell}}, such as {{ Fictional character redirect}} and its siblings. This creates a hassle for the few editors who watch those redirects, as we then have to manually add the template back. Please fix this ASAP. Thanks. InfiniteNexus ( talk) 05:55, 30 September 2022 (UTC)
When relisting RfD discussions, XfDcloser fails to locate the RfD tag to update the link. It is possible that the format of Template:RfD has changed since this feature was last updated. – LaundryPizza03 ( d c̄) 12:05, 14 May 2023 (UTC)
This is a courtesy disclosure that I have tinkered with Template:Cfm2 and Template:Cfd all (showing the parameter label target2 on the category page) in order to make Template:Cfm-double correctly prepare the standard discussion starter. I do not expect my edits to adversely affect XFDcloser, because the CFD log entries should still be in the same format, and I do not think the change in the category page template will affect the process for its removal. However, if XFDcloser now malfunctions with merges, then please revert my changes to those templates and ping me. – Fayenatic London 13:07, 31 May 2023 (UTC)
![]() | This is an archive of past discussions. 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 1 | ← | Archive 3 | Archive 4 | Archive 5 | Archive 6 |
When closing Wikipedia:Redirects for discussion/Log/2021 January 2#Akira (2009 film), I got the below error and had to add the talk page template manually.
TypeError: date.getUTCDate is not a function error: could not edit page Talk:Akira (2009 film)
fwiw, this followed a pop-up indicating that adding the Old RfD template would overwrite a redirect, though apparently Talk:Akira (2009 film) was not a redirect? It also threw an error rather than passing me the template code to add myself.
Not sure if related, but XFDC also didn't redirect to the section I specified in the form Akira (planned film)#Film rights and conception. Instead it just dropped the section and redirected to the article itself. czar 21:37, 2 January 2021 (UTC)
It also threw an error rather than passing me the template code to add myself– that's because the error occurred while trying to create the wikitext (template code) for the talk page. - Evad37 [ talk 09:15, 20 January 2021 (UTC)
{{ resolved}}
{{ resolved}}
Unlinking after deleting an article and got a prompt to process a bulleted link in the section "List: LA}}LA Giltinis", referring to
List of 2020–21 Major League Rugby transfers § LA Giltinis but struggling with the section heading, which contains an anchor tag: =={{anchor|LA}}LA Giltinis==
czar 21:50, 25 December 2020 (UTC)
{{ resolved}}
Both when loading the closer on the daily AfD page and after the AfD closes, I'm losing my place often with the beta when I generally want to refer to the discussion I was reading. There appears to be some page resituating when the closer is first loaded. And when the AfD is closed, v3 had more visual indication of the closed action, like it was easier to tell which one I just closed and where, if I scrolled through the page and looked at a glance. If there was some way to change the background of the section or otherwise indicate which discussions have been addressed, would help contextualize the change. czar 21:50, 25 December 2020 (UTC)
{{ resolved}}
It would be great if the beta XFDcloser defaulted to using Wikipedia:XFDcloser/Soft deletion rationale when closing as 'soft delete' Eddie891 Talk Work 17:55, 16 January 2021 (UTC)
{{ resolved}}
ProcrastinatingReader ( talk) 13:23, 23 January 2021 (UTC)
Received this in my watchlist:
Mai Minokoshi diffhist -4 Spartaz talk contribs Removing link(s): Wikipedia:Articles for deletion/Cinema Today closed as delete (XFDcloser) rollback
Doesn't make sense, as one article has nothing to do with the other. Regards,
GenQuest
"Talk to Me" 07:42, 7 June 2020 (UTC)
{{ User:ClueBot III/ArchiveNow}}
I keep getting spammed by this entity with a pop-up ad that says "Hey its now a gadget, here's how to enable that". Well I did that, and the ad keeps popping up anyway. What's more, there's not even an X to close the pop-up window, and I haven't figured out a way to do that -- I have to leave the page, which impacts my productivity. Is there any way to make this stop? Herostratus ( talk) 14:35, 21 June 2020 (UTC)
{{ User:ClueBot III/ArchiveNow}}
When closing as 'redirect', it would be cool if the tool auto-changed the assessed class to 'redirect'. Just a thought. Eddie891 Talk Work 23:05, 17 November 2020 (UTC)
{{ resolved}}
In the past, I've been able to close multiple AfDs at once, which is especially useful when one is taking a while to unlink. Doesn't look like a second instance loads in v4. czar 21:50, 25 December 2020 (UTC)
{{ resolved}}
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)
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)
{{ resolved}}
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)
{{ resolved}}
I'd like:
to both be changed either to
or
Reason: more explanatory and word-flowy. Also we don't put a period after deleting a talk page when the associated page is deleted per PROD/CSD, and we should explain what reason to delete redirects AFD or not, not bring up what is already happening in our eyes. (Disclaimer: Fat (song) is a placeholder and that AFD is actually a run-of-the-mill April Fools joke. ミラ P 04:13, 26 December 2019 (UTC)
{{ resolved}}
I know this has been discussed before somewhere, but I just couldn't find the discussion. Doing the usually automated actions of removing nom-templates and adding {{ old cfd}} takes quite a lot of time and really should be automated here as well. It looks like a lot of ground work is done for these features with old cfd formatting and nom-template regexs appearing in the source code so is there and I don't really see anything that different about CfD compared to other venues in this area. What would happen if the code handling CfD in basic mode was removed? -- Trialpears ( talk) 21:44, 11 July 2020 (UTC)
{{ resolved}}
I don't quite see what that void subst-ing is being used for in this script, but since subst-ing doesn't work inside references it results in this string appearing in articles, see here and here. Not a very common problem, I've just fixed about 20 instances of this, but maybe this can be avoided. – Thjarkur (talk) 16:44, 27 July 2020 (UTC)
{{ resolved}} In my More tab XFDC Prefs appears (and I can access those), but I can no longer see/use the tool. I have not knowingly changed anything. Thoughts, please? Ping me on answers, or I may miss it. FiddleTimtrent FaddleTalk to me 11:37, 20 June 2021 (UTC)
{{ resolved}} I wish to withdraw my nomination from an AfD. I am trying to use my XFD closer. But the only button I have for this is "xfdc preferences." When I click on that I don't get the box that asks me to choose what kind of close. Instead I see something about enabling Beta version, add edited pages to my watchlist, collapse task warnings if at least:, and collapse task errors if at least. Is the xfd closer malfunctioning or is my particular closer malfunctioning? I am unable to close this AfD using the XfD closer. --- Steve Quinn ( talk) 21:01, 10 August 2021 (UTC)
If someone wants to look at the page, here is the AfD [1]. I am not interested in having the AfD closed. I am interested in having my XFD closer work. Thanks. --- Steve Quinn ( talk) 21:10, 10 August 2021 (UTC)
{{ resolved}} I can't currently use the script because the text fields for the result and the rationale don't show up. Screenshot: https://imgur.com/a/i6Z1WOW. I'm using the current Chrome browser on Windows 10. Sandstein 11:18, 21 January 2022 (UTC)
Investigating now. My suspicion is a breaking change to mw:OOUI. (Please continue to ping me and/or leave talk page messages when reporting urgent issues, or if I'm taking a long time to reply. My watchlist is too big to be useful given that I'm less active then I used to be.) - Evad37 [ talk 01:13, 22 January 2022 (UTC)
{{ resolved}} I'm seeing an admin use XFDcloser to remove links from deleted articles that are not deleted through XFD discussions. How is that possible? I'd like to find a tool to use to do that but reading over the tool page, I don't see how XFDcloser can be used to remove links from articles deleted through PROD or CSD. I'd appreciate any information anyone familiar with the tool can provide. Many thanks. Liz Read! Talk! 00:34, 2 May 2022 (UTC)
{{ resolved}} See this. It should have an exception for this. Piotr Konieczny aka Prokonsul Piotrus| reply here 02:59, 18 August 2022 (UTC)
{{ resolved}} Hello, all,
I'm having no luck with XFDcloser closing AFD nominations where there are a lot of articles bundled together. These have been nominations proposed by different editors so I know it isn't just one person not understanding how to do this. XFDcloser deleted the primary, first article mentioned in the nomination and ignores all of the articles listed (sometimes they are hatted, sometimes they are not). This requires a manual deletion of sometimes dozens of separate articles which can be a little time-consuming. Or, you can make a huge blunder, like I did last night, and try to batch delete them using Twinkle and end up with a huge mess to clean up. That's a mistake you only make once.
What do you think might be the problem here? Is it XFDcloser or is it the way that the bundled nomination is formatted that XFDcloser can't "see" all of the other articles that are proposed for deletion? I've discussed this with the nominators and maybe there just has to be a better explanation in the instructions for bundled nominations. Thanks for any ideas you can offer. Liz Read! Talk! 21:27, 21 August 2022 (UTC)
{{ resolved}} Hello, XFDCloser
The daily deletion log pages are not loading correctly. But it's not a good sign though that apparently the maintainer, Evad37, is inactive. There should really be a backup contact person as when the systems fail, they seem to fail spectacularly and affect the work of a lot of editors. Help! Liz Read! Talk! 01:29, 1 January 2023 (UTC)
not loading correctly- what do you mean? Primefac ( talk) 13:08, 1 January 2023 (UTC)
{{ resolved}} Add a delete button when closing a discussion, instead of having to add manually via the custom button. Preferably put it after the third tab/button, "soft redirect". Qwerty284651 ( talk) 02:58, 2 February 2023 (UTC)
{{ resolved}} I have the ability to close as a "regular" delete, but no option to soft-delete. Running on Chrome. Joyous! | Talk 19:59, 12 February 2023 (UTC)
![]() | This page is an archive of past discussions. 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. |
I've opened multiple AfD pages in the last 15 minutes, using two different browsers on different devices, but XFDCloser doesn't appear to be loading on any of them. No close/relist links, and or the option to show/not show closed discussions. I've not had this problem previously. RL0919 ( talk) 06:59, 22 January 2024 (UTC)
mw.util.addPortletLink ( 'p-tb', "javascript:importScript('MediaWiki:Gadget-XFDcloser-core.js')", 'Load XFDCloser', 'pt-loadxfdc', 'Manually loads XFDCloser');
Uncaught Error: inheritClass: Origin is not a function (actually undefined)
at OO inheritClass (oojs.js:85:9)
at 164.../../globals (<anonymous>:21:126600)
at o (<anonymous>:21:254)
at <anonymous>:21:288
at 170.../../globals (<anonymous>:21:145875)
at o (<anonymous>:21:254)
at <anonymous>:21:288
at 225.../../globals (<anonymous>:21:469338)
at o (<anonymous>:21:254)
at <anonymous>:21:288
Parse error: Unexpected: ( on line 21
css @ ext.gadget.XFDcloser-core-beta-script-0.js:24
runScript @ startup.js:1275
(anonymous) @ startup.js:1353
flushCssBuffer @ startup.js:606
requestAnimationFrame (async)
addEmbeddedCSS @ startup.js:637
execute @ startup.js:1367
doPropagation @ startup.js:757
requestIdleCallback (async)
setAndPropagate @ startup.js:830
impl @ startup.js:2009
(anonymous) @ load.php?lang=en&modules=ext.gadget.XFDcloser-core-beta&skin=monobook&version=1t9io:1
Extended content
|
---|
(Large block of minified code, removed as not relevant) |
/* jshint esversion: 5, esnext:false, laxbreak: true, undef: true, eqnull: true, maxerr: 3000 */
and here's line 24: (function(){
voorts (
talk/
contributions) 23:38, 19 February 2024 (UTC)
MediaWiki:Gadget-XFDcloser-core-beta.js. Clicking on the source mapping, it takes me to load.php?lang=en&modules=ext.gadget.XFDcloser-core-beta&skin=monobook&version=1t9io which contains this function:
mw.loader.impl(function() {
return ["ext.gadget.XFDcloser-core-beta@1svn5", function($, jQuery, require, module) {
mw.log.error("Parse error: Unexpected: ( on line 21");
}
, {
"css": [".xfdc-status{font-size:small;margin-left:13px;font-weight:normal}.skin-timeless .xfdc-status{font-size:0.98rem}.skin-minerva .xfdc-status{font-size:0.98rem;display:block;margin:-1rem 0 1rem}.xfdc-action{font-weight:normal}.xfdc-action a{cursor:pointer}.xfdc-qc-cancel{cursor:pointer;border:1px solid #777;border-radius:10px;font-weight:bold;font-size:90%;color:#777;padding:0;margin:0 1px} .xfdc-old .xfdc-action{background-color:#c6ffc6}.xfdc-notOld .xfdc-action{background-color:#ffc6c6}.xfdc-unknownAge .xfdc-action{background-color:#ffffc6}.xfdc-notOld.xfdc-relisted .xfdc-action{background-color:#ffe9c6} .xfdc-actioned-heading{text-decoration:line-through double black;opacity:75%}.xfdc-actioned-discussion{opacity:50%} html body.ooui-draggbleWindow-open{position:unset;overflow:unset;margin-right:unset !important; }html body.ooui-draggbleWindow-open .oo-ui-windowManager-modal \u003E .oo-ui-dialog.oo-ui-window-active{position:static;padding:0} html body.ooui-draggbleWindow-open .oo-ui-dialog.oo-ui-window-active \u003E div{z-index:110;transition:all 0.25s ease-out 0s,transform 0s !important} .oo-ui-textInputWidget.oo-ui-textInputWidget-labelPosition-before.padLeft2em .oo-ui-inputWidget-input{padding-left:2em !important}.oo-ui-textInputWidget.oo-ui-textInputWidget-labelPosition-before.padLeft4em .oo-ui-inputWidget-input{padding-left:4em !important} .xfdc-menuOptionWidget.oo-ui-decoratedOptionWidget{padding:7px 12px} .xfdc-taskItemWidget \u003E .oo-ui-fieldLayout-messages{clear:both} #XFDcloser-showhide{bottom:0;display:block;position:fixed;right:0;z-index:100;padding:5px;box-shadow:0 2px 4px rgba(0,0,0,0.5);background-color:#fef9e6;border:1px solid #aaa;border-radius:5px;font-size:85%}"]
}];
});
// Saved in localStorage at 2024-02-12T22:09:25.448Z
//# sourceURL=https://en.wikipedia.org/w/load.php?lang=en&modules=ext.gadget.XFDcloser-core-beta&skin=monobook&version=1t9io
//# sourceMappingURL=/w/load.php?lang=en&modules=ext.gadget.XFDcloser-core-beta&skin=monobook&sourcemap=1&version=1t9io
Not sure how helpful this is, but I'll collect any additional data you need. The Wordsmith Talk to me 20:46, 19 February 2024 (UTC)
Parse error: Unexpected: ( on line 21. That might have an error message that could be further debugged. – Novem Linguae ( talk) 23:29, 19 February 2024 (UTC)
Anybody else not seeing "[Close] [quickClose] [Relist]" and getting "Parse error: Unexpected: ( on line 21" in console? Seems to be happening on every XfD page. I tried disabling all gadgets except XFDcloser and still got it. The console says it's coming from ext.gadget.XFDcloser-core-script-0.js:24:1 (not 21!), which is not helpful. Works on every other skin and, worse, in debug mode. Nardog ( talk) 17:35, 8 February 2024 (UTC)
mw.loader.impl(function(){return"ext.gadget.XFDcloser-core@30cwo",function($,jQuery,require,module){mw.log.error("Parse error: Unexpected: ( on line 21");
},{"css":".xfdc-status{font-size:small;margin-left:13px;font-weight:normal}.skin-timeless .xfdc-status{font-size:0.98rem}.skin-minerva .xfdc-status{font-size:0.98rem;display:block;margin:-1rem 0 1rem}.xfdc-action{font-weight:normal}.xfdc-action a{cursor:pointer}.xfdc-qc-cancel{cursor:pointer;border:1px solid #777;border-radius:10px;font-weight:bold;font-size:90%;color:#777;padding:0;margin:0 1px} .xfdc-old .xfdc-action{background-color:#c6ffc6}.xfdc-notOld .xfdc-action{background-color:#ffc6c6}.xfdc-unknownAge .xfdc-action{background-color:#ffffc6}.xfdc-notOld.xfdc-relisted .xfdc-action{background-color:#ffe9c6} .xfdc-actioned-heading{text-decoration:line-through double black;opacity:75%}.xfdc-actioned-discussion{opacity:50%} html body.ooui-draggbleWindow-open{position:unset;overflow:unset;margin-right:unset !important; }html body.ooui-draggbleWindow-open .oo-ui-windowManager-modal \u003E .oo-ui-dialog.oo-ui-window-active{position:static;padding:0} html body.ooui-draggbleWindow-open .oo-ui-dialog.oo-ui-window-active \u003E div{z-index:110;transition:all 0.25s ease-out 0s,transform 0s !important} .oo-ui-textInputWidget.oo-ui-textInputWidget-labelPosition-before.padLeft2em .oo-ui-inputWidget-input{padding-left:2em !important}.oo-ui-textInputWidget.oo-ui-textInputWidget-labelPosition-before.padLeft4em .oo-ui-inputWidget-input{padding-left:4em !important} .xfdc-menuOptionWidget.oo-ui-decoratedOptionWidget{padding:7px 12px} .xfdc-taskItemWidget \u003E .oo-ui-fieldLayout-messages{clear:both} #XFDcloser-showhide{bottom:0;display:block;position:fixed;right:0;z-index:100;padding:5px;box-shadow:0 2px 4px rgba(0,0,0,0.5);background-color:#fef9e6;border:1px solid #aaa;border-radius:5px;font-size:85%}"]}];});
vector
to
vector-2022
or
monobook
or
remove &version=m2csj
, you get the whole script with no errors. This suggests something is wrong with the validation and/or the server caching. @
SD0001: Do you have a clue why this is?
Nardog (
talk) 10:54, 9 February 2024 (UTC)
I've got good news. phab:T359014 patch is written and merged, and will be deployed soon. This will likely fix this bug. May take a week to deploy though. Feel free to check the phab ticket for updates. – Novem Linguae ( talk) 20:12, 6 March 2024 (UTC)
The [Close] option is not appearing on AfD, CfD, FfD, or TfD discussions for me. I'm using Firefox 122.0.1 (64-bit) to browse, vector-2022 with dark mode, and these userscripts. voorts ( talk/ contributions) 19:17, 19 February 2024 (UTC)
{{ resolved}} I just noticed a new bug with XFDcloser: It now seems that on some pages of RFD where there are closed discussions, XFDcloser Now completely hides some of these discussions. This is quite problematic because it makes it so closed discussions cannot be reviewed; In fact, sometimes, this problem will make it so the evidence of a discussion even existing on that subpage is hard to find, unless one looks through the table of contents (provided one even shows up) or edits the page. Steel1943 ( talk) 14:24, 28 April 2024 (UTC)
Did you have closed discussions hidden?" Yes, and I don't know when I clicked that thing since it's in a really inconspicuous spot. Dang it XFDcloser. Steel1943 ( talk) 15:11, 28 April 2024 (UTC)
I am writing up a close for a TFD, and while writing I used a {{ tq}} for a quote. In the preview box it (for some reason) triggers the {{ FormattingError}} in the template ("Template:Tq is only for quoting in talk and project pages. Do not use it in actual articles."), but that's only triggered when the template is used in the article space (NS0). Why would this script, when previewing the content, make the template think that it's in the mainspace? If the answer is "who knows" that's totally fine (I can still read what I wrote in the edit box!) but I'm curious is there's a line of code somewhere that might be making the environment think that the preview is in ns0. Primefac ( talk) 11:20, 30 August 2021 (UTC)
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)
The script doesn't detect the bundled articles in this nom (just tested in sandbox) czar 19:04, 5 December 2019 (UTC)
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)
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)
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)
This has probably been brought up before, but just curious: Any chance this script can be configured to also handle closing WP:RM requests? Steel1943 ( talk) 16:21, 20 December 2019 (UTC)
Hi. A while ago I closed a discussion as delete but it looks like the script failed to delete (and I failed to notice it, but someone pointed it to me and deleted the page afterwards). Links: the MfD page, and the page itself: Talk:IQ classification/Archive 1 (which exists, again, because it was recreated as a move from some other page). Maybe the script does not like to delete "Talk:.*", or "Talk:.*/.*", pages? Thanks! - Nabla ( talk) 15:59, 17 February 2020 (UTC)
Hi. A (very low priority) suggestion. Is it possible to add a link to the retargeted to page when closing a RfD as retarget? I like to add it, because I think it is important information about the closure, I do not know if it is common enough, and wanted enough, to be worth the effort; but as it probably is not a huge effort, you already have all the info, it is probably "only" adding it to one string. See a example diff. - Nabla ( talk) 16:05, 17 February 2020 (UTC)
Noting there's a suggestion at [3] that XFDcloser should handle closing of WP:Deletion review discussions, including adding {{ olddelrev}} to talk pages as appropriate - Evad37 [ talk 00:45, 26 February 2020 (UTC)
It would be useful if all the automated actions associated with closing an AfD as delete could be logged, probably to the article's talk page (and creating one if necessary). That way, if the deleted article is ever restored, you'd have a record of what incoming links had been removed, making it easier to restore them. It's probably not possible to fully automate the restoration process (even if the log was machine parsable), but at least having a human-readable log would be useful.
Hmmm, as I'm writing this, it occurs to me that the information actually already exists. It should be possible to datamine the deleting user's contribution log to discover this. I need to think on that. -- RoySmith (talk) 15:39, 26 February 2020 (UTC)
When deleting redirects to other deleted pages, XFDcloser incorrectly handles redirects that are currently at
RFD. Rather than deleting those as well, it simply removes the link so that the pages look like this: "[
Template:rfd, which for technical reasons shouldn't be transcluded]
#redirect Foo"
This is obviously not desirable, so can it be fixed? (I don't know precisely how XFDC works, so excuse any errors in that department.)
Glades12 (
talk) 10:57, 25 February 2020 (UTC)
#REDIRECT [[Article]]
line within the RFD template is changed to #REDIRECT Article
Could the procedure for non-administrator close (nominator withdrawal) be added as an option?-- Goldsztajn ( talk) 12:13, 12 March 2020 (UTC)
I've noticed that when re-listing files at FfD ( example), the "delete" link is not updated to the current listing's date. Could this please be fixed? Thanks, FASTILY 03:35, 22 April 2020 (UTC)
Looks like this example came up in the unlinker/delinker. If possible, would be nice to add these cases to be excluded from the logic that asks whether the line should be removed. czar 11:56, 26 May 2020 (UTC)
I would like to know how this gadget can be used in other Wikis. Will it only require importing MediaWiki:Gadget-XFDcloser.js to the target wiki? Adithyak1997 ( talk) 10:33, 1 June 2020 (UTC)
User:Evad37, It would be great to have a "do not merge" option for merge discussions. Right now, I use "custom" with "do not merge" as the result and then I subsequently edit the talk pages to add the |merge=
or |mergeX=
parameter to the XFD result template. For example,
here and
here. Thanks for script/gadget, its been big timesaver.
Plastikspork
―Œ(talk) 14:11, 4 June 2020 (UTC)
If I'm not mistaken, XFDcloser only adds {{ Old AfD multi}} etc. if the page is kept. But the template is also useful (perhaps more useful) for recording when a page is deleted at XfD and subsequently recreated. Would it be possible to get the gadget to add the old XfD templates to the talk page immediately before it is deleted? – Joe ( talk) 12:14, 12 June 2020 (UTC)
I closed AfDs for the first time in a while today, and the script keeps skipping the "unlinking backlinks" step, saying that I've cancelled it, when I haven't. Is this a bandwidth issue? Because it doesn't happen every time...or is it something else? Vanamonde ( Talk) 16:25, 20 July 2020 (UTC)
I recently closed the RfD associated with the redirect Software Entertainment Company using XFDcloser. However, when I did so, it did not recognize the RfD template in this revision. Because of that, XFDcloser claimed there was no RfD template on the redirect, and did not remove the template from the redirect. (Of course, I ended up removing the template manually.) I'm assuming the issue is related to the template the Page Curation tool uses to tag pages for RfD, which seems to be {{ Rfd-NPF}}. Steel1943 ( talk) 00:23, 30 August 2020 (UTC)
Consider this scenario:
XFDcloser will disallow this close, saying "Non-admin closure is not appropriate when the result will require action by an administrator (per WP:BADNAC)". We should adjust it to allow non-admins to choose the "delete" reason if the page in question is already deleted. Jackmcbarn ( talk) 21:50, 10 August 2020 (UTC)
This issue has been raised before. Perhaps the non-admin view should have a little note saying to use the custom close option if a page has already been deleted. - Evad37 [ talk 01:02, 31 August 2020 (UTC)
So I just closed this discussion as a merge to Module:ISO 639 name, but the script put {{ being deleted}} on that module's /doc. I know the module handling is already a little odd, but it should (in theory) work the same as template mergers, and just remove the TFD tags from the merge target. Primefac ( talk) 01:22, 6 August 2020 (UTC)
Notice: Discussion is taking place at Wikipedia talk:Non-admin closure#Proposal - limiting use of WP:XFDCloser to those on a list, similar to WP:AFC tool user list ( permalink). davidwr/( talk)/( contribs) 17:27, 23 September 2020 (UTC)
If you close an XfD as "speedy delete", the page's deletion reason will just be a link to the XfD discussion, as if it were just closed as "delete". I think it would make more sense for the deletion reason to contain the given reason in that case, though. Jackmcbarn ( talk) 16:50, 3 October 2020 (UTC)
When selecting the merge option, XFDcloser would currently add the following to WP:TFDH:
What do we think about organising this slightly differently? Along the lines of:
When closing, the closer is required to select a single merge target (which would be line one). All other templates would be sub-bullets. Would help TFDH look less like this. Technically, it would be done in Task.prototype.doTask.addToHoldingCell I think. ProcrastinatingReader ( talk) 17:34, 26 September 2020 (UTC)
Clicking relist button, cancelling, then taking a quick delete action shows "reload page to see the actual relist" rather than "reload page to see the actual close" I'm guessing it's maybe because the relisting var isn't unset after closing the dialog, but haven't looked closely enough. Minor thing, don't think it's taking any relist actions after the close, but just pointing it out. ProcrastinatingReader ( talk) 00:29, 20 October 2020 (UTC)
Preceding discussion: User_talk:Pppery#Noinclude_list_and_XFDCloser
Closing a TfD as "quick-delete" causes the template to be listed at "to orphan" in TfD Holding, rather than tagging it for deletion. I figured it may be because User:Pppery/noinclude list transcludes every template which would fit that category, but not sure. If that is indeed the case, is there any way this template can exclude "User:Pppery/noinclude list" for the "has transclusions" check (I assume one is taking place when deciding where in holding to put the page, but I haven't looked at the source)? ProcrastinatingReader ( talk) 17:58, 23 October 2020 (UTC)
There's something odd in this deletion log (the entry from earlier today) – judging from the edit summary, this was part of the closure of one MfD discussion, but the result was the deletion of another, unrelated, page (whose MfD had concluded as "keep" several hours previously). What has happened here?
An unrelated incident from a few days ago (which involved the same admin) had resulted in the G8 deletion of Talk:Islamic languages, a page that I seem to recall having tagged with {{ G8-exempt}}. Was this an automatic action that wasn't supposed to happen, or could it have been a deliberate action by the admin? – Uanfala (talk) 21:01, 31 October 2020 (UTC)
In Wikipedia:Templates for discussion/Log/2020 November 7#Template:Ethiopian-Eritrean Cultural and Historical Community, presumably since Gyrofrog used Template:Lt when discussing a template in a comment, XFDCloser (when closing) thought that template was part of the TfD and hence tried to take automated actions on it ( Special:Diff/988714563). Perhaps it should only try to detect Template:Tfd links (and that too, at the start of the nomination)? ProcrastinatingReader ( talk) 22:22, 14 November 2020 (UTC)
"Unlinking backlinks: Done! (3/4)" is counterintuitive (4/4 is "done"). I've never been dissatisfied with anything the closer has skipped. I think it's fine to mark this as "4/4"/fully processed. It's fine to have a collapsed/unfurlable "show skipped" but otherwise hide the hazard/warning triangle symbol and save that only for something that warrants action. Having the status is nice when I want to click through, but all I really need to know after the close is whether it was successful or needs manual intervention. czar 21:56, 25 December 2020 (UTC)
See the edit in the middle
here with the edit summary "Relisting
Wikipedia:Articles for deletion/Cathy Tie (2nd nomination)". For some reason, neither updateDiscussion
nor updateNewLogPage
ran successfully, but updateOldLogPage
did, so the discussion wasn't transcluded anywhere until Cyberbot noticed it a couple of weeks later.
Probably extremely uncommon for this to happen, but possibly updateOldLogPage
could be deferred until the others have finished successfully?
– Thjarkur (talk) 22:09, 22 January 2021 (UTC)
Also no "soft delete" option (works in v3, not v4-beta). ProcrastinatingReader ( talk) 13:29, 23 January 2021 (UTC)
I planning to deploy version 4 of XFDcloser next week, probably MondaySunday. It has been available as a beta version since last November. While there are some minor issues still to be worked on, I don't think they are significant enough to delay rolling out the new version. As well as a new user interface, the introduction of some preferences, and making the "unlink backlinks" functionality available for any non-existent page, version 4 fixes various issues reported above, including
Thank you to the editors who have been testing out the beta version. At this stage I intend to keep the beta version around for trialling any new features and other non-urgent updates prior to the main version. - Evad37 [ talk 03:47, 26 January 2021 (UTC) Updated 10:54, 30 January 2021 (UTC)
It looks like when updating talk page links, the script currently tries to access logs at Wikipedia:Redirects for discussion/Log/DD Month YYYY
instead of Wikipedia:Redirects for discussion/Log/YYYY Month DD
. Examples from my recent closures are
Talk:Complete list of species in genus Persea,
Talk:Complete list of Grewia species,
Talk:Red Indians,
Talk:Red Indians. signed,
Rosguill
talk 17:53, 31 January 2021 (UTC)
Closed Wikipedia:Articles for deletion/Stirrings Still (journal) as quick delete and received a notice that the unlinking failed (so I did it manually) czar 10:01, 30 January 2021 (UTC)
Extended content
|
---|
load.php?lang=en&modules=jquery|jquery.ui&skin=monobook&version=1bti2:144 JQMIGRATE: Migrate is installed with logging active, version 3.1.0 |
So I just closed this discussion, which resulted in a merge to {{ Infobox officeholder}}. However, that template was subsequently tagged with {{ being deleted}}, despite the fact that it, well, isn't being deleted. Pre-version-4 versions of this tool would just remove the {{ tfm/dated}} template for any merge target. Is this new procedure intentional or a bug? Primefac ( talk) 13:50, 8 February 2021 (UTC)
It's great that CfD has some support for automated actions, I've started closing CfDs again partly because of it. I just have some feedback on how to make it even better without a huge time investment. I think the option to remove nomination templates and tag talk pages should be available for renames, merges and redirects to, now I've closed them using custom to actually get the option. Also worth noting that closing CfDs as redirect is very rare since category redirects don't work properly. By my count only 7 of the over 5000 CfDs in 2020 were closed as redirect. I would probably replace it with upmerge which is a lot more common. -- Trialpears ( talk) 21:37, 11 February 2021 (UTC)
Not a fan of having to click through two panes to close as opposed to one, especially since the second pane seemingly has so few options; could this not simply be included in the first pane for expedience and convenience? That aside, the option to make the close result part of a new sentence or not was sorely needed and is much appreciated. — Godsy ( TALK CONT) 15:09, 12 February 2021 (UTC)
This edit by Rosguill is not how XFDcloser ought to behave. Is that because of this change by JJMC89, i. e. because the module was renamed? 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 ( 𝗍𝗮𝘭𝙠) 13:24, 19 February 2021 (UTC)
So! I just closed Wikipedia:Articles for deletion/Lloyd Yancey, an article about a man who didn't do enough sports to become notable. Super. Imagine my surprise when he had several dozen links to his name. Now imagine my surprise when a bunch of them turned out to be links to Chestnut Hill Academy. That's weird, because that article isn't a redirect to Lloyd Yancey. It does feature, interestingly, a redirect to Springside Chestnut Hill Academy, except somebody didn't actually remove the content from the Chestnut Hill Academy article when they added the redirect link to Springside. And, surprise surprise, Chestnut Hill Academy contained a link to Lloyd Yancey!
So it turns out that in the unlikely event that the article being deleted is wikilinked in an article that contains redirect markup as well as article content, the unlink function of XfDcloser will treat that second article as a redirect target to the article being deleted, even if the redirect link points elsewhere. Damned unlikely, but one never knows. I'll clean up the mess myself; this is mostly to inform anyone else who has this issue in the future. ♠ PMC♠ (talk) 22:40, 2 March 2021 (UTC)
trying to do a speedy withdrawal, but the 'next' button is greyed out. what do? -- Ysangkok ( talk) 16:55, 10 March 2021 (UTC)
While unlinking Sunday Driver (film), which was PROD-deleted in December, XFDcloser put " undefined" (including the link) as the unlink reason (cf. [8] [9] [10]). In the popup, the reason was automatically set to the page's delete reason and not altered. The page was open in Visual Editor mode (i.e. [11]), which could be the cause of this bug, although it would be an odd one. IceWelder [ ✉] 11:13, 18 March 2021 (UTC)
In the last few days I've seen a large number of templates that were closed as "delete" and listed at the Holding Cell (pretty much everything from 13 Mar and 14 March) where the {{ Template for discussion/dated}} template was not removed. I wasn't aware of any major/recent changes to XFDC, so... any idea what happened? Did this set of changes or this change mess up the language the script was looking for? Primefac ( talk) 18:02, 21 March 2021 (UTC)
|otherpages=
, as
this close didn't have that parameter and it worked as normal.
SMcCandlish, what was the intention behind
Special:Diff/1010900409, as I don't quite follow the logic or see the need (especially since Twinkle doesn't add this param anyway?).
Primefac (
talk) 18:10, 21 March 2021 (UTC)
I noticed that both in the selection menu (for selecting which Rcats to use) and in the actual wikitext generated, XFDcloser uses {{R from less specific name}}}
(note the extra closing curly bracket). See
diff #1020394565 as an example.
Tol |
Talk |
Contribs 20:57, 28 April 2021 (UTC)
Actions will be applied to this redirect's target page. To use the nominated page instead, undo the redirection before continuing.
I just started using this gadget, and I'm having problems understanding the unlinking part. The first part is telling it to unlink backlinks; what exactly does that do? The next part is it gives me a list of pages with the unlinked badlinks saying that they can be edited unless they are transcluded. The problem is there's no way to tell which pages listed can in fact be edited. The it unlinks the backlinks (again not sure what that means). Usually it then gives me options as to what to do with the unlinked badlinks (the one I'm doing right now doesn't give me any options, not sure why). What I want to do depends on the page. If, for example, it's a page that lists notable people, I'd want to remove the entry. If, however, it's an actor and they're in a cast section of the page, I want to leave the item but remove the redlink. I don't see how to do the latter.
Thanks for any help.-- Bbb23 ( talk) 15:28, 3 June 2021 (UTC)
And it is said that bar won the race...it would just turn bar into bar.
It would be nice to hit the /sandbox, /doc, and /testcases subpages when a TFD is closed as delete (now, rather than holding), and possibly associated redirects. (Maybe with checkmarks? Not sure.) In almost all my recent deletes there I've had to open the 'subpages' link and then manually G8 the remaining subpages. Izno ( talk) 16:47, 24 May 2021 (UTC)
So XFDC should only perform the unlink and not remove AfD tags. If it does the latter, it might need some sort of check to make sure the AfD tag matches the AfD in question. czar 13:37, 23 July 2021 (UTC)
TfD is currently experiencing some quite severe PEIS issues with {{
Tfd links}} being the main culprit. By using the module directly instead could reduce the size significantly. Therefore I believe XfDCloser should on top of the * {{tfd links|__PAGE__}}\n
format also recognize * {{#invoke:tfd links|main|__PAGE__}}\n
. --
Trialpears (
talk) 22:04, 3 August 2021 (UTC)
Please take a look at Wikipedia:Articles for deletion/Log/2021 August 7 - there are entries which were relisted but which were not properly commented out ( manual fix) nor copied over ( idem) to the next log page. RandomCanadian ( talk / contribs) 17:27, 15 August 2021 (UTC)
Please see
this discussion. It appears that XFDcloser is unable to delete pages in the Wikipedia talk:
namespace if they are nominated directly.
Evad37, is there an easy way to solve this issue?
✗
plicit 06:47, 16 September 2021 (UTC)
When I closed Wikipedia:Articles for deletion/Living presidents of the United States, XFDCloser deleted the secondary article ( Living vice presidents of the United States), but not the main one. I haven't closed any other multi-AfDs to be able to tell you if this is a recurrent problem, but this behaviour was unexpected. Did I do something wrong, or is this a bug? – bradv 🍁 23:43, 4 September 2021 (UTC)
Some excess colons were removed {{ Cfd2}}, {{ Cfm2}}, {{ Cfr2}} and {{ Cfs2}}, per Template talk:Cfd2#Remove leading colons. I don't know if this would break XFDcloser, but if something starts going wrong in CfD closure process, this could be the reason. – SD0001 ( talk) 03:14, 25 October 2021 (UTC)
Special:Diff/1055247133-- not sure what happened, bu it wasn't me... Eddie891 Talk Work 19:31, 14 November 2021 (UTC)
working on the merge backlog, I'm coming across quite a few articles (in the May list I'm working on) where
Afd-merge to was added without adding
Afd-merge from on the target, and these seem to be generate by the use of XFDcloser. For example:
I wonder whether XFDcloser might include this step (as suggest in the Adf-merge to documentation) to include this step, as it should help to advertise the need for a merge on the high-traffic target pages.
Klbrain (
talk) 13:23, 9 October 2021 (UTC)
Review unlinked list item
A backlink has been removed from the following list item:
List:
List of children's television series by country#Australia
I saw this today, and when I clicked through the link it brought me to this broken link. So there's an error in the URL encoding/escaped character. Note that in my example I replaced the ampersand character (as it was displayed to me) with the character reference so that it would display properly here. But as it reads to you, that's how it looked to me. czar 16:21, 25 November 2021 (UTC)
See Special:Diff/1064766039. Some well-meaning person, apparently not realizing that {{ subst:rfd2}} includes an anchor to serve as a fallback for when the redirect's name isn't the same as the header, added a bunch of anchors to this RfD section heading. When I went to close the RfD, it aborted because it could not find the section heading, showing a grayed-out abort button and a blue close button, without any message (like Twinkle has and SPIhelper have for failed-to-saves) giving me a copy of what I'd written.
The failure seems like a bug—the script shouldn't rely on the displayed section heading being the same as the wikitext section heading, because that's not a guarantee with MediaWiki—but would be less of an issue if the feature I referenced were implemented. -- Tamzin cetacean needed (she/they) 03:30, 10 January 2022 (UTC)
Hi, it was brought to my attention that XFDcloser is not updating the dates on templates when relisting WP:RFD discussions, as it failed to do here. This is an issue I noticed when a second relist was performed, but now it doesn't seem to update the date at all. ✗ plicit 00:51, 26 June 2021 (UTC)
I love the little "Show/Hide closed discussions" button but it would be even better to have its corrolary now that XFDC can see closure-eligible discussions. It would only show the "amber" and "green" discussions (i.e., ready for closure), filtering out the "red", when viewing any given AfD log. I imagine there are a few different ways to approach, but one idea would be to use the same button and toggle between the three filtered states (Show all discussions/Hide discussions ineligible for closure/Hide only closed discussions). Another option would be to ignore that third option and only toggle between the first two. czar 00:34, 10 January 2022 (UTC)
TODO - investigate this issue when an AFD'd page is moved. Situation can also occur if the page is just replaced with a redirect to an already-existing page (an out-of-process redirection, since that shouldn't be happening during the AFD discussion) XFDcloser should be asking the closer if the actions should be applied to the redirect's target or the redirect. My suspicion is that the wording presented to the closer using XFDC isn't clear enough, so the option they choose results in the old afd template being placed on the wrong page. Another possibility is something going wrong within the script itself. Ping @ Wbm1058: who has come across several, see their contributions on 2022-01-11 approx 05:00 to 06:00UTC - Evad37 [ talk 14:15, 11 January 2022 (UTC)
Just had an idea: the script should be able to check the age of redirect. If created as the result of a move, it would have been created after the xfd discussion started. Whereas an out-of-process redirection would just be an additional edit, so the page would have been created before the xfd discussion started. - Evad37 [ talk 14:25, 11 January 2022 (UTC)
Extracted from Wikipedia talk:Articles for deletion#Bug/edge case in XFDcloser tool ( permalink):
By the time Wikipedia:Articles for deletion/İkinci Ərəbcəbirli closed as "speedy keep" the page had been moved to Arabdzhabirli Vtoroye "per WP:NCGN."
When Buidhe closed it using the XFDcloser tool, it put the {{ Old AfD multi}} template at the top of the redirect page, breaking the redirect.
I removed it from the redirect and added it to the renamed page.
Please consider fixing this issue in a future release. If a fix is not feasible, please consider detecting it as an error or warning if that is not already being done.
davidwr/(
talk)/(
contribs) 16:27, 27 February 2020 (UTC)
#REDIRECT
line (and any other existing content). -
Evad37 [
talk 00:38, 28 February 2020 (UTC)
Found this thread while following up on the unusual situation discussed at User talk:Sandstein § Article still around six months after delete close ( Special:Permalink/1067398279). Was going to suggest a feature similar to what Evad37 says is meant to already happen. Sandstein, I know it was six months ago, but I don't suppose you recall if you got any warning message when deleting that page? And @Evad, is the warning in this case just the generic "not tagged" warning, or does it explicitly say that the page is now a redirect? Because, if the former, I could see that bamboozling a closer who gets the "not tagged" warning, clicks the link, gets redirected to the new page, doesn't notice that they've been redirected, sees the XfD tag, and thinks "Huh, XFDcloser being weird I guess". -- Tamzin cetacean needed (she/they) 08:20, 23 January 2022 (UTC)
Following this discussion it was determined that new TFD discussions should be added to the bottom of the relevant daily log page. At this discussion it was mentioned that XFDC wasn't updated, and when relists occur they are being added at the top of the page. I don't know how easy a fix this will be, but changing it would be much appreciated so that XFCD is in line with current TFD practices. Thanks! Primefac ( talk) 15:44, 5 February 2022 (UTC)
The "Result is a new sentence" checkbox does not really mean what it says. What it actually does is "Rationale is a new sentence". That's had me confused for years. Spinning Spark 17:29, 3 February 2022 (UTC)
I closed a CfD at Wikipedia:Categories for discussion/Log/2021 December 4#Recording artists using XfDcloser with consensus to rename all 5 categories, and the outcome wasn't implemented automatically. See also this AWBREQ report, where I have filed a request to clean this up. – LaundryPizza03 ( d c̄) 05:08, 11 February 2022 (UTC)
An issue came up at WP:AN involving outstanding AfD closures. Upon investigation, I found that a user had re-listed seven AfDs using XFDcloser, but whilst they were all removed from the February 3 log, only two of them had been added to the February 10 log ( Link). Is this likely to be a glitch at the user's end, or is it something that might happen again? Black Kite (talk) 22:59, 14 March 2022 (UTC)
So ... there's been some bugs with this gadget for a while, especially bugs with matters which pertain to WP:RFD. In addition, the only editor who seems to maintain this tool has not edited for about 3 months now. Unless someone else wants to take over responsibility for maintaining this gadget, I think it's time for it to no longer be a gadget. Steel1943 ( talk) 03:28, 28 April 2022 (UTC)
Hi! At Wikipedia_talk:XFDcloser#Advance_notice:_Version_4_deployment, it was noted that @ Randykitty's request re: not having backlinks clutter watchlist was addressed. Do any of the gadget users know where to toggle that? I hadn't much worried about it, until Wikipedia:Articles for deletion/Futsal positions murdered my watchlist. Thanks! Star Mississippi 16:47, 30 April 2022 (UTC)
Can anyone produce a list of pages in the "Template:" namespace which XFDcloser is reliant on? I'm wanting to create a template similar to {{ Twinkle standard installation}} to put on those pages to notifying editors to take care when editing those templates to make sure the edits don't break XFDcloser if they are major. Steel1943 ( talk) 02:09, 1 May 2022 (UTC)
Hello, folks,
I closed some deletion discussions at Wikipedia:Redirects for discussion/Log/2022 March 13 and noticed that the redirects that were supposed to be deleted were not and the RFD tags were still on the pages. I thought, of course, this must be me but then I noticed other discussions closed as "Delete" by Explicit also had existing redirects that were supposed to be deleted but were not. XFDcloser closes the discussion properly, just doesn't follow through on the deletion decision. I'm not sure if this is also an issue on other deletion discussion forums but if it was, I'd expect to see messages here already. Thanks for any help you can provide. Liz Read! Talk! 22:19, 20 March 2022 (UTC)
The title says it all. Steel1943 ( talk) 22:08, 25 March 2022 (UTC)
Evad37 is the sole developer, and last made an edit on January 22. MediaWiki:Gadget-XFDcloser.js last updated on 31 January 2021, deploying version 4, and MediaWiki:Gadget-XFDcloser-core.js last updated 22 January 2022 (fix missing rationale input). MediaWiki:Gadget-XFDcloser-core.css was deployed 31 January 2021 (version 4), and hasn't been changed since. I don't know what could have changed around March 20 that would have broken anything that previously worked, other than maybe a MediaWiki software update. Anyone with a good working knowledge of javascript might investigate to better diagnose the issue. – wbm1058 ( talk) 02:05, 28 March 2022 (UTC)
I can't imagine this could be a bug in XFDcloser. My bet is that the gadget fails to figure out the name of the redirect from the nomination, and that in turn is probably down to the changes that were made to {{ rfd2}} in early March. – Uanfala ( talk) 21:53, 30 April 2022 (UTC)
Fixed ...sort of. XFDcloser will now work on any nominations at RFD that are opened after this time stamp. (Please see the above discussion or further details.) Thanks again to
Uanfala for finding the issue that caused XFDcloser to break on closing RFD nominations.
Steel1943 (
talk) 02:12, 1 May 2022 (UTC)
neither @ Liz nor I are able to close this AfD. I'm not sure if it's space exclamation point or another issue. It says there's an edit conflict, but none actually present. Star Mississippi 00:36, 8 April 2022 (UTC)
"
instead of ''
when this title was created was someone who should have known better as an editor with a permission to bypass the title blacklist. Also, in most cases recently, such titles have qualified for
WP:G6 due to causing technical issues since consecutive apostrophes are interpreted as wiki markup (provided the title is a redirect, of course.)
Steel1943 (
talk) 01:21, 16 July 2022 (UTC)Is there a way to allow a clickthrough on this failure message? I often use XFDcloser to relist orphaned AfD discussions, which definitionally don't have an old logpage. Currently, this requires me to add them to a logpage and then relist it, which is fairly time-consuming. jp× g 23:35, 21 July 2022 (UTC)
Hello,
Midway through looking through today's expiring AFD log page ( Wikipedia:Articles for deletion/Log/2022 August 4), XFDcloser stopped completing relistings. It would relist the discussion on today's log page, for August 11th, but not remove them from the log for August 4th. So, I handled this manually. I had noticed that ocassionally, XFDcloser would do this with relistings (it's probably happened with me about 6 or 7 times) but doing this to two relistings in a row makes me worried that this will become a regular problem. Of course we can go edit the log page ourselves but XFDcloser is normally so reliable, I thought I'd bring the issue to the talk page. Liz Read! Talk! 22:55, 11 August 2022 (UTC)
I added this to the main XFDC page for now; XFDC removes all other content, including WP:RCAT templates, whenever a WP:RFD is closed to any result that alters the nominated redirect. ( Here is an example.) I think the fix here is to remove XFDC's ability to tag redirects with RCAT templates during a close (or fix XFDC's apparently greedy regex used when replacing the content of the redirect being retargeted), but I have no idea how to go about doing or suggesting that. Steel1943 ( talk) 17:14, 19 August 2022 (UTC)
Edit summary links to undefined here: https://en.wikipedia.org/?title=Unified_Payments_Interface&diff=1108464577&oldid=1107719925 – SD0001 ( talk) 09:31, 17 September 2022 (UTC)
Please fix the bug in XFDcloser that sometimes omits the action parameter in {{ Old CfD}}, e.g. [14]. I highlighted this as my "top request" for 2022 above.– Fayenatic London 08:06, 29 August 2022 (UTC)
This relisting edit recorded that a CFD discussion was removed from the 23 September log, but it was not inserted into the 1 October log. I have relisted it today.
Pinging Qwerfjkl in case they have any recollection of the event, although I doubt it after 3 weeks.
This talk page shows that similar failings have been occurring earlier this year with AfD relistings. Are these malfunctions linked? – Fayenatic London 17:57, 21 October 2022 (UTC)
I was wondering how I can get The Revels Group Wikipedia back up. CarsonHolland ( talk) 19:12, 6 February 2023 (UTC)
Close is aborting for
WP:Redirects for discussion/Log/2023 February 8#Invisible Child : Poverty, Survival & Hope in an American City. The error is Possible edit conflict detected, found section heading"Invisible Child : Poverty, Survival & Hope in an American City"
. Note that there is only one section header with that title. Perhaps something to do with the colon or space or space near the colon?
Jay
💬 16:47, 15 February 2023 (UTC)
Hi, I've noticed that XFDcloser automatically removes templates on a redirect page that aren't wrapped in {{ Redirect category shell}}, such as {{ Fictional character redirect}} and its siblings. This creates a hassle for the few editors who watch those redirects, as we then have to manually add the template back. Please fix this ASAP. Thanks. InfiniteNexus ( talk) 05:55, 30 September 2022 (UTC)
When relisting RfD discussions, XfDcloser fails to locate the RfD tag to update the link. It is possible that the format of Template:RfD has changed since this feature was last updated. – LaundryPizza03 ( d c̄) 12:05, 14 May 2023 (UTC)
This is a courtesy disclosure that I have tinkered with Template:Cfm2 and Template:Cfd all (showing the parameter label target2 on the category page) in order to make Template:Cfm-double correctly prepare the standard discussion starter. I do not expect my edits to adversely affect XFDcloser, because the CFD log entries should still be in the same format, and I do not think the change in the category page template will affect the process for its removal. However, if XFDcloser now malfunctions with merges, then please revert my changes to those templates and ping me. – Fayenatic London 13:07, 31 May 2023 (UTC)