Wikipedia:Bots/Requests for approval/AnomieBOT III 4

The following discussion is an archived debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA. The result of the discussion was

Approved.

AnomieBOT III 4

Operator: Anomie (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 14:09, Wednesday, March 15, 2017 (UTC)

Automatic, Supervised, or Manual: Automatic

Programming language(s): Perl

Source code available: User:AnomieBOT/source/tasks/BrokenRedirectDeleter.pm

Function overview: When a redirect was broken by a move-without-redirect, update it instead of deleting it.

Links to relevant discussions (where appropriate): User talk:AnomieBOT/Archive 9#Broken redirects to List of supporting A Series of Unfortunate Events characters

Edit period(s): Continuous

Estimated number of pages affected: Depends how often people move-without-redirect and don't fix incoming redirects first.

Exclusion compliant (Y/N): Yes

Already has a bot flag (Y/N): Yes

Function details: Before deleting a broken redirect per Wikipedia:Bots/Requests for approval/AnomieBOT III, the bot will check if the most recent log entry for the target page was a move with the 'suppressredirect' flag set. If so, it will look at the target of the move, bypassing double redirects and following further chains of moves-without-redirects, and update the broken redirect's target instead of deleting it if the eventual target of the move still exists. If the eventual target does not exist, the broken redirect will be deleted as before.

Discussion

Until this is approved, I've adjusted the task to ignore redirects that would be fixed by this task (they'll be logged to User:AnomieBOT III/Broken redirects#Recently changed instead). If a trial is approved before someone manually takes care of the redirects complained about in User talk:AnomieBOT/Archive 9#Broken redirects to List of supporting A Series of Unfortunate Events characters, I'll undelete them and let the bot fix them for the trial. Anomie ⚔ 14:09, 15 March 2017 (UTC)[reply]

Which namespace(s) does this affect? What about cross-namespace moves (is that even possible?)?

Approved for trial (current batch). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Everything looks good otherwise. — HELLKNOWZ ▎TALK 15:15, 15 March 2017 (UTC)[reply]

It'll do this in every namespace except the user and user talk namespaces, since the bot doesn't process broken redirects in those namespaces. The code that's up at this moment will create cross-namespace redirects, but I'm going to change that to ignore cross-namespace moves and cross-namespace double redirects before starting the trial now that you pointed it out. Anomie ⚔ 19:37, 15 March 2017 (UTC)[reply]

Trial complete. edits and deletions. The interesting ones here are obviously the "Redirecting $FROM to $TO following a move-without-redirect of $OLD". Anomie ⚔ 00:51, 16 March 2017 (UTC)[reply]

There are also e.g. Association Of Muslim Clerics, Muslim Clerics' Association, Muslim Clerics Association, and Association of Moslem Scholars redirecting to Association of muslim scholars, which Beeblebrox moved back to Association of Muslim Scholars using suppressredirect. Their latest edits were all double redirect fixings. There was also previously a redirect at that broken target that was then "deleted by overwriting" by Silver Master. If that redirect gets undeleted, bots would then fix the resulting double redirects. GeoffreyT2000 (talk) 00:17, 14 April 2017 (UTC)[reply]

I have manually fixed the above 4 broken redirects. GeoffreyT2000 (talk) 16:38, 14 April 2017 (UTC)[reply]

Approved. SQL ^{Query me!} 04:00, 22 May 2017 (UTC)[reply]

The above discussion is preserved as an archive of the debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA.