Extension talk:UserSnoop
Suggestion
editSaw your quick fix for the UserPageViewTracker and it worked for UserSnoop too (Super thanks!!). Do you think you could make it so that you can either search the user list (ajax would be great) or pick users from a drop down list?
Since the UserSnoop does what the UserPageTracker does, are you going to just continue one of them and improve it?
Also you might want to take a look at http://firestats.cc/ your plugin would be great if you could integrate that into a full blown statistics system.
SellFone 07:30, 4 December 2007 (UTC)
- Thanks! I am thinking about continuing the UserSnoop extension and add more functionality to it going forward. I have considered extending it all the way to a full wiki stats extension but, haven't really had the time to dedicate to it. My paying job takes precedence :) Perhaps over the holidays. --Kimon 18:14, 4 December 2007 (UTC)
- Great extension, i think you should extend it to a full statistic extension. I would like to request a feature: I would like to see a special page showing all external links of the wiki, with total of clicks of each external link. Will be interesting too, if we have an option to show this information between specifics periods. What do you think? Lleoliveirabr 02:02, 9 December 2007 (UTC)
- Thanks for your kind words! I'll give it a try --Kimon 02:13, 9 December 2007 (UTC)
- I think we could have a statistic extension, this could log everything, and real live statistics. like this examples: http://www.getclicky.com/ and http://feedback.phpmyvisites.net/feedbacks/2630-last-n-visitor-details-config-info-path-etc look the comments. Could have an option to search an IP and see all activity of the user or IP user in the wiki.
- Better: As phpmyvisites statistic program is now http://piwik.org/ i think you could help in development and try to port it to Mediawiki, Add more features and so on.. What do you think?
SQL
editI get following error when trying to run UserPageHits.sql (in phpMyAdmin).
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'VIEW `user_page_hits` AS SELECT `u`.`user_name` AS `user_name`, `u`.`' at line 1
--Mopster 20:00, 5 December 2007 (UTC)
- Hmmmm.... I just copy & pasted this into my test DB and it worked fine. I'm running on MySQL 5.0.41-community. What version are you running? (Execute "select @@version"). --Kimon 20:26, 5 December 2007 (UTC)
Mediawiki 1.7.1? (Debian stable version)
editCan you make this extension work with Mediawiki 1.7.1? That's the Mediawiki version that Debian Etch uses.
I get:
Warning: require_once(/var/lib/mediawiki1.7/includes/Pager.php) [function.require-once]: failed to open stream: No such file or directory in /var/lib/mediawiki1.7/extensions/usersnoop/UserSnoop.php on line 489
The file Pager.php does not seem to exist in Mediawiki version 1.7.1.
Todu 00:17, 6 December 2007 (UTC)
- Pager.php is a required file for this extension. I don't know when this was introduced to MediaWiki (I'll have to do some research) but, without it, you won't get the pagination of the results. Would it be possible to upgrade to a newer version? --Kimon 01:20, 6 December 2007 (UTC)
- I need to stay with 1.7.1 for security reasons. My policy is to stay with whatever version is included in the current Debian stable distribution. That way I get a very secure installation with the obvious drawback of not getting the latest features. Is there a possibility for a workaround? I could live with less functionality of your extension if needed. Btw: I'm the same guy commenting on your BreadCrumbs extension implementation. Todu 14:23, 6 December 2007 (UTC)
- I know :) - sent you an email in response.
- I'll try to do some research into what is not available in 1.7.1 and what workarounds I can come up with. BTW, is your wiki public? --Kimon 14:30, 6 December 2007 (UTC)
- [OT] Thanks. I have two wikis. The first is a personal wiki only localhost can access that I use as a form of diary/notepad. The second wiki I use for work. We are four coworkers who often get insults from our boss about us forgetting stuff he has told us. He emails us stuff that we are supposed to remember. But it's so much stuff now that we need to document how we work or we will keep forgetting. One of us asked the others if anyone knew of a system we could use to help us remember. I suggested and demonstrated a wiki and the other three coworkers all wanted one. So I try to install extensions that would make our job even easier. I installed your Breadcrumbs extension because we work with customer support over the phone and need to switch between more or less related documentation as we speak to the customer. It's quite stressful and a breadcrumb function would help us toggle between pages that are related to a particular issue we are having with the current customer we are talking to.
- I need to stay with 1.7.1 for security reasons. My policy is to stay with whatever version is included in the current Debian stable distribution. That way I get a very secure installation with the obvious drawback of not getting the latest features. Is there a possibility for a workaround? I could live with less functionality of your extension if needed. Btw: I'm the same guy commenting on your BreadCrumbs extension implementation. Todu 14:23, 6 December 2007 (UTC)
- As our wiki is new and none of us has ever worked with one (we tried to remember everything without documentation) I figured this extension would help us find differences in how we use the wiki. And that would lead to a discussion about "tricks" one of us uses but the others do not. We could also see if we should reorganize our pages depending on the statistics UserSnoop could provide for us. So what I want from this extension is the function to be able to see who has watched what page, how many times. If there are differences there, then we would know that we work differently. Lets say one of us has very many hits on a page that the others have almost no hits to. Then we could ask the person with many hits what is so useful with that page that he keeps reloading it so often. The built in counter only reports per page hit counts, not per user per page hit counts. Maybe your UserPageViewTracker would be easier to make work with Mediawiki 1.7.1 since it has only that particular function? I haven't tried to install that extension yet. It says it's only been tested with v1.10 Todu 00:01, 9 December 2007 (UTC)
- Do you run any public wikis? Todu 00:02, 9 December 2007 (UTC)
- As this is not relevant to the extension, let's continue this on my talk page or in email.
- Specifically on the implementation of this extension on 1.7.1.... I don't see a good solution without backporting Pager.php
- What I would suggest to get what you want would be to use UserPageViewTracker without implementing the special page. This way the data will be updated/stored in the db and you could then query the data via whatever db client you want. The alternative is to generate a LONG list with the data. I know there is a QueryPage.php file which may do the same but, it may take a while to figure out what the differences are --Kimon 01:15, 9 December 2007 (UTC)
- Ok thanks I'll try to do that as soon as our wiki grows a little. Hopefully someone will have made an extension to make this easier by then. We have just started using it. I updated your talk page regarding the OT part of this conversation. Todu 17:26, 9 December 2007 (UTC)
- Do you run any public wikis? Todu 00:02, 9 December 2007 (UTC)
- As our wiki is new and none of us has ever worked with one (we tried to remember everything without documentation) I figured this extension would help us find differences in how we use the wiki. And that would lead to a discussion about "tricks" one of us uses but the others do not. We could also see if we should reorganize our pages depending on the statistics UserSnoop could provide for us. So what I want from this extension is the function to be able to see who has watched what page, how many times. If there are differences there, then we would know that we work differently. Lets say one of us has very many hits on a page that the others have almost no hits to. Then we could ask the person with many hits what is so useful with that page that he keeps reloading it so often. The built in counter only reports per page hit counts, not per user per page hit counts. Maybe your UserPageViewTracker would be easier to make work with Mediawiki 1.7.1 since it has only that particular function? I haven't tried to install that extension yet. It says it's only been tested with v1.10 Todu 00:01, 9 December 2007 (UTC)
spreadBlock
editcase 'spreadblock':
if($this->newUser->isBlocked()) {
$this->blockUser($this->uid);
}
$this->newUser->spreadBlock();
break;
Probably a bad idea. This just blocks the user who calls it. What you want is something like what Block::doRetroactiveAutoblock does. Werdna 23:20, 9 December 2007 (UTC)
- Hmmmmm didn't happen when I was testing.... will have to check it out. But, admittedly, I don't use that button, I just block. Thanks for pointing it out.--Kimon 01:24, 10 December 2007 (UTC)
Slight edit to UserSnoop.php for lazy users !!
editI found it a bit of a hassle to always type the user's name exactly as it was registered, mainly with a First letter as capital and the rest as lowercase ...
In my Wiki, its aimed at Radio Amateurs (Hams) who 'usually' use the callsigns as usernames. (e.g ZS6RO, W1AW) .. These get transformed to 'Zs6ro and 'W1aw' .. For the lazy Ham, this a real pain !!
So, in line 146 of UserSnoop.php I changed this line from
$this->targetUser = isset($par) ? $par : $wgRequest->getVal( 'username' );
to --
$this->targetUser = isset($par) ? $par : ucfirst(strtolower($wgRequest->getVal( 'username' )));
This solved my problem - A user can type a username in any mixture of lower or/and uppercase ..
I'm assuming this won't cause any 'bugs' to raise their respective heads ??
--Dick 08:01, 8 January 2008 (UTC)
- Cool! But, I can't see this happening on a wider variety of wikis since usernames are case sensitive on purpose. Great contribution though for those who want to avoid case sensitivity in user names. --Kimon 13:30, 10 January 2008 (UTC)
Database prefix
editHey there,
All of the tables in my database begin with wiki_. When running th SQL queires I've modified the FROM field on the second one to read:
FROM ((`wiki_user` `u` JOIN `wiki_page` `p`) JOIN `user_page_views` `v`)
...I've also tried to create the tables as wiki_user_page_views and wiki_user_page_hits. The initial page (Special:UserSnoop) loads and I can pull up user info such as Username, Real name, E-mail, New talk, etc.
But when I pull up "Page Views" it just refreshes the screen, nothing comes up. When I try to pull up "Watchlist" I get the error:
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "IndexPager::reallyDoQuery (UserSnoopPagerWatchlist)". MySQL returned error "1146: Table 'itwiki.page' doesn't exist (localhost)".
When I try to pull up "New Pages" I get:
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "IndexPager::reallyDoQuery (UserSnoopPagerWatchlist)". MySQL returned error "1146: Table 'itwiki.page' doesn't exist (localhost)".
What a mess!! Does anyone have any suggestions? It seems like the extension wasn't written to take into consideration database prefixes. Any thoughts? Thanks!!
Acook 18:18, 17 January 2008 (UTC)
- As a side note, when I create the table wiki_user_page_views, it seems like it's updating rows, where as user_page_views does not get updated. And neither wiki_user_page_hits or user_page_hits is getting updated at all. Acook 18:20, 17 January 2008 (UTC)
- This is because you have not included the prefix in the final JOIN statement when creating the view. You do not (or should not) have a table named "user_page_views" and you should not have a view named "user_page_hits". Be careful not to create a table with the same name as a view. If your tables have a "wiki_" prefix, your FROM in the VIEW query should be:
FROM ((`wiki_user` `u` JOIN `wiki_page` `p`) JOIN `wiki_user_page_views` `v`)
It works fine for me doing that. --Fungiblename 11:05, 2 March 2009 (UTC)
Fatal error: Class 'AlphabeticPager' not found in D:\wamp\www\mediawiki193\extensions\UserSnoop.php on line 493
editmy wiki version is Mediawiki1.9.3 ,so what's the problem?
Error
editHi, my db gives this error:
#1146 - Table 'wikidb.wiki_user' doesn't exist
What should I do now? ps, my db accepted the other sql... 81.205.35.85 17:19, 18 March 2008 (UTC)
- you might need to remove the wiki_ prefix. Your DB might not have it, which is why it accepted the first but not the 2nd one 70.240.67.10 11:19, 1 April 2008 (UTC)
My screen Turns Blank When Adding the LocalSettings.php Code
edit- The mysql update works fine
- But after I add the code to localsettings.php, my pages all turn blank. Any ideas?
Running MWv 1.9.3 / php 5.2.5 / mysql 5.0.51a
Help
When you say your pages turn all blank, do you mean completely blank? Or do you mean that you see the mediawiki border, but no content. I'll assume completely blank. If that's the case, it typically means that there's a syntax error in what you added to LocalSettings.php. If you cut/paste from this page, did you install UserSnoop.php directly in the extensions directory? (Remember, case matters.) Could you be missing a semicolon at the end of a line?
Notice: Undefined variable: uid in wiki\extensions\UserSnoop\UserSnoop.php on line 178
editHi
I don't know php, so I am not sure where to start investigating. I get this error not only on line 178, but also on other places where uid are used in the function "execute".
I also get this when I go into the user snoop special page: "Notice: Undefined property: UserSnoop::$uid in wiki\extensions\UserSnoop\UserSnoop.php on line 165"
Thanks
I also have had this problem, but don't know enough about php to resolve it. I have MediaWiki 1.14.0 installed and the error occurs on different lines depending on what I am doing:
- Displaying the Special:User_snoop page: Line 165
- Clicking the Search button with action "None" selected: Line 182
- Clicking the Search button with action "Page views" selected: Line 172
- Clicking the Search button with action "Watchlist" selected: Line 175
- Clicking the Search button with action "New pages" selected: Line 178
I've tried restarting the machine this is installed on, but this doesn't resolve. The new tables created ok and I've checked that the php file and localsetting.php look correct. Any help would be greatly appreciated!
change line 155
if($wgRequest->getVal('userid') && $wgRequest->getVal('useraction')) {
to
if($wgRequest->getVal('username') && $wgRequest->getVal('useraction')) {
- That was me btw - --Simon Oliver 14:12, 25 March 2010 (UTC)
Found: Bug when using MediaWiki 1.14.0 - need to add parameter/value for wfGetDB
editI was getting an error starting on line 604 of UserSnoop when running under MW 1.14.0 - it is necessary to replace "wfGetDB()" with "wfGetDB(DB_SLAVE)". This (apparently) fixes the problem.
Quick fix in vim:
vim UserSnoop.php
once in vim (including colons):
:%s/wfGetDB()/wfGetDB(DB_SLAVE)/g :wq
--Fungiblename 11:01, 2 March 2009 (UTC)
Using postgresql
editmy mediawiki running under postgresql database, how to convert that mysql query to postgresql?
Security Issue
editOn my wiki Children of StarClan it appears that anyone who wishes to can use this extension (I noticed a user on the page, probably having noticed it off the 'whose here' function that comes with our forum). Both logged in as an unregistered user and as a plain registered user I was able to access and use the usersnoop extension.
- I'm using mediawiki 1.15.0
I'm wondering if this issue exists for anyone else and if there's a major security compromise here. At the moment I have the extension commented out of my local settings to protect privacy.
Kitsufox 21:36, 8 November 2009 (UTC)
- The extension's special page didn't actually check whether the user had the
usersnoop
permission. I've fixed this in the code listed on the extension page, but I still recommend you approach this extension with caution, since it hasn't really been maintained in a couple years. —Emufarmers(T|C) 06:01, 12 November 2009 (UTC)
- Is there a currently maintained alternative to this script? I've used it until I noticed the security hole... I'd much prefer something being maintained, that is for sure. Kitsufox 13:56, 12 November 2009 (UTC)
- LookupUser is the best alternative: its authors are trusted and available. It doesn't do all the things this extension does, though. —Emufarmers(T|C) 00:57, 13 November 2009 (UTC)
MediaWiki 1.15
editWhen running this extension on version 1.15 using PHP 5.3.0 I get the following error when trying to display the special page.
PHP Notice: Undefined property: UserSnoop::$uid in c:\Inetpub\wiki\extensions\UserSnoop\UserSnoop.php on line 171
Any suggestions?
show only "new pages" in Main namespace
edithow do I have to change the code in the usersnoop.php in order to show only the "new pages" which are in the "Main" namespace (I am not interested in the other namespaces like "File" or "Category")? Thanks!
1.16 bugs
editJust a note that when any user selects en-gb as their language, this extension makes that account unusable. It also crashed after using the updated code to fix permissions. I'd say it's time to stop using this extension for anyone using it who is considering upgrading their software to 1.16. --Resplendent 05:03, 2 August 2010 (UTC)
Fatal error: Call to a member function getDBKey() on a non-object in /var/www/wiki/extensions/UserSnoop.php on line 488
editHello, I'm geting this error, how can it be solved? --Tsouchon 16:58, 19 May 2011 (UTC)
- Uninstall UserSnoop.--87.78.136.143 16:36, 23 July 2011 (UTC)
- I`ve changed previous line from
$title = Title::newFromText($text);
- to
$title = Title::makeTitle(NS_SPECIAL, $text);
- And that worked for me! --pathfinder 18:47, 14 November 2011 (UTC)