Last modified: 2010-05-15 15:41:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8183 - add warnings to rebuildrecentchanges.php
add warnings to rebuildrecentchanges.php
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
PC Linux
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-12-07 17:53 UTC by Dan Jacobson
Modified: 2010-05-15 15:41 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Dan Jacobson 2006-12-07 17:53:35 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...
$ 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
Comment 1 Rob Church 2006-12-09 09:45:17 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.