Re: View Counts
Posted: Fri Feb 14, 2014 4:53 am
Is the view counts having problems, or is it officially gone?
I'm pretty sure TLG disabled it again, in favor of faster caching.RikiNutcase wrote:Is the view counts having problems, or is it officially gone?
thelastguardian wrote:More importantly, however, is that the server is getting overloaded. Mediawiki is not very efficient and requires much computation power. One common way to cut down on usage is to disable the page counter and enable caching.
However every time I do that, people start complaining.
We still have spammers so i think that is a bigger problem.Nurin wrote:thelastguardian wrote:More importantly, however, is that the server is getting overloaded. Mediawiki is not very efficient and requires much computation power. One common way to cut down on usage is to disable the page counter and enable caching.
However every time I do that, people start complaining.
^that...
We already changed to a new server, but still...
It would be a bit tricky because of the same-origin policy, i.e. you can't easily call another website via AJAX. A common workaround is using a script (or img) tag to force the browser to load the external site nonetheless (see JSONP). But in general I think it would be better to use the load event on all pages, because you have no guarantee that the request will be fired at all when the user leaves the page after the click event. On the other hand, using that workaround, the user will have to load additional content if you use an external script, increasing the loading time depending on the bandwidth of the external server.I was imagining some kind of javascript click counter. "Onclick", it'll submit things to a third party database that tracks the number of times a link on the sidebar is clicked. Would this work on BT (provided the code is added to common.js)? XDD
I think we would have to deal with that problem either way, since there would still be a "data manager" who has access to the server (unless we collectively rent a server that is, but that's overkill) — with the difference that Google might be more reliable than a (probably) cheap server, both in terms of stability and accessibility.Aorii wrote:Although account permission management with Analytics may prove more annoying, as Analytics is only accessed via Google account and permission given on such a basis. Since the extension seems to modify wiki's general setting and thus forcibly tie all pageview counting for the entire site into one Google Analytics account, information dissemination may require a lot of managing...
I volunteer Simon. XDEusthEnoptEron wrote:I think we would have to deal with that problem either way, since there would still be a "data manager" who has access to the server (unless we collectively rent a server that is, but that's overkill) — with the difference that Google might be more reliable than a (probably) cheap server, both in terms of stability and accessibility.Aorii wrote:Although account permission management with Analytics may prove more annoying, as Analytics is only accessed via Google account and permission given on such a basis. Since the extension seems to modify wiki's general setting and thus forcibly tie all pageview counting for the entire site into one Google Analytics account, information dissemination may require a lot of managing...
Speaking of which, I just exported the pageview data that I have collected for my lil' statistics web app. Those who are interested can grab them here. All saved as CSV files, but there's also an Excel workbook with a nice chart.