add warnings to rebuildrecentchanges.php
Closed, InvalidPublic
Actions

Assigned To

None

Authored By

	Jidanni
	Dec 7 2006, 5:53 PM

Description

Following up [Bug 7948] importDump.php: warn no Recentchanges,
our attention now shifts to rebuildrecentchanges.php

RC> Well, has one tested the script against one's database?
$ m="http://localhost/mediawiki/index.php?title=Special:Recentchanges&limit=1000&days=222"
(By the way, tweak much higher and limit snaps back to 50 etc. etc.)
$ w3m -dump $m|wc

241  1354 12512

$ cd /var/lib/mediawiki1.7/maintenance
$ php rebuildrecentchanges.php
Loading from page and revision tables...
Updating links...
Done.
$ w3m -dump $m|wc

56   107  1288

I.e., well gosh, it wiped out all the Recentchanges.
Maybe because my last change was 10 days ago.
Anyway, ho hum, confidence shaken, just another maintenance program
"that must be tailored to big wikis, but for me something to not dare
execute a second time."

Conclusion: at least add warnings inside rebuildrecentchanges.php

Version: 1.7.x
Severity: minor
OS: Linux
Platform: PC

Details

Reference: bz8183

Event Timeline

• bzimport raised the priority of this task from to Low.Nov 21 2014, 9:32 PM

• bzimport added a project: MediaWiki-Parser.

• bzimport set Reference to bz8183.

• bzimport added a subscriber: Unknown Object (MLST).

Jidanni created this task.Dec 7 2006, 5:53 PM

robchur wrote:

You're running a *rebuild* script. Doesn't this suggest that, perhaps, we might
dare to rebuild the recent changes table? The recent change age ought to be
customisable in LocalSettings.php, although whether or not it's observed in the
rebuild script is another matter.

add warnings to rebuildrecentchanges.phpClosed, InvalidPublicActions

Description

Details

Event Timeline

add warnings to rebuildrecentchanges.php
Closed, InvalidPublic
Actions