Last modified: 2014-02-12 23:32:45 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 T49739, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47739 - initStats.php help message is misleading about noviews and update options
initStats.php help message is misleading about noviews and update options
Status: NEW
Product: MediaWiki
Classification: Unclassified
Maintenance scripts (Other open bugs)
1.20.x
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-26 16:54 UTC by Dan Barrett
Modified: 2014-02-12 23:32 UTC (History)
0 users

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


Attachments

Description Dan Barrett 2013-04-26 16:54:08 UTC
The initStats.php maintenance script has a confusing help message.

1. It gives this description of the "noviews" option:

    --noviews: Don't update the page view counter

The phrase "Don't update" is ambiguous, sounding like the page view counter will be left alone. In fact, it sets the page view counter to zero, according to showStats.php. Perhaps the help message should really be, "Do not calculate Total Views: set its value in the cache to zero."

2. The description of the "update" option is:

    --update: Update the existing statistics (preserves the ss_total_views field)

How is this different from the default behavior when initStats.php is invoked WITHOUT the --update option? To my eye (as an end-user, not reading the SiteStatsInit source code), it also seems to update the existing statistics and preserve the ss_total_views field. Is there a better way to explain what $counter->update() vs. the default $counter->refresh() does?

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


Navigation
Links