Wikipedia talk:Database reports/Broken redirects

Change

Can you change or get rid of the bit where it says "can be deleted without review" as nothing should be deleted without review and I've often been able to fix ones that are on coloured rows. Cheers--Jac16888^Talk 20:24, 10 April 2009 (UTC)

Done. Cheers. --MZMcBride (talk) 06:21, 24 April 2009 (UTC)

Brokenness, now fixed

Seems when I was refactoring some code I accidentally broke this report (a symptom of still using pywikipedia for this one report). Fixed now. Let me know if you see any breakage elsewhere. --MZMcBride (talk) 00:37, 3 May 2009 (UTC)

Honest policies

In the interests of morality, we should remember from time to time that the policy that forbids ALL redirects to non-existent pages was not created by an honest process, but by bullies. This happened in the spring of 2005. Michael Hardy (talk) 02:10, 4 June 2009 (UTC)

I love you. --MZMcBride (talk) 06:05, 4 June 2009 (UTC)

I've written to Brion Vibber about this. Bug #378 deals with the fact that links to redirects to non-existent pages appear as blue links, whereas they should be red links. If that bug gets fixed, I'm going to propose abolition of the policy against pre-emptive redirects. Michael Hardy (talk) 18:41, 6 June 2009 (UTC)

Redirects with existing targets still listed

Flores Warty Pig and Sus heureni have been listed for nearly a month, despite the fact that they both redirect to the existing page Flores warty pig. The same is now happening with the airport-related redirects. Is this a bug, or a known issue with a foreseeable repair? — ξ^xplicit 01:01, 27 June 2012 (UTC)

It looks like someone went through (very recently) and null edited these pages, which was essentially going to be my advice. I'm re-running the report manually now to see if those null edits clear out the bad results. --MZMcBride (talk) 01:24, 27 June 2012 (UTC)

Hmm, nope. Database is corrupt: <https://jira.toolserver.org/browse/TS-1431>. --MZMcBride (talk) 01:48, 27 June 2012 (UTC)

Looks like everything is fixed. Thank you for looking into it. — ξ^xplicit 04:26, 5 July 2012 (UTC)

Heh, it's really not fixed. thyme's copy of enwiki is still corrupt. I switched database reports to use rosemary today (in order to temporarily fix a separate report). I guess it had the inadvertent effect of fixing this report as well. Still, someone ought to fix thyme.... --MZMcBride (talk) 04:45, 5 July 2012 (UTC)

It seems like it's happening again, and it's getting progressively worse. — ξ^xplicit 00:52, 12 November 2012 (UTC)

enwiki exists on two Toolserver hosts: thyme and rosemary. Currently, both copies are corrupt.

The Toolserver admins are re-importing the databases now. You can follow their progress here: <http://lists.wikimedia.org/pipermail/toolserver-l/2012-November/date.html>. (Scroll down and read any message with "sql-s1" in its subject line. enwiki is part of the S1 cluster.)

Once the databases have been re-imported, if you're still seeing issues in this report's output, please let me know. --MZMcBride (talk) 00:56, 12 November 2012 (UTC)

Intentionally broken redirects: testcase in userspace

I created a testcase in userspace for a special type of broken redirect. Specifically, the target is malformed because it starts with #, and I did this to test an edge case (now fixed) in (my customized) linkclassifier script in which the link's tooltip would be removed entirely. The original linkclassifier is theoretically still affected.

The page in question currently appears on this report. Is anyone expecting me to {{db-u1}} the redirect to remove it from here? Or may I keep it around in case future testing requires it? --SoledadKabocha (talk) 03:38, 22 October 2013 (UTC)

language articles okay

69% of this list in mainspace have the word "language" in them. Nearly all of them are to anchored targets in List of unclassified languages of South America. Looks like they were just added w the latest update, though they were created months ago. I've checked several hundred, and all are fine, except that Russbot dropped the anchor when fixing dbl rd's. [Looks like this bug has now been fixed.] The three rd's beginning in "ISO_" are also correct. I don't want to just delete them from the db, since I don't know why they were mistakenly tagged as broken.

Okay, you can remove all 500. 3 rd's beginning w "Signed" rd. as iw's. Please advise if there's a better way to do that. — kwami (talk) 01:27, 10 January 2014 (UTC)

You might want to check RussBot's edits, to see if you can catch & fix where the anchors were dropped. — kwami (talk) 01:55, 10 January 2014 (UTC)

The current version of the database report seems to be useless as a large number of the redirects in it aren't broken. There's no point in removing wrong entries manually as you (User:Kwamikagami) did; the bot will just ignore that next time the page is updated. Maybe User:MZMcBride needs to do something with the bot. --Stefan2 (talk) 20:59, 13 January 2014 (UTC)