@
Evad37 and
Jo-Jo Eumerus, hey, thought it would be good to centralize feedback here.
It would be good to have an option for hiding closed discussions (especially when hunting for the one that needs closure in a stack of dozens) – perhaps include something like
User:Mr.Z-man/hideClosedAFD.js?
Should also bold the keep rationale in the template:
[1]
I'd also consider not reloading the page after each image is processed (you lose your place, have to reset any toggles like hiding closed discussions, etc.) The tool on Commons marks the item as processed and adds a notice that it'll update on page refresh. (That way you can just keep going through the queue.)
qDel works but it takes a while to process—not sure how the
Commons and
AFD scripts handle it, but they're much faster and might be worth copying czar20:34, 23 July 2016 (UTC)reply
4: Will have to investigate, but doesn't seem to hard.
Done, discussions which have been closed will have the heading striked-out and a note of the close (replacing the close options) - Evad37[
talk05:33, 24 July 2016 (UTC)reply
Working well for me! Thanks for your work! A thought: I can't tell whether the confirmation of deletion is the pop-up or the change in HTML. The pop-up seems redundant and it would be best just to have the HTML change serve as the confirmation czar20:22, 24 July 2016 (UTC)reply
Also if the image is already deleted and I am just closing the discussion (Delete with comment), I get this pop-up: "FFDcloser says: API error: missingtitle", though it closes the section just fine anyway. czar20:37, 24 July 2016 (UTC)reply
Thank you for testing and providing useful feedback. I think I'll change the message delivery to be via the html changes only, and try to differentiate between warnings (something may have gone wrong) and errors (something has definitely gone wrong) - Evad37[
talk00:58, 25 July 2016 (UTC)reply
@
Czar: Done. If no files are detected by the script, it will only offer "[Close]", which will just close the FFD section without making any other edits. - Evad37[
talk05:46, 27 July 2016 (UTC)reply
(Actually, I see you're using your vector.js rather than common.js, so that probably rules out skin-compatibility issues... - Evad37[
talk09:59, 7 August 2016 (UTC))reply
Are the line breaks something the template can handle? I've removed them from a dozen multinoms, which tend to sit if no one can easily close them czar09:55, 15 January 2017 (UTC)reply
All the other XfD processes have newer discussions above older discussion, I didn't realise that FfD was the other way around. I'll look into adjusting the script later today. - Evad37[
talk23:08, 1 September 2016 (UTC)reply
@
Evad37, sometimes a discussion has already been partially closed, and I'll use the "custom keep" rationale to close it out, only to find that the tool re-creates a talk page notice on the deleted file's talk page. E.g., two-file FfD: one file was already deleted as F5 (fair use not in use), and the other is ready to keep. I'll close with a custom keep rationale, and the talk page of the deleted F5 talk page will be re-created, when it should just be skipped. Thanks for your help with this tool—saves a lot of time! czar19:59, 26 December 2016 (UTC)reply
The script expects that for "keep"-type closes, the old ffd template should be added to the talk page (which gets created if it doesn't already exist). It should be possible to fix this by first doing a check to see that the File: page actually exists. - Evad37[
talk07:57, 27 December 2016 (UTC)reply
@
Czar: I've set it to add a linebreak just before the Relist template is added, which should stop it adopting any indentation. Per this edit
[3], this should also solve the formatting of the relist comment. - Evad37[
talk09:53, 15 January 2017 (UTC)reply
Not sure if it's on every file, but sometimes I delete a file and the talk page is not deleted with it. (They should always be deleted with the file as
G8.) czar10:08, 20 January 2017 (UTC)reply
That's on the to-do list for version 2. I think the "sometimes" is because a lot of the time file talk pages haven't been created in the first place. - Evad37[
talk16:04, 20 January 2017 (UTC)reply