Last modified: 2010-05-15 15:41:05 UTC
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
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.
