Last modified: 2010-05-15 15:50:56 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T13220, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 11220 - Error in NUMBEROFARTICLES
Status: RESOLVED DUPLICATE of bug 4650
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-09-06 23:56 UTC by Poon Poi Ming
Modified: 2010-05-15 15:50 UTC (History)
1 user (show)

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


Description Poon Poi Ming 2007-09-06 23:56:21 UTC
My <nowiki>[[Special:Statistics|{{NUMBEROFARTICLES}}]] </nowiki> gives a reading of 18,446,744,073,709,551,610. I have not been able to receive any concrete help, including my webhost and the various forums. I wonder whether I can get any assistance from this platform.
Comment 1 Roan Kattouw 2007-09-07 10:34:53 UTC
This is what happens if there aren't any articles present, not even the Main Page. The software tries to subtract one (the Main Page) from the total of 0,  but since this particular DB field can't handle negative numbers, it'll wrap around to the largest possible number it can handle, which is 2^64-1. Check that $wgContentNamespaces (in LocalSettings.php) isn't empty (for what it should be, see below), and create a page called "Main Page" with at least one wikilink on it. This should bring the total back to zero.

$wgContentNamespaces = array(NS_MAIN);

*** This bug has been marked as a duplicate of bug 4650 ***
Comment 2 Rob Church 2007-09-07 14:40:06 UTC
The usual means to repair the table is to run maintenance/initStats.php from the command line.

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