Last modified: 2014-09-26 01:21:43 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 T43327, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 41327 - Add page views graph(s) to MediaWiki's info action
Add page views graph(s) to MediaWiki's info action
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: analytics
Depends on: 43666
Blocks: 38450 41326
  Show dependency tree / graph
 
Reported: 2012-10-23 21:28 UTC by MZMcBride
Modified: 2014-09-26 01:21 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description MZMcBride 2012-10-23 21:28:29 UTC 
It would be nice to have a graph/graphs of page views over time in MediaWiki's info action.
Comment 1 MZMcBride 2012-10-24 02:39:14 UTC 
I talked to David S. about this earlier today. The problem currently is that this data simply isn't available (yet). The analytics infrastructure simply isn't there (yet!). I think we'll see a usable API by the end of 2013.

In the meantime, this gives us a bit over a year to get the feature request we do already have data for (bug 41329, "Add edit history graph(s) to MediaWiki's info action") implemented nicely (sanely). :-)  This bug is going to be open for a bit, even though it's not really directly actionable right now.
Comment 2 Tyler Romeo 2012-11-04 05:29:06 UTC 
Well, there's no way this can be done on server-side, because that would mess up Squid caching completely. The only option would be to some sort of JavaScript that reports back to the server, which would then enqueue a Job. I would guess the actual DB update would only occur after a certain number of views. The only problem is that jobs are stored in the database, so it would mean a query anyway, so there may just have to be a separate caching mechanism.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links