Extension talk:CheckUser

About this board

Extension info box lists wrong version support

Mcint (talkcontribs)

As of https://phabricator.wikimedia.org/rECHU59f3a1f257384b0370cac4f770403eaa12ce7eea in Mar, or time of merge, this requires MediaWiki >=1.41.0. I tried to edit, but this is pulled automatically by a template and i don't want to dig deeper at the moment.

Additionally the repository is not tagged with the version information as suggested by documentation on the page.

Please: update the requirements pulled into the infobox, and/or push tags to the repo with latest compatible version, e.g. compatible-mw-1.35

Ciencia Al Poder (talkcontribs)

The required version is not pulled from git. It can be edited in the template parameters. You can download a compatible version for 1.35 if you download the REL1_35 branch of this extension, either from git or from extension distributor.

Dreamy Jazz (talkcontribs)
Reply to "Extension info box lists wrong version support"

Upgrade from 1.35→1.39 isn't creating cu_changes.cuc_actor?

4 (talkcontribs)

Just finished troubleshooting an odd condition where Special:RecentChanges completely stopped updating after an "upgrade" to MediaWiki 1.39, reinstalling the supposedly latest-and-greatest version of all installed extensions, including this one.

Debugging with LocalSettings.php settings: $wgDebugDumpSql = true; $wgDebugLogFile = "/var/log/mediawiki/debug-{$wgDBname}.log";

I'd see [DBQuery] attempts to add records to recentchanges, searchindex and the like; I'd also see an attempt to add a record to cu_changes. The latter attempt would fail because cuc_actor apparently does not exist; PHP would dump the call stack and then exit. The end result was no updates to Special:RecentChanges, Special:NewPages, Special:NewImages and possibly others.


ALTER TABLE `cu_changes` ADD `cuc_actor` INT NOT NULL AFTER `cuc_title`;

and rebuilding (on a one-time basis) with rebuildrecentchanges.php seems to bring Special:RecentChanges back to life. I'm seeing this issue on multiple wikis and yes, that is despite running maintenance/update.php

Why is this happening? 23:22, 3 May 2023 (UTC)

Dreamy Jazz (talkcontribs)

What database type are you using?

The update path for the three different supported database types are different. However, all three seem to be working on a visual inspection (so I would need to know what database type you are running to try to re-produce).

Also what version of MediaWiki were you running before updating to 1.39? (talkcontribs)

PHP 7.4.29 MariaDB 10.6.12

A direct jump from MediaWiki 1.35 to 1.39.3 using maintenance/update.php

Dreamy Jazz (talkcontribs)

Thanks. I aim to take a look at this in the next few days.

Reply to "Upgrade from 1.35→1.39 isn't creating cu_changes.cuc_actor?"

Unclear that need to run updater script on newer Mediawiki installations

Hamishmb (talkcontribs)

It is unclear that you need to run the updater script on newer Mediawiki installations for this extension to work, could this be added to the page please?

Wikis Beer (talkcontribs)

Kind of a late reply but I have just had issues of this as well.

I use this after the domain.


Hamishmb (talkcontribs)

Yeah, that's what I ended up doing too. However, it really should be stated clearly somewhere.

I no longer use mediawiki for anything so this isn't of concern to me any more.

Ciencia Al Poder (talkcontribs)
Hamishmb (talkcontribs)

Right you are. I guess either I missed that, or you added it since last year, but either way, this is resolved now I guess.

Cheers :)

ERROR: date/time field value out of range

Justman10000 (talkcontribs)

@Nikerabbit Maybe you can help me here:

Among other things, I have installed the extensions CheckUser and UserGroups! But now this comes up when I change permissions of groups:

Mon Oct 31 15:00:18 CET 2022 debian mediawiki-public- Error 22008 from MediaWiki\CheckUser\Hooks::updateCheckUserData, ERROR: date/time field value out of range: "20221031140018" LINE 1: ...efügt: apihighlimits; Entfernt: (keine)',,0,0,3,'202210311...

HINT: Perhaps you need a different "datestyle" setting. INSERT INTO "cu_changes" (cuc_namespace,cuc_title,cuc_minor,cuc_user,cuc_user_text,cuc_actiontext,cuc_comment,cuc_this_oldid,cuc_last_oldid,cuc_type,cuc_timestamp,cuc_ip,cuc_ip_hex,cuc_xff,cuc_xff_hex,cuc_agent,cuc_page_id) VALUES (-1,'Benutzergruppen/*',0,1,'Justman10000','Justman10000 änderte die Benutzergruppe „*“. Hinzugefügt: apihighlimits; Entfernt: (keine)',,0,0,3,'20221031140018','','5CCEC4F5',0,NULL,'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0',0)

Nikerabbit (talkcontribs)

Most of MediaWiki extensions are not tested with PostgreSQL and contain various incompatibilities. See Manual:PostgreSQL.

Reply to "ERROR: date/time field value out of range"

Error: Class 'Firebase\JWT\JWT' not found

6 (talkcontribs)

Hello folks, I installed this extension on my site and the basic use at Special:CheckUser works fine without any issue, but when I'm running this tool at Special:Investigate and click on the submit button for result I see the follwing error so is there anyone who can help?

"Error: Class 'Firebase\JWT\JWT' not found"

MediaWiki 1.36.1
PHP 7.4.14 (cgi-fcgi)
CheckUser 2.5 (c0771c4) 17:38, 22 July 2021

Thank you

Ciencia Al Poder (talkcontribs)

How did you download it? The extension requires to run composer update, unless you download from Extension Distributor (talkcontribs)

Hello @Ciencia Al Poder: I installed the app by follwing the instructions at Extension:CheckUser#Basic using the Extension Distributor and then added some configuration settings in my LocalSettings.php inclduing $wgCheckUserEnableSpecialInvestigate to true. Everything works fine except the result for special investigation. :|

Ciencia Al Poder (talkcontribs)

Looks like Extension Distributor is not bundling the required composer dependencies again...

If you have shell access, go to the extensions/CheckUser folder and run composer update --no-dev. See Composer for more info. (talkcontribs)

running composer update --no-dev helped in creating those missing files and it's working now. Cheers

Ciencia Al Poder (talkcontribs)

I've just downloaded a snapshot for 1.36.1 and it contains a vendor/firebase/php-jwt folder with those Firebase\JWT\JWT classes. Can you check if you also have those?

Reply to "Error: Class 'Firebase\JWT\JWT' not found"

I have a suggestion about the CheckUser Tools:

DarkMatterMan4500 (talkcontribs)

I've been thinking about this for quite some time, and don't you think that the data results should last longer than 3 months? I mean, why not just stick to 6 months instead of 3 as it just feels drastically too short. You don't have to agree with me on this if you don't want to. It's just a suggestion, not a requirement.

2403:6200:8832:C8D5:E891:A390:99B8:CAAF (talkcontribs)

This is a perennial question. I believe the WMF considers it a breach of personal data policy to permit searching the records further back. Technically it is quite possible to extend the period and it would help combat the fiercly growing abuse of Wikipedia - at least on en.Wiki - for commercial purposes. ~~~~

DarkMatterMan4500 (talkcontribs)

That could be true either way.

Ciencia Al Poder (talkcontribs)

You can change that by setting $wgCUDMaxAge to a longer period.

If you want to change that on WMF wikis, the request should be discussed and approved first, but anyway this talk page is not the place to take this discussion. Maybe try a bugreport?

Kudpung (talkcontribs)

Exactly. The way MediaWiki is used on WMF projects is driven by the WMF and it's unlikely they will approve any changes to their policy even if asked time and time again by a majority RfC from their volunteer communities. Hence making a request at Phab would be a waste of time. The simple $wgCUDMaxAge setting is free for anyone to use who is using MediaWiki for other purposes.

DarkMatterMan4500 (talkcontribs)

Oh yeah. Although I'm not a Steward on any of these wikis.

Kudpung (talkcontribs)

I believe we have adequately explained the situation with the use of CU on WMF and non-WMF websites powered by MediaWiki. ~~~~

Reply to "I have a suggestion about the CheckUser Tools:"

Logged actions: Which actions actually generate CU data?

Sense Amid Madness, Wit Amidst Folly (talkcontribs)

In the description it says: "Get edits from IP: returns all edits and logged actions made by a user (registered or anonymous) from an IP address or range."

Apparently this is not true for all logged actions. Page reviews, which do leave a log entry, do not generate data for the CU extension. Please clarify which actions actually generate relevant data. One other action which does not leave a (public) log but is available for CU is sending a wikimail.

Reply to "Logged actions: Which actions actually generate CU data?"
Il Gatto Obeso (talkcontribs)

I've installed CheckUser extension on my wiki and imported the file <code>cu_changes.sql</code> and <code>cu_log.sql</code>.

When I run the CheckUser special page, after filling in everything I get only a query error of type <code>[a4d205656bdaeb2ad048ee23] 2019-08-26 17:00:06: Errore irreversibile di tipo "Wikimedia\Rdbms\DBQueryError"</code>. However, it does not affect the CheckUserLog special page, which is displayed as expected.

My MediaWiki version is 1.33.0, with PHP 7.1.26 (cgi-fcgi), MySQL 5.6.33-log, ICU 50.1.2. Can somebody help?

Ciencia Al Poder (talkcontribs)
Il Gatto Obeso (talkcontribs)

Now the [fb42dddde2e2823b929178c4] /w/index.php?title=Speciale:CU Wikimedia\Rdbms\DBQueryError from line 1587 of /membri/kaymoskva/w/includes/libs/rdbms/database/Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading? Query: SELECT cuc_ip,cuc_ip_hex,COUNT(*) AS count,MIN(cuc_timestamp) AS first,MAX(cuc_timestamp) AS last FROM `kwiki_cu_changes` FORCE INDEX (cuc_user_ip_time) WHERE cuc_user = '8' AND (1 = 1) GROUP BY cuc_ip,cuc_ip_hex ORDER BY last DESC LIMIT 5001 Function: SpecialCheckUser::doUserIPsDBRequest Error: 1176 Key 'cuc_user_ip_time' doesn't exist in table 'kwiki_cu_changes' (localhost) Backtrace:

  1. 0 /membri/kaymoskva/w/includes/libs/rdbms/database/Database.php(1556): Wikimedia\Rdbms\Database->getQueryExceptionAndLog(string, integer, string, string)
  2. 1 /membri/kaymoskva/w/includes/libs/rdbms/database/Database.php(1274): Wikimedia\Rdbms\Database->reportQueryError(string, integer, string, string, boolean)
  3. 2 /membri/kaymoskva/w/includes/libs/rdbms/database/Database.php(1784): Wikimedia\Rdbms\Database->query(string, string)
  4. 3 /membri/kaymoskva/w/extensions/CheckUser/includes/specials/SpecialCheckUser.php(529): Wikimedia\Rdbms\Database->select(string, array, array, string, array)
  5. 4 /membri/kaymoskva/w/extensions/CheckUser/includes/specials/SpecialCheckUser.php(497): SpecialCheckUser->doUserIPsDBRequest(integer, integer)
  6. 5 /membri/kaymoskva/w/extensions/CheckUser/includes/specials/SpecialCheckUser.php(105): SpecialCheckUser->doUserIPsRequest(string, integer)
  7. 6 /membri/kaymoskva/w/includes/specialpage/SpecialPage.php(569): SpecialCheckUser->execute(NULL)
  8. 7 /membri/kaymoskva/w/includes/specialpage/SpecialPageFactory.php(558): SpecialPage->run(NULL)
  9. 8 /membri/kaymoskva/w/includes/MediaWiki.php(288): MediaWiki\Special\SpecialPageFactory->executePath(Title, RequestContext)
  10. 9 /membri/kaymoskva/w/includes/MediaWiki.php(865): MediaWiki->performRequest()
  11. 10 /membri/kaymoskva/w/includes/MediaWiki.php(515): MediaWiki->main()
  12. 11 /membri/kaymoskva/w/index.php(42): MediaWiki->run()
  13. 12 {main}

What does the cuc_user_ip_time index mean?

Ciencia Al Poder (talkcontribs)

Did you run update.php after installing the extension? If not, please run it and try again.

Otherwise, there may be a bug on the extension that failed to run one of the scripts. Apparelty you'll need to run manually, replacing /*$wgDBprefix*/ with kwiki_

Reply to "Query error"
2600:8801:1F00:675:D96B:83A0:888B:12EE (talkcontribs)

I'm running MW 1.26.3 and PHP 7.0.32 and am trying to follow the instructions here. I have shell access and did the git clone command. After adding in the LocalSetting stuff I get error code 500. Doing php maintenance before was fine, but after adding it in I get this error:

  1. PHP Fatal error: Uncaught exception 'Exception' with message '/SNIP/extensions/CheckUser/extension.json: unsupported manifest_version: 2' in /SNIP/includes/registration/ExtensionRegistry.php:184

Asked in the IRC channel and they were saying the instructions are not correct and that install.php should not be used here for any version, then said it should be but that an older version of CheckUser needs to be obtained. They told me to run git checkout origin/REL1_26 but that did nothing.

Please fix the instructions for MW 1.26

星耀晨曦 (talkcontribs)

Please run git checkout REL1_26, it will checkout the code to version 1.26. By default, the cloned code is the latest code and is probably not compatible with your MW version. Note: Your MW version is very old and unsupported, I recommend you to upgrade to 1.31.

Reply to "Instructions are wrong"
Summary by 机智的小鱼君


机智的小鱼君 (talkcontribs)
[6e1c670f739f92204931b713] 2018-10-12 19:35:37: 类型“Wikimedia\Rdbms\DBQueryError”的致命错误

What is that mean , I feel very confused……

Ciencia Al Poder (talkcontribs)

See Manual:How to debug to enable the display of exception details and have a more meaningful error message. Maybe you forgot to run update.php after installing the extension?

机智的小鱼君 (talkcontribs)

THX,I forgot run update.php!

Return to "CheckUser" page.