Thanks for creating this - I was about to file a production error report after also discovering this on testwiki myself :)

In case it's helpful, noting here that - on test2wiki - the database error refers to loginwiki.flaggedrevs rather than loginwiki.ores_classification:

https://test2.wikipedia.org/wiki/Special:GlobalContributions/~2025-14155

[c9ab70e3-3905-45ae-917b-3435da93145c]

Error 1146: Table 'loginwiki.flaggedrevs' doesn't exist
Function: MediaWiki\CheckUser\GlobalContributions\GlobalContributionsPager::reallyDoQuery

Thanks @A_smart_kitten - I've updated the task description to check for other extensions too.

This issue is happening on Special:GlobalContributions becuase GlobalContributionsPager is building a query on the local wiki (running hooks locally, handled by extensions that are loaded locally, potentially adding extension-specific statements to the query), then running that query on external wikis, where the extension may not be loaded.

Several hooks are run from ContributionsPager, which is the parent class of pagers for various contributions pages (Special:Contributions, Special:DeletedContributions, Special:IPContributions, Special:GlobalContributions). The hooks are: onContribsPager__reallyDoQuery, onContributionsLineEnding, onDeletedContribsPager__reallyDoQuery, onDeletedContributionsLineEnding, onSpecialContributions__formatRow__flags and onContribsPager__getQueryInfo. The hooks used to be run from ContribsPager (for Special:Contributions) and DeletedContribsPager (for Special:DeletedContribuitons), before these were refactored to extend a single parent class.

• Pro of running the hooks from the parent: they potentially allow extra information to show up on all contributions pages, e.g. Flow edits, FlaggedRevs statuses.
• Con of running the hooks from the parent: new special pages extending the parent may behave in ways that the extension hook handlers didn't predict

Possible approaches to solve this:

• Only run the above hooks from ContribsPager and DeletedContribsPager as originally intended (but then we lose information from some pages)
• Adapt all of the extension handler to specify which special pages they should work on (difficult to maintain, and odd for extensions to know about each other, e.g. Flow adding a case for IPContributions)
• Allow subclasses of ContributionsPager to configure whether to run the various hooks

Change #1115906 had a related patch set uploaded (by Tchanders; author: Tchanders):

[mediawiki/core@master] ContributionsPager: Allow subclasses to run hooks optionally

https://gerrit.wikimedia.org/r/1115906

Change #1115907 had a related patch set uploaded (by Tchanders; author: Tchanders):

[mediawiki/extensions/CheckUser@master] GlobalContributions: Prevent running hooks from the pager class

https://gerrit.wikimedia.org/r/1115907

Thanks @Dreamy_Jazz; I was looking for "DBQueryError", and didn't find anything). Sorry for the duplicate!

Change #1115906 merged by jenkins-bot:

[mediawiki/core@master] ContributionsPager: Allow subclasses to run hooks optionally

https://gerrit.wikimedia.org/r/1115906

Change #1115907 merged by jenkins-bot:

[mediawiki/extensions/CheckUser@master] GlobalContributions: Prevent running hooks from the pager class

https://gerrit.wikimedia.org/r/1115907

I could successfully load https://test.wikipedia.org/wiki/Special:GlobalContributions/~2025-14155 and https://test2.wikipedia.org/wiki/Special:GlobalContributions/~2025-14155 without seeing an error.