Closed (works as designed)
Project:
Documentation
Component:
Correction/Clarification
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
25 Apr 2010 at 05:00 UTC
Updated:
25 Mar 2025 at 01:42 UTC
Jump to comment: Most recent
Comments
Comment #1
drummYep, that was manually updated. And I deleted an older scheme that needed Drupal's statistics module, http://drupal.org/cvs?commit=394570. I recommend asking around for Google Analytics access. Maybe even stick 'has book hierarchy' in for segmentation to filter out non-handbook pages.
Comment #2
arianek commentedAh thanks for the update - have posted a discussion on g.d.o to see if anyone is interested in monitoring analytics http://groups.drupal.org/node/81404
Marking this postponed, since it sounds like it's not re-createable automagically. If I find someone who wants to monitor and update the page, I spose it'll republish it.
Comment #3
cliffWell, I'm willing to help, but I got a question from Amazon that threw me for a loop:
Help?
Comment #4
arianek commentedHmm... I wonder how this was being done before then? There were lists kept manually and the stats must have been gathered somehow... wish I knew a bit more of the history there.
I suppose that it'll be obvious with pages with Handbook URL aliases. But Kieran might be right about it being more effective to put a tracking code into handbook pages... which we can't do right now, but will be able to really soon I imagine, once docs.d.o launches.
Comment #5
cliffCan you send me a screenshot of the page I can share with Kieran? That might prompt another idea. Otherwise, I'll let him know that we'll wait until docs.d.o is deployed.
Comment #6
drummGoogle can do http://code.google.com/apis/analytics/docs/tracking/gaTrackingCustomVari.... We use http://drupal.org/project/google_analytics.
Comment #7
arianek commentedcliff - http://drupal.org/handbook/most-popular-pages (which i hadn't looked back at in a while actually has a note that it was being made using AWStats logs... no clue if that's still accessible anyway...) looks like (2 more months below this as stated in the text at the top):
Comment #8
cliff@arianek, AWStats is generally provided free of charge by hosting services. At least I could run it for free on one of the sites I administered recently. It couldn't do fancy stuff, but it could quickly produce easy-to-download reports on page hits, unique visitors, and maybe even ISP of the visitor. But wouldn't one need webmaster-like access to the d.o server to run it?
@drumm, are you saying that if I were to get access to the Google Analytics for d.o I could set up my own report, selecting the pages I wanted reports on — as opposed to having to glean handbook pages by node from a sitewide report? If so, that sounds promising… really promising!
Comment #9
drummAccess won't help right now; we don't log whether node pages are in the book hierarchy or not. We would have to start doing that.
Comment #10
add1sun commentedJust for more background on how this page has worked in the past, originally back in the day we automatically generated the page from Drupal core's statistics module. When we did the upgrade to 6 (I think) statistics module was disabled due to performance concerns and the page went stale. We took that down and (I) started to manually review the AWStats, pick out handbook pages, and then write the popular pages page by hand. It didn't last long as you can see because it was a royal PITA.
Comment #11
add1sun commentedI should add that I was given special access to the AWStats each month by Killes to do this. It is a very manual and not easily accessible way of doing it.
Comment #12
arianek commentedWell, we may need to leave it be until docs.d.o is live then, but I think it'd be valuable information to start gathering again if/when it becomes less difficult - would be good to keep an extra eye on the quality of the popular pages.
Comment #13
arianek commentedadding tags
Comment #14
leehunter commentedIt might be very helpful if the reader could look at the most popular pages *per guide*.
In other words, if I'm a developer I'm probably more interested in what other developers are looking at rather than seeing that the new d7 install guide is hot this month.
When we have tagging it would also be nice to have the option of both "most viewed" and "most starred (or whatever the term is)".
As a reader (and as a docs person) I'd REALLY want to know what other people think is the most valuable information in a given guide.
Comment #15
krina.addweb commentedThis link redirects on 403 page.
Comment #16
quietone commentedNearly nine years and there has been no further support for this. I am going to close this for lack of interest. Re-open, or start of new issue referring to this one, is you want to pursue this.