Problem: Add a checkbox to the (un)delete forms to (un)delete the associated talk page simultaneously with the content page. Add a corresponding parameter to the (un)delete actions in the Action API.
Who would benefit: Administrators
Proposed solution: Self-explanatory.
More comments: There is a fairly recent WIP patch for some of this. However, the sooner this is delivered the better. This may sound trivial, but there is a lot of stuff that gets deleted and therefore will save quite a bit of time.
Thank you MER-C. The only thing demotivating me from completing that patch is really lack of commitment for review. In my understanding PET is not interested in reviewing patch for this feature and there's really no one else to do. If anyone or team is committing to reviewing I can complete it in as far I am available. And by the way I just abandoned that patch because so many things have changed and it would be easier to rewrite from scratch. – Ammarpad (talk) 09:05, 25 November 2020 (UTC)[reply]
@MER-C: This would certainly be useful, but don't forget about the API. (the proposal only mentions "checkbox") When tools and gadgets (like Restore-a-lot and DelReqHandler) can do this, it would save loads of work. And creating a language-independent workaround within the gadget is surprisingly difficult because the gadget doesn't "know" in what namespace a page is and even if it did, can't guess the name of the associated talk namespace, and even if it could, performance is already not great and would be roughly halved. — Alexis Jazz (talk or ping me) 11:42, 25 November 2020 (UTC)[reply]
It only takes two simple API calls to get the name of a pages's associated talk page: One to get the pageid (example) and one to the title from pageid (example). That shouldn't be hard for a tool or gadget to do. --Dipsacus fullonum (talk) 14:30, 25 November 2020 (UTC)[reply]
@Dipsacus fullonum: Thanks! That's easier than what I was thinking of. (a lookup table or something) Performance is still an issue though, and implementing this in gadgets (and having to implement and maintain it in every gadget separately) is likely more error-prone. — Alexis Jazz (talk or ping me) 15:01, 25 November 2020 (UTC)[reply]
Support Maybe also add a warning when deleting a root userpage and this box is ticked. More often than not, user talk pages dont need to be deleted together with the root userpage. Victor Schmidt (talk) 19:54, 8 December 2020 (UTC)[reply]
Comment@GeneralNotability: I am not sure to understand your point of view. This proposal is for talk pages for articles rather than user talk pages. If an article gets deleted, then undeleted, then its associated talk page is permanently gone. MarioSuperstar77 (talk) 11:22, 10 December 2020 (UTC)[reply]
Support It would be nice to have the option as admin to have the check for "not create redirect" would be than active for the talk page, too. Quedel (talk) 21:39, 18 December 2020 (UTC)[reply]
Support Will definitely save time: after an undeletion, I often find that I have to go back to the admin and ask them to also restore the corresponding talk page. Uanfala (talk) 21:00, 19 December 2020 (UTC)[reply]
Support Would be useful to have DannyS712 (talk) 17:58, 8 December 2020 (UTC)
Oppose This is just a hounding/stalking incident waiting to happen, and I don't think the benefits outweigh the risks. GeneralNotability (talk) 23:32, 9 December 2020 (UTC)
Comment @GeneralNotability: I am not sure to understand your point of view. This proposal is for talk pages for articles rather than user talk pages. If an article gets deleted, then undeleted, then its associated talk page is permanently gone. MarioSuperstar77 (talk) 11:22, 10 December 2020 (UTC)
