Topic on Extension talk:CheckUser/Archive 2

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.

Attempting

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? 204.237.89.128 23:22, 3 May 2023 (UTC)

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?

PHP 7.4.29 MariaDB 10.6.12

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

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

Haven't been able to take a further look at this due to IRL time pressures. May be able to look some point this week.

Chiming in to say I have had the same problem. I recently updated from 1.35. Here's my current setup:

Product	Version
MediaWiki	1.39.4
PHP	7.4.33 (fpm-fcgi)
MariaDB	10.4.20-MariaDB-1:10.4.20+maria~buster-log
ICU	65.1

I was too hasty with my previous comment. I went back to the installation instructions and realized that I didn't properly follow the directive "If you have installed other extensions without running php maintenance/update.php, run that first." I guess at the time, since I was using all the same extensions before I upgraded from 1.35 to 1.39, I hadn't done this. In other words, I had run php maintenance/update.php, but I had not run it with the CheckUser extension disabled. Thus, I decided to:

1. Disable the extension
2. Run php maintenance/update.php
3. Enable the extension
4. Run php maintenance/update.php again

Lo and behold, everything is working just fine now. So that's mea culpa for not following instructions!

Good to hear that worked.